User question
“I am trying to work out which policy applies to my situation. I found several pages and an archive of past guidance, but I am not sure which one is current. Where should I start, and when do I need to ask someone?”
A sample operating memo
What the organisation sees when one question moves through the operating layer.
This memo is fictional. The organisation and source material are fictional. It demonstrates the operating architecture, not a real client, user exchange, or source body.
No professional advice is being given.
Question Approved source Gate check Careful answer Right next step Operating memo
The gate is not a final step. It is checked before, during, and after the answer.
Approved source boundary
In scope
- current orientation page
- approved policy summary
- first-step checklist
Out of scope
- archived guidance
- exception decisions
- personal recommendation
- professional judgement
- individual assessment
- high-impact decision-making
This answer is limited to three approved sources held by the source owner for first questions of this shape. The archive is not in scope. Applying an exception or choosing a course of action is reserved to a human owner.
Gate check
- Gate status
- No escalation in this exchange.
- Watched categories
-
- distress or crisis language
- request for professional judgement
- exception or approval request
- personal, confidential, or sensitive context
- individual assessment
- high-impact decision-making
- governance or authority question
The gate observed the question before the answer was given. In this exchange, the user is asking for orientation, not exception handling or professional judgement.
User-facing answer
Careful answer
You do not need to begin with the whole archive. The current orientation page exists for this question.
The orientation is short: two approved pages and one checklist. It is not a complete answer to every possible case. It is the organisation’s approved starting point for this question.
The recommended first step is to read the orientation once before using older guidance.
The approved next step is the first-step checklist. The system should not assemble alternatives from the archive unless a source owner has approved that route.
If your question shifts from “where do I start?” into an exception, a high-impact decision, confidential context, or a request for judgement, this conversation should move to a named person.
Right next step
- Primary next step
- Current orientation page
- Supporting route
- First-step checklist
- Optional human route
- Contact the named owner if the question shifts into an exception, confidential context, authority, or support.
- Optional live route
- Review queue
The user receives one primary next step, plus clearly marked support routes. The system does not present the archive as an open field.
Organisation-facing operating memo
- What was asked
- A user is overwhelmed by source material and asks where to start.
- What was answered
- The user was oriented to the approved starting page and first-step checklist.
- What was not answered
-
- The system did not assemble a personal plan.
- The system did not interpret the user’s circumstances.
- The system did not draw from the archive.
- The system did not imitate a reviewer or owner.
- Gate result
- No escalation in this exchange. Escalation would have occurred if the question moved into exception handling, professional judgement, confidential context, crisis, governance, or high-impact decision-making.
- Review note
- Users are not asking for more content. They are asking for the approved sequence, current source, and a clear gate between self-service and human review.
- Review suggestion
- Consider creating a current-start page for users who find several relevant sources but do not know which one is authoritative.
- Source/gate review
- Review whether the current orientation page should remain the first approved source for this question shape, or whether a distinct “which source is current?” route is needed.
What is recorded
The example shows structure, not a data policy. In a live operating layer, the organisation decides what is recorded, how long it is retained, whether user language is anonymised, and which gate categories require human review. The operating layer records the gate category and escalation reason. Sensitive wording is only retained if the organisation’s consent and data policy explicitly requires it. The default should be data minimisation: record what is needed for review, governance, and improvement; do not record more because the system can.