Blog · Board and management reporting
Productivity dashboards compare completed output with labor hours while keeping quality and workload mix visible. Work a shared-services example, reconcile the hours and output, and see why a raw items-per-hour ranking can mislead.
Productivity dashboards compare output per labor hour across teams and periods while showing the work mix and quality behind the rate. The basic calculation is simple; deciding what counts as output and which hours belong underneath it takes more care. A useful comparison directs attention to the process conditions the manager can change.
Start with a work export containing an item ID, completion date, assigned team, work type, and quality result. Add the corresponding time export with period, team, hours, and time category. Preserve the original rows so the completed count and hours can be checked independently.
Define one completed unit. A finished invoice, a processed order line, and a resolved customer case are different outputs. Do not combine them into a common item count merely because the export has one status column. Likewise, an item passed between teams is not a new unit of company output at every handoff.
Output per labor hour = Completed units / Matching labor hours
Choose the denominator to fit the question. Productive task hours support a process comparison. All worked hours include time spent on meetings or training. Paid hours can also include paid leave and help describe the output supported by the payroll commitment. These rates can all be useful when labeled clearly; they are not interchangeable.
For the broader team plan, pair the rate with goals and the remaining queue using team dashboards. A productivity rate does not by itself show whether the team has enough capacity to complete the arriving work.
An illustrative US distributor processes supplier invoices through North and South teams. The following complete weekly export distinguishes routine invoices from exception invoices. Each invoice is counted once at completion; a later correction changes its quality outcome rather than creating another completed invoice.
| Team | Routine completed | Exceptions completed | Productive hours | Training hours | Paid leave hours | Paid hours | Invoices needing correction |
|---|---|---|---|---|---|---|---|
| North | 360 | 40 | 200 | 20 | 20 | 240 | 8 |
| South | 200 | 100 | 200 | 20 | 20 | 240 | 9 |
| Total | 560 | 140 | 400 | 40 | 40 | 480 | 17 |
The paid-hours total reconciles: 400 productive + 40 training + 40 paid leave = 480. There are no other time categories in this illustrative week. In a real export, retain any additional categories rather than forcing unexplained hours into productive time.
Completed output is 560 + 140 = 700 invoices. Divide the team outputs by the same type of hours:
| Team | Completed invoices | Invoices per productive hour | Invoices per paid hour |
|---|---|---|---|
| North | 400 | 2.00 | 1.67 |
| South | 300 | 1.50 | 1.25 |
| Total | 700 | 1.75 | 1.46 |
North's productive-hour rate is 400 / 200 = 2.00. South's is 300 / 200 = 1.50. The department rate is 700 / 400 = 1.75; the paid-hour rate is 700 / 480 = 1.46. Rates display two decimal places and are calculated from unrounded inputs.
The raw figures favor North. They do not yet show that North performs the work more effectively, because South has more exception invoices. The dashboard needs the work-type columns beside the rate, not hidden in another export.
The operations owner has approved illustrative workload standards of 10 minutes for a routine invoice and 30 minutes for an exception. Those are reference weights, not measured actual completion times. Their ratio makes an exception worth 30 / 10 = 3 routine-equivalent units.
Equivalent units = Routine invoices + (Exception invoices × 3)
Mix-adjusted output per hour = Equivalent units / Productive hours
| Team | Routine units | Exception units × 3 | Equivalent units | Equivalent units per productive hour |
|---|---|---|---|---|
| North | 360 | 120 | 480 | 2.40 |
| South | 200 | 300 | 500 | 2.50 |
| Total | 560 | 420 | 980 | 2.45 |
North is (360 + 40 × 3) / 200 = 2.40. South is (200 + 100 × 3) / 200 = 2.50. The department is 980 / 400 = 2.45. The adjusted comparison reverses the raw ranking because it recognizes the assigned exception workload.
This is a management-defined workload measure, not a claim that every exception takes exactly the same effort. Reassess the weights against observed work and keep the approval date. Use versioned metric definitions so a change in the weight does not masquerade as a change in productivity.
OPM's guidance on performance standards treats quality, quantity, timeliness, and cost-effectiveness as distinct measurement choices. That distinction matters here: completing more invoices is not enough if more need correction.
For this example, all completed invoices have received a quality outcome by the review cutoff. First-pass accepted invoices are completions less those needing correction:
| Team | Completed | Needing correction | First-pass accepted | First-pass acceptance |
|---|---|---|---|---|
| North | 400 | 8 | 392 | 98.0% |
| South | 300 | 9 | 291 | 97.0% |
| Total | 700 | 17 | 683 | 97.6% |
Department acceptance is 683 / 700 = 97.6%, rounded to one decimal place. Accepted output per productive hour is 683 / 400 = 1.71, rounded to two decimal places. This adds a quality check without pretending that the complex-work adjustment proves equivalent customer outcomes.
Investigate correction reasons before setting a higher rate target. A missing supplier reference, unfamiliar invoice type, or repeated processing error calls for a different response. NIST's management-by-fact principle supports measuring and analyzing performance; the practical application is to test an explanation against the underlying rows before treating it as established.
Count distinct completed invoice IDs and reconcile the count to the completion register. Check for duplicate rows introduced by multiple time entries or quality reviews. Those detail records cannot each become another invoice in the numerator.
Reconcile paid hours to the source time report, then reconcile productive and other categories back to paid hours. Missing hours remain a data issue, not zero effort. Reconcile the accepted and correction counts to the same completed cohort, and mark pending quality outcomes separately if they exist.
The control-total and identity checks serve different purposes: the source export establishes completeness, while the arithmetic relationships establish internal consistency. Both must pass before a team comparison is used in a staffing discussion.
Bring a sample of your own completion register, time export, and approved workload weights; Covirage maps the columns, and its tools compute and check the output, hours, mix, and quality comparisons. The external AI model explains the results with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring your file.
See capacity planning for the related staffing and workload decisions.
Divide completed output by the matching labor hours for the same period and team. State whether the hours are productive work hours, all worked hours, or paid hours. Sum output and hours before calculating a combined rate across teams.
Use a target grounded in your own process, required quality, and expected work mix. A rate from routine work is a poor target for a team handling complex exceptions. Review the assumptions with the people who perform and own the work.
No. Productivity compares output with an input such as labor hours. Utilization compares used capacity with available capacity under a stated definition. A team can use its available hours fully while producing little accepted output because of rework or blocked tasks.