How to build a weekly management dashboard
Build a weekly management dashboard from source exports, reconcile current and prior KPIs, and give each exception a clear action and owner.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What a weekly management dashboard is
A weekly management dashboard compares a business unit's results for the latest closed week with the prior closed week and any approved targets. It shows which changes need attention, which metrics still need verification, and who should take the next action. For a founder preparing a weekly business review, the result is a table the leadership team can use to make decisions and trace each reported value to its source.
A KPI report tracks key performance indicators, the measures that show how an operation is doing against its goals. Its reliability depends on whether the periods, populations, and definitions line up. A fresh export can still leave out a day of transactions. A higher conversion rate can reflect a change in who qualified for the measure. Reconcile the inputs before explaining what moved, then carry any unresolved gap into the review with an owner and a due date.
What it does for the business
- Use review time for decisionsA short exception list helps the team spend the meeting on issues that need a response. Lead with the action or decision due this week and leave the full metric table available for anyone who needs the detail.
- Direct resources to a specific problemA measured gap gives you a place to investigate before moving staff or spending more. If support backlog exceeds its agreed limit, for example, the owner can check which queue contributed to the increase and decide where additional coverage would help.
- Close the gaps in weekly reportingWhen the table identifies exactly which export, cutoff, or definition is missing, you can assign the repair to the person who controls it. That gives the next review a specific improvement to check.
- Follow through on management commitmentsCapture the owner, review date, and evidence you expect to see next week. You can then use the following review to decide whether to continue an action, change it, or close it.
Weekly management dashboard, step by step
Set the reporting week and check source coverage
The reporting period follows the date of the underlying event.
What to do
- Write down the business unit, the start and end of each closed week, the timezone, and the reporting cutoff. Confirm which event date puts a row in a week, such as the completion date for completed orders.
- List the requested metrics and the owner, export date, and approved target version for each. Check which dates and units the source exports actually cover and flag any gaps, including days with records still arriving.
- Keep the original exports and their row identifiers. Remove duplicate rows only when a documented transaction key establishes that they represent the same item. Link refunds and reversals to the original event and apply the documented sign.
- Ask the source owner to confirm any missing file or reporting window. Mark the metric unavailable or partial until you have enough evidence to support a full-week value.
Why
A file generated on Monday might contain events only through Saturday. An event just after midnight can also land in a different week when systems use different timezones. Keeping export time, event time, and verified coverage visible lets a reviewer tell when an apparent weekly change comes from the reporting window.
Reconcile metric definitions before comparing weeks
A weekly comparison is meaningful when both values measure the same thing.
What to do
- For each metric, record its source fields, filters, scope, period, unit, and currency. For each rate, record the numerator, the count of qualifying outcomes, and the denominator, the population eligible for those outcomes.
- Check whether current and prior values cover the same type of population. For example, confirm that both conversion rates include the same channels and use the same rule for when a visitor qualifies.
- Confirm that the target applies to the same period and uses the same calculation as the actual. Keep recognized revenue, which follows the accounting recognition rules, separate from signed bookings and cash receipts.
- Document any definition or coverage change and its effect on comparability. If the underlying rows support a consistent recalculation, record the revised basis. If a rate has a missing or zero denominator, mark it unavailable and give the reason.
Why
A change to eligibility or scope can move a metric even when the underlying operation stays steady. A written definition also shows what a team can combine. Rate totals need the counts for each eligible group because group sizes determine how much each rate contributes to the combined result.
Calculate the movement and identify exceptions
The threshold and direction of a metric determine which gap needs attention.
What to do
- For counts and amounts, subtract the prior value from the current value to get the absolute change. For relative percent change, divide that difference by the absolute value of the prior result and multiply by 100. With a zero prior value, show the absolute change and mark relative change unavailable.
- For a rate, sum the qualifying numerators and denominators separately, then divide the totals. Express the difference between the two weekly rates in percentage points by subtracting the prior rate from the current rate.
- Calculate target variance by subtracting the approved target from the actual in the original units. When the target is nonzero and the review calls for a relative variance, divide the gap by the absolute target and express it as a percent. Use the agreed direction and threshold to flag exceptions.
- Keep the source rows, operands, and unrounded results with the calculation. Recompute from the source and reconcile totals and coverage before applying display rounding.
Why
A rounded display can make a value appear to meet a threshold that it missed. Use the unrounded result when assigning status. Keep the direction of the gap visible so the reader can interpret a variance without guessing whether an increase is favorable.
Write the management pack around the decisions
An exception earns meeting time when someone can investigate it or act on it.
What to do
- Summarize the changes that affect a decision this week. Include current and prior actuals, the approved target where available, the gap, and the dates. Put stale, incomplete, or incomparable metrics in a visible exception list.
- Connect each explanation to its evidence. If cancellations and support demand rise in the same week, record both observations and assign a check of whether the affected accounts overlap.
- Name the person responsible for the next action and what they need to bring back. If the owner needs a leadership decision, identify who must make it and when it is needed.
- Label any forecast separately from actuals and include the approved assumptions that drive it. Keep the weekly table focused on the closed periods and send readers to the forecast when they need to discuss expected results.
Why
An observed gap, an explanation, and a proposed response each need their own support. Showing the evidence next to the finding allows the team to act on what it knows and assign a precise check where the cause is still uncertain.
Deliver the weekly table and review the handoff
A reader should be able to trace every decision-worthy figure without reconstructing the report.
What to do
- Lead with the finding that needs a decision. State the business unit, the dates of both weeks, and any coverage limitations in the summary.
- Give readers the metric, current and prior actuals, target, change or gap, status, owner action, and evidence. Point to the relevant source rows and keep detailed calculations available for review.
- Have a second reader trace decision-worthy values to the source. Check that dates, units, and rounding match and that each action is clearly proposed or complete. Record any unresolved issue with a named owner and review date.
Why
The review table needs to be brief enough to scan while the supporting records answer follow-up questions. A concise handoff also gives an absent stakeholder the dates, evidence, and outstanding decisions they need to pick up the work.
Common mistakes
- Treating the export date as proof of coverageConfirm the event dates and completeness of the source before using it for a closed week.
- Filling missing values with zeroUse zero only when the source supports it and label unavailable figures with the specific reason.
- Averaging rates across unequal groupsCombine the qualifying counts and eligible populations before calculating the overall rate.
- Comparing against the wrong targetCheck the target version and confirm it applies to the metric's unit, scope, and period.
- Reporting a suspected cause as settledRecord the known movement and assign someone to verify the proposed explanation.
What a good result looks like
- Both weeks have explicit boundaries, a timezone, and a reporting cutoff.
- Each visible actual ties to a definition, source rows, and a reproducible calculation.
- Comparisons use matching units and populations, with missing or stale values flagged.
- Target gaps use the agreed direction and threshold, with forecast figures labeled separately.
- Each exception that needs action has a named owner, a clear request, and a review date.
And then what? Using the result
- Put the decision-worthy exceptions on the weekly business review agenda and give attendees the table before the meeting.
- Ask each owner to confirm the action, due date, and evidence they will bring to the next review.
- Assign missing exports and definition questions to the owners who can resolve them before the next cutoff.
- Record any decision to change a target or definition and date the approved version before using it in a comparison.
- Start the next meeting by checking the previous actions and deciding which should stay open.
When to run it
- Before a recurring leadership reviewUse it when the leadership team needs a shared view of the latest results and a short list of decisions or follow-ups.
- When totals differ across teamsReconcile filters, periods, and metric definitions before deciding which values can guide the review. Give each unresolved mismatch a source owner.
- After a reporting source changesCheck the new export against the previous one for coverage, identifiers, and field definitions. Flag any break in comparability before interpreting the change.
- When a metric repeatedly crosses its thresholdBring forward the earlier owner actions and review whether they were completed. Use the current evidence to decide which follow-up belongs on the agenda.
Questions people ask
How do you build a weekly management dashboard?
Define two closed weeks, reconcile the metric definitions and source coverage, calculate comparable results, and assign actions for the exceptions. Include a source reference for each figure and put the most urgent decision first.
Which KPIs belong in a weekly management dashboard?
Choose KPIs the team uses to make weekly decisions and can calculate consistently from available sources. A measure earns its place when a meaningful change has a clear owner who can investigate it or act.
How do you compare weekly KPIs across teams?
Compare the values only when teams use matching definitions, periods, populations, and units. If you combine rates, sum their underlying counts first and check for overlapping populations.
What should you do when a weekly KPI is missing?
Mark the KPI unavailable or partial, explain exactly what is missing, and name the person who can supply or verify it. Keep the data gap visible as an exception if it affects a decision.
How do you show a change in a conversion rate?
Show the difference between the current and prior rates in percentage points. Calculate each rate from qualifying outcomes divided by the eligible population for that week, using a consistent eligibility rule.
Can 10folds build the dashboard from spreadsheets?
Yes, 10folds uses supplied exports and metric definitions to compare two closed weeks for one business unit. You can also supply prior-week results and approved targets so the app can verify applicable comparisons and gaps.
More jobs in Ops
Build a weekly management dashboard, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac