Dashboard vs weekly report: which one an owner reads

It's Monday at 7:10. The software you pay for every month has a reporting tab, and the login is saved in a browser you never use on your phone. You opened it twice in the spring. So the weekly numbers come the way they always have: you ask your office manager how last week went, and she spends the first hour of her Monday pulling jobs from the field software, payments from the accounting package, and calls from the phone portal into one spreadsheet. You get the answer around 10:30, when you're already on a job site, and you read it Tuesday night.

Most owners I talk to have both a dashboard and a spreadsheet. They don't use the dashboard, and the spreadsheet costs them a person's morning every week.

The short answer

For a business with one owner and a small team, a short weekly report that shows up where you already read things beats a dashboard as the main way you keep track. Keep the dashboard for the days a number looks wrong and you want to dig. A dashboard earns its place when watching it is somebody's job, like a dispatcher on a busy day or an operations manager at a shop big enough to have one.

It comes down to who has to go get the information. You have to go to a dashboard, while a report comes to you. On a week when you're short a tech and the furnace calls are stacking up, you won't be going anywhere to look at numbers.

Dashboard vs weekly report, side by side

The "covers more than one system" row is where most owners get stuck. Your field software dashboard knows about jobs. It has no record of the calls that rang out before anyone booked a job, or of the invoice that got paid in your accounting package and never marked paid in the field app. I wrote about that gap for one trade in the Wheaton HVAC owner report post, and it's why a busy week can look fine on a dashboard and still have cost you work.

What the wrong choice costs

When an owner leans on a dashboard nobody opens, small problems sit for weeks. A customer drifts to 45 days past due, or a phone line starts dropping calls after someone changes a setting. It's all there in the data, and nobody looks. You find out once it's big enough to be obvious, and by then it costs a lot more to fix.

The hand-built spreadsheet has the opposite problem. It does get read, but it takes the most organized person on your payroll off real work every Monday, and it changes with whoever built it that week. Maybe "jobs completed" counts the warranty callbacks one week and leaves them out the next. Then you're comparing numbers that were never counted the same way and drawing conclusions from them anyway.

What a weekly report looks like when it builds itself

These are the steps I take when I set one up.

1. Pick the numbers and write down what each one means. Five to seven, no more. For a service shop that's usually calls missed and not returned, jobs booked, quotes still open, revenue invoiced, revenue collected, and invoices past due. Writing the definitions down settles the warranty-callback argument once.
2. Connect the sources. The report pulls from the systems you already pay for: phone, field or practice software, accounting. Nobody re-keys anything.
3. Run it on a schedule. Sunday night it gathers the week, and Monday at 6 a.m. it's in your inbox, or arrives as a short text if that's where you actually read.
4. Put each number next to last week, and next to the same week last year when that data exists. A total by itself tells you very little. You want to know which way it moved.
5. Flag what needs a person. Quotes older than a week with no reply, invoices past 30 days, and missed calls nobody returned come as short lists with names on them.
6. Link every line to the list behind it. When a number looks off, one tap takes you to the jobs or invoices that make it up. That's the one time you need the dashboard, and it opens already filtered.

The flagged lists are the part I've built before. The lead capture and tracking I set up for a Chicago-area pool service company gives every lead a status, so the leads that went quiet show up as a sorted list instead of a hunch. A weekly report is that same list with last week's totals on top.

What stays human

The report counts things, and it can't tell you why they happened. If collected revenue dropped, it shows you which invoices are late. It has no way of knowing your biggest commercial customer changed who signs their checks. That takes a conversation, and the conversation is still yours.

Picking the numbers is yours too, and so is changing them when the business changes. The report is also only as good as what people enter. If techs close jobs from the truck two days late, Monday's numbers are two days behind, and no build fixes that. A five minute talk with the crew usually does.

And the report can put the three customers who need a call at the top of your Monday, but calling them is up to you.

When a dashboard is the better choice

If you have a dispatcher or office manager who runs the day from a live board, keep the board. It does a different job than a weekly report. The same goes for a business with more than one location, where each manager needs a separate view. And if your software's reporting tab already shows the five numbers you care about and you really do open it every Monday, you don't need a report built.

Where to start

If your Monday numbers come from someone's morning in a spreadsheet, the free 20 minute process audit is where I'd start. We go through what you track now, where each number lives, and which ones you'd read if they showed up on their own. Builds start at $500 one time, then a flat monthly from $99 after an included run-in period, cancellable. There's more on how this works for businesses across Illinois. Book the audit here.