The Workbench · Craft

Clause 8.4 names six inputs a data review can't skip

This blog has already covered how Clause 8.2.1 wants feedback, not just complaints, and what a CAPA tracker has to track once a corrective action opens. Clause 8.4, analysis of data, sits between those two activities and is easy to satisfy by accident — a quality system that already runs feedback intake and a CAPA process can look, from a distance, like it has covered data analysis without ever building the clause's own record. It hasn't. Clause 8.4 names its own required inputs, separate from the processes that feed it and the ones that are supposed to consume what it produces.

A planning clause and an analysis clause aren't the same thing

This blog has already covered Clause 8.1's planning duty, which requires an organization to determine the monitoring, measurement, and analysis methods it will use before it uses them. Clause 8.4 is the clause that actually requires the analysis those methods were chosen to perform: it requires the organization to establish a documented procedure to determine, collect, and analyze appropriate data, generated from monitoring and measurement and from other relevant sources, to demonstrate the quality management system's suitability and effectiveness. A file that documents which statistical methods it selected under 8.1, and then never runs an analysis using them, has planned the exercise Clause 8.4 requires and stopped short of performing it.

Six inputs, not a general dashboard

Clause 8.4 doesn't leave what counts as “appropriate data” to the organization's own judgment. At minimum, the analysis has to cover: feedback; conformity to product requirements; the characteristics and trends of processes and product, including opportunities for preventive action; suppliers; audits; and service reports, where applicable. That's six named categories, not a single quality metric or a customer-satisfaction score standing in for the whole requirement. A data-analysis record that reports on complaint volume alone, however well it's trended, has covered one of the six inputs the clause requires and left the other five unaddressed.

Trends are where preventive action starts

The third item on that list carries more weight than its place in the sentence suggests: trends in process and product characteristics have to be reviewed specifically for opportunities for preventive action, not just tracked for awareness. That's a forward-looking read the other five inputs don't carry the same way — a supplier's data or an audit finding usually points at something that has already happened, while a trend in a process characteristic can surface a problem before any single unit fails because of it. A data-analysis record that logs trend charts without a corresponding preventive-action review has produced the chart Clause 8.4 asks for and skipped the judgment call the clause built the chart to support.

The output has somewhere specific to go

Clause 8.4's analysis isn't an end in itself. Its results are meant to feed two places this blog has already covered: as input to the management review record, and, where the analysis surfaces a nonconformity or a preventive-action opportunity, into the CAPA process itself. A data-analysis exercise that produces a report and files it without a documented link forward into either process has performed the analysis and orphaned its own conclusion — the record exists, but nothing downstream is required to act on what it found.

Where this meets the file

A data-analysis worksheet built around this structure needs one section per required input — feedback, conformity, trends and preventive-action opportunities, suppliers, audits, and service reports — plus a field routing each finding to management review or to a CAPA record by name, rather than a single combined dashboard that reports the six inputs without distinguishing them. A worksheet built that way, alongside the feedback and CAPA logic this blog has already covered, is previewed in the launch catalog. If your program runs data analysis to a different structure, the shelf takes that correction directly.

The Regulatory Toolkit launches soon — a free shelf of source-mapped templates, checklists and browser-only tools for regulatory teams. Get one email when it opens, or contribute a template.

All Workbench notes