Receiving requests and routing services

Intake is the first operational decision linking the service's public promise to its real capacity. Accepting every request merely to look helpful is unsafe; automatically rejecting every sensitive request is also unhelpful when safe information or a responsible handoff is possible. The intake form should collect only what helps identify a route: why the person contacted the service, what they expect, apparent urgency, accessibility needs, and a safe channel for replies. Do not demand a life history at first contact. A person seeking help organising a school procedure may need only an appointment and contact preferences. A credible sign of danger or abuse calls for the appropriate safeguarding process before routine registration continues.

Use three functional gates, not a clinical screening instrument. First, is there an apparent urgent safety concern? A plausible immediate threat activates the organisation's qualified response and emergency contacts. Second, is the topic inside the stated service scope? Consult the role card rather than intuition. Third, can the service provide the necessary conditions and capabilities, including language, privacy, supervision, and a suitable alternative service if needed? A request may be non-urgent but outside remit because it asks for interpretation of a medical test. It should be directed to a qualified provider rather than answered by an unqualified worker. Another request may be in scope but impossible to carry out accurately without an interpreter; arrange access or an alternative appointment instead of pretending that accommodation exists.

A usable intake record contains checkable statements: the person's own description without diagnostic reinterpretation, a route decision such as accepted, clarification required, or referred, the reason, the responsible person, and the next action and timing where relevant. Do not insert an unvalidated field called depression score or risk probability. Such numbers may appear objective but often require professionally controlled methods beyond the service. Describe observed or reported concerns and follow the safety protocol instead. If the request is ambiguous, ask a narrow clarifying question such as, “Are you looking for information about a service or for an individual assessment of your condition?” Avoid collecting intimate details that would not change the routing decision.

Routing does not end with sending a generic web address. Determine whether the proposed service actually handles that category, how a person can reach it, whether they agree to a contact, and whether the nature of the concern calls for urgent assistance. A nationally recognised organisation may operate local branches with different eligibility or hours. If availability is unconfirmed, state the uncertainty and provide a way to verify it rather than promising admission. Where danger is immediate, do not delay a required emergency action while searching for a perfect information page. Referral directories change; contact details need live verification when used.

Apply a test of executability. Every route decision needs an owner, a next step the person understands, suitable timing, and a fallback if the first contact fails. Not every request needs an extensive meeting. Some close after a reliable public information response and confirmation that the person can use it. Records should not be retained indefinitely simply because software has storage space. The organisation's relevant retention rules and lawful obligations matter. When a supervisor later asks why a case was routed, the evidence should be visible in recorded facts rather than the writer's tone or private assumptions.

Review decisions against common mistakes. A staff member accepts a request because they know the caller; another treats ordinary examination stress as automatically requiring clinical care; a third excludes a person who cannot complete the intake form; or a worker closes a case after sharing a telephone number that does not connect. In each case, identify the failed gate: scope, accessibility, safety, or continuity. Such review improves service delivery without turning non-clinical helpers into diagnosticians. Accurate routing combines clear limits, dignity, evidence, and a next action that can genuinely be carried out.