Real-Time Dashboard Audit Checklist for Manufacturing Plants

By Caroline Whitmore on June 5, 2026

real-time-dashboard-audit-checklist

A real-time dashboard audit is the difference between a shop floor that acts on data and a shop floor that ignores the screens on the wall. Most manufacturing plants have invested in dashboard displays — TVs on the shop floor, tablets at workstations — but fewer than 30% of those dashboards are actually used for decision-making. The screens are frozen, the KPIs are wrong, the refresh rate is too slow, or the audience is mismatch. This dashboard audit checklist covers every dimension of dashboard effectiveness — data freshness, visual design, KPI relevance, technical performance, user engagement, and governance — based on iFactory's audit methodology applied across 1,000+ manufacturing plants. Each of the 30 items helps you identify exactly what is wrong with your current dashboards and what to fix first.

Audit Your Shop Floor Dashboards in One Week — Identify Every Gap

iFactory's dashboard audit service evaluates every screen on your shop floor against 30 audit criteria and delivers a prioritised fix list within 5 days. See a sample audit report in a 30-minute session.

Why a Structured Dashboard Audit Drives Action

Plants that conduct a structured dashboard audit every 6 months achieve 3.4x higher daily active dashboard usage and identify an average of 8 critical gaps per audit that directly impact operational decisions. The six audit dimensions below cover every aspect of dashboard effectiveness.

30 Audit Criteria Six dimensions with five criteria each — covering data freshness, visual design, KPI relevance, performance, user engagement, and governance.
6 Audit Dimensions Data freshness, visual design, KPI relevance, technical performance, user engagement, and governance — the six pillars of dashboard effectiveness.
8 Critical Gaps Average number of critical issues found per plant during initial dashboard audit — issues that directly impact operational decision-making.
3.4x Usage Uplift Daily active dashboard usage increase in plants that conduct structured audits every 6 months vs plants that never audit.

Dashboard Health Scores — Grade Your Current Dashboards

Each audit dimension is scored on an A–F scale. A grade means the dimension meets best-practice standards. F grade means the dimension is broken and requires immediate intervention. Use this scoring framework to assess your current dashboards before working through the detailed checklist.

A
Data Freshness

90%

Live data streaming with <1 s latency. Auto-refresh without page reload. Data source connection health monitored and alerted on failure. Historical data available for comparison.

B
Visual Design

78%

Clean layout with clear hierarchy. Colour coding consistent (green/good, yellow/warning, red/bad). Charts appropriate for the data type. Mobile-responsive. No chartjunk or misleading scales.

C
KPI Relevance

65%

KPIs match audience needs. Targets visible next to actuals. Leading and lagging indicators balanced. Metrics align to plant objectives. No vanity metrics or unused KPIs cluttering the view.

D
Tech Performance

52%

Page load time <3 s on shop floor hardware. Works on TV displays, tablets, and phones. No browser compatibility issues. Touch-friendly for gloved operators. Offline fallback available.

E
User Engagement

40%

Operators look at dashboard at least once per hour. Supervisors use dashboard in shift handover. Managers reference dashboard in daily stand-up. Users can drill down for detail. Feedback mechanism exists.

F
Governance

25%

Dashboard owner assigned per screen. Review cadence defined (monthly, quarterly). KPI change process documented. Data source dependencies mapped. Version history maintained. No orphaned dashboards.

Dashboard Types by Audience — Audit Criteria Vary by Viewer

Not all dashboards should be audited against the same criteria. An operator station dashboard has different requirements than an executive strategic dashboard. Use this reference to apply the right audit lens for each screen on your shop floor.

Operator Station
Machine operators and line technicians Real-time cycle time, target vs actual, alarm status, production count, next-part indicator 55–65" display at 3–5 m viewing distance, font ≥48pt, touch or glance-only, colour-coded alerts, no scrolling
Supervisor Shift
Shift supervisors and production leads Shift-level OEE, downtime Pareto, quality yield, operator performance, labour tracking, shift comparison 43–55" display at 2–3 m, font ≥24pt, drill-down to station level, exception highlights, shift handover summary
Manager Daily
Production managers and plant managers Daily production vs plan, MTBF/MTTR trends, PM compliance, throughput vs target, financial metrics Desktop + large display, font ≥14pt, trend charts, month-to-date comparison, exception-based drill-down
Executive Strategic
VP operations, COO, CFO, corporate leadership Plant-level OEE, cost per unit, overall equipment effectiveness trend, sustainability metrics, ROI dashboards Desktop + boardroom display, font ≥12pt, monthly/quarterly aggregation, financial + operational, PDF export

Get a Complete Dashboard Audit in 5 Days — See What Is Wrong and What to Fix

iFactory's dashboard audit team evaluates every screen on your shop floor against 30 criteria and delivers a prioritised fix list. No commitment, no consulting fee — just an honest assessment.

Data Source Health — How Reliable Are Your Dashboard Data Feeds?

Every dashboard is only as good as the data sources powering it. This reference shows the typical health profile for each source type across iFactory's 1,000+ plant deployments. Use these benchmarks to assess whether your dashboard data feeds are performing at industry standard.

PLC / SCADA Systems
99.7% uptime <1s latency Healthy
Direct plant-floor controllers streaming real-time equipment data. Most reliable source with redundant failover. Connection loss triggers immediate dashboard alert.
MES / SCADA Historian
98.2% uptime 5-30s latency Healthy
Manufacturing execution systems and data historians aggregating production data. Slight buffering delay. Batch data sync may lag behind real-time PLC feeds by seconds.
CMMS / EAM Systems
95.8% uptime 1-15min latency Warning
Computerised maintenance management systems feeding work order and asset data. API-dependent sync. Latency increases during peak maintenance scheduling hours.
ERP / Business Systems
93.4% uptime 15-60min latency Warning
Enterprise resource planning systems providing production schedules, orders, and financial data. Nightly batch sync typical. Real-time dashboards should not depend on ERP for fresh data.
Quality / Lab Systems
91.5% uptime 5-30min latency Warning
Quality inspection and laboratory information systems. Often require manual result entry or semi-automated data transfer. Most common source of data staleness on dashboards.
Manual Entry Data
85.2% timeliness 15-120min latency Critical
Operator-entered production counts, quality events, and downtime codes via tablets or terminals. Highest latency and variability. Flag as stale if entry exceeded 30 min past expected time.

Data Freshness SLA Reference — How Current Should Your Data Be?

Not every dashboard KPI needs real-time data. The required freshness depends on the decision being made. Use this SLA reference to set appropriate refresh expectations for each dashboard in your plant. Mismatched SLAs are the leading cause of dashboard distrust.

Level 1
Real-Time < 1 second latency
Auto-refresh Continuous stream

Operator station dashboards showing cycle time, alarm status, and production count. Data must update without page reload. WebSocket or MQTT feed. A freeze longer than 3 seconds triggers operator confusion. This is the most critical SLA — broken real-time dashboards cause operators to stop trusting all dashboards.

Operator OEE, alarm panels, line speed
Level 2
Near Real-Time 1–30 second latency
Polling refresh Every 5–10 seconds

Supervisor shift dashboards showing OEE, downtime Pareto, and quality yield. Data refreshes automatically but a few seconds delay is acceptable. Polling-based refresh from historian or MES is sufficient. Stale-data indicator should show last-refresh timestamp.

Shift summary, downtime Pareto, yield board
Level 3
Near Real-Time 30 seconds – 5 minutes
Interval refresh Every 30–60 seconds

Manager daily dashboards showing production vs plan, MTBF/MTTR trends, and PM compliance. Minute-level latency is acceptable. Auto-refresh expected but manual refresh button also provided for on-demand checks. Most common SLA for production management screens.

Daily production, maintenance KPIs
Level 4
Shift / Batch 5 minutes – 1 hour
On-change refresh Or manual refresh

Department-level dashboards for weekly reviews and cross-functional meetings. Data refreshes when the underlying report is updated or on a scheduled interval. Acceptable to have a "Refresh Now" button. Stale data less than 1 hour old is acceptable.

Weekly OEE trend, quality reports
Level 5
Daily / Manual 1 hour – 24 hours
Manual trigger Once per day

Executive strategic dashboards for monthly and quarterly business reviews. Data is typically from nightly batch syncs. No auto-refresh expected. Clear data-date label required. Acceptable for financial or aggregated metrics that do not change intra-day.

Monthly ROI, corporate scorecard

Real-Time Dashboard Audit Checklist — 30 Items

Each checklist item includes the specific audit criterion, type, priority, and status toggles. The type indicates whether the item is a pass/fail check, a structured selection, or a numeric configuration. Priority marks impact on dashboard effectiveness. Use the Photo, Required, and Critical toggles to track completion per dashboard screen.

Fresh Data Freshness & Refresh Audit 5 items
#Audit CriterionTypePriorityPhotoReq.Crit.
1Dashboard data refreshes automatically without manual page reload — auto-refresh interval ≤5 s for real-time dashboards, ≤60 s for shift-level dashboardsPass/FailHigh
2Last-refresh timestamp or data-age indicator visible on the dashboard — operators can see how fresh the data is; stale data older than 2x refresh interval flagged in yellowPass/FailHigh
3Data source connection health monitored — each data source (PLC, MES, ERP) shows connection status (green/red) on a dashboard admin panel; connection loss triggers alertPass/FailHigh
4Historical data available for comparison — current value shown alongside prior shift, prior day, or prior week value; trend line or sparkline visible for each KPIPass/FailMed
5Data gap detection configured — if data stops flowing from a source for more than 2x the expected interval, a data freshness alert is raised and the dashboard shows the affected KPI as stalePass/FailMed
Vis Visual Design & Layout Audit 5 items
#Audit CriterionTypePriorityPhotoReq.Crit.
6Colour coding consistent across all dashboards — green = good (at or above target), yellow = warning (within 10% of threshold), red = bad (below target or alarm state); no colour conflictsPass/FailHigh
7Chart type appropriate for the data — bar chart for comparisons, line chart for trends, gauge for target vs actual, pie chart used only for parts-of-a-whole with ≤5 segmentsPass/FailHigh
8Dashboard layout follows F-pattern or Z-pattern visual hierarchy — most important KPI top-left, supporting metrics top-right and middle, details bottom; no random placementPass/FailHigh
9Font sizes appropriate for viewing distance — operator station (≥48 pt at 3 m), supervisor (≥24 pt at 2 m), desktop (≥14 pt at 0.5 m); no tiny fonts on big screensPass/FailHigh
10No misleading visualisations — y-axis starts at zero for bar charts, no 3D charts that distort perception, no truncated axes, no area charts that hide data below overlapping seriesPass/FailMed
KPI KPI Relevance & Content Audit 5 items
#Audit CriterionTypePriorityPhotoReq.Crit.
11Every KPI on the dashboard has a defined target or threshold — no numbers displayed without context; targets visible adjacent to actual values with traffic-light statusPass/FailHigh
12Leading and lagging indicators balanced — lagging (what happened: OEE, throughput, quality) and leading (what will happen: backlog trend, PM compliance, cycle time trend) both presentPass/FailHigh
13No vanity metrics or unused KPIs — every metric on the dashboard has been used in a decision within the last 30 days; metrics not used for 60+ days are flagged for removalPass/FailHigh
14Dashboard KPIs align to plant or company OKRs — each KPI can be traced upward to a strategic objective and downward to a daily action; no orphan metrics disconnected from goalsPass/FailMed
15KPI definition and calculation method documented and accessible — one-click access to metric definition, data source, refresh frequency, and owner; no ambiguous or differently-interpreted KPIsPass/FailMed
Perf Technical Performance & Access Audit 5 items
#Audit CriterionTypePriorityPhotoReq.Crit.
16Dashboard page load time ≤3 s on target hardware — tested on the actual shop floor display hardware (TV, thin client, tablet), not on a developer laptopNumericHigh
17Dashboard renders correctly on all target screen sizes — TV (1920×1080), tablet (1024×768), phone (390×844), and desktop (1920×1080); no cutoff content, overlapping elements, or scrollbars on TVPass/FailHigh
18Touch interface functional for shop floor tablets — buttons and links minimum 44×44 pt tap target, swipe for page navigation, pinch-to-zoom enabled, no hover-dependent interactionsPass/FailHigh
19Dashboard functions during network interruptions — cached data visible with stale-data indicator; non-critical elements degrade gracefully; critical KPIs show last-known-good valuesPass/FailMed
20Browser compatibility verified — dashboard tested and functional on Chrome, Edge, Firefox, and Safari; no Flash, Silverlight, or deprecated dependenciesPass/FailMed
Engage User Engagement & Adoption Audit 5 items
#Audit CriterionTypePriorityPhotoReq.Crit.
21Operator glance time tested — operator can read the most important KPI in ≤2 s from the typical viewing position; tested with actual operators, not assumedNumericHigh
22Supervisor uses dashboard in shift handover — shift-change meeting includes walking through the dashboard together; both shifts review the same screenPass/FailHigh
23Dashboard usage analytics collected — daily active users, most-viewed pages, average session duration, common exit pages; usage below 50% of expected audience triggers investigationPass/FailMed
24User feedback mechanism exists — operators and supervisors can report dashboard issues, suggest new KPIs, or flag incorrect data directly from the dashboard with a one-click feedback buttonPass/FailMed
25Dashboard referenced in daily stand-up meeting — the plant manager, shift supervisor, or team lead refers to a specific dashboard during the daily stand-up at least 4 out of 5 days per weekPass/FailMed
Gov Governance & Review Process Audit 5 items
#Audit CriterionTypePriorityPhotoReq.Crit.
26Dashboard owner assigned per screen — a named person responsible for accuracy, relevance, and performance of each dashboard; owner visible on a dashboard metadata panelPass/FailHigh
27Dashboard review cadence defined and scheduled — monthly for operational dashboards, quarterly for tactical, annually for strategic; last-reviewed and next-review dates visible on dashboardPass/FailHigh
28KPI change management process documented — any change to a KPI definition, target, or data source requires a change request with approval, effective date, and communication to all affected usersPass/FailHigh
29Orphaned dashboards identified — no dashboard has been inactive (not viewed by anyone other than the creator for >90 days); orphan dashboards archived or deletedPass/FailMed
30Dashboard version history maintained — each dashboard change tracked with timestamp, author, and change description; rollback to previous version possible within 30 days of changePass/FailMed
Legend: Pass/Fail Selection Numeric Priority: High Med Toggles: ✓ Required — Photo ✓ Critical

Dashboard Maturity Levels

Dashboard maturity progresses from static poster boards to intelligent adaptive displays that adjust content based on viewer, time of day, and production conditions. Most plants operate at Level 1 or 2. A structured audit typically accelerates maturity by one full level within 90 days.

1

Static

Poster Boards & Frozen Screens

Dashboards are printed posters or static screens that update weekly. No live data. No interaction. Operators walk past without looking. Shift handover uses paper reports. No audit needed — everything is broken.

2

Live

Auto-Refreshing Display

Dashboards show live data with auto-refresh. Basic KPIs visible. Colour coding applied. Some targets shown. Operators glance at screens. Supervisors reference during shift. First audit identifies 10–15 gaps.

3

Interactive

Drill-Down & Role-Based

Dashboards offer drill-down from plant to station level. Role-based views for operators, supervisors, and managers. Usage analytics collected. User feedback captured. Review cadence established. Audit finds 3–5 gaps.

4

Adaptive

AI-Personalised Displays

Dashboard content adapts to the viewer (operator vs manager), time of day (shift start vs shift end), and production conditions (normal vs disruption). Predictive alerts embedded. No audit gaps found.

Dashboard Audit Deployment Stages

iFactory conducts dashboard audits in four sequential stages. Each stage builds on the previous one — from inventory and scoring through gap analysis, prioritised fix planning, and re-audit cycle establishment.

01 Inventory Day 1: Dashboard Discovery & Categorisation
  • Inventory every dashboard screen in the plant — TV, tablet, desktop, boardroom
  • Categorise by audience — operator, supervisor, manager, executive
  • Document screen specs — size, resolution, viewing distance, hardware, network
  • Identify dashboard owner (or absence of one) per screen
02 Score Day 2–3: Criteria Assessment & Grading
  • Score each dashboard against the 30 audit criteria
  • Measure page load time, test mobile rendering, verify touch targets
  • Interview operators and supervisors for engagement assessment
  • Assign A–F health score per audit dimension per dashboard
03 Prioritise Day 4: Gap Analysis & Fix Plan
  • Group findings into priority matrix — quick wins, major projects, fill-ins, low priority
  • Estimate effort hours per fix and assign owners
  • Define dashboard governance — owners, review cadence, change process
  • Produce prioritised fix plan with timeline and expected impact per fix
04 Re-Audit Day 5 + Quarterly: Re-Audit Cycle
  • Implement quick wins and fill-ins within 2 weeks
  • Track dashboard usage analytics to measure improvement from fixes
  • Schedule re-audit every 6 months with the same 30 criteria for trend comparison
  • Review and update score targets per dimension each audit cycle

Real-Time Dashboard Audit — Frequently Asked Questions

How often should manufacturing dashboards be audited?

iFactory recommends a full dashboard audit every 6 months for all production-critical dashboards — operator station, supervisor shift, and manager daily screens. Executive strategic dashboards can be audited annually. The audit cycle should align with the plant's operational review calendar so that findings feed directly into the next quarter's improvement plan. In addition to scheduled audits, an out-of-cycle audit should be triggered whenever there is a significant change in data sources, a new production line or product launch, a change in plant leadership, or when dashboard usage analytics show a sustained decline in daily active users (more than 20% drop over 30 days).

What is the most common dashboard audit finding?

The most common finding across iFactory's 1,000+ plant deployments is stale or frozen data — dashboards that appear to show live data but are displaying values from hours or days ago. This happens when the auto-refresh mechanism fails silently (browser tab throttling, WebSocket disconnect, data source timeout) and no one notices because there is no stale-data indicator. The second most common finding is KPI overload — more than 12 KPIs on a single screen, making it impossible for operators to identify the most important number in a glance. The third most common finding is missing targets — KPIs displayed as raw numbers without target context, forcing viewers to know from memory what the number should be. All three of these issues are addressed by items 1, 11, and 12 in the checklist above.

How do you measure if a dashboard is actually being used?

Dashboard usage should be measured through four methods: (1) technical analytics — page views, unique users per day, average session duration, and most-viewed pages collected from the dashboard platform's built-in analytics, (2) observational audit — a person stands near the dashboard during a shift and counts how many times operators glance at it, how long each glance lasts, and whether the glance leads to an action, (3) meeting integration — track how often the dashboard is referenced in daily stand-up meetings, shift handovers, and weekly reviews, and (4) user survey — ask operators and supervisors a single question monthly: "Did you make a decision based on this dashboard in the last week?" A dashboard with fewer than 50% of respondents answering yes needs improvement. The target is 80%+ for operator and supervisor dashboards.

What screen size and viewing distance guidelines should dashboards follow?

Manufacturing dashboards must be designed for the specific screen and viewing distance where they will be used. The three standard configurations are: (1) Operator station — 55–65" display mounted 3–5 m from the operator, minimum font size 48 pt, no more than 6 KPIs, colour-coded alerts only (no detailed charts), (2) Supervisor area — 43–55" display at 2–3 m, minimum font size 24 pt, trend charts allowed, drill-down to station level, and (3) Desktop — standard monitor at 0.5 m, minimum font size 14 pt, full analytics, filtering, and export capabilities. The single most common visual design error in manufacturing dashboards is taking a desktop-designed dashboard and displaying it on a 55" TV — the fonts are too small, the charts are too dense, and operators cannot read anything from their working position.

What is the difference between an operational and a strategic dashboard audit?

An operational dashboard audit (for operator, supervisor, and manager screens) focuses on data freshness, visual clarity, real-time accuracy, and actionability — can the viewer make a decision within 5 seconds of looking at the screen? A strategic dashboard audit (for executive screens) focuses on KPI relevance to business objectives, data accuracy for financial reporting, trend visibility for long-term decisions, and alignment with corporate OKRs. The operational audit uses the full 30-point checklist. The strategic audit places heavier weight on dimensions 3 (KPI relevance) and 6 (governance) and uses a modified version of the checklist with more emphasis on data lineage, calculation definitions, and audit trail. Regardless of the dashboard type, every screen should have a named owner and a defined review cadence — no dashboard should exist without accountability.

How does iFactory's dashboard audit service work?

iFactory's dashboard audit service is a fixed-scope, fixed-price engagement delivered in 5 days. Day 1: our team inventories every dashboard in your plant and categorises them by audience and screen type. Day 2–3: we score each dashboard against the 30 audit criteria, measuring page load time, testing mobile rendering, interviewing operators and supervisors, and reviewing governance documentation. Day 4: we produce a prioritised fix plan with effort estimates, owner assignments, and expected impact per fix. Day 5: we present the audit report to plant leadership with a dashboard health scorecard, critical findings, and a 90-day improvement roadmap. The audit does not require any software installation, data access, or plant downtime. It is purely observational and interview-based. At the end of the engagement, you receive a complete picture of every dashboard's health and a step-by-step plan to fix every issue.

Audit Every Dashboard in Your Plant in 5 Days — Know Exactly What to Fix

iFactory's dashboard audit service evaluates every screen against 30 criteria and delivers a prioritised fix plan. No software, no downtime, no consulting fee. See a sample audit report in a 30-minute session.