Run a monthly review of the intake script

The operational decision

Catch drift in practice scope, contact routes and consultation wording. A reliable intake workflow needs an owner after launch. Staff availability, practice scope and public contact routes change, so the operating record should explain who can update the system and how changes are verified.

Prepare the workflow

Review changed policies, unresolved failures and staff feedback using synthetic examples; distinguish maintenance from a new practice-area implementation.

Example wording for approval

“This month's example review checks public service scope, callback wording and the escalation fallback. New collection fields require separate approval before use.”

Worked example

A fictional monthly review finds a new public service description, an expired consultation offer and repeated uncertainty about callback wording. Assign separate owners and tests to those items. Do not combine them into a single script updated checkbox. A changed service description may alter scope, while a callback clarification may remain routine maintenance. After approval, rerun the relevant golden scenarios and record the observed result so the meeting produces verified improvements rather than a list of intentions.

Handoff record

Record these task-specific fields: review date, changed policy, unresolved issue, assigned owner.

Acceptance check

Select one approved change and retest its original failure case. A review meeting without an applied and verified correction should remain incomplete.

Related guides