Employee performance dashboard: output and capacity

An employee performance dashboard compares agreed output, workload, and quality measures so a manager can see where a team needs support or capacity. Start with completed work and hours from operating exports, then show targets and quality checks beside the totals. Read the measures together before deciding what caused a shortfall.

Define the job before choosing the measures

For a support team, completed requests can be a useful output. For an accounts payable team, the unit might be invoices accepted after checking. A request and an invoice are different units, so their hourly rates should not appear in a shared ranking.

The US Office of Personnel Management's guidance on performance standards separates quantity, quality, timeliness, and cost effectiveness. It also calls for standards that are measurable, realistic, and clearly recorded. Although the guidance addresses federal employment, that separation is useful for a business operating review: more volume is not sufficient evidence of better work.

Write down which work counts, which hours belong in the denominator, how quality is observed, and who agreed to the target. The wider performance dashboard covers the business results around this team view. Keep employee-level judgments out of a calculated composite score that hides the underlying measures.

A worked example: a US distributor's support team

Consider three support groups handling the same standard request category for a US industrial distributor. The review covers the week ending October 16, 2026. Managers agreed volume targets before the week began. The example quality and timeliness thresholds are both 95.0%, chosen internally for this work.

The completion export provides request identifier, group, completion date, agreed due date, and any subsequent reopen date. A separate team hours export supplies actual worked hours, excluding paid leave. Include time spent on meetings, coaching, and other work in the chosen hours definition, and apply it consistently.

To give quality time to emerge, the report checks each completed request for reopening during the following seven days. Quality is therefore finalized on October 23, 2026. Each reopened request is counted once, even if it reopens repeatedly. On-time completions are requests completed by their agreed due dates.

These are group operating results, not individual activity logs. The review needs completed work and agreed hours; it does not need keystrokes, screen recordings, or time spent moving a mouse.

Calculate output and quality from the same rows

Use these definitions for this example:

Output per hour = Completed requests / Worked hours

Volume attainment = Completed requests / Agreed volume target

No-reopen share = (Completed requests - Reopened requests) / Completed requests

On-time share = On-time completions / Completed requests

The no-reopen share is a defined quality proxy, not proof that every unreopened request was correct. Separate audits or customer feedback may find issues that never generate a reopen record.

For North, output is 90 / 120 = 0.75 requests per worked hour. Its no-reopen share is (90 - 12) / 90 = 86.7%. South's no-reopen share is (85 - 3) / 85 = 96.5%, even though its completed volume remains below the agreed target.

The total no-reopen share uses (243 - 17) / 243 = 93.0%. The total hourly rate is 243 / 300 = 0.81. Divide summed numerators by summed denominators; do not average the displayed group percentages. Percentages are rounded to one decimal place and hourly rates to two; all calculations use unrounded inputs.

Change one input: additional hours without more output

Suppose South's worked hours change from 100 to 120, with completed work, target, and quality counts unchanged. This is a sensitivity example: only the hours input changes.

Output and quality have not changed, but the hourly rate has fallen. Ask what the additional hours covered: training, helping another queue, unusually difficult cases, or waiting for an upstream decision. The number identifies a question; the operating context supplies the explanation.

Keep the agreed target visible during that discussion. Changing the target after seeing the result makes the comparison hard to trust. If future assignments change, agree a revised basis for the next period and document the change.

Reconcile before discussing performance

Count distinct request identifiers in the completion export and confirm the total is 243. The group counts must add to that same total, and each request must belong to one group for this measure. A transfer history can otherwise place the same completion in several groups.

The 17 reopened requests must all belong to that completion cohort, within the stated observation window. The 230 on-time records must also be a subset of the same 243 completions. Tie the 300 worked hours to the approved hours report and the 260 target to the agreed planning file.

Investigate missing quality outcomes as missing, rather than marking them successful. Keep unfinished requests and their age in a separate workload view. A completion dashboard can appear healthy while difficult work remains open.

Use the review to choose support

North warrants a conversation about both rework and timeliness. South shows stronger quality on this definition but remains short of its volume target. West warrants a look at due-date handling. None of those observations establishes an individual's motivation or ability.

OPM describes development as increasing capacity through training, assignments, and better work processes. For this team, the practical next step could be coaching, reassignment, or removing a recurring handoff delay, followed by another review using the same definitions.

Keep employee turnover, employee satisfaction, and the performance appraisal dashboard as distinct views. Staffing changes, survey responses, and formal appraisal each answer questions that the output table cannot resolve.

Where it goes wrong

• Unequal work treated as equal. Different case complexity or mentoring duties can change output without changing how well people work.
• Paid hours substituted for worked hours. Leave and inconsistent time categories move the denominator. State the chosen basis and reconcile it.
• Quality measured too early. A recent completion cohort has had less time to reopen. Use a fixed observation window.
• Volume read alone. High completion counts can coexist with rework, missed deadlines, or growing unfinished work.
• A score treated as a personnel decision. Use the dashboard to guide a human review with employee context, rather than automating appraisal or employment actions.

Review your own operating export in Covirage

Upload a work-completion export and a team hours file, or bring a Google Sheet with the same fields. Covirage maps the columns, and its tools compute and check the figures; 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 a sample of your own data.

See capacity planning for the wider staffing and workload review.