A 3-step weekly branch check-in
The previous lesson unified procedures across branches, but a unified procedure does not follow up on itself. Most owners follow up by calling when something feels off, then two weeks pass without a single question. The result is follow-up driven by anxiety rather than by work: intense when it is not needed, absent when it is.
The fix is not more follow-up, it is follow-up with a rhythm: fixed checkpoints the team knows in advance, each with one question and one output. People who know when the question is coming prepare an answer; people who are surprised by it produce an excuse.
Why random follow-up fails
- It costs you the most: every question becomes a call, and every call interrupts two people.
- It gives a snapshot: you learn about today, never about a trend forming over two weeks.
- It unsettles the team: a surprise question reads as an inspection, so the answer comes polished rather than accurate.
- It leaves no trace: what was said on a call compares to nothing next month.
The three checkpoints
Three checkpoints are enough for most small and mid-sized businesses. What matters is that each has exactly one question and ends with a written output:
| Checkpoint | When | The single question | Output |
|---|---|---|---|
| Operations | Daily before work starts, 5 minutes | What could block us today? | A blocker list cleared the same day |
| Numbers | Weekly, on a fixed day | Are the metrics inside the expected range? | One corrective decision with an owner and a date |
| Procedure | Monthly, first week | Which step keeps causing the same problem? | A written change to the procedure |
The checkpoints escalate from daily to monthly: the first clears a blocker, the second corrects a number, the third fixes the procedure itself. Blend them together and each one turns into an open meeting that ends without a decision.
A worked example: the branch checkpoint on WhatsApp
A maintenance business with two branches. The old way: the owner calls the branch manager each morning and asks how things are going, and gets a descriptive answer - busy day yesterday, all fine. No number to compare, no trace left behind.
Once the rhythm was fixed, the branch manager sends one request from the WhatsApp thread and receives the same picture every day, in the same order:
Branch manager: yesterday's report for North branch
System: North branch - yesterday
Jobs closed: 14
Jobs open past 24 hours: 3
Invoices issued: 12
Items below reorder level: 2Branch manager: the open jobs
System: 3 open: 2 waiting on a spare part, 1 waiting on customer confirmation
The difference is not that the information now exists - it was already in the system. The difference is what it costs to reach it: a question inside the same app the team uses all day, instead of opening a dashboard or waiting for a report. That is what keeps a daily checkpoint alive instead of dying after two weeks, and the approach is detailed on the operations over WhatsApp page.
When a line such as items below reorder level appears, the daily checkpoint becomes the early catch for a stock gap rather than discovering it at the moment of demand - covered further on the inventory over WhatsApp page.
Build the rhythm in one week
- Pick three numbers only: one for output, one for delay, one for money. More turns the checkpoint into a recital.
- Fix the time and write it down: a known day and hour, not whenever things allow. A floating slot dies.
- Standardise the report format: same order in every branch, every day, so comparison takes a glance.
- Give each checkpoint one output: a single line with the decision, the owner and the date, reopened at the next checkpoint.
- Review the rhythm after a month: which checkpoint never produced a decision? Drop it or change its question.
Checklist
- Does each checkpoint have one written question, or does it open with no agenda?
- Does the branch report arrive in the same shape daily, or does each manager phrase it their own way?
- Does the weekly meeting end with a decision that has an owner and a date?
- Is last week's decision reopened at the start of this week's meeting?
- Can a branch manager get their number without waiting on anyone?
In short: follow-up driven by anxiety exhausts you and reveals little. Fix just three checkpoints: daily to clear blockers, weekly to correct numbers, monthly to change the procedure itself. Give each one question and one output carrying an owner and a date, and standardise the report format so comparison takes a glance. Above all, make reaching the number as cheap as possible - a question inside the same app your team already works in - because checkpoints die when they cost time, not when they lack value.