The Monday brief: running a service business by exception

Most owners run their business from a windshield and a gut feeling, then spend Sunday night reconstructing the week from the field-software reports, the bank balance, and memory. The tools all have dashboards. Nobody has time to stare at dashboards.

Running by exception flips it: the system reads everything, and you read one page. What happened, what it means, and the short list of things that genuinely need an owner's judgment. Everything else either ran on rules you already approved, or waits quietly in an inbox.

What belongs in the Monday flash

• Last week in numbers: calls answered versus missed, jobs booked, follow-ups sent, what got paid.
• This week's capacity: what's on the board, where the thin days are, which tech is overloaded Thursday.
• Exceptions worth knowing: the booking rate that dipped, the estimate aging past its window, the pattern that broke.
• At most three asks. If everything needs you, nothing does — a brief that ends in ten decisions is a dashboard wearing a costume.

The two rules that make it trustworthy

First: the brief never fabricates. A number the system can't compute shows up as missing, plainly — an em-dash is honest, a guessed zero is not. Second: the asks in the brief are real approvals with real consequences — approve the ad spend, release the refund, resolve the schedule conflict — not FYIs dressed as decisions.

“The whole week in five minutes. What happened, what needs you, what to decide.”

In Caliber OS this is Derek's job — the director-of-operations seat. He reads the other four seats all week, catches exceptions midweek when they're small, counts answered-versus-expired on your own approvals honestly, and writes the flash you read with coffee. He briefs the money. He does not take the books.

You can run this playbook with a spreadsheet and discipline. The discipline is the hard part — which is rather the point of hiring it out.