Operations Manager KPIs: Cost, Delivery, and Quality

Operations manager KPIs show whether a site delivers the agreed work at the expected cost, time, and quality. Put the actual result beside an accountable target and the exceptions requiring action; a list of percentages without ownership does not tell a manager what to change.

Choose measures that lead to a decision

Start with the operating promise: what must be delivered, to whom, and by when. Then select the measures that show whether the promise was met efficiently. NIST's Baldrige criteria commentary connects operations effectiveness with cost control and discusses cycle time, yield, and process performance measures.

For a distributor, the review might use the definitions below. These are illustrative management definitions, not universal industry benchmarks.

A KPI needs a defined decision and an owner. The broader KPI examples page covers measures across teams; this review concentrates on the operations manager's responsibility for the site result.

Keep a target register beside the definitions. It should identify the target, the person who approved it, its effective period, and whether improvement means moving up or down. NIST's key terms distinguish goals, which describe desired future performance, from measures and indicators, which quantify performance.

Build the review from export rows

Use an order export with order ID, site, original promised date, actual delivery date, completion status, and initial acceptance outcome. Preserve the original commitment when a delivery is rescheduled; otherwise a missed promise can disappear from the result.

Bring a cost export with site, posting period, cost category, amount, and the allocation basis for shared costs. The exception register needs an exception ID, site, opening date, owner, action due date, and closing date. Keep those IDs available for checking a reported total.

Define the reporting cutoff before comparing sites. Delivery uses orders due in the review period, while an open-exception balance is a snapshot at the cutoff. They answer different questions and should not share a denominator. Compare transportation detail separately using fleet management KPIs, rather than expanding the manager's review into every vehicle measure.

A worked site review

An illustrative US distributor reviews a closed operating period. Every order due in this example was completed and inspected by the review cutoff, so the completed, due, and inspected populations happen to match. That will not always hold in a live export.

The operating cost includes the same categories at both sites. Open exceptions may concern delivery, quality, or another issue; they are not an additional count of failed orders.

Company cost per order = Total included operating cost / Total completed orders

Company rate = Total qualifying outcomes / Total eligible observations

The company has approved illustrative targets of no more than $52.00 per completed order, at least 95.00% on-time delivery, at least 98.00% first-pass acceptance, and no overdue open exceptions. Calculate the results from the source table:

Dollar rates and percentages are rounded to two decimal places after calculation. The company rates divide summed numerators by summed denominators. Do not average the displayed site rates.

If the source table starts in row 2, with completed orders in column B and costs in column E, the company cost formula is:

=SUM(E2:E3)/SUM(B2:B3)

Prove the totals before assigning actions

The delivery count must reconcile: East has 500 minus 470 = 30 late orders, and West has 300 minus 270 = 30. The company has 740 on-time orders plus 60 late orders = 800 orders due.

Quality also reconciles. East has 500 minus 490 = 10 orders requiring correction, and West has 300 minus 285 = 15. The 775 first-pass accepted orders plus 25 requiring correction equal the 800 inspected orders. An order can be both late and corrected, so those failure counts must not be added together as unique affected orders.

Finance should tie $43,000 of included cost to the approved ledger categories and explain exclusions. The volume-adjusted cost allowance is 800 × $52.00 = $41,600. Actual cost exceeds it by $1,400: East is $1,000 below its allowance, while West is $2,400 above its allowance.

That result gives West a cost investigation and a delivery investigation, but it does not prove the same issue caused both. Review comparable order types and a selection of exception rows before changing staffing. Where availability is the suspected cause, examine demand planning KPIs alongside the delivery result.

Change one input and read the result again

Suppose West delivers 285 orders on time instead of 270, with every other input unchanged. Its delivery rate becomes 285 / 300 = 95.00%. The company result becomes (470 + 285) / 800 = 94.38%, compared with 92.50% before.

The additional 15 on-time orders improve the company result by 15 / 800 = 1.88 percentage points, rounded. West now meets its delivery target, but the company still falls short: 95.00% × 800 requires 760 on-time orders, and the revised total is 755, leaving a gap of 5 orders.

Cost and acceptance do not change in this variation. This is why a review needs separate accountable measures rather than one combined score. If delivery commitments differ for strategic customers, confirm the promise with the account owner; key account management covers that customer responsibility.

Where it goes wrong

• Changing the population. Completed orders cannot replace orders due in the delivery denominator when unfinished orders remain. Show those unfinished orders explicitly.
• Moving promised dates. Overwriting the original date can turn late deliveries into apparent successes. Retain the commitment used for measurement.
• Inconsistent cost scope. Shared labor, freight, and overhead must follow the same treatment across sites and periods. Show a separate bridge when the policy changes.
• Treating overlapping failures as separate orders. Delivery, quality, and exception records can refer to the same order. Use IDs when counting unique affected orders.
• Reading the snapshot as throughput. Open exceptions measure unresolved work at a cutoff. Closed exceptions measure work completed over a period; report them separately.

Review your own operating file in Covirage

Bring a sample of your own order, cost, and exception exports or a Google Sheet to Covirage. Covirage maps the columns, its tools compute and check the site comparisons, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, then set up your business and bring your file.

See self-service analytics for operating reviews for the supporting approach.