CONTACT NORLA
Platform evaluation, marketplace support, enterprise deployment, course partnerships, seller onboarding, or media enquiries.
NORLA / WORKING GUIDE
State whether your question concerns a listed system, a course, a collaboration or a service scope. Include the public item reference and the outcome you need, rather than only saying that something is not working.
For a technical issue, record the relevant steps and the exact error text. Remove credentials, personal information and confidential business records before sharing diagnostics.
Describe the tools your team is authorized to use, the people who need to approve the work and any genuine deadline. Separate non-negotiable requirements from preferences.
If the question relates to an actual transaction, use its private record through the agreed support channel. Do not publish payment details in a general forum.
Keep your enquiry and any confirmed response together. A delivery promise, price or support commitment should be stated explicitly by the party responsible for providing it.
A locally prepared message is not proof that it was delivered. Confirm the communication channel before assuming a recipient has received the request.
Read the service-scoping guide →NORLA EDITORIAL / FIELD NOTES
Working methods, decisions to document, and useful questions to take into your next project.
Keep hypotheses, observations and decisions together so a future team can understand what a test did and did not establish.
A knowledge workflow should identify its source and route gaps to an owner, rather than filling every silence with a plausible answer.
A useful review process preserves the reason behind each comment and gives conflicting feedback a decision owner.