Operations dashboards

Run tighter operations with fewer status meetings

Cycle times live in Asana, SLAs in ServiceNow, vendor and order data in NetSuite and capacity in a planner's spreadsheet. RapidDashboard joins them in a private data store and shows COOs and operations managers where work is slowing down, in one plain-English question.

Live examples

One question, one full dashboard

Pick a question. RapidDashboard answers with KPIs, charts, the records behind them and an AI summary of what to do next. Hover any chart for values or open its table view.

Asked

Show average cycle time by workflow this month against our 5-day target. Which workflows exceed it, and where does the time go?

Built in 3.3s

Process cycle time

September All workflows Target: 5 days

Avg cycle time

6.2 days

+1.2 days vs 5-day target

Items over SLA

34%

+11 pts vs August

On time this week

61%

-4 pts vs last week

Throughput

412

+3% items completed

Avg cycle time by workflow
  • Customer onboarding 9.4 days
  • Change requests 7.1 days
  • Vendor setup 6.0 days
  • Returns (RMA) 5.2 days
  • Order fulfillment 4.8 days
  • Invoicing 2.9 days

Target: 5.0 days

Where onboarding time goes, by step
  • Working
  • Waiting
WorkingWaiting
Contract handoff0.6 days0.9 days
IT provisioning0.8 days3.1 days
Training1.9 days0.7 days
Go-live check0.9 days0.5 days
Weekly cycle time, slowest workflows
  • Customer onboarding
  • Change requests
  • Order fulfillment
  • All workflows
  • 5-day target
Customer onboardingChange requestsOrder fulfillmentAll workflows
W297.8 days6.2 days5.1 days5.3 days
W307.9 days6.3 days5.0 days5.4 days
W318.1 days6.1 days5.0 days5.4 days
W328.0 days6.5 days4.9 days5.5 days
W338.4 days6.6 days4.9 days5.6 days
W348.6 days6.8 days5.0 days5.7 days
W358.5 days6.7 days4.8 days5.8 days
W368.9 days6.9 days4.9 days5.9 days
W379.0 days7.0 days4.8 days6.0 days
W389.2 days7.0 days4.8 days6.0 days
W399.3 days7.2 days4.7 days6.1 days
W409.4 days7.1 days4.8 days6.2 days

What changed and what to do

  • Critical: Customer onboarding averages 9.4 days. IT provisioning accounts for 3.9 of them, and 3.1 days of that is waiting in the queue.
  • Warning: Change requests have crept from 6.2 to 7.1 days over 12 weeks, with most of the wait at the approval step.
  • Good: Order fulfillment runs at 4.8 days, under target and steady for the last six weeks.

AI summary

Average cycle time is 6.2 days against a 5-day target, and 34% of items finished over SLA in September. Customer onboarding is the main driver at 9.4 days, and 3.1 days of it is spent waiting in the IT provisioning queue. Recommend a process review with IT to pre-provision accounts at contract signature, which takes the provisioning wait off the onboarding critical path.

Ask next

  • Which customers are in onboarding now?
  • Cycle time by team
  • Show change request approvals by approver

Sample data for a fictional company. Your dashboards run on your own connected systems.

Sound familiar?

Where the numbers live today

Exceptions take a morning to find

Spotting what is late means checking Asana, the ERP and a few Slack channels before the stand-up.

SLA status arrives with the escalation

Targets are documented, and this week's actual compliance usually surfaces when a customer calls.

Vendor reviews run quarterly

Building a scorecard is a half-day export project, so on-time and defect data gets reviewed a few times a year.

Capacity is a judgment call

Whether a team runs at 60% or 110% shows up when milestones start to slip.

Metrics glossary

The metrics behind these dashboards

How each number is defined, so everyone reads it the same way.

Cycle time

The elapsed time from when work on an item starts until it is finished, including both working and waiting time.

FormulaCompletion date − Start date

Throughput

The number of work items, orders or tickets completed in a period.

FormulaItems completed ÷ Time period

OTIF (On Time In Full)

The share of orders delivered by the promised date with the full quantity and correct items.

FormulaOrders delivered on time and complete ÷ Total orders shipped

SLA compliance

The share of tickets or requests resolved within the time agreed in the service level agreement.

FormulaItems resolved within SLA ÷ Total items resolved

Capacity utilization

Hours of scheduled or logged work as a share of the hours a team has available.

FormulaScheduled or logged hours ÷ Available hours

Backlog

The volume of open work that has been received and is still in progress or waiting, often tracked by age.

FormulaOpening backlog + Items received − Items completed

Connections

How your systems connect

Supported APIs and exports sync into a private RapidDashboard store you approve. Dashboards read from that store, so source systems keep their normal load.

NetSuite

PullsSales orders, fulfillments, purchase orders, vendor receipts

Official REST APIs on a scheduled, audited sync into your private data store.

ServiceNow

PullsTickets, SLA timers, escalations, backlog age

Table API refreshed on the cadence you choose, down to every 15 minutes.

Asana / Smartsheet / Monday.com

PullsTask status, cycle times, assignee load, milestones

Official REST APIs mapped to your workflows, teams and capacity model.

What you can build

Dashboards and reports teams build next

Process performance

  • Cycle time by workflow
  • Working vs waiting time by step
  • Exception alerts

Service & fulfillment

  • SLA compliance by tier
  • OTIF and miss reasons
  • Backlog by age

Vendor management

  • On-time and defect scorecards
  • Contract renewal flags
  • Spend concentration

Capacity planning

  • Utilization by team and week
  • Milestones at risk
  • Rebalancing options

Operational data stays in your boundary

Process data and vendor scorecards often include contract terms, pricing and customer details. RapidDashboard keeps everything in a private data store with role-based access, so team leads see their own teams and executives see the summary. AI features are optional and run on enterprise endpoints whose terms prohibit training on your data.

FAQ

Operations dashboards: common questions

What KPIs should an operations dashboard track?

Most operations leaders track cycle time, throughput, SLA compliance, OTIF, backlog and team utilization, plus a vendor scorecard for key suppliers. The useful version shows each against its target with the exceptions listed underneath. RapidDashboard builds each view from a plain-English question against your connected systems.

How is OTIF calculated?

OTIF is the number of orders delivered on time and in full divided by the total orders shipped in the period. For example, 1,186 perfect orders out of 1,284 shipped gives an OTIF of 92.4%. Splitting misses into late versus incomplete shows which fix will move the number most.

What is the difference between cycle time and lead time?

Lead time runs from the moment a customer request arrives until it is delivered. Cycle time starts when work actually begins, so it excludes the time an item waits before anyone picks it up. Tracking both shows whether delays come from the queue or from the work itself.

Can RapidDashboard connect to ServiceNow, NetSuite and Asana?

Yes. ServiceNow, NetSuite, Asana, Smartsheet and Monday.com connect through their official APIs and sync on a schedule into a private data store. That lets one dashboard combine tickets, orders and project tasks with shared definitions.

What is a healthy team utilization rate?

Many operations teams plan around a ceiling of 80% to 85% so there is room for urgent work and absences. Utilization above 100% for several weeks in a row usually shows up later as missed milestones or overtime. The right ceiling depends on how much unplanned work your teams handle.

See dashboards like these on your own data

Fifteen minutes with an AIBMM™ Certified Coach: bring one question, leave with the dashboard it would build on your systems.

Schedule a demo