Policy, SOP, or Workflow: What Does Your Program Actually Need?
Something in your program isn't working consistently. Staff handle it differently, work gets stuck, or the same questions keep coming up.
The instinct is to write an SOP. But an SOP only fixes one kind of problem. If the real gap is a missing decision or a broken handoff, a new SOP adds a document and leaves the problem in place.
Three tools solve three different problems. They work together, but they aren't interchangeable.
A policy sets the rule. It establishes what the program requires and gives direction for decisions. Policies often reflect regulatory, contract, or funding requirements.
A workflow shows how work moves. It follows a process from start to finish across people, decisions, and systems, and shows where each handoff happens.
An SOP standardizes a task. It gives the steps for doing one piece of the work the same way every time.
Most programs know these are different. The harder part is looking at a problem and telling which one is missing.
Find Where the Breakdown Lives
Every operational gap shows up somewhere specific. Where it shows up tells you what's missing.
A Policy Gap: Nobody Decided
Take a program where staff handle missed appointments differently. Some close a participant's file after two no-shows. Others keep it open indefinitely. Supervisors give different answers when asked.
This looks like staff doing the same process differently. But ask why, and the answers sound like: "I thought that was the rule." "My last supervisor said to." "No one ever told us."
That's a policy gap. The program never decided what should happen. Writing an SOP here just puts one person's guess in writing.
The fix is a decision. Leadership, and sometimes the funder's requirements, have to settle the rule before anyone documents the steps.
A Workflow Gap: It Breaks Between People
Take a program that refers participants to outside services. Case managers send referrals correctly. The front desk logs them correctly. But referrals still fall through, and no one finds out until the participant says they never heard back.
Each person is doing their part. The problem is in the space between them. No one owns confirming the referral was received. No one knows whose job the follow-up is.
That's a workflow gap. An SOP for each role won't fix it, because every role is already doing its piece.
The fix is mapping the whole path with the people involved, from start to finish, and naming who owns each handoff.
An SOP Gap: Same Step, Different Results
Take a program that submits monthly service data to a funder. Everyone knows the report is required. Everyone knows who enters the data. But service categories get coded differently depending on who enters them, and the numbers need cleanup every month.
The rule is clear. The handoffs work. The step itself is done differently.
That's an SOP gap. Ask why, and the answers sound like: "That's how I was trained." "I figured it out myself."
The fix is writing the steps so the task gets done the same way every time.
Gaps That Look Like Something Else
Some gaps hide behind others.
A workflow gap often looks like an SOP gap. Staff notice the step in front of them, not the handoff that failed before it. Tightening that one step won't help if the work arrived late or incomplete.
A policy gap often looks like a training problem. Retraining staff on a rule no one actually decided just spreads the confusion.
Sometimes it isn't documentation at all. If staff know the rule, the path, and the steps and still can't keep up, the issue may be caseload, staffing, or a system that doesn't support the work. No document fixes that.
Test It on One Real Example
You don't need a full review to find the gap. Start with one case, request, or report that went wrong recently.
Walk it through from start to finish with the people who handled it. Mark the point where it broke. Then look at what caused the break.
If it came from not knowing what should happen, it's a policy gap.
If it came from something stalling or getting lost between people, it's a workflow gap.
If it came from a step being done differently than it should have been, it's an SOP gap.
One example won't show you everything. But it usually shows you where to look first.
Match the Fix to the Gap
Writing the wrong document is how programs end up with binders full of procedures and the same problems. If you're still deciding whether a process needs attention at all, start with the seven signs.
A policy gap needs a decision before it needs a document. A workflow gap needs the whole path mapped with the people who work it. An SOP gap needs the steps written down and tested with staff.
This is where Program to Practice starts. The Assess phase finds the breakdown before anything gets built.
Not Sure Where the Gap Is?
The Program Readiness Assessment helps you look at your program's documentation, workflows, and implementation, and identify where to focus.