Building a Quality Dashboard Executives Will Actually Read

Executives do not read 40-row CAPA aging spreadsheets. They will read a one-page view that answers: are we safe, are we inspectable, and where should we spend money this quarter. This article is how to build that dashboard from QMS data without turning quality into a vanity score.

FDA's quality metrics initiatives and ISO 13485 5.6 / 8.4 expect management to review data. The failure mode is presenting activity (training completions, SOP count) instead of outcomes (repeat complaints, overdue effectiveness checks, overdue calibrations on critical equipment).

Start with decisions, not charts

List the decisions the CEO, CFO, and Head of Quality actually make:

• Pause a launch
• Fund a line or a supplier change
• Add headcount in QA or in operations
• Accept residual risk on a field issue
• Tell the board about inspection exposure

Each dashboard tile should change one of those decisions. If it cannot, it belongs in an operational huddle, not the exec pack.

Ask the CEO which three numbers they remember from last quarter. If the answer is "none," the pack failed, not the CEO.

A working tile set

1. Patient / customer harm signals MDR / vigilance submitted, serious complaints, field actions open. Trend 12 months. Annotate any open FSCA.

2. Repeat problems CAPAs past due effectiveness check; complaints with the same failure code twice in 90 days; deviations recurring on the same line.

3. Inspection readiness Overdue internal audit findings, overdue training for GxP roles, overdue calibration of critical instruments, incomplete batch / DHR releases older than a defined number of days.

4. Supplier concentration risk Single-source critical materials with open SCARs or incoming OOS.

5. Change load Open design and process changes that affect validated state; percent implemented past target date.

6. Cost of poor quality (optional, with finance) Scrap, rework, recall reserve, idle line time from quality holds. Only if finance agrees the definition.

Six tiles beat sixteen. Additional detail lives one click down for the quality director.

A seventh tile for "open regulatory commitments" (483 responses, NB findings) is worth adding after a tough inspection year. Retire it when the commitments close.

Definitions that survive an auditor

Write a data dictionary:

• When a complaint is open
• When a CAPA is effective (not when the form is closed)
• Which equipment is critical
• Which training is GxP required

If two sites count differently, the exec chart is fiction. Harmonize before you graph.

Effectiveness of CAPA should require a defined window with no recurrence, not a checkbox that the trainer ran a module.

Serious complaint should match your MDR / vigilance SOP, not a local adjective.

Cadence

Weekly: harm signals and holds that block release (operations + quality).

Monthly: the six-tile pack in management review.

Quarterly: board excerpt: field actions, inspection outcomes, investment asks.

Do not email a 20-tab workbook monthly and call it management review. ISO 13485 wants inputs and outputs recorded, including decisions.

Minutes should capture the decision under each red tile. "Discussed" is not an output.

Visual rules

• One idea per chart
• Time on the x-axis so a spike is obvious
• Red only for items past a defined threshold, not for decoration
• Names of owners on overdue items
• No gauges that say 73 percent quality

Executives ask what they need to do. The dashboard should answer in a sentence under the tile: Approve overtime on CAPA-1044 effectiveness, or Hold SKU until supplier SCAR closes.

Avoid 3D charts, rainbow heat maps, and logos. They read as a pitch deck.

What to keep off the exec page

• Training percent for non-GxP courses
• Number of SOPs revised
• Help-desk ticket volume
• Audit observation counts without severity and closure age
• Digital transformation scores

Those can be department KPIs. They dilute the harm and inspectability story.

Do not average sites into one green number if one site is red. Dual reporting (network plus worst site) is more honest.

Data integrity of the dashboard itself

The dashboard is a report. 21 CFR Part 11 and Annex 11 thinking still apply if it drives release or quality decisions:

• Source systems identified
• Refresh time shown
• No silent filters (exclude legacy products)
• Export that matches the screen for the management review record

If someone can spreadsheet-filter away the red items before the meeting, you do not have a management review input.

Access control matters. A plant manager should not be able to edit the definition of overdue.

When you change a KPI definition, version it. Comparing January apples to June oranges is how trust dies.

Linking tiles to action

Every red tile needs a record: CAPA, change, or a documented risk acceptance with an expiry date. Orphan red tiles train executives to ignore the page.

Review the dashboard in the same meeting as resource decisions. If quality only presents after the budget is closed, the tiles are theater.

Tie bonuses with care. Paying people to lower complaint counts without auditing the complaint gate will lower counts.

Building it in the QMS versus a BI tool

BI is fine if the definitions are pulled from the system of record. Native quality dashboards avoid a second mapping layer. Either way, owners live in the eQMS: the chart does not close a CAPA.

Start with two tiles if that is all the data you trust. Expand when the dictionary is real.

Validated quality platforms with role-based views can give the plant a working list and the executive a six-tile pack from the same records. People still interpret the red. A walkthrough is at cloudtheapp.com/demo.

Sources

• ISO 13485:2016 5.6 Management review, 8.4 Analysis of data
• 21 CFR 820 / QMSR management responsibility
• FDA quality metrics and management responsibility inspection guides
• ICH Q10 pharmaceutical quality system, management review
• 21 CFR Part 11 / EU Annex 11 for electronic reports used in GxP decisions