📚 Part of the Operations That Actually Work series
Also in this series:
• Stop Building SOPs Nobody Reads
• I Automated My SOP Writing With AI — Here's What I Learned
• The Weekly Review Template That Caught Problems
I used to hate weekly reviews. They felt like paperwork. Fill out a form nobody reads. File it somewhere nobody looks. Repeat until you stop doing them entirely. But I started doing them anyway because the alternative was worse — arriving on Monday with no idea what was blocked what was urgent or who was waiting on what.
The weekly review changed for me when I stopped treating it as reporting and started treating it as diagnosis. The question is not what happened this week. The question is what almost broke and do we have a process for it.
What a real weekly review captures
Most weekly reviews are activity logs. Here is what I did this week. This is not useful. A diagnostic review captures four things. What was accomplished versus what was planned. What was blocked and why. What ad hoc work consumed the team and whether it is becoming a pattern. And most importantly a process health score that tells you which system is straining before it breaks.
The four quadrants
Accomplished versus planned. If you planned five things and accomplished two the problem is not execution. It is planning. Either you are overcommitting or something is repeatedly derailing the week. Track the gap over four weeks and you will see the pattern.
Blocked items. For each blocked task ask why. If the answer is waiting on a client that is normal. If the answer is waiting on internal approval or missing information that is a process problem. Blocked items are not failures. They are signals about where your systems are fragile.
Ad hoc work. The stuff that appeared midweek and consumed hours without planning. Client emergencies. Vendor surprises. Technical fires. If ad hoc work is less than twenty percent of the week that is normal. If it is more than forty percent your processes are not preventing fires. They are leaving you to fight them. This is the single most important metric in the review and almost nobody tracks it.
Process health score. Rate four statements on a scale of one to five. We spent time on the right things this week. No processes are breaking or slowing down. We are fixing root causes not just symptoms. There is nothing we should stop doing. Total score out of twenty. Eighteen to twenty means healthy. Fourteen to seventeen means one area needs attention this week. Below fourteen means schedule a process review now not later. Below ten means operations are not sustainable and need escalation.
The handoff section
If someone else needs to cover your work this section saves them hours. Anything urgent. Anything fragile or easy to break. Who to contact for questions. Where the files live. Write it as if you are handing off to someone who knows nothing about your week. Because someday that will be true.
A team I worked with used this template every Friday for three months. In the first review their process health score was eleven. By month three it was seventeen. The difference was not working harder. It was seeing the same blocker appear three weeks in a row and finally fixing the root cause instead of working around it. The review did not solve the problem. The review made the problem visible enough that someone solved it.
Build your processes first. If you haven't read Stop Building SOPs Nobody Reads, start there — it covers the four rules that make any template actually usable. And my AI automation disaster story explains why human-tested docs beat AI-generated ones.
Start here: Download the free Daily Operations Checklist — morning open, evening close, five minutes to fill. If it works for your team, the full SOP Template Pack includes the exact Weekly Review template with health scoring, filled examples, and escalation triggers built in.
But start with the free one. Fill one template this Friday. See if it changes your Monday morning.
Browse all templates at fieldwork-sops.surge.sh — including free checklists, process improvement tools, and full SOP packs.
Top comments (0)