Tag: Business Operations

  • How to Build a Monthly KPI Scorecard

    Build it in the spreadsheet you already use. Put four to seven metrics on a Scorecard tab that shows, for the current month, the target, the actual, the variance, and a green, yellow, or red status. Keep the twelve-month history on a Trend tab, calculations on a Data tab, and each raw export on its own import tab. Start targets from your own recent history, and update the sheet the same way every month after the books close.

    That is the whole design. Most of the work is in the decisions behind each cell: which metrics earn a row, what counts as on target, and how the numbers get in without someone retyping them.


    What a Monthly Scorecard Is For

    A scorecard answers one question each month: is the business on track, and if not, where? It is not your accounting system and it is not a report. It is a single view that someone can read in a minute and act on.

    That purpose sets the rules:

    • Four to seven metrics. My rule of thumb, depending on the business, is four to seven, and no vanity metrics. Each one has to move the needle: when it changes, someone makes a decision. How Many KPIs Should a Small Business Track? covers how to choose them.
    • One screen. The Scorecard tab fits on a laptop screen without scrolling sideways. If it doesn’t, you have too many metrics or too many columns. The full history lives on another tab.
    • Metrics in rows, in the same order on every tab. Row 6 is the same metric on the Scorecard and the Trend tab, which keeps formulas simple to copy.
    • Every number has a comparison. A figure with no target beside it doesn’t tell anyone whether to act.

    Use Google Sheets if your business runs on Google Workspace, and Excel if it runs on Microsoft 365. My view is that a small business should stay with the tools it already pays for as long as they do the job, and a monthly scorecard is well within what either can do.


    Step 1: Choose the Rows

    Group the metrics so the sheet reads in a consistent order. A practical split for most small businesses:

    • Money (two or three rows): revenue, gross margin, operating cash flow.
    • Operations or capacity (one to three rows): billable utilization for a service firm, first-pass yield for a shop, jobs completed for a trade business.
    • Customers and pipeline (one or two rows): qualified pipeline value, on-time delivery, customer retention.

    Pick from these, don’t take all of them. If you already track seven metrics and want an eighth, one of the seven should go. For service-business examples with formulas, see KPIs for a Small Professional Services Firm.

    For each metric, write down four things before you build anything:

    • Definition, including where the number comes from.
    • Unit: dollars, percent, days, or count.
    • Direction: whether higher or lower is better. Revenue is better high. Days sales outstanding is better low. The sheet needs to know the difference, or it will color a collections problem green.
    • Type: a flow, a ratio, or a point-in-time figure. This decides how year-to-date is calculated in Step 3.

    Step 2: Lay Out the Tabs

    Build the workbook in layers, so the tab people read never touches raw data.

    Scorecard tab. This is what people read. A header block at the top holds the company name, the reporting month, the date last updated, and who updated it. Put the reporting month in its own cell (say, B2), because the formulas will use it. Below that, each metric gets one row:

    ColumnContents
    AMetric name
    BOwner
    CUnit ($, %, days, count)
    DDirection (higher or lower is better)
    EThis month’s target
    FThis month’s actual
    GVariance
    HStatus (green, yellow, red)
    IYear-to-date actual
    JYear-to-date target

    Ten columns fit on one screen. If a comparison with the same month last year matters in your business, add it after F, as long as the tab still fits.

    Trend tab. The same metric rows, with January through December in columns C through N and the month names in row 5. This is where people look when they want to know whether this month is a blip or a trend. Below the metric rows, keep the components that ratios need, such as monthly gross profit and revenue, or billable and available hours.

    Data tab. Calculations only. Each metric’s monthly value is calculated here from the import tabs, in a labeled block. Nobody pastes anything onto this tab.

    Import tabs. One tab per source: accounting, CRM, time tracking. Each month, the owner clears the tab and pastes that source’s standard export into cell A1. Nothing is typed or calculated on an import tab, so a longer or shorter export can’t overwrite a formula. On the Data tab, refer to whole columns or use lookups by label, so the calculations still work when the export has more rows than last month.


    Step 3: Add the Formulas

    These formulas behave the same way in Google Sheets and Excel. The examples use row 6.

    Pull this month’s actual. Rather than retyping, have column F on the Scorecard look up the month named in B2 from the Trend tab. The month in B2 has to be spelled exactly as it is in the Trend headers. With the month names in C5:N5:

    =INDEX(Trend!C6:N6, 1, MATCH($B$2, Trend!$C$5:$N$5, 0))

    The 1 tells INDEX to stay in the first (and only) row of the range, and MATCH supplies the column. Change B2 next month and every row updates.

    Calculate the variance. For dollars and counts, use the percentage difference from target:

    =(F6-E6)/E6

    For metrics that are already percentages, such as gross margin or utilization, use the difference in points instead:

    =F6-E6

    The two give different impressions. A margin target of 42% against an actual of 38.5% is 3.5 points below target, which is also 8.3% below it. “3.5 points” is the figure most people understand when they read a margin. Pick one convention per metric, label it, and keep it.

    Flip the sign for lower-is-better metrics. If D6 says “lower,” multiply the variance by −1 so that a negative number always means worse:

    =IF(D6="lower", -1, 1) * (F6-E6)/E6

    Handle zero targets. A percentage variance divides by the target, so a target of zero, such as zero overdue invoices or zero safety incidents, returns an error. Track those metrics in units instead: the variance is simply the count. Give that row its own status rule, for example =IF(F6="", "No data", IF(F6>0, "Red", "Green")), in place of the band formula in Step 5. Give “No data” a neutral style so a missing actual is never shown as Green.

    Calculate year-to-date by metric type. Averaging twelve monthly figures is right for almost nothing. Use the type you wrote down in Step 1:

    • For flows such as revenue, jobs completed, or operating cash flow, sum the months.
    • For ratios such as gross margin, utilization, or on-time delivery, recompute them from the summed components. Year-to-date margin is total gross profit divided by total revenue; year-to-date utilization is total billable hours divided by total available hours.
    • Point-in-time figures such as pipeline value, days sales outstanding, or cash balance: use the latest month-end value, or another method you define and write down.

    Retention depends on how you define it, so write the year-to-date rule into its definition. The year-to-date target follows the same rule as the actual.

    The ratio difference is real. Suppose January brings in $50,000 at a 40% margin ($20,000 gross profit) and February brings in $100,000 at 30% ($30,000). The average of the two percentages is 35%. The actual year-to-date margin is $50,000 ÷ $150,000, or 33.3%, because February’s larger month counts for more.


    Step 4: Set Targets, Starting From Your Own History

    A target picked because it sounds good gets ignored after the first miss. Start from what the business has actually done, then decide what it should do.

    1. Find a baseline. The trailing three-month average is a reasonable starting point, because recent months reflect your current staff, prices, and customers. If your business is seasonal, look at the same month last year as well.
    2. Turn the baseline into a target. Check it against your budget, your capacity, commitments you’ve already made, the season, and any improvement you’re planning. A baseline built from weak months will simply repeat them if you adopt it unchanged.
    3. Write down the reason for any difference between baseline and target, so the target can be explained later.
    4. Round to a number people can remember.

    Here is an example, not a client case. A business had revenue of $78,400 in June, $81,200 in July, and $76,900 in August. The three-month baseline is about $78,800. September is usually similar to the summer months; nothing unusual is planned, and the budget agrees, so the target is set at $79,000. September comes in at $72,600, which is $6,400 short, or 8.1% below target.

    Whether 8.1% is a problem depends on the band you set.


    Step 5: Set Tolerance Bands

    A tolerance band says how far a metric can move before anyone needs to act. Without one, every small dip gets discussed, and the meetings lose their point.

    I set bands from the business’s own history. I look at how much each metric actually moved over the last six to twelve months. Movement inside that normal range I treat as noise. Movement outside it means something changed. One caution: several months drifting the same way inside the band is still a trend, which is why the Trend tab matters.

    I also set them metric by metric, because metrics don’t behave the same way. A 5% miss on gross margin can be serious, while a 5% dip in inquiries may be an ordinary month.

    If you don’t have enough history yet, you still need a placeholder. There is no standard band. As a rough starting point, not a hard rule, some businesses could begin with something like:

    • Green: within 5% of target, or better.
    • Yellow: 5% to 15% worse than target.
    • Red: more than 15% worse than target.

    Replace it with bands from your own data once you have a few months. On that sample starting point, the September revenue example above (8.1% below) is yellow. A days sales outstanding target of 45 days against an actual of 52 is 15.6% worse, so it’s red.

    To fill the Status column, add a formula that returns a word:

    =IF(G6>=-0.05, "Green", IF(G6>=-0.15, "Yellow", "Red"))

    Then add three conditional formatting rules to column H: text is exactly “Green,” “Yellow,” or “Red.” Use the word as well as the color so the status still reads correctly in a printout or for anyone who has trouble telling the colors apart. Keep the rest of the sheet in neutral tones so the color means something when it appears.

    For percentage metrics tracked in points, the formula compares against point thresholds instead, for example −1 and −3 points. Record the band for each metric in a note on the Data tab so nobody has to guess later why margin turned red at a smaller miss than revenue did.

    A red status should trigger a short note from the metric’s owner: what happened, what it means, what we’ll do, and who does it by when. How to Get Your Team to Actually Use Your Reports covers that note and the meeting around it.


    Step 6: Update It the Same Way Every Month

    A scorecard that takes an afternoon to update gets skipped within a few months. If the update drags, the problem is usually how the data gets in, not the scorecard.

    Here is an example routine for a business that finishes its month-end bookkeeping within the first few business days. Adjust the days to your own close.

    1. Books closed. Wait until the month’s transactions are reconciled. Numbers pulled earlier will change, and the scorecard will disagree with your accounting.
    2. Exports in. Each metric owner clears their import tab and pastes the same standard export into cell A1. Save each export with the same filters and date range every month, and write those settings down.
    3. Record the month. Copy the Data tab’s results into that month’s column on the Trend tab using paste values, so next month’s imports don’t change them.
    4. Review. Change the reporting month in B2. Check the status column, then check that two or three headline figures match your accounting system before anyone else reads the sheet.
    5. Lock the month. Protect the finished month’s column on the Trend tab so nobody edits it by accident. In Google Sheets, use Protect sheets and ranges. In Excel, lock the cells and turn on Protect Sheet.

    When numbers do disagree, don’t adjust the scorecard to make them match. Find the cause. Revenue that differs between your payment processor, your bank, and your books usually has an ordinary explanation: payout timing, processor fees, or a different cutoff date. The Business Data You Already Have explains why those sources rarely line up.


    Monthly Scorecard Checklist

    • Four to seven metrics, each with a written definition, unit, direction, and type.
    • One owner per metric.
    • A Scorecard tab that fits on one screen, with a Trend tab, a Data tab, and one import tab per source behind it.
    • This month’s target, actual, variance, and status in adjacent columns.
    • Year-to-date figures calculated by type: flows summed, ratios recomputed from components, point-in-time figures taken at month end.
    • Targets that start from a baseline and account for budget, capacity, and season, with adjustments written down.
    • A tolerance band for each metric, and a separate rule for any metric with a zero target.
    • A written monthly routine, with each finished month recorded as values and locked.

    Frequently Asked Questions

    Should the scorecard be weekly or monthly?
    Both can exist. Weekly suits operating numbers people can act on quickly. Monthly suits numbers that only settle after the books close, such as margin and cash flow. Build the monthly scorecard first if your accounting only closes monthly.

    Can I download a template instead?
    Yes, if it’s close to what you need. Check that it lets you set your own four to seven metrics, keeps raw data away from the results, and uses formulas you can follow. If you’d have to delete most of it, building the tabs yourself may be simpler. Either way, make sure you understand every formula before something breaks.

    When should the scorecard move out of a spreadsheet?
    When the spreadsheet becomes the hard part: refreshing the data takes more time than acting on it, different people need different access, you need a record of who changed what, the data volume slows the file down, or keeping it working has become a job of its own. Until then, a spreadsheet is easier to change as you learn which metrics matter.

  • How Much Does a Small Business Dashboard Cost?

    There is no responsible single price for a small business dashboard, because "dashboard" covers everything from a spreadsheet scorecard to a multi-system software project. What you can judge is the work behind a quote. Four things drive it, and none of them is how the charts look: how clean your data already is, how many systems have to feed it, whether the numbers update on their own, and how many metrics you ask for. One tidy source in a spreadsheet is the cheapest build. Several automated feeds cost more. A build that needs a database or custom integration costs the most. Software licenses and upkeep are separate and ongoing.

    That is also why two honest quotes for "a dashboard" can differ widely. They are pricing different amounts of work, and most of that work happens before anything appears on a screen.


    What Actually Drives the Price

    How clean your data is. This is usually the biggest single factor. If the same customer appears three ways in your invoicing system, if products were never mapped to consistent codes, or if someone types entries by hand each week, that all gets sorted out before any chart is accurate. Clean, consistent records make a build straightforward. Messy ones turn it into a data project with a dashboard at the end.

    How many systems feed it. Each additional source adds more than a connection. It adds a definition to agree on and a reconciliation to maintain. Your accounting software, your payment processor, and your bank will each report a different number for what looks like the same month, for legitimate reasons, and someone has to decide which one the dashboard shows. The Business Data You Already Have covers why those three rarely agree.

    Whether it updates by itself. A dashboard you refresh by pasting an export is cheap to build and costs you time every week. An automated refresh costs more up front and less afterward, as long as someone maintains the connection when a source changes its format.

    How many metrics you ask for. This is the one you control most directly. My rule of thumb is four to seven metrics on the main view, and the question I ask about each one is whether it makes a difference: does it help bring in revenue, make the business more efficient, or cut costs? A request for twenty-five charts does not just add twenty-five drawings. Each metric needs its data found, cleaned, defined, and tested. Cutting the list is the cheapest change you can make to a quote. How Many KPIs Should a Small Business Track? covers how to choose them.


    Three Scope Tiers, Lowest to Highest

    One or two clean sources in a spreadsheet. Google Sheets or Excel, fed by exports you download from your accounting or payment system and paste in, with formulas doing the rest. This suits a business that wants a reliable monthly scorecard and can live with updating it by hand.

    Automated feeds in a reporting tool. Looker Studio or Power BI pulling from two to four systems on a schedule, with metric definitions agreed and built in. This is the common choice for a business that reviews numbers weekly and does not want anyone handling files.

    A multi-system pipeline. Five or more sources, a proprietary POS or ERP in the mix, data landing in a cloud database before it reaches the dashboard, and user permissions controlling who sees what. This is a software project, priced accordingly, and worth it mainly when the alternative is several people reconciling by hand.


    What a Comparable Quote Contains

    Quotes vary more because of scope than because of rates. Before comparing two numbers, make sure both describe the same work. A quote you can compare states, in writing:

    • Which systems get connected, and who provides the access.
    • Which metrics get built, and the agreed definition of each one.
    • How the data refreshes, and how often.
    • What happens when a source changes its export format.
    • Who owns the file or workspace when the project ends.
    • How ongoing maintenance is requested and billed.

    Hourly billing suits small changes and work where the scope is still unclear. A fixed price caps your cost for the work written into the scope, so ask how the quote handles changes you request later. A short paid scoping step before a fixed quote can reduce that risk, because it forces the definitions conversation early, when changing your mind costs the least.


    The Costs That Don't Stop

    Software licensing is separate from the build. Looker Studio is free for authoring and sharing reports. Power BI Pro is a paid per-user license, listed at $14.00 per user per month billed annually at the time of writing. If a system you use has no native connector, a third-party connector service may add its own monthly subscription.

    Maintenance is the easiest part to leave out of a budget. Upstream software changes column headers, an API updates, a new service line needs a new definition. Some businesses pay a fixed retainer; others handle changes as they arise, billed hourly or under a service agreement. What matters is agreeing in advance who does it, not how many hours it takes.


    Building It Yourself Isn't Free

    The tools can be free. Your time isn't. Estimate the hours you expect to spend building it, add the hours to keep it running every month, and multiply by what an hour of your own time is worth to the business. Use your own figures rather than a published average.

    Compare that against a quote before deciding. The common failure is not a bad decision either way. It is the half-built file that gets abandoned three weeks in, after the hours are already spent.


    Frequently Asked Questions

    Why won't anyone publish a price?
    Because "a dashboard" can mean a single spreadsheet tab or a multi-system software project. Most of the difference is in your data, which nobody can see until they look at it.

    Can I start small and add to it later?
    Yes, and it's usually the better path. Start with one source and the few metrics that pass the revenue, efficiency, or cost test. Adding a second source later is easier than removing four you never used.

    Should I fix what I have instead?
    Often, yes. If your numbers are accurate and the dashboard is just cluttered, renovation is often the smaller job. Have someone inspect how the current one is built before you decide. How to Improve a Business Dashboard You Already Have walks through that.


    Before You Spend Anything

    Check whether you already have what you need. Pull two or three headline numbers from your existing systems and see whether they hold up. If they do and the problem is presentation, renovate. If you're not sure whether you need outside help at all, When Should a Small Business Hire a Data Analyst? covers that decision.

  • KPIs for a Small Professional Services Firm

    A small professional services firm can run on five KPIs: billable utilization, realization, project gross margin, days sales outstanding (DSO), and qualified pipeline. Together, they answer the questions that decide whether a firm that sells time makes money. Are people spending their hours on billable work? Is that work getting billed and paid at the rates you set? Are projects finishing on budget? Is cash arriving on time? Is next quarter’s work lined up?

    What those numbers should be in your firm is a separate question, and it is where generic advice is weakest.


    Why Generic Benchmarks Don’t Fit Your Firm

    You’ll find plenty of published targets for utilization and margin. I wouldn’t lean on them. Setting a utilization target without looking at what a firm does and how it does the work is like generalizing about a family’s culture from the outside. A five-person engineering firm where the owner writes every proposal is a different business from a ten-person agency with a dedicated salesperson, even though both sell hours.

    Margin works the same way. What a healthy project margin looks like depends on the industry and the market you serve.

    So use the formulas below as written, but set your normal ranges from your own history: the last six to twelve months of time, invoice, and payment records, with seasonal periods compared like for like. The point is to notice when a number moves away from your normal and to know what to do about it. For why five metrics is enough, see How Many KPIs Should a Small Business Track?


    1. Billable Utilization

    Formula: billable hours ÷ available working hours × 100

    A consultant who records 30 billable hours in a 40-hour working week is at 75 percent. Define available working hours consistently by excluding company holidays and approved leave. Whether 75 percent is right depends on the role. Someone whose job is mostly client delivery will run higher than a senior lead who also reviews work and trains staff. An owner who writes proposals and runs the firm will run lower still. If an owner’s billable hours climb while the pipeline shrinks, check whether client delivery is crowding out business development.

    Set a normal range for each role based on what that role is actually expected to do, rather than one number for the whole firm.

    Watch for: utilization rising while realization falls. People are busy on work the firm isn’t getting paid for.


    2. Realization

    Realization shows how much of the work you record turns into revenue. Track it in two parts.

    Billed realization: fees invoiced ÷ (billable hours × standard rate) × 100

    If a team records 120 billable hours at a $150 standard rate, that work is worth $18,000 at standard rates. If the invoices total $15,300, billed realization is 85 percent. The missing $2,700 went to write-downs, discounts, or scope that never got billed.

    Collected realization: cash collected against a group of invoices ÷ the value of those invoices × 100

    Measure the same invoice group in the numerator and denominator, or use a rolling window long enough to absorb ordinary payment lag. Otherwise, this month’s collections divided by this month’s invoices can compare unrelated work. The measure catches disputes, deductions, and invoices that never get paid.

    On fixed-fee work, the same idea appears as an effective hourly rate: fees collected on the project ÷ all hours worked on it, including rework. A $10,000 fixed-fee project that took 100 hours earned $100 an hour. At a $175 standard rate, the same 100 hours have a standard-rate value of $17,500, leaving a $7,500 gap to investigate. That gap is not automatically lost profit; it may reflect deliberate pricing, scope growth, or delivery inefficiency.

    Watch for: billed realization dropping on the same clients or project types. The fix is usually tighter scope and change orders, not more hours.


    3. Project Gross Margin

    Formula: (project revenue − direct labor cost − direct project expenses) ÷ project revenue × 100

    Use burdened direct labor cost: wages plus employer payroll taxes and employee benefits for the hours spent on the project. Keep overhead separate unless your project-costing method allocates it consistently.

    Because margin expectations vary so much by industry and market, compare each project with its own budget. A project priced for a 55 percent margin that finishes at 38 percent tells you something went wrong in the estimate, the scope, or the delivery. Find out which before you quote similar work.

    Watch for: the same type of project repeatedly finishing below its budgeted margin.


    4. Days Sales Outstanding (DSO)

    Simple formula: ending accounts receivable ÷ credit sales for the period × days in the period

    With $90,000 in ending receivables and $270,000 in credit sales over the last 90 days, DSO is 30 days. If receivables swing sharply during the period, use average receivables instead of the ending balance and label the method so comparisons stay consistent.

    DSO estimates how long clients take to pay, but it lags. By the time it jumps, the late invoices are already late. I prefer to set up receivables so someone sends reminders and talks with clients around the due date. That way, the firm can identify payments that may lag and address issues before invoices drift past 60 days.

    Watch for: individual invoices getting close to 60 days, not just a rising average.


    5. Qualified Pipeline

    Definition: total value of qualified proposals and opportunities expected to close in the next 90 days

    Some firms weight each opportunity by its chance of closing. A simple total works too, as long as you count the same way every week.

    The first four KPIs describe the work you already have. Pipeline tells you whether there will be work next quarter, and it’s the number that suffers first when senior people are too busy billing to sell. Client retention matters as well, but it changes slowly; review it quarterly rather than weekly.

    Watch for: pipeline shrinking while utilization is high. That’s a firm that is busy now and will be short of work later.


    A Simple Scorecard Layout

    KPISource recordsReviewExample ownerWhen it moves outside your range
    Billable utilization, by roleTime trackingWeeklyOperations leadRebalance assignments; check who is overloaded
    Billed and collected realizationTime tracking and invoicingMonthlyManaging partnerLook for write-downs by client or project type; tighten scope
    Project gross marginTime, payroll, and project expensesAt milestones and closeProject leadCompare with the estimate; adjust pricing for similar work
    DSO and open invoicesAccounting receivables agingWeeklyOffice or finance managerFollow up on invoices near their due date
    Qualified pipelineCRM or proposal listWeeklyOwner or sales leadProtect time for business development

    Most of this data already lives in your time-tracking, invoicing, and accounting software. Start with a simple spreadsheet if you need to bring the sources together.

    If pulling these numbers together each week takes longer than acting on them, it may be time for outside help. When Should a Small Business Hire a Data Analyst? covers how to tell.

  • How to Get Your Team to Actually Use Your Reports

    Reports get used when they feed a routine that ends in decisions. Keep the report to one page with four to seven core numbers. Have each manager prepare a short note on any number that’s off track. Then run a short weekly meeting built around three questions: What do the numbers mean? Who will act on them? By when? Open the next meeting by checking whether those actions happened.

    To me, a useful conversation about the numbers is an action-oriented one: what the numbers mean, who will act on them, and by when. Most reporting routines stop at the first part. Without a name and a date, a team can discuss the same bad number every week and nothing changes.


    Why Doesn’t Your Team Read the Reports You Send?

    Often because reading them is not connected to a decision or a follow-up. A report emailed on Monday competes with customer calls, staffing problems, and everything else on a manager’s list. If no meeting depends on it and nobody will ask about it, reading it is optional, and optional work gets pushed to later.

    Two other problems make it worse:

    • The report makes the reader do the analysis. A ten-tab spreadsheet or a 15-page PDF asks each manager to find what changed and decide whether it matters. Most probably won’t.
    • The report describes the past without asking for anything. If a report never leads to a decision, people reasonably conclude it isn’t meant for them.

    If the problem runs deeper, and people don’t trust the numbers or can’t connect the metrics to their work, start with Why Nobody Looks at Your Dashboard. The routine below works best once people believe the numbers.


    What Should the Report Look Like Before the Meeting?

    One page. If it doesn’t fit on one page, each reader has to do the sorting the report should have done for them.

    A one-page weekly summary needs four parts:

    1. The scorecard. Four to seven core metrics, each with its current value, target range, prior period, and a simple on-track or off-track status. Four to seven is my rule of thumb for most small businesses; How Many KPIs Should a Small Business Track? covers how to choose them.
    2. What’s off track. The metrics outside their range this week, called out at the top so nobody has to hunt for them in a table.
    3. What went well. One to three things that improved, and why. This keeps the meeting from turning into a list of problems and tells people what to keep doing.
    4. Decisions needed. Anything that needs an approval, a trade-off, or resources from the owner this week.

    Everything else goes in an appendix or a linked file: full financial statements, transaction detail, breakdowns by customer or crew. People open it when they need to investigate. A monthly version can add that detail without crowding the weekly operating view.


    How Should Managers Prepare for the Meeting?

    They should read the one-page summary beforehand and write a short note for any metric they own that is off track. Meeting time is for deciding, and reading numbers aloud wastes it.

    Send the summary early enough to read: Friday afternoon for a Monday meeting, or first thing in the morning for a late-morning meeting. Put the notes in one shared document so everyone can see them before the meeting starts.

    The Off-Track Note

    Each note answers four questions in a few sentences:

    1. What happened? The number, its target, and how far off it is.
    2. What does it mean? The effect on cash, customers, delivery, or cost.
    3. What will we do? The specific action.
    4. Who, and by when? One name and one date.

    Here is a hypothetical example, not a client case:

    What happened: First-pass yield fell to 88% this week against a target of 95%.

    What it means: About 12 hours of rework, roughly $2,500 in scrapped material, and one order at risk of shipping late.

    What we’ll do: Recalibrate the tooling on the cutting station and review the new tolerances with the operators.

    Who and by when: Shop lead. Tooling done by Tuesday; operator review Wednesday morning.

    A short note like this changes where the conversation starts: with a proposed fix instead of an argument about what went wrong.

    One rule matters more than the format. Don’t penalize people for reporting a red number. Ask them to bring either a proposed next step or a clear request for help. If off-track numbers get people criticized in front of the team, expect to see numbers explained away instead of fixed.


    How Do You Run the Meeting?

    Keep it short, run it the same way every week, and end with names and dates. The agenda below is a 15-minute starting point for a small team; add time when several metrics need real decisions.

    Here is a starting agenda for a 15-minute meeting. Stretch the off-track section if you need a longer one.

    MinutesTopicWhat happens
    0–3Last week’s actionsEach owner says done, in progress, or missed; a missed action gets a new date
    3–5ScorecardWalk through the metrics and confirm which are off track
    5–12Off-track metricsEach owner gives their note in about a minute; the group agrees on the action, owner, and date
    12–15Decisions and blockersThe owner approves resources or settles conflicts between departments

    A few rules keep it on track:

    • Show the report itself. Put the one-page summary or the dashboard on the screen. A separate slide deck is one more document to maintain and one more place for numbers to disagree.
    • Skip what’s on track. If a number is in range, move on.
    • Take long problems out of the meeting. If something needs more than a few minutes, assign someone to work on it and set a date to report back.
    • Record every action before anyone leaves, with its owner and due date.

    How Do You Make Sure Actions Actually Happen?

    Keep a running action log and open every meeting with it. This step is easy to skip, but it is the one that shows people the routine matters.

    The log can be a simple table in the same shared document. The entries below are samples:

    RaisedMetricActionOwnerDueStatus
    Sept. 8Days sales outstandingCall the five largest overdue accountsOffice managerSept. 12Done
    Sept. 8Labor cost as % of salesAdjust Tuesday and Wednesday schedulesOperations leadSept. 15In progress
    Sept. 15First-pass yieldRecalibrate cutting station toolingShop leadSept. 16Open

    When you review the log each week:

    • Done: Check whether the metric responded. If it didn’t, the action didn’t address the cause, and the owner needs a new plan. Or, decide if the action did address the cause and the response needs more time to become indicative.
    • In progress: Confirm the date still holds.
    • Missed: Ask for a new date and what got in the way. If the same action slips twice, investigate whether the constraint is time, authority, resources, or an unclear assignment instead of sending another reminder.

    Over a few months, the log also shows which problems keep coming back. That pattern can be more useful than any single week’s report.


    What About Monthly Reviews and One-on-Ones?

    Use the same pattern at a different pace.

    A monthly review covers the numbers that only change meaningfully after the books close, such as gross margin, and looks at trends across several weeks. It uses the same off-track notes and the same action log, with additional financial and operating detail where needed.

    A one-on-one is where you help a manager with their own numbers. Start with the metrics they own, look at the trend, and ask what they need to bring an off-track number back into range: time, budget, help from another department, or a decision from you. Asked that way, the conversation becomes about solving the problem together rather than checking up on them.


    How Do You Keep Reports From Piling Up Again?

    Review every recurring report once a quarter and stop the ones nobody would miss. Reports accumulate: someone asks a one-time question, the answer becomes a weekly report, and nobody ever turns it off.

    For each scheduled report, ask the people who receive it: “If this report stopped tomorrow, what decision would you be unable to make?” If nobody can name one, stop sending it. If someone misses it later, you can bring it back.

    Apply the same test to the metrics on the weekly summary. If your dashboard has grown well past what the meeting can use, How to Improve a Business Dashboard You Already Have walks through cutting it down.


    Your First Four Weeks

    • Week 1: Cut the report to one page with four to seven metrics, and assign an owner to each.
    • Week 2: Send the summary before the meeting and ask owners of off-track metrics for their notes. Some notes will be missing; ask for them anyway.
    • Week 3: Open the meeting with the action log from week 2.
    • Week 4: Look back at the log. Which actions got done, which slipped, and did the numbers respond? Adjust the metrics, the timing, or the meeting length based on what you find.

    Expect the routine to feel mechanical at first. It starts to stick once people see that a number raised in one meeting leads to an action, and that the action gets checked in the next one.

  • Why Nobody Looks at Your Dashboard (and How to Fix It)

    People stop looking at a dashboard for a few predictable reasons: they don’t trust the numbers, the metrics don’t connect to their work, nobody has shown them what to do when a number changes, the screen is a hassle to use, or the person in charge ignores it too. Training alone will not fix those causes. What works is rebuilding trust in the numbers, cutting the dashboard down to metrics people can act on, and tying each one to a decision.

    I have seen reports get ignored for several of these reasons. A recurring one was that people didn’t understand what difference the numbers could make, or how to act on them. Once, the reason was simpler: the person in charge was sure they already knew the business better than any report could tell them.

    The good news is that each cause leaves a recognizable trail, so you can figure out which one you are dealing with before you change anything.


    How Does a Dashboard Go From Launch to Ignored?

    Usually gradually, and for reasons that started weeks before anyone noticed the drop in use. Abandoned dashboards tend to follow the same pattern.

    1. Launch. The dashboard is introduced in a meeting. People open it out of curiosity, click around, and say it looks useful.
    2. The first doubt. Someone notices a number that doesn’t match what they know: a sales total that looks low, a job count that seems off. Nobody explains the difference.
    3. The quiet return. Instead of reporting the problem, that person goes back to their own spreadsheet. Others follow for their own reasons: the dashboard is slow, or it doesn’t show what they need.
    4. Neglect. With fewer people looking, nobody notices when a data connection fails, or a metric goes stale. The out-of-date numbers confirm everyone’s decision to stop using it.

    The clearest sign you have reached step 3 or 4 is that managers arrive at meetings with their own spreadsheets. A dashboard that has lost to private spreadsheets has usually lost on trust, relevance, or both.


    Why Do People Stop Trusting the Numbers?

    At some point, a dashboard number disagreed with something they knew was true, and nobody could explain why, or worse, could figure out why. That single discrepancy erodes confidence entirely.

    Take a sales manager who knows the team closed about $55,000 in new work last month. The dashboard says $42,000. There may be a perfectly good reason. The dashboard might count invoiced revenue, while the manager counts signed contracts. It might use a different month-end cutoff, or leave out a job still waiting on an invoice. Without an explanation, though, the manager concludes the dashboard is wrong and stops trusting the other numbers on the screen, too.

    Numbers drift apart for a handful of common reasons:

    • Different definitions. “Sales” can mean booked, invoiced, or collected. Each is legitimate, and each produces a different total.
    • Timing. Cash and accrual accounting put the same transaction in different periods. Payment processors deposit money days after the sale.
    • Unmapped categories. A new product, service code, or customer type gets added to the source system but never mapped into the dashboard, so its revenue disappears from the totals.
    • Silent failures. A data refresh fails, or a formula breaks, and the dashboard keeps showing old numbers without any warning.

    Most of these aren’t errors in the usual sense. They are definitions and rules that were never written down where the people using the dashboard could see them. Tracing a mismatch starts with documenting which system, definition, date range, and cutoff produced each number.


    Why Don’t the Metrics Feel Relevant to the Team?

    Because the dashboard shows what the owner wants to know rather than what the people using it can influence.

    A shop supervisor can’t do much with quarterly net profit. They can act on the number of jobs waiting for inspection or the parts that failed first inspection this week. A service coordinator can’t move company-wide revenue directly, but they can act on unbilled hours or open slots in next week’s schedule.

    When the main view shows only company-level results, frontline managers reasonably decide the dashboard isn’t for them. They aren’t resisting data. They are ignoring numbers they can’t do anything about.

    Each person should see the few metrics they can move, alongside the company results those metrics feed. For choosing those metrics, and keeping the list short enough to act on, see How Many KPIs Should a Small Business Track?


    What If People Don’t Know What to Do With the Numbers?

    Then the numbers are trivia, and people stop checking trivia. In my experience, this is a recurring reason reports get ignored: nobody understood what difference the number could make or how to act on it.

    Suppose a dashboard shows that days sales outstanding rose from 38 to 47 over two months. To an owner who watches cash closely, that is an obvious warning: customers are paying more slowly, cash will be tighter, and someone should start calling the largest overdue accounts. To a manager who has never had that explained, it is just a number that went up.

    A practical fix is to write one line for every metric on the main view that answers three questions: what it means when the number moves, what usually happens next, and who does it. Put those lines on a notes tab or beside each card.

    Here is what that looks like for a few metrics. The metrics, triggers, and owners are illustrative; set your own.

    MetricWhen it moves the wrong wayWhat usually happens nextWho
    Days sales outstandingRises two weeks in a rowCall the five largest overdue accounts; review payment terms on new workOffice manager
    Gross margin by jobA job finishes below targetCompare actual hours and materials with the estimate; adjust the next quoteOperations lead
    Qualified inquiriesFalls below the monthly rangeCheck whether the source changed (referrals, website, repeat customers) before spending more on marketingOwner
    Booked hours next weekBelow available capacityContact customers with pending work; move maintenance tasks into the open timeScheduler

    Writing these lines also tests the metric. If nobody can say what action would follow a change, the metric probably doesn’t belong on the main view.


    Is the Dashboard Too Much Trouble to Use?

    It may be. Every extra login, filter, click, and scroll makes it easier to just ask someone for the number.

    Watch for these signs:

    • People email or message you asking for figures that are already on the dashboard.
    • Getting to the dashboard requires a login people forget, or a link buried in an old email.
    • Each visit starts with setting date ranges and filters before anything useful appears.
    • It loads slowly, or the important numbers are below the fold.

    Most of these have simple fixes: save a default view with the right filters already applied, share one bookmarked link, and fit the main metrics on one screen. For the design problems that make dashboards hard to read, see 7 Dashboard Mistakes Small Businesses Make.


    What If the Person in Charge Doesn’t Use It?

    Other people are unlikely to use it for long too. One of the reports I have seen ignored went unused for exactly this reason: the boss believed they already knew better and didn’t need it.

    People take their cues from what the person in charge pays attention to. If the owner makes decisions from instinct and never mentions the dashboard, managers learn that keeping the numbers current is wasted effort, and they stop.

    This doesn’t mean experience and instinct should be ignored. An experienced owner often does know things a report can’t show. But when instinct and the dashboard disagree, that disagreement is worth resolving. The data may be wrong, the instinct may rely on context the dashboard does not capture, or an old assumption may need another look.

    If you are the person in charge, three habits change the signal you send:

    1. Ask about the numbers first. Start conversations with managers by looking at their metrics together.
    2. Say which number informed a decision. “We’re holding off on the new hire because booked hours dropped for three weeks” teaches more than a memo about being data-driven.
    3. Treat disagreement as a question. When a number surprises you, ask why before dismissing it.

    How Do You Get People Looking at the Dashboard Again?

    Fix trust first, then relevance, then habit. Redesigning the layout before people trust the numbers produces a better-looking dashboard that people still ignore.

    Step 1: Reconcile the Numbers in the Open

    Sit down with the managers who use the dashboard. Pick the headline numbers and compare each one with its source: bank deposits, accounting reports, payroll, or the scheduling system. For every gap, either fix it or explain it. Then write each metric’s definition in plain language where everyone can see it, such as “Revenue = invoiced amounts by invoice date, excluding sales tax.”

    Step 2: Let Managers Challenge Their Metrics

    If a manager says a metric doesn’t reflect their work, take it seriously. Either the definition needs to change or the metric needs to be replaced. Separate two kinds of objections, though: “this is measured wrong” gets fixed, while “I don’t like what this shows” doesn’t.

    Step 3: Cut the Main View Down

    Keep four to seven metrics on the main screen, which is my rule of thumb for most small businesses. Move the rest to a detail tab. How to Improve a Business Dashboard You Already Have walks through the cleanup step by step.

    Step 4: Attach an Action and an Owner to Every Metric

    Write the one-line action notes described above, and put one person’s name on each metric.

    Step 5: Put the Dashboard on a Meeting Agenda

    A dashboard that people are only invited to check will keep sliding back toward neglect. Make it the first thing a regular meeting opens, and ask each owner to speak to their number: what changed, what it means, who will act, and by when.


    Which Problem Do You Have?

    Match what you see to the likely cause and the place to start:

    What you noticeLikely causeStart with
    Managers bring their own spreadsheets to meetingsThe numbers aren’t trustedStep 1: reconcile in the open
    “That’s not really my number”Metrics don’t fit their workStep 2: let managers challenge metrics
    People look at the numbers, but nothing changesNo action attachedStep 4: write action notes
    People ask for figures that are already on the dashboardToo much trouble to useDefault views, one link, one screen
    Decisions get made without mentioning the numbersLeadership doesn’t use itAsk about the numbers first
    Nobody opens it between meetings, or there are no meetingsNo routineStep 5: put it on the agenda

    Most ignored dashboards have more than one of these problems. Start with trust. Nothing else sticks until people believe the numbers.

  • 7 Dashboard Mistakes Small Businesses Make

    The most common dashboard mistakes are showing too many metrics, featuring vanity metrics that don't lead to decisions, displaying numbers without targets or comparisons, pasting raw tables onto the main screen, paying for real-time updates nobody acts on, leaving metrics without an owner, and mixing headline results with detail. Each one makes the dashboard harder to read quickly, and reading quickly is the whole point of a dashboard.

    Most of these mistakes start the same way: the dashboard gets built around what the software can show instead of the decisions the business needs to make. Use the seven below as a checklist against your own screen.


    1. Too Many Metrics on One Screen

    What it looks like: Twenty or thirty charts, cards, and gauges, and you have to scroll to see them all.

    Why it hurts: When everything competes for attention, the number signaling a real problem looks the same as the twenty that don't. People skim, then stop opening it.

    What to do instead: Keep four to seven core metrics on the main view. That's my rule of thumb for most small businesses, and the reasoning is in How Many KPIs Should a Small Business Track?

    2. Vanity Metrics in the Top Row

    What it looks like: Page views, social followers, total sign-ups, or revenue booked sit in the most prominent spots.

    Why it hurts: These numbers can climb while margins shrink or cash gets tight. They feel like progress and give you nothing to act on.

    What to do instead: Ask whether each metric makes a difference. Does it help bring in revenue, make the business more efficient, or cut costs? Then ask who would do what if it dropped 20 percent next week. A metric that fails both questions doesn't belong at the top.

    3. Numbers With No Context

    What it looks like: A card that says "Revenue: $45,000" or "DSO: 48 days" and nothing else.

    Why it hurts: The reader has to remember last month, recall the budget, and do the math. Is $45,000 a good month? The card can't say.

    What to do instead: Show each number beside a target and the prior period: "$45,000 against a $50,000 target, up from $41,500 last month."

    4. Raw Tables on the Main Screen

    What it looks like: A 50-row export of invoices or transactions embedded on the dashboard.

    Why it hurts: A large raw table usually has to be read line by line, which makes trends and outliers harder to spot at a glance.

    What to do instead: Summarize on the main view with a number card or a small trend line. Keep the table on a separate detail tab for when you need to investigate.

    5. Real-Time Updates for Weekly Decisions

    What it looks like: Live feeds refreshing every few minutes for sales, pipeline, or margin that the team reviews once a week.

    Why it hurts: Real-time connections can add cost or maintenance complexity, and they can invite overreaction to swings that even out by the end of the week.

    What to do instead: Refresh as often as you act. A scheduler may need daily capacity data, while a closed-month margin calculation only needs to update after the accounting period ends.

    6. Metrics Nobody Owns

    What it looks like: Everyone can see the dashboard, but when a number turns red, nobody is sure whose job it is to explain it.

    Why it hurts: Problems get noticed and discussed but not fixed. After a few weeks of that, people stop taking red numbers seriously.

    What to do instead: Put one person's name on each metric. That person explains the number when it moves and says what they'll do about it. Build that ownership into a regular meeting and follow-up routine.

    7. Headline Results Mixed With Detail

    What it looks like: Gross margin and cash runway sit beside ad cost per click and scrap at a single workstation, all the same size.

    Why it hurts: This can happen even on a dashboard with only a handful of metrics. When detail gets the same weight as headline results, reviews drift into the detail and nobody steps back to ask whether the business is on track.

    What to do instead: Use two tiers. The main view holds the headline metrics. Detail lives on a separate tab you open when a headline number moves. The two-tier setup is explained in How Many KPIs Should a Small Business Track?


    A Quick Dashboard Check

    Open your dashboard and answer yes or no:

    1. Does the main view show seven metrics or fewer, without scrolling?
    2. Does every metric on it help bring in revenue, improve efficiency, or cut costs?
    3. Does every number show a target and a prior period?
    4. Are detailed tables kept off the main view?
    5. Does the refresh schedule match how often you act on the numbers?
    6. Does every metric have one named owner?
    7. Is detail kept on a separate tab from headline results?

    Each "no" points to the matching mistake above.


    Next Step: Fix What You Found

    Once you know which mistakes your dashboard has, How to Improve a Business Dashboard You Already Have walks through repairing them in order, starting with whether the numbers can be trusted. If the dashboard is in good shape and people still ignore it, investigate trust and routine rather than redesigning it again.

  • How to Improve a Business Dashboard You Already Have

    Edit your dashboard before you replace it. Confirm the numbers match your source systems, cut the main view to four to seven metrics, lay out what remains on one screen with a target beside each number, fix the manual data steps that keep breaking, and put one person's name on each metric. Most cluttered dashboards can be repaired in the tool you already have.

    A rebuild feels cleaner, but it tends to recreate the same problem in new software. Dashboards get cluttered because requests keep getting added and nothing gets removed. A new tool doesn't change that habit.


    Should You Fix Your Dashboard or Rebuild It?

    Fix it if the underlying numbers are right and the business still works the way it did when the dashboard was built. Rebuild only when the data feeding it can't be repaired, or the business has changed so much that the old metrics no longer describe it.

    Answer three questions before changing anything:

    1. Do the numbers match the source? Pick two or three headline figures, such as last month's revenue or current receivables, and compare them with your accounting system, bank, or POS for the same period. If they match, or the gaps have a known cause like payout timing, the foundation is usable. If nobody can explain the gaps, fix the data first. Redesigning a screen full of wrong numbers wastes the afternoon.
    2. Does the dashboard still describe the business? If you've added a service line, closed a location, or changed how you price, some metrics may describe a business you no longer run.
    3. Is the tool really the problem? Google Sheets, Excel, Looker Studio, and Power BI can all display a clean, focused set of KPIs. Switching tools rarely fixes a layout problem.

    If the answers point to renovation, work through the four steps below in order.


    The Four-Step Dashboard Renovation

    Step 1: Cut the Main View to Four to Seven Metrics

    The fastest improvement is removal. List every chart, card, and table on the dashboard, then mark each one: keep on the main view, move to a diagnostic tab, or delete.

    Which metrics survive depends on the business, but the question I ask is the same: does this metric make a difference? Does it help bring in more revenue, make the company more efficient, or cut costs? If it does none of those, it's a candidate for deletion.

    My rule of thumb is four to seven core metrics, and each one has to move the needle: when it changes, someone makes a specific decision. The full test for sorting metrics is in How Many KPIs Should a Small Business Track?

    Expect pushback on deletions. Instead of arguing, move disputed metrics to a tab labeled "Diagnostic." If nobody opens that tab in two months, delete them.

    Step 2: Make It Readable at a Glance

    Arrange what's left so someone can tell whether the business is on track within a few seconds, on one laptop screen, without scrolling.

    • Replace gauges and dials with number cards. A speedometer graphic uses a lot of space to show one value. A card showing the current value, the target, and last period's value shows more in less room.
    • Take large tables off the main view. A 50-row table is a report. Summarize it in a card or a small trend line and move the detail to the diagnostic tab.
    • Give every number a comparison. "$74,200" alone doesn't tell you much. "$74,200 against an $80,000 target, up from $69,800 last month" tells you where you stand and which way you're heading.
    • Save color for exceptions. Use gray and neutral tones for the layout. Reserve red, yellow, and green for metrics outside their target range, so color means something when it appears.

    If the main view still doesn't fit on one screen, go back to Step 1. The next useful check is to look for repeated design errors such as missing comparisons, raw tables, and detail mixed with headline results.

    Step 3: Fix the Data Steps That Break

    Find every place where someone copies, pastes, or retypes data to update the dashboard. Manual steps are where errors creep in, and where updates stop when that person is on vacation.

    • Connect instead of paste where your tools allow it: a built-in data connector in Looker Studio or Power BI, or the IMPORTRANGE function to pull from another Google Sheet.
    • Document what can't be connected. Write down which report is exported, with which filters and date range, by whom, and when.
    • Match the refresh schedule to your decisions. A metric you review weekly needs a dependable daily or weekly refresh, not necessarily a live feed. Real-time connections can add cost or maintenance complexity, and faster data can invite reactions to swings that even out by the end of the week.

    Step 4: Put a Name on Every Metric

    Assign one person to each metric on the main view and show their name or initials on the card. That person explains the number when it moves outside its range and says what they're doing about it.

    When a metric belongs to everyone, nobody follows up. A named owner means a red number gets an explanation and a next step. Ownership works best when the dashboard is reviewed at a regular meeting with a consistent follow-up routine.


    Dashboard Renovation Checklist

    1. Compare two or three headline numbers with your accounting, bank, or POS records.
    2. List every item on the dashboard and mark it keep, diagnostic, or delete.
    3. Move diagnostic items to a separate tab and delete the rest.
    4. Fit the remaining four to seven metrics on one screen.
    5. Replace space-heavy gauges with cards showing actual, target, and prior period.
    6. List every manual data step, then connect or document each one.
    7. Add an owner's name to every metric.

    Frequently Asked Questions

    How long does it take to fix a cluttered dashboard?

    The cuts and layout changes are usually the quickest part. Data problems take longer, especially if nobody documented how the dashboard was built.

    Should a small business dashboard update in real time?

    Rarely. Match the refresh to how often you act on the number. A scheduler may need daily capacity data, while a closed-month margin calculation only needs to update after the accounting period ends.

    When is it worth paying for a rebuild?

    When the source data can't be reconciled, the business has changed enough that the metrics need to be redesigned, or nobody on staff can maintain the data connections.


    Start With the Numbers

    Begin with the first check: pull two headline figures and compare them with your source systems. If they hold up, the rest of the renovation is editing. If your team still ignores the dashboard after it's cleaned up, investigate trust and routine rather than redesigning it again.

  • How Many KPIs Should a Small Business Track?

    Most small businesses should track four to seven KPIs on their main scorecard. Where you land in that range depends on the business, but the rule for what earns a place does not change: every metric has to move the needle. A change in the number should lead someone to make a specific decision about cash, capacity, or customers. You can still measure everything else. It just belongs in a second layer you open when a core number goes off track.

    Four to seven is an operating guideline, not a scientifically fixed limit. It is deliberately shorter than most “essential KPI” lists. Those lists are written to cover every possible business. Your scorecard only has to cover yours, and it has to be short enough that you and your team will read it every week.


    Why Four to Seven KPIs?

    Four to seven metrics can cover the questions that keep a small business healthy: Do we have cash? Are we making money on the work? Can we deliver? Is new work coming in? That is enough coverage without turning the weekly review into a research project.

    Below four, something important usually goes unwatched. An owner who tracks only the bank balance sees problems weeks after they start: a slow-paying customer, a job that ran over budget, a quiet month in the pipeline. The balance tells you where you are. It says little about what is coming.

    Above seven, three things tend to happen.

    The review takes too long. A short scorecard can fit into a brief weekly review. A 25-metric dashboard is more likely to turn that review into a status recital, so the meeting gets skipped, or the important change gets buried.

    Nobody can tell which change matters. In any given week, some of 25 numbers will rise, and some will fall for ordinary reasons. When everything moves, the one signaling a real problem is easy to miss.

    Ownership blurs. Each of the seven metrics can have a named person responsible for explaining it. With twenty-five metrics, ownership is harder to keep clear, and follow-up becomes less consistent.

    Treat the range as a guideline. A business with several distinct departments may need a short scorecard for each one. The principle holds at every level: the list any one person reviews should be short enough to act on.


    What Makes a Metric a Needle-Mover Instead of a Vanity Metric?

    A needle-mover leads to a specific decision when it changes. A vanity metric can look impressive and still tell you nothing about what to do next.

    Analytics expert Avinash Kaushik calls this the “Three Layers of So What” test. Keep asking “so what?” until the metric leads to a recommended action. If it cannot, it does not belong on the main scorecard.

    Run every metric you currently track through three questions:

    1. The Monday test. If this number dropped 20 percent by Monday morning, who on the team would do what? If the honest answer is “nobody” or “we’d keep an eye on it,” the metric is not a KPI.
    2. The anchor test. Does the metric connect directly to cash, margin, delivery capacity, or keeping customers? If the connection takes three steps of reasoning to explain, it is a supporting metric at best.
    3. The response test. Can your team make a useful decision when this number changes? You may not control the weather, the economy, or a vendor’s pricing, but you can still change staffing, purchasing, pricing, or cash plans in response. If the team cannot influence the number or respond to it, keep it off the main scorecard.

    A metric has to pass all three to earn a place on the main scorecard.

    Here is how some common vanity metrics compare with metrics that answer a similar question in a form you can act on:

    Looks usefulMoves the needleWhy
    Website page viewsQualified inquiries, and the share that become quotesTraffic can rise while the phone stays quiet
    Social media followersCost to acquire a paying customerFollowers don’t pay invoices
    Revenue bookedGross margin and cash collectedRevenue earned at a loss still costs you money
    Total labor or machine hours loggedShare of work done right the first timeBusy hours can hide rework
    Number of proposals sentProposal win rate and pipeline valueVolume without wins is activity, not progress

    The metrics in the left column still have uses. Page views can help explain why inquiries fell. They just don’t belong in the weekly review.


    What Do You Do With All the Other Metrics?

    Keep them, but take them off the main scorecard. Move them into a diagnostic layer that you open only when a core KPI goes outside its normal range.

    Think of it as two tiers.

    Tier 1: the scorecard. Four to seven KPIs, reviewed on a fixed schedule, usually weekly. (Some, such as gross margin, only update meaningfully once the month closes.) Each has a normal range, a named owner, and a place on one page or one screen without scrolling.

    Tier 2: diagnostics. The supporting detail: revenue by customer, overtime by crew, cost by vendor, scrap by workstation, website traffic by source. These live in a separate tab, a saved report, or an export from software you already use. You don’t review them every week. You open them to find out why a Tier 1 number moved.

    Here is how the two tiers work together. Say gross margin is one of your scorecard KPIs and normally runs between 45 and 50 percent. One month it comes in at 39 percent. That is a clear signal, so you open the diagnostics: material costs by vendor, overtime hours, rework on specific jobs. The scorecard tells you that something is wrong. The diagnostic layer tells you where.

    Most Tier 2 data already exists in your accounting, payment, scheduling, and operations systems. The Business Data You Already Have covers where to find it and how to test an export in a spreadsheet.


    Which Four to Seven KPIs Fit Your Business?

    The right KPIs depend on what limits your business: billable time in a service firm, flow through the shop in a manufacturer, food and labor costs in a restaurant. The three scorecards below are starting points. Replace any metric that fails the three-question test in your business.

    Each list includes a cash measure in a form that fits the business model. Whatever you change, keep one.

    Professional Services Firm

    Consulting, accounting, design, engineering, and agency firms sell expert time.

    1. Billable utilization: billable hours as a share of available hours, tracked by role
    2. Project gross margin: project revenue minus direct labor and project expenses, as a share of project revenue
    3. Days sales outstanding (DSO): how long, on average, clients take to pay
    4. Qualified pipeline: value of opportunities likely to close in the next 90 days
    5. Client retention: share of last year’s clients that still buy from you this year

    Job Shop or Light Manufacturer

    Output is limited by the slowest step in the process, so this scorecard watches flow, quality, and delivery.

    1. Queue time: how long work in progress waits between operations, such as between machining and assembly
    2. First-pass yield: share of parts or jobs completed without rework or scrap
    3. On-time, in-full delivery: share of orders shipped complete by the promised date
    4. Quote-to-order rate: share of quotes that become orders
    5. Cash runway: weeks of operating expenses covered by available cash

    Queue time is the one most shops overlook. A part can spend two hours on a machine and several days waiting for the next operation. Adding machine capacity won’t shorten that wait if the delay is downstream.

    Restaurant or Hospitality Business

    Food and labor are the highest costs you can control week to week, and they move quickly.

    1. Prime cost: cost of goods sold plus total labor, as a share of sales
    2. Labor cost as a share of sales, by shift or day of the week
    3. Average check, or spend per guest
    4. Table turns during peak periods
    5. Weekly cash in compared with fixed costs going out

    Prime cost and labor overlap on purpose. Prime cost tells you whether the combined total is under control. Labor by shift tells you where to change the schedule.

    Each list stops at five. That leaves room for one or two metrics specific to your situation, such as a major customer’s order volume or a seasonal inventory position, without going past seven.


    How Do You Cut an Existing Metric List Down?

    Use four steps: list what you track now, sort each metric with the three-question test, set a normal range for the survivors, and move everything else to the diagnostic tier.

    Step 1: List Everything You Currently Track

    Include dashboard widgets, spreadsheet tabs, numbers in your accountant’s monthly packet, and figures you check inside software on your own. Most owners find more than they expected.

    Step 2: Sort Each Metric Into Three Groups

    Apply the Monday, anchor, and response tests, then mark each metric:

    • Scorecard: passes all three tests
    • Diagnostic: helps explain a scorecard metric but fails the Monday test on its own
    • Drop: fails the anchor test and doesn’t help explain anything on the scorecard

    If more than seven metrics pass, rank them by how much cash or capacity is at stake and keep the top seven. Several of the ones that fall off will make good diagnostics.

    Step 3: Set a Normal Range and a Trigger

    For each scorecard KPI, write down its normal range and the point that requires action. Base the range on your own last 12 months rather than an industry average you found online. For example: “Gross margin normally runs 45 to 50 percent. Below 44 percent, the operations manager reviews job costs within a week.”

    Assign each KPI to one person, who explains it when it moves.

    Step 4: Move the Rest to the Diagnostic Tier

    Put diagnostic metrics in a separate tab or saved report, and remove dropped metrics from the weekly view. If someone objects to losing a metric, move it to diagnostics and check whether anyone opens it over the next two months.

    Example: 16 Metrics Down to 5

    This is an illustrative example, not a client case. An eight-person commercial cleaning company tracks 16 metrics in a spreadsheet. After the three-question test, they sort like this:

    ResultMetrics
    Scorecard (5)Weeks of cash on hand · Gross margin by contract · Invoice dollars more than 45 days past due · Labor hours versus bid hours by site · Contracts at risk or cancelled
    Diagnostic (7)Revenue by client · Supply cost by site · Overtime by crew · Re-cleans and complaints by site · Quote win rate · Average contract value · Days from signed quote to first service
    Drop (4)Website visits · Social media followers · Total square feet cleaned · Prospecting emails sent

    Labor hours versus bid hours made the scorecard because a site that consistently takes longer than bid is losing money, and the site supervisor can act on it that week. Overtime by crew stayed in diagnostics: it helps explain a labor problem but doesn’t need weekly attention on its own. Total square feet cleaned was dropped. It grows as the company grows but says nothing about whether the work is profitable.


    Next Step: Put Your KPIs on a Scorecard

    Once you have your four to seven, lay them out so they are quick to review: current value, normal range, prior period, and owner, all on one page. Start in a spreadsheet if that is the tool your team already uses. The important part is the decision and follow-up attached to each number.

  • The Business Data You Already Have (No New Tools)

    Your business probably already generates records in five places: accounting software, payment or POS systems, banking, scheduling tools, and Google Business Profile. Depending on the platform and permissions, those records may reveal unpaid invoices, customer concentration, transaction patterns, cash timing, booked capacity, and local-search demand. You can test many in a spreadsheet without buying analytics software, although not every system provides a clean spreadsheet file or every field required for every metric.

    If you run a small business, you have probably been told that getting value from data starts with new software: a dashboard subscription, a data warehouse, or an integration service. For most businesses with two to 25 employees, that is the wrong starting point.

    The records already exist. Each time you send an invoice, run a card, clear a deposit, book an appointment, or get a call from your Google listing, a system you already use stores a date, an amount, and often a customer or status. The first job is not buying a tool. It is learning what those records contain, how to get them out, and which questions they can honestly answer.


    What Business Data Do I Already Have Without Buying New Tools?

    Your business already generates or controls access to financial, sales, scheduling, and customer-demand records. What you can learn from them depends on the fields, history, permissions, and export options each source provides.

    Business data usually shows up in one of three forms:

    1. Dashboard summaries: The charts and totals on your software's home screen. They are useful for a quick check, but the numbers are already added up, so you cannot see which invoices, days, or customers drove them.
    2. Record-level reports and exports: Files where each row is one transaction, invoice, appointment, or interaction. This is usually the best starting point, because you can sort, filter, and total the rows yourself. They are often downloaded as a CSV (a plain-text file of rows and columns that any spreadsheet opens) or an Excel file.
    3. Portable archives: Backup or transfer formats such as Google Calendar's .ics files. They preserve the records, but they open as raw text in a spreadsheet and need conversion before analysis.

    The table below covers the five sources most small businesses already use.

    The Existing Data Inventory Matrix

    Source Category Example Records Three Questions It May Answer Example Export Path & Format Important Limitation
    Accounting and invoicing Invoices, payments received, customer balances, vendor bills, expenses 1. Who owes us money, and how overdue is it?
    2. How much of our sales come from our largest customers?
    3. Which vendor costs have changed over the past year?
    QuickBooks Online: Reports → Standard reports → open a report (e.g., A/R Aging Summary or Sales by Customer Detail) → Export/Print → Export as CSV or Excel Report availability and customization vary by subscription and interface version.
    Payment processor or POS Transactions, items sold, refunds, fees, timestamps 1. What is our average transaction value by day of the week?
    2. Which hours bring in the most sales?
    3. How much do refunds and processing fees take each month?
    Stripe: Reporting → Financial reports → Balance summary → Download (CSV)
    Square: Reports → select report → export icon (CSV)
    Some Square reports cannot be exported. Repeat-customer analysis requires a stable customer identifier (an ID that stays the same across visits).
    Online banking Deposits, withdrawals, descriptions, balances 1. When does cash actually arrive?
    2. Which charges recur every month?
    3. Do deposits line up with processor payouts?
    Chase Connect (example only): Account Activity → Download Options → CSV, PDF, or Excel Paths, formats, and history limits vary by bank and account. Bank activity shows cash movement, not revenue or profit.
    Scheduling or booking Appointment start and end, creation time, invitee status, service type 1. How far ahead do customers book?
    2. How many hours are booked each week?
    3. Where do cancellations cluster?
    Google Calendar: Settings → Import & export → Export (ZIP file of .ics files) Not spreadsheet-ready, and permissions or an administrator may restrict export. No-show, capacity, and channel analysis require consistently recorded statuses, defined available hours, and a lead-source field.
    Google Business Profile Searches, views, calls, website clicks, direction requests 1. How are people finding us?
    2. Which interactions are rising or falling?
    3. Which periods show stronger local demand?
    Business Profile Manager: select profile(s) → Actions → Insights → select timeframe → Download Report (spreadsheet) Interactions are not confirmed leads, sales, or revenue. Available metrics vary by business.

    Each source describes a different step in the same cycle: people find you, book time, pay, get recorded in your books, and turn into cash in the bank. Because each system measures a different step, evaluate each one on its own terms before expecting them to agree.


    What Can Accounting, Payment, and Bank Records Tell Me?

    Accounting, payment, and bank records show what was invoiced, what was collected, what moved through your accounts, and when those events occurred. They all deal in dollars, but they answer different questions and should not be treated as interchangeable versions of revenue.

    Accounting and Invoicing Records

    Your accounting software is the system of record for what you billed and what you owe. Beyond the profit-and-loss statement, it supports three useful analyses:

    1. Customer concentration: Export Sales by Customer Detail for the last twelve months, total sales by customer, and calculate each customer's share. There is no universal danger threshold. The real question is whether losing your largest one or two accounts would affect payroll or debt payments.
    2. Unpaid invoices and payment timing: The A/R Aging Summary groups open balances by how overdue they are. If invoice dates and payment dates are both recorded reliably, you can also calculate average days to pay. When that number moves from 24 days to 41, cash tightens even while sales look healthy.
    3. Vendor cost changes: Compare the same vendor and expense category across matching periods, such as the first quarter of this year against the first quarter of last year. Before calling it a price increase, check quantity: higher spending on materials or tooling may reflect more jobs or more scrap, not higher prices.

    Limitation: Report availability and customization vary by subscription and interface version. Confirm the report you need exists on your plan before building a routine around it.

    Payment Processor and POS Records

    Payment processors and point-of-sale systems such as Stripe and Square may record each sale with an amount and a timestamp. When those fields are available, these records are a useful source for patterns by day and hour:

    1. Average transaction value by day and hour: This requires record-level amounts and timestamps. In restaurants and other hourly businesses, it shows whether your busiest hours are also your highest-value hours, or only your busiest.
    2. Refund and fee burden: Define the calculation before running it. Fee rate is total processing fees divided by gross charges for the same month. Refund rate is total refunds divided by gross charges for the same month. A changing fee rate may reflect processor pricing, payment method, or transaction mix. A rising refund rate is a reason to investigate products, fulfillment, or service, not proof of a particular cause.
    3. Repeat purchase interval: If checkout captures a stable customer identifier, such as an email address, customer record, or member ID, you can calculate the median number of days between a customer's first and second purchase.

    Limitation: Anonymous cash and guest transactions cannot support repeat-customer analysis. If your checkout does not collect an identifier, do not try to infer return visits from card types or amounts.

    Online Banking Records

    Your bank records the cash that actually posted to your accounts:

    1. Deposit timing: Comparing deposits with processor payout dates shows the lag between a sale and usable cash, including weekend and holiday delays. That helps you time payroll and vendor payments.
    2. Recurring outflows: Sorting withdrawals by description surfaces subscriptions, leases, and recurring fees. Treat the result as a follow-up list: contracts, invoices, or software administration records are needed to confirm whether a charge is still necessary or duplicated.

    Limitation: Bank activity shows cash movement and nothing more. A deposit may be a loan disbursement, a customer deposit, or sales tax you collected. A withdrawal may be a loan payment or an owner draw rather than an expense. Download formats and history limits vary by bank.

    Why These Three Systems Rarely Match

    Your processor's monthly sales, your accounting revenue, and your bank deposits may not agree, and that does not necessarily mean your books are broken:

    • A processor report may show gross charges, refunds, fees, net activity, or payouts, depending on the report selected.
    • An accounting report may show invoiced or recognized revenue, depending on the report, configuration, and accounting method.
    • A bank export shows posted deposits, whose amounts and dates depend on payout settings, fees, refunds, batching, and settlement timing.

    Forcing these numbers to match in one spreadsheet without documented reconciliation rules creates more confusion than insight. For now, let each source answer its own question: accounting shows what was billed and owed, the processor shows how customers paid, and the bank shows when cash arrived.


    What Can Scheduling and Local-Search Records Tell Me?

    Scheduling records may show when work is booked and how far ahead customers reserve; Google Business Profile may show how people find and interact with your business. Both are demand signals, not proof of completed sales.

    Scheduling and Booking Records

    If you use a booking tool or shared calendar, your appointment records may support three analyses:

    • Booking lead time: The time between when a booking was created and when the appointment starts. This requires both fields. If lead time shrinks from three weeks to four days, it may be an early sign of softening demand before revenue reflects it.
    • Booked hours: The total duration of consistently categorized service appointments. This is booked time, not utilization. Utilization requires first defining your available hours, such as staffed hours minus breaks and administrative time.
    • Cancellations and no-shows: These are available only when cancellation and attendance statuses are recorded consistently. Once they are, group them by weekday, service type, or staff member. Analyzing cancellations by marketing channel also requires a lead-source field.

    Limitation: Statuses need to be recorded when they happen. If staff update appointments in a batch at the end of the day, timestamps cluster and distort the analysis. Google Calendar exports only .ics archives, so leave it out of your first spreadsheet test. Many booking tools offer appointment exports; check your tool's help documentation for the current path and format.

    Google Business Profile

    Google Business Profile shows how people find and interact with your listing, without installing any tracking code:

    1. Searches: How often your profile appeared in search results. The Performance view may also list the search terms that surfaced your profile; check whether your downloaded report includes them.
    2. Views: How many times people viewed your profile over the selected period.
    3. Interactions: Counts of calls, website clicks, direction requests, and other actions available for your business type.

    Limitation: A tap on the call button does not prove a conversation happened, and a direction request does not confirm a visit. Compare consistent periods, such as month over month or the same quarter last year, and treat the results as demand trends rather than revenue inputs.


    How Do I Test One Export in a Spreadsheet?

    Choose one business question and one source, download a detailed CSV or Excel report, preserve the untouched file, and test whether its rows, dates, identifiers, and amounts can support the question.

    The most common mistake is trying to build a master dashboard on day one: six months of bank records, four QuickBooks reports, and a Stripe file pasted into one workbook. The result is broken lookups, mismatched dates, and totals that disagree. Start with one source instead.

    This is a manual, periodic process. You download a fresh file weekly or monthly; nothing updates on its own.

    The 30-Minute Single-Source Test

    Use whichever spreadsheet program you already have: Google Sheets, Microsoft Excel, or LibreOffice.

    Step 1: Define One Question (5 Minutes)

    Write down one question with a practical business consequence before opening any software. For example:

    • Invoicing: "Which five customers accounted for the largest share of invoiced sales over the last twelve months?"
    • Payments: "What was our average transaction value on Saturdays compared with Tuesdays last month?"
    • Banking: "How much did we pay in recurring subscriptions over the last 90 days?"

    Name the period and define your terms. For example, does "sales" include refunds and sales tax?

    Step 2: Export and Preserve the Raw File (5 Minutes)

    Use the platform's documented report or export menu, and choose CSV or Excel over PDF when both are available. Then:

    1. Save the file in a dedicated folder, such as Data_Exports/2026-Q3/.
    2. Rename it with the export date, source, and report, such as 2026-09-12_QBO_SalesByCustomerDetail_RAW.csv.
    3. Record the source, report name, filters, date range, and export date in a short note saved beside the file.
    4. Open a copy and save it as a workbook, such as ..._WORKING.xlsx or a Google Sheet. A CSV file cannot store pivot tables or multiple tabs.

    Never edit the raw file. An untouched original lets you retrace your steps if a formula or deletion goes wrong.

    Step 3: Inspect Before Cleaning (10 Minutes)

    Check the working copy against basic tidy data principles, as described by statistician Hadley Wickham: each variable in its own column, each observation in its own row.

    • One kind of record per row: Each row should be one invoice, transaction, or appointment, not a group header or subtotal.
    • One variable per column: Date, customer or ID, amount, and status should each have their own column.
    • Presentation rows: Many exports, including QuickBooks reports, add title rows, blank separator rows, and totals.
    • Duplicates and gaps: Sort by date and look for repeated rows or missing weeks and months.
    • Dates: Confirm the spreadsheet recognizes dates as dates, not text, and note the format used.

    Here is what that difference looks like, using invented sample data.

    As exported:

    A B C D
    Sales by Customer Detail
    January–December 2025
    Customer Date Invoice Amount
    Acme Supply
    01/14/2025 1041 2,400.00
    03/02/2025 1057 1,150.00
    Total for Acme Supply 3,550.00

    Ready for analysis:

    customer invoice_date invoice_number amount
    Acme Supply 2025-01-14 1041 2400.00
    Acme Supply 2025-03-02 1057 1150.00

    Step 4: Clean and Answer the Question (10 Minutes)

    In the working copy:

    1. Delete title, blank, subtotal, and total rows so that row 1 holds only column headers.
    2. Fill down group values, such as the customer name, so every row carries its own customer.
    3. Give each column one unique header and unmerge any merged cells.
    4. Add a new date column in YYYY-MM-DD format and keep the original date column unchanged.
    5. Insert a pivot table with customer in Rows and amount in Values (set to SUM), then sort in descending order. To see each customer's share, show values as a percentage of the grand total.
    6. Check the pivot table's grand total against the report's total. If they differ, find out why before trusting the answer.

    Keep This Test Inside Your Spreadsheet
    Do not paste unredacted customer lists, payroll data, or financial exports into consumer AI chatbots to clean or summarize them. Whether any AI tool is appropriate depends on the account type, its data settings, and your obligations to customers and employees.

    Do Not Combine Sources Yet

    Resist merging this file with exports from other systems. Combining sources requires agreed definitions, matching keys, and documented reconciliation rules, and that work belongs after a source audit. A well-structured single-source spreadsheet can answer a surprising number of small-business questions. For how far that can take you before you need specialist help, see Do You Need a Data Analyst or Better Spreadsheets?

    If one export answers a real question in thirty minutes, you have confirmed that your existing systems hold usable records, with no new software purchase.


    When Are the Records or Existing Tools Not Enough?

    Existing tools are not enough when the required records are missing, inaccessible, too aggregated, inconsistently defined, or too difficult to maintain at the frequency and level of control the decision requires.

    Native exports are a sound, low-risk starting point, but they are not a permanent answer for every business. Watch for these signs:

    1. You cannot get record-level data. The system offers only summaries or PDFs, or an authorized person cannot get access. A common example is an account owned by a former employee or an outside bookkeeper that the company cannot recover.
    2. Required fields are missing. The export lacks the date, status, amount, or stable identifier your question depends on.
    3. History is missing or definitions conflict. The platform keeps only limited history, or "sales" means one thing to the office and another to operations.
    4. Differences between systems cannot be explained. Gaps between processor, accounting, and bank totals cannot be traced to documented timing, fee, refund, or accounting-method rules.
    5. The process depends on one person. The report is late, or it breaks whenever the person who builds it is out.
    6. Control needs outgrow the workflow. Multiple locations, entities, or users edit the same file, or sensitive customer data travels by email attachment.

    There is no universal row count or hours-per-week cutoff. Whether a spreadsheet is still the right tool depends on its formulas, how consistent the sources are, how many people use it, how often it must update, and what happens if it is wrong.

    The Next Step: Audit Your Sources

    If you recognize one or more of these signs, the answer is not to buy a business intelligence subscription right away. First, document what you have: which sources exist, who owns access, how much history each keeps, and which fields are complete. Take the inventory from this article and work through The Small Business Data Audit Checklist.

  • The Small Business Data Audit Checklist

    A small business data audit is not the same thing as a cybersecurity or compliance audit. This audit has a simpler, more practical purpose: identify the business data you already have, find out where it lives, test whether you can use it, and choose the first problem worth fixing.

    You can complete the first pass in an afternoon. By the end, you should have a one-page inventory of your core commercial, financial, operational, production, and quality sources; a usable/fixable/unusable rating for each; one clear next action; and evidence for the rules that may belong in a company-wide data policy. You do not need a data warehouse, a new analytics platform, or a technical team to begin.

    What is a small business data audit?

    A small business data audit is a structured review of the information your company already collects through its everyday systems. It answers four basic questions: What data exists? Where is it stored? Who controls access? Can the records support the decisions you need to make?

    The emphasis here is usability. A security audit asks whether systems and information are adequately protected. A privacy or compliance review asks whether data is collected, retained, and handled according to applicable rules. Those are important disciplines, but they are separate from determining whether last month’s sales, customer, marketing, or operating records are complete enough to analyze.

    Why should a small business audit its data?

    A data audit prevents you from building reports on assumptions. Small businesses often have plenty of data but no reliable path from the original records to a decision. Revenue may differ between sales, accounting, and bank systems. In a production business, output, scrap, rework, downtime, inspection, and maintenance records may all exist while nobody can use them together to identify the current constraint. An agency, former employee, vendor, or single supervisor may control the only account or spreadsheet needed to explain the result.

    Without an inventory, these problems stay hidden until a decision depends on them. Teams then spend hours debating which total is right, manually rebuilding reports, or buying software before they understand the underlying issue.

    The goal is not to make every source perfect. It is to learn which sources are dependable now, which need a bounded repair, and which cannot support the intended reporting.

    What should you prepare before you start?

    Block two to three uninterrupted hours for the first pass. Open a blank spreadsheet (or copy the free Data Audit Sources Template) and create one row for every system or record set you use. Ask the relevant owners to join you: that may include operations, finance, sales, production, quality, maintenance, or a trusted administrator. No single person needs to know every system.

    Create these columns:

    • System or source
    • Business process supported
    • Data owner
    • Administrator or account owner
    • What records it contains
    • Export available
    • History available
    • Reliable date field
    • Reliable customer, job, transaction, work-order, batch, lot, machine, or product identifier
    • Completeness and freshness
    • Rating
    • Failed check
    • Next action

    Do not place passwords, customer records, credentials, or sensitive exports in the inventory. Record what exists and who can access it; keep the underlying data in its approved system.

    Step 1: Start with the decisions you need to make

    Before listing tools, write down the decisions you want your data to support. Examples include how much cash will be available next month, which services or products are most profitable, which marketing sources produce customers, where jobs are delayed, which operation constrains throughput, why scrap or rework is rising, whether planned and actual cycle times differ, and whether corrective actions improve quality.

    This keeps the audit from becoming a software inventory. A system matters because it holds records needed for a decision. If you do not know what decision a source supports, note that uncertainty instead of inventing a purpose.

    Choose one to three priority decisions for this first audit. Then name the five to seven headline numbers you currently use—or wish you could use—to make them. In a production setting, those might include throughput, schedule attainment, first-pass yield, scrap or rework, downtime by reason, work in process, on-time delivery, or a constraint measure. That short list becomes the test for whether your sources are useful.

    Step 2: List where commercial, operational, production, and quality data lives

    Most small businesses can begin with the categories below. Use the ones that apply to your operating model, then add one row for every other source that supports a priority decision:

    • Point of sale, order-management, ecommerce, or booking system
    • Accounting software or finance module
    • CRM, customer-service platform, or shared sales inbox
    • Bank and merchant processor
    • Payroll and timekeeping system
    • Scheduling or workforce-management tool
    • Website, campaign, or ecommerce analytics
    • Spreadsheets
    • Production planning, ERP, MES, machine, or operator logs
    • Quality management, inspection, test, nonconformance, and corrective-action records
    • Maintenance, downtime, and changeover logs
    • Inventory, warehouse, procurement, and supplier-quality records

    Add other systems only when they contain records needed for your priority decisions. This can include project-management software, laboratory or test equipment, supplier portals, paper inspection sheets, operator logs, and industry-specific applications. If the business relies on the record—even if it is informal—it belongs in the inventory.

    At this stage, do not evaluate quality. First, make the list complete. Include the “unofficial” spreadsheet someone updates every Friday and the inbox that functions as a lightweight CRM. If the business relies on it, it belongs in the inventory.

    Step 3: Confirm ownership, access, and exportability

    For each source, identify a named data owner and a named administrator. The data owner understands what the records mean. The administrator can manage access and produce an export. One person may perform both roles, but write down both responsibilities.

    Then answer three questions:

    • Can an authorized employee sign in without relying on an agency, former employee, or personal account?
    • Can that employee export record-level data rather than only view a dashboard or screenshot?
    • Can a second authorized person recover access if the primary administrator is unavailable?

    Open a current export when it is safe to do so. A successful download is better evidence than a remembered feature. You are looking for detailed rows with dates and stable identifiers, not only a monthly total. Record the file format and the person who completed the test.

    If nobody can export the data, mark the source as a priority access issue. Do not request or collect live credentials in the audit worksheet.

    Step 4: Test each source on five usability checks

    Rate every source against the same five checks. Consistent criteria make the result more useful than a general impression that the data is “good” or “messy.”

    Exportability. Can an authorized employee obtain detailed records in a usable format? A screenshot or summary PDF usually cannot support reconciliation or flexible analysis.

    History depth. Does the source cover the period needed for the decision? Twelve months may be enough for a recent trend; seasonality or retention analysis may require more.

    Reliable date field. Does each important record have a date or timestamp that means what you think it means—such as order date, service date, production start or completion, inspection time, failure time, payment date, or lead-created date? Document which date you intend to use.

    Reliable customer, job, transaction, work-order, batch, lot, machine, line, shift, or product identifier. Is there a stable ID that distinguishes one record from another and connects inputs, process events, quality results, and outcomes? Names and free-text descriptions alone are often inconsistent.

    Completeness and freshness. Are expected records present, are there unexplained gaps, and is the data updated quickly enough for the decision?

    Write the failed check in the inventory. “Fixable—date field unclear” is far more actionable than “data quality problem.”

    Step 5: Rate each source as usable, fixable, or unusable

    Use three ratings:

    • Usable: The source can be exported, covers the needed period, and has reliable critical fields that are current enough for the intended reporting.
    • Fixable: A bounded cleanup, access change, definition, or export change can make the source usable.
    • Unusable: The source cannot be exported or lacks critical history or identifiers needed for the intended analysis or reconciliation.

    The rating depends on the decision. A scheduling export without customer IDs may still be usable for staffing by hour but unusable for customer-level profitability. State the intended use beside the rating so nobody treats it as universal.

    For every fixable source, write one concrete repair and an owner. Examples include moving administrator access to a company-controlled account, documenting which date field governs a metric, standardizing campaign names, recovering older exports, or adding a stable job ID.

    Do not spend the afternoon cleaning every source. The audit identifies work; it does not need to complete all of it.

    Step 6: Check whether two systems agree

    Choose one important number that appears in at least two systems. Monthly revenue is a common commercial example; completed units, scrap quantity, downtime, yield, or on-time delivery may be more useful in production. Compare the same period, products, locations, lines, and status rules using written definitions.

    Differences do not automatically mean one system is wrong. A point-of-sale system may report orders when they are placed, accounting software may recognize revenue according to a different rule, and bank deposits may be reduced by fees or shifted by settlement timing.

    When totals differ, test these common causes:

    • Different date fields or time zones
    • Refunds, cancellations, discounts, or taxes treated differently
    • Cash versus accrual timing
    • Processing fees or grouped deposits
    • Missing locations, channels, products, or manual entries
    • Duplicate or late records
    • Different definitions of the metric

    Record the difference, the explanation if known, and the source that should govern the specific metric. If you cannot explain a material difference, mark reconciliation as the next action instead of averaging the totals or choosing the most convenient one.

    Step 7: Choose the single issue to fix first

    Your finished inventory may contain several red flags. Resist the urge to start all of them. Choose the issue that sits furthest upstream and blocks the most important decision.

    A useful priority order is:

    • Agree on the metric definition.
    • Assign its source of truth.
    • Secure company-controlled access and record-level exports.
    • Repair missing dates, identifiers, or coverage.
    • Reconcile conflicting totals.
    • Build or improve the report.
    • Set a recurring review and assign actions.

    This order prevents a polished dashboard from hiding a weak foundation. If you do not agree on what revenue includes, dashboard formatting is not the first problem.

    Write the first fix as a small outcome that can be verified. “Improve data quality” is too vague. “Export twelve complete months of order-level records with order date and order ID by Friday” is specific enough to own and check.

    What if your company already collects production and quality data?

    If you already collect production and quality data, the audit should focus less on finding more data and more on connecting existing records to operating decisions. Many manufacturers have years of inspection results, downtime logs, production counts, scrap records, corrective actions, and process documentation. The problem is often that those records were created for different purposes, use different identifiers, or are reviewed without a clear decision rule.

    Depending on region and customer requirements, this work may already sit inside a formal quality-management initiative. In many European and Middle Eastern businesses, that may be an active ISO 9001 project; in the United States, similar process-documentation and quality-improvement work may exist without the ISO label. Those documented processes and retained records are valuable inputs, but documented collection does not automatically make the data decision-ready. The audit adds an analytical layer by asking: Which decision should this record change? What threshold or pattern triggers action? Who reviews it, how often, and what happened after the last review?

    Useful production questions include:

    • Where does work wait longest between operations?
    • Which line, machine, tool, supplier, material, product, or shift contributes most to lost throughput?
    • How do planned and actual cycle times differ?
    • Which downtime and changeover reasons consume the most constraint time?
    • Where do first-pass yield, scrap, rework, defects, or nonconformities change?
    • Can corrective actions be linked to a later measurable result?
    • Do production, quality, maintenance, and planning systems agree on the same work order, batch, lot, quantity, and status?

    Do not begin with a plant-wide average. Constraints are usually local, and averages can hide the operation that governs the system’s output. Start with the flow of one important product family or value stream, map the records at each step, and identify the decision that should follow when performance crosses an agreed threshold.

    A manufacturing example: finding the real production constraint

    Imagine a midsize manufacturer that wants to increase output without adding another shift. It already records work orders and due dates in its planning system, machine cycle times and downtime codes on the floor, inspections and nonconformities in its quality process, scrap and rework in spreadsheets, and maintenance events in a separate application.

    The audit shows that most of the data is exportable, but it is difficult to connect. Machine records use equipment IDs, quality records use batch numbers, and rework spreadsheets rely on product descriptions. Downtime reasons are entered inconsistently, while some changeovers are recorded as planned stops and others as equipment downtime. The business has substantial documentation and many measurements, but no dependable thread from work order to process event to quality outcome.

    When the team aligns work orders, batches, machines, shifts, and completion timestamps, it finds that the apparent capacity problem is concentrated around one operation. Average plant utilization had hidden the queue. Inconsistent changeover and downtime coding made the constraint look like several unrelated issues.

    The first fix is not a new dashboard or another sensor. It is a shared identifier and reason-code rule, followed by a weekly constraint review that compares planned versus actual cycle time, queue time, downtime, scrap, and rework for the constrained operation. That is a successful first audit: the business connects existing records to a decision and can verify whether the corrective action improves flow.

    Keep privacy and security in scope—but keep the boundary clear

    During the audit, you may discover personal information, weak access controls, or unclear retention practices. Record the issue and route it to the appropriate owner. Do not copy sensitive records into an informal worksheet, email exports unnecessarily, or request passwords from colleagues.

    Privacy, security, retention, and legal obligations vary by business, location, industry, and data type. This checklist is not legal, privacy, cybersecurity, or assurance advice. If the audit reveals a material concern in those areas, seek qualified guidance rather than expanding this usability review into a do-it-yourself compliance assessment.

    Your completed SMB data audit checklist

    Before you finish, confirm that you can answer every item below:

    • We listed every system that supports a priority business decision.
    • We identified the records each source contains.
    • We named a data owner and an administrator for each critical source.
    • An authorized employee tested record-level export access.
    • We recorded how much history is available.
    • We identified the date field used for reporting.
    • We identified stable customer, job, transaction, work-order, batch, lot, machine, line, shift, or product IDs where needed.
    • We checked completeness and freshness.
    • We rated each source usable, fixable, or unusable for a stated purpose.
    • We compared one important number across two systems.
    • We documented the reason for any known difference.
    • We chose one upstream fix, one owner, and one verification step.
    • We recorded recurring rules that should become company policy.
    • We set a review cadence and event-based triggers for future audits.

    If several answers are “not sure,” that is a useful result. Verification should come before new analytics work.

    What should you do after the audit?

    Keep the inventory as a living one-page reference. Update it when you add a system, change an administrator, revise a metric definition, or discover a gap. Use repeated findings to distinguish one-time cleanup from rules the whole company should follow.

    Turn the audit into a company-wide data policy

    A completed audit gives you the evidence to create or improve a company-wide data policy. The policy turns lessons from one review into repeatable rules for how the business defines, owns, collects, accesses, checks, uses, shares, corrects, and retires important data.

    The policy does not need to be long. It should define:

    • The business decisions and processes that critical data must support
    • The owner and source of truth for each headline metric and critical data set
    • Required definitions, identifiers, naming rules, and quality checks
    • Who receives administrator access and how the company retains control when people or vendors change
    • Where sensitive data may be stored, exported, and shared
    • How errors, missing records, conflicting totals, quality exceptions, and access failures are reported and resolved
    • How reports are reviewed, how actions are assigned, and how results are verified
    • When retention, deletion, privacy, security, contractual, or regulatory questions require qualified guidance
    • Who owns the policy, approves changes, and confirms that teams follow it

    The policy should also establish when the next audit happens. Set a regular cadence appropriate to how quickly the business and its systems change, then add event-based triggers. A new ERP, CRM, MES, site, production line, product family, acquisition, vendor transition, ownership change, recurring reconciliation problem, or serious quality issue can justify an earlier review.

    Treat the policy as an operating document, not a file created once and forgotten. Each audit should test whether the rules still match reality, record exceptions, and update the policy when the business learns something new.

    Then test the broader analytics system around the data. The free SMB Analytics Health Assessment checks four connected areas: metrics, data, reporting, and ownership. It takes about five minutes and gives you an immediate score, your primary barrier, and a first recommendation before asking for contact details.

    Take the free SMB Analytics Health Assessment

    The purpose of the audit is not to prove that your data is perfect. It is to replace uncertainty with a usable map: what exists, what can be trusted, what needs repair, and what to do first.