A Plan Is Not a Routine: The Implementation Gap
The implementation gap begins after a policy is adopted. Trace handoffs, recurring tasks, and feedback to turn a formal decision into a routine public service.
The most common mistake after a policy is adopted is to treat approval as delivery. That implementation gap leaves residents facing the old process while staff are expected to make a new promise work without clear handoffs or recurring tasks. A policy becomes routine only when people can carry it out in ordinary working conditions.
Approval changes rules
A vote, directive, or signed regulation can establish authority and intent. It does not assign every task, update a form, prepare a call center, or tell a resident what to do differently. Each is a separate piece of implementation, and any can lag behind the formal decision.
Look for the distance between the policy’s public description and the actual path a person must follow. If a new benefit is announced but the application still asks for documents the policy no longer requires, the announcement and service have diverged. The gap appears in the interaction, not just in the project plan.
Handoffs carry work
Many public services pass through several desks or organizations. A policy change may begin with a central office, move to regional managers, then reach caseworkers, contractors, or local partners. At each handoff, someone must interpret the change, pass along usable instructions, and confirm the next person received them.
Vague ownership is a common failure point. “The department will inform staff” does not say which team prepares guidance, who answers exceptions, or who updates public materials. Name the owner on each side of a handoff and specify what information must travel with the work.
- Check whether a named role initiates the task; if not, assign one, or move the trigger into an existing team’s workflow.
- Check whether the receiving role knows what information is required; if not, define the required fields, or return incomplete work to the sender with a clear request.
- Check whether unusual cases have a route; if not, name an escalation role, or keep the case with the current owner until that route is established.
- Check whether anyone confirms receipt; if not, add a confirmation in the existing system, or assign a role to follow up on unacknowledged work.
- Check whether public-facing instructions match the current process; if not, update the form or notice, or pause directing residents to it until the correction is ready.
- Check whether staff can identify the current version of guidance; if not, establish one accessible source, or withdraw conflicting copies from routine use.
Imagine a county adopts a rule allowing residents to submit a proof document online. The policy office asks a digital team to add an upload option, but intake staff have no instructions for unreadable files. The county assigns an intake lead to write the return message and escalation route, then places that guidance beside the upload queue; staff can give residents the same next action when a file cannot be read.
Recurring tasks need owners
Implementation is not a launch-day event. It includes recurring tasks such as issuing notices, processing requests, answering questions, renewing approvals, correcting records, and handling appeals. An announcement can start a change; only an assigned routine can sustain it.
For each recurring task, ask who does it, what triggers it, what information or authority the person needs, and where the result is recorded. These questions expose quiet dependencies. A frontline worker may be expected to apply a new rule while the case-management system still offers only the old choices.
Make the task visible in existing work. A short decision aid beside the relevant screen, a revised form, or a clear queue assignment can help more than a broad message staff must remember later. Avoid adding a tracking sheet if an existing system can record the same handoff.
Capacity shapes delivery
A policy can create work faster than an agency can absorb it. New eligibility checks may add review work; a new service channel may generate questions before staff have answers; a revised deadline may concentrate tasks during a busy period. If the plan assumes spare capacity without identifying it, pressure may appear as delays, rushed decisions, or work displaced from another service.
Ask managers and frontline staff to map added tasks against current roles and queues. The useful question is not simply whether the agency has enough staff, but whether the right people have time, access, authority, and support where the work occurs. If they do not, leaders can adjust the sequence, simplify the process, or make an explicit capacity choice.
Training helps when staff need to learn a new decision or tool, but it cannot fix missing authority or an impossible workload. Keep instruction close to the moment of use, and provide a route for questions that do not fit the standard case. A brief reference card or searchable internal guidance can put an answer within reach during service.
What does routine require?
How is implementation different from adoption?
Adoption establishes a formal policy choice; implementation organizes the people, processes, and resources that put it into practice. A policy can be valid on paper while the public-facing service remains unchanged.
Who should own a handoff?
Assign an identifiable role on both sides: one sends the work and another accepts it. The receiving role should know what counts as complete and where to raise an exception, rather than guessing which office is responsible.
What should managers monitor?
Managers should check whether required tasks happen, where work pauses, and which exceptions recur. Pair operational signals, such as unresolved cases, with staff and resident feedback so a dashboard does not mistake recorded activity for a usable service.
When should a process be revised?
Revise a process when the same confusion recurs, instructions conflict, or a handoff regularly returns incomplete. Make a targeted change, tell affected roles what changed, and check whether the source of the problem has moved.
Feedback keeps routines usable
Implementation needs a route from the point of service back to the people responsible for policy and operations. Frontline staff can identify confusing instructions; residents can reveal where a form or notice fails to make the next action clear. Without a defined route, those observations stay local or arrive only after frustration builds.
Keep feedback specific. Record the task involved, where it stalled, and what information was missing; protect personal information and use the agency’s appropriate channels. Assign recurring issues to someone with authority to change guidance, systems, or staffing arrangements.
Do not confuse a full activity log with a working routine. A system may show that a notice was sent without showing whether the resident understood it or whether a reply was handled. Choose a small set of operational questions that reveal whether the intended process is happening, then review them with the people doing the work.
Keep plans workable
Useful implementation documents are short enough to consult and specific enough to guide action. For each important process, record the trigger, responsible role, next recipient, expected record, and escalation path. Keep detailed references available where needed, but do not bury basic ownership in a long plan that staff rarely open.
It is not worth building an elaborate dashboard before anyone has agreed what a completed task means. Clarify the routine and its evidence first; add reporting only when it helps a named person resolve a real operational question.
The implementation gap narrows when a policy’s promise becomes clear, repeated work. Before calling a decision delivered, trace an ordinary case from its first trigger through its final handoff and ask the people at each point what they need to complete it. That simple check can reveal a missing owner or instruction while there is still time to fix it.
