What should be on a daily report for the owner of a service business?
Yesterday's booked jobs and revenue against expectation, today's scheduled capacity, unbooked bookable calls, unsold estimates that are aging, and anything sitting outside its normal range with a one-line explanation. That is enough. An owner's daily report should be readable in under a minute and should end with the two or three items that need a decision today.
Yesterday, today, exceptions
That three-part structure holds up because it maps to how an owner thinks. Yesterday is the scoreboard. Today is the commitment — what is on the board and whether it is enough. Exceptions are the only part that requires action.
Anything that does not fit one of those three buckets is reference material and belongs in the dashboard rather than the daily report.
Compare to expectation, not to yesterday
"Revenue was down from yesterday" is nearly meaningless in a business with weekday patterns and weather-driven demand. "Revenue was below the pace needed to hit the month, and the gap came from a light install schedule" is a sentence someone can act on.
Expectation means a stated basis: month-to-date pace against plan, or same weekday over recent weeks. State which one you are using, because the two can disagree and the reader needs to know which lens they are looking through.
What to leave off
- Anything you cannot influence before tomorrow. Retention, average ticket trends, channel mix — real metrics, wrong cadence.
- Raw volume with no ratio. Call counts on their own invite the wrong reaction.
- Metrics with no owner. If nobody is accountable, it becomes noise in the owner's inbox.
- Anything computed on a sample too small to mean anything. One rep's daily close rate is not news.
Every number needs a sentence
The difference between a daily report that gets read and one that gets deleted is whether the numbers are accompanied by a plausible reason. "Booking rate was low" prompts a question. "Booking rate was low; nineteen calls came in during the two hours the phones were down to one person" prompts an action.
Producing that second sentence requires joined data — calls, staffing, jobs and spend in one place. That is what written briefs are built on, and why they depend on operational AI rather than a reporting tool.
Delivery time decides readership
A daily report competes with the day. Arriving before the day starts, it gets read in full. Arriving at eleven, it gets skimmed. Arriving at four, it gets archived unread and the pattern sets in permanently.
That constraint is worth designing around, and it interacts with data freshness: a brief that waits for perfectly settled numbers often waits too long to be read at all. Slightly earlier with a clear as-of label generally beats slightly more complete.
Topics: daily reporting · owners · briefs · home services
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.