Sign in

Blog · Board and management reporting

Tactical dashboard: team targets and near-term actions

A tactical dashboard compares departmental commitments with recent results and identifies the next action. See a worked review of output, spending and recovery capacity, with checks that connect the figures to the source files.

The short answerA tactical dashboard compares departmental performance with weekly or monthly commitments and makes the next management action explicit. It combines targets, actual results, gaps, spending and accountable owners. Unlike a process-flow view or a long-term strategy review, its main purpose is to show whether a team can deliver its near-term plan and what needs to change.

A tactical dashboard compares a team's recent results with near-term targets and shows what the manager will do about the gap. It belongs in a weekly or monthly plan review. The useful output is a decision with an owner, supported by figures that reconcile to the team's exports.

What makes a dashboard tactical

The time horizon and the decision matter more than the chart type. An operational dashboard helps a manager understand current process flow. A strategy dashboard tracks longer-term outcomes. The tactical view connects the department's current commitments to the actions available before the next review.

It asks whether the team delivered its agreed work, whether spending followed the plan, and whether the next period has enough capacity. A measure belongs here when a manager can name the action a material gap would trigger.

There is a broader performance-management principle behind that choice. Performance.gov describes communicating goals, how they will be accomplished and why they matter. Its public-sector framework is not a company dashboard specification, but the connection between a goal and its execution is useful for a business review.

Start with commitments and matching exports

Use the approved plan, rather than a target revised after the result became known. Select the period and the completion rule before comparing teams. A completed quote, supplier review or customer onboarding case must mean the same thing in the target and the actual export.

File Fields to retain Purpose
Approved departmental plan Period, team, measure, target, unit, owner, plan version Establishes the commitment
Work register Work ID, team, completion date, completion status, acceptance status Counts qualifying output
Cost export Period, team, expense category, amount Supplies actual spending
Capacity plan Next period, team, work type, available capacity, committed new work Tests whether recovery is feasible

Keep a distinct identifier for each item of work. Decide how reopened items and rejected completions are treated. Record any approved changes to the target separately so the reviewer can distinguish an original commitment from a later adjustment.

The department manager owns the output definition. Finance owns the cost boundary and checks that allocations do not count the same expense twice. The meeting owner ensures every exception ends with a named action.

A worked review across departments

An illustrative US business reviews a completed management cycle. The sales support team counts accepted quotes, procurement counts completed supplier reviews, and customer onboarding counts accepted cases. These units are different, so there is no company output total.

Output gap = Actual completed output − Target output

Target attainment = Actual completed output / Target output × 100

Team and measure Target Actual Output gap Target attainment
Sales support: accepted quotes 120 108 −12 90.0%
Procurement: supplier reviews 100 95 −5 95.0%
Customer onboarding: accepted cases 200 190 −10 95.0%

Sales support delivered 108 / 120 × 100 = 90.0% of its commitment and has 120 − 108 = 12 quotes left from the plan. Procurement is short 100 − 95 = 5 reviews. Onboarding is short 200 − 190 = 10 cases.

These differences identify work to investigate, not the reason it was missed. The owner must distinguish demand changes, unavailable information, capacity constraints and quality rejections before choosing an action. A team dashboard can provide the underlying team detail without replacing this plan review.

Read spending beside completed work

The financial export covers the same teams and period. All values are USD. The completion counts come directly from the preceding table.

Team Planned cost (USD) Actual cost (USD) Actual less plan (USD) Planned cost / target unit (USD) Actual cost / completed unit (USD)
Sales support 24,000 23,760 −240 200.00 220.00
Procurement 15,000 15,200 200 150.00 160.00
Customer onboarding 30,000 28,500 −1,500 150.00 150.00
Total spending 69,000 67,460 −1,540 — —

Sales support spent 23,760 − 24,000 = −$240 against plan. Yet its period cost per completed quote was 23,760 / 108 = $220, compared with planned cost per target quote of 24,000 / 120 = $200. Lower spending did not mean the team delivered the plan at a lower average cost.

Procurement's actual average was 15,200 / 95 = $160 per review, against 15,000 / 100 = $150 planned. Onboarding's average stayed at 28,500 / 190 = $150, equal to 30,000 / 200 = $150 planned. Ratios are calculated before rounding and displayed to cents.

These are period cost ratios, not precise costs of individual work items. Fixed staffing costs and work still in progress affect them. Do not assume an output shortfall creates an immediately recoverable saving. The variance dashboard covers the wider analysis of plan differences.

Test the next action against available capacity

Suppose the uncompleted work remains required and carries into the following week. Managers supply the new commitments and available capacity below, using each team's own unit. Capacity means accepted completions achievable with the resources already assigned.

Required completions = Carried work + New committed work

Capacity shortfall = Required completions − Available capacity

Team Carried work New committed work Required completions Available capacity Capacity shortfall
Sales support 12 30 42 36 6
Procurement 5 25 30 30 0
Customer onboarding 10 50 60 55 5

Sales support needs 12 + 30 = 42 completions, leaving 42 − 36 = 6 beyond available capacity. Procurement's 5 + 25 = 30 fits its capacity of 30. Onboarding needs 10 + 50 = 60 against capacity of 55, a shortfall of 5.

The sales support manager must negotiate priorities or obtain approved capacity; asking everyone to catch up does not close that arithmetic. Procurement should confirm dependencies are ready. The onboarding owner should agree which commitments move if capacity cannot change. Record the decision and the next review date beside each exception.

NIST's Baldrige framework describes performance management in terms of accomplishing the mission and improving results. The tactical application is concrete: a target gap should lead to an owned choice about the work.

Reconcile before presenting the review

Recount accepted completions from distinct work IDs and match the period cutoff to the plan. The carry column must equal the unmet commitment that managers confirm is still required. Canceled demand should have an explicit adjustment rather than silently disappearing.

The spending check is 23,760 + 15,200 + 28,500 = $67,460. Planned spending is 24,000 + 15,000 + 30,000 = $69,000. The variances reconcile: −240 + 200 − 1,500 = −$1,540, matching 67,460 − 69,000.

Refresh capacity estimates when staffing or dependencies change. Retain the estimate used in the meeting so the next review can explain what changed after the decision.

Where it goes wrong

  • Partial actuals against a full-period target. Use a completed period or a clearly labeled target for the same elapsed period.
  • Different units added together. Quotes, reviews and cases have separate meaning. Add compatible expenses, not unrelated output counts.
  • Revised targets replacing the original plan. Preserve the approved baseline and show changes explicitly.
  • Lower spending called success by itself. Read expense against accepted output, quality and unfinished work.
  • Actions without capacity checks. Carrying missed work forward creates commitments that must fit the next period's available resources.

Review your team plan in Covirage

Bring the approved plan, completed-work register and matching cost export as a file or Google Sheet. Covirage maps the columns; its tools compute and check the gaps and ratios, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.

See Covirage for self-service analytics for working from your own business files.

Questions people ask

How often should a tactical dashboard be reviewed?

Review it at the pace managers can meaningfully change staffing, priorities or spending. Weekly reviews suit short delivery commitments; monthly reviews suit departmental plans. Keep the reporting cutoff consistent and distinguish a completed period from a partial period before comparing results.

What is the difference between tactical and operational dashboards?

A tactical dashboard focuses on delivering a departmental plan over the next weeks or months. An operational dashboard focuses on the current process, such as queues or orders moving through work. They can use the same source records while answering different management questions.

Which measures should a tactical dashboard contain?

Use agreed output targets, actual completed work, gaps, relevant costs, available capacity and an action owner. Add quality or completion rules so volume cannot improve by counting unfinished work. Choose measures that managers can influence during the next review period.