Organizational Diagnostic and Implementation Report
What is happening between intake and the next stage, what may explain the delay, and which action is reasonable to test first.
This report demonstrates the path from an observed service delivery challenge to an organizational decision that can be implemented and reviewed.
No personal, clinical, or operational information from a real organization was used. Fictional figures are marked throughout.
Executive Summary
The main finding is a delay between intake and the next stage. Only 41 of 68 referrals progressed within 14 working days. The evidence suggests that capacity alone may not explain the pattern. Ownership of the handoff is also unclear: who closes the transfer, what information must move, and when the transfer is complete. The first recommendation is to clarify the handoff in one team before considering a wider structural or technology change. Implementation will be checked before outcome.
| What is happening? | 41 of 68 referrals moved to the next stage within 14 working days. Average intake-to-placement time was 19.4 working days. FICTIONAL DATA |
| What may explain it? | Ownership and responsibility may be unclear at the handoff. No single moment confirms that the receiving role has accepted the case. |
| What first action is recommended? | Run a four-week handoff protocol in one team, with one named owner, a short checklist, acknowledgment by the receiving role, and a clear time expectation. |
| How will we learn? | First check whether acknowledgment occurred. Then review transfer time, stalled cases, and progression to the next stage. |
Separating these stages makes it possible to tell whether an action was unsuitable, or whether it was never implemented as intended.
Purpose and Scope
The organization asked why some people were not moving consistently from intake into the first stage of employment support. The shared objective was to reduce transfer time, clarify responsibility, and reduce disengagement between stages.
14 staff across frontline, middle-management, and senior-leadership perspectives. FICTIONAL DATA
Three questionnaires, process documents, a staff-built journey map, four interviews, and operational data covering 68 referrals.
Outside scope: clinical quality, individual staff performance, longer-term employment outcomes, and capacity in later stages. External referrer response times were only partly examined.
Professional boundary: this is an organizational process diagnostic. It does not replace managerial, professional, or clinical judgment.
Service Journey Map
| Stage | Current practice | Roles | Point of friction | Required output |
|---|---|---|---|---|
| 1. Referral | Referral arrives by phone, email, or an external partner. | Administration, intake coordinator | Information is sometimes incomplete. | Contact details and reason for referral |
| 2. Intake | Intake conversation, form, and case opening. | Intake coordinator | Needs are documented inconsistently. | Open record and conversation summary |
| 3. Initial assessment | Assessment is scheduled with an available practitioner. | Coordinator, practitioner | It is unclear who confirms completion. | Assessment and next-stage recommendation |
| 4. Progression decision | A decision is made in a meeting or undocumented conversation. | Team lead, practitioner | No defined transfer of responsibility. | Recorded decision and receiving owner |
| 5. Placement | Placement depends on availability. | Placement coordinator | Capacity varies across programs. | First appointment date |
Findings
Finding 1: The handoff has no consistently understood owner
In 27 of 68 records, the receiving owner was not documented. Leadership described the process as more defined than frontline staff did. FICTIONAL DATA
Unknown: whether missing documentation indicates a missed transfer or an undocumented transfer.
Finding 2: Information does not move consistently
Four of ten manually reviewed cases required the receiving practitioner to contact intake for missing information. FICTIONAL DATA
Unknown: whether the gap reflects the absence of a standard template or insufficient time to complete it.
Possible Mechanism
Mechanism hypothesis: unclear ownership and responsibility at the handoff may leave cases dependent on individual follow-up. The evidence supports testing this explanation, but it does not establish causality.
- No named owner in many records
- Staff rely on personal tracking lists
- Delay clusters around the handoff
- Caseload increased during the period
- Two programs have genuine waiting lists
- Delay is not consistent across teams
Recommendation State
| State | Meaning | This report |
|---|---|---|
| recommended | There is enough basis for a limited, reversible first action. | Selected |
| direction_possible_needs_more_info | A direction is plausible, but more information is needed. | No |
| no_basis_yet | There is not enough basis for a recommendation. | No |
| fit_not_tested | The organizational fit has not yet been tested. | No |
The recommendation state applies to a first action that can be tested. It does not mean the mechanism has been proven.
Intervention Options
| Option | Rationale | Status |
|---|---|---|
| Clarify the process without new technology | Name an owner, use a short transfer checklist, and require acknowledgment. | Start here |
| Add a brief coordination routine | Review stalled cases weekly and escalate when no response is received. | Supporting option |
| Introduce a workflow tool | Could help at scale once the process is clear. | Not recommended yet |
| Procure a new system or automation | Current evidence points to ownership, not a systems gap. | Not recommended |
Selected Recommendation
For four weeks, use one consistent handoff protocol in one team. Each transfer has a named owner, a short information checklist, acknowledgment by the receiving role, and a clear time expectation.
| What changes | The receiving role acknowledges the case within one working day and records the next step. |
| Burden | About three minutes per transfer. The receiving team's workload must be checked. |
| Owner | The team lead coordinates implementation. The center director reviews weekly. |
| Stop condition | Reported burden rises, availability worsens, or implementation stays below 40% after two weeks. |
| Expansion condition | Implementation exceeds 80% in the final two weeks without higher reported burden. |
Implementation Behaviour and Practice
The receiving role acknowledges each case within one working day and records the next step.
A ten-minute demonstration, three fictional practice cases, and a weekly team-level review.
At receipt of a new case, rather than at the end of the day or in the weekly meeting.
The case appears on a stalled-case list and the team lead examines what blocked the process.
Measurement
Implementation measures
| Measure | Baseline | Target | Current |
|---|---|---|---|
| Cases with a named owner | 34% | 90% | 71% |
| Transfers acknowledged | Not measured | 80% | 64% |
| Acknowledged within one day | Not measured | 75% | 58% |
Outcome measures
| Measure | Baseline | After four weeks |
|---|---|---|
| Average time to next stage | 19.4 working days | 15.1 working days |
| Stalled cases | 27 | 11 |
| Progression to next stage | 60% | 72% |
All figures in this chapter are fictional. Process outcomes do not substitute for direct feedback from people using the service.
Follow-up Review
- Was the action implemented? Partly, in one team.
- Did the target behavior occur? 64% of transfers were acknowledged; 58% within one working day.
- What helped? The short checklist and weekly list of stalled cases.
- What made it harder? End-of-day transfers and urgent cases that did not fit the routine.
- What remains unknown? Whether lower referral volume also contributed to the shorter transfer time.
- Next decision? Continue with an exception rule for urgent cases.
Organization Decision
- Four weeks in the employment team
- Weekly review of stalled cases
- Follow-up questionnaire
- New workflow software
- Expansion to other teams
- Changes to job descriptions
Decision owner: Team lead, with oversight from the center director. Review date: End of the four-week implementation period. FICTIONAL DATA
Next Learning Cycle
The mechanism hypothesis is retained and receives a new observation. The previous record is not overwritten. Outcome measures are compared with baseline, implementation is checked first, and the recommendation state may strengthen, change, or be retired. A new mechanism is created only when the explanation itself changes materially.
Limitations
- All data, names, and quotations are fictional.
- The mechanism is a supported hypothesis, not a proven cause.
- Some measures rely on staff report or a small sample.
- Capacity, external partners, and variation between teams remain plausible explanations.
- Four weeks can test implementation and an early process signal. It cannot establish a durable outcome.
Appendix
| Source | Scope | Timing | Quality |
|---|---|---|---|
| Frontline questionnaire | 9 respondents | May 2026 | Moderate to high |
| Middle-management questionnaire | 4 respondents | May 2026 | Moderate |
| Leadership questionnaire | 1 respondent | May 2026 | Limited |
| Operational records | 68 referrals | March to May 2026 | Moderate, incomplete documentation |
| Interviews | 4 conversations | June 2026 | Qualitative |
What was observed, with its source and date.
A possible explanation linking an organizational condition, behavior, and outcome.
A focused intervention aligned with the mechanism, evidence, and context.
What the organization chose to do, with an owner and review point.
ALNA can help translate the selected recommendation into a workable implementation plan, review what happened, and carry the learning into the next cycle.