Agency operations

How to Map Agency Processes

A process document is useful only if it helps somebody perform or improve the work. Agencies often produce SOP libraries that look organized but become outdated because the real process continues evolving elsewhere.

Document decisions and handoffs

Capture the trigger, owner, inputs, important decisions, expected output and common exceptions. Screenshots of every click can be useful for fragile tool steps, but they should not bury the logic of the process.

Documentation test: Could a capable teammate use this to understand both what to do and why the important checkpoints exist?

Keep documentation close to the work

Assign an owner and a review trigger. When the workflow changes materially, update the documentation as part of the change rather than waiting for a quarterly cleanup that never arrives.

Use the next handoff as the test

Give the document to a capable teammate who does not normally own the process. Watch where they hesitate or ask for context. Those questions show where the SOP is missing a decision rule, prerequisite or exception—not merely another screenshot.