Operations is where promises to customers either get kept or quietly broken. A good operations scorecard tells you which one is happening this week — before a customer tells you. It is a short list of numbers, each with an owner and a target, that the ops team looks at together every week.
Most ops teams already have the data. It sits in a fulfilment system, a ticket queue, a production schedule and three spreadsheets. The scorecard’s job is not to replace those. It’s to pull the handful of numbers that matter into one place and put a name next to each.
What makes a good operations metric
Before you pick metrics, hold each candidate to four tests:
- It’s measured weekly (or daily). A number you only see monthly can’t steer a weekly meeting.
- Someone owns it. One person who reports it and explains it when it’s off — not “the warehouse”.
- It has a target. Without one, the team debates whether 87% is good every single week.
- It predicts trouble. Lagging numbers (revenue, NPS) matter, but ops is best served by numbers that move before the customer feels it — backlog, cycle time, on-time rate.
Aim for 8–12 metrics. Fewer and you’ll miss things; more and the scorecard review turns into a reading exercise.
Example operations KPIs, with cadence and direction
“Inverted” means lower is better — the number goes red when it rises above target, not below.
| Metric | Cadence | Inverted? | Example target |
|---|---|---|---|
| On-time delivery / completion rate | Weekly | No | 95% |
| Average cycle time (order to ship, ticket to resolved) | Weekly | Yes | 3 days |
| Open backlog (orders, jobs or tickets waiting) | Weekly | Yes | 120 |
| Rework or defect rate | Weekly | Yes | 2% |
| Items shipped / jobs completed | Daily or weekly | No | 400 per week |
| Tickets older than 48 hours | Weekly | Yes | 10 |
| Capacity utilisation | Weekly | No | 80% |
| Safety or quality incidents | Weekly | Yes | 0 |
| Inventory accuracy | Monthly | No | 98% |
| Cost per unit / cost per job | Monthly | Yes | $14 |
Adapt the list to your business. A services firm swaps “items shipped” for “projects delivered on budget”; a SaaS support team swaps inventory for first-response time (inverted). Keep the shape: volume, speed, quality, cost.
Setting it up in Clarion
Open Metrics on your operations team and use Add Metric for each one. The form asks for:
- Name and Definition — write how it’s calculated, not just what it is. “Orders shipped by the promised date ÷ orders due this week” ends arguments that “on-time delivery” starts.
- Target and Unit — dollars, percent, count or a custom unit like “orders” or “hrs”.
- Frequency — daily, weekly or monthly. Values are stored per day, per week (starting Monday) or per month to match.
- Owner — the person accountable for the number.
- Inverted metric — tick this for anything where lower is better: backlog, cycle time, defects, incidents, cost.
The step-by-step clicks are in create a metric and set targets and inverted metrics. Star the three or four metrics leadership cares most about as key metrics — those appear on the dashboard.
If your ops team has sub-teams — a warehouse team and a support team reporting into Operations, say — give each its own metrics. The Operations team’s metrics page then shows a Team Roll-Up with metrics health from each team that reports to it. See teams and companies.
Getting numbers in without chasing people
A scorecard dies when updating it is a chore. In order of effort:
- Owners type them in. Each owner records the week’s value on the metrics page, or during the sync’s Scorecard step. See record metric values.
- Push from a spreadsheet or automation tool. Every metric can have a private push URL. A Google Sheets Apps Script, Zapier, Make or n8n workflow can POST the week’s number to it. Clarion has no native connector to your WMS, ERP or helpdesk — these generic tools are the bridge.
- Let Clarion fetch it. If a system exposes the number at a JSON URL, an admin can set up pull from a URL to read it hourly, every six hours or daily. This only reads JSON APIs — not web pages or files.
Pushing or fetching again in the same period replaces that period’s value, so a scheduled job can run as often as you like without double-counting.
Reviewing it every week
The scorecard earns its keep in the weekly ops sync. The first step of every Clarion sync is the Scorecard: walk the list, and for each number say only “on” or “off”. Don’t discuss yet.
Anything off target goes to the challenge list. On the metrics page, expand a metric and click Flag as challenge — Clarion creates a challenge titled “[metric] off target” with the actual and target values filled in, assigned to the metric’s owner. The team then solves the most important ones in the challenge discussion.
Common mistakes
- Tracking what’s easy instead of what matters. Volume metrics are easy to pull; quality and speed metrics are what customers feel. Make sure at least half your list is speed or quality.
- Forgetting to invert. If backlog is shown as “below target” in red when it’s actually low, people stop trusting the colours. Tick Inverted metric for every lower-is-better number.
- No definition. Two people calculating cycle time two ways produces two numbers and a wasted meeting.
- Changing targets mid-quarter to make red go away. Revisit targets quarterly, not when they’re inconvenient.
- Discussing every number. The scorecard review is for spotting; solving happens in challenges.
A cadence that works
- Daily: owners of daily metrics record today’s number before the end of the day — or let automation do it. Entering a value in the app records it for the current period, so a missed day is best filled by a push with a
date. - Weekly: the ops team reviews the scorecard in its sync and flags anything red.
- Quarterly: revisit targets and retire metrics nobody has acted on in three months.
For more on scorecard design in general, see build a weekly scorecard.