Who the proposed service serves
Scope first; clarify questions that fall outside it.
In this example, the service is being planned for adults discharged from Northstar Care Network facilities who need a scheduled community follow-up conversation. The planning scope is limited to coordination for the Riverside clinic's proposed weekday service.
The brief does not define clinical suitability, referral acceptance criteria, appointment availability, or care decisions. A referral that appears to fall outside the described scope is a question for the designated referral-coordination role, not an assumed acceptance or rejection.
Boundary example: A request arrives from a community organization for someone who was not discharged from a Northstar facility. The receiving coordinator flags the mismatch and asks the service-scope owner to clarify the route before representing the request as accepted.
Four coordination areas
Use these areas to identify the right kind of question and the role that should receive it.
Coordination sequence
A handoff sequence for questions, not a care-delivery procedure.
Record the question and its source, route it to the role accountable for that topic, and keep unresolved operational dependencies with the launch-support lead.
-
1
Identify the question
State whether the issue concerns the proposed service boundary, referral route, team responsibility, or a launch dependency. -
2
Route to the accountable role
Send scope questions to the service-scope owner and routing questions to the referral-coordination role. Do not treat a handoff as an acceptance decision. -
3
Escalate unresolved coordination
If a question crosses teams or its owner is unclear, raise it with the launch-support lead, who identifies the next accountable role. -
4
Record the agreed clarification
Keep the clarified operational boundary in the approved source maintained by its owner; this brief is not the system of record.
Question-to-owner reference
Illustrative role assignments for the fictional Northstar example; not an approval or live work queue.
| Coordination question | First role to ask | Handoff or boundary |
|---|---|---|
| Does the proposed service cover this location and population? | Service-scope owner | Clarify against the approved local service description before describing the request as in scope. |
| Where should a referral-routing question go? | Referral coordinator | Clarify the route using the locally approved referral material; do not infer acceptance. |
| A request is from a community organization, not a Northstar facility | Referral coordinator, then service-scope owner if needed | Treat it as a scope question and seek clarification; the example does not mark it accepted or rejected. |
| Two teams disagree about a launch dependency | Launch-support lead | Identify the accountable operational owner and record the agreed handoff in the approved source. |
Illustrative planning milestones
-
12 October 2026
Scope discussion
The planning group reviews the proposed Riverside location, intended population, and questions that require domain-owner clarification. -
19 October 2026
Referral-route review
Referral coordination and service-scope roles compare the proposed handoff with locally approved operational material. -
26 October 2026
Cross-team dependency review
The launch-support lead convenes owners for unresolved operational dependencies and records where each clarification belongs. -
2 November 2026
Planning checkpoint
The accountable local owner reviews the current planning record and identifies any outstanding questions. This date is a planning example, not evidence of approval or launch readiness.