Clause 8.2.1 wants feedback, not just complaints

8.2.1 is a gathering duty, not a response duty

Clause 8.2.1 requires the organization to establish a documented procedure for obtaining and monitoring feedback as one of the measurement systems that assesses whether the quality management system is actually meeting requirements, and it specifically names production and post-production activities as sources that procedure has to reach. That's a different kind of obligation than the reactive process complaint handling runs on: a complaint waits for someone to call; a feedback process is supposed to be actively looking, across a wider set of sources than any inbound line can cover on its own.

The sources 8.2.1 names go well past what a customer reports

Rework records, service reports, field observations, distributor communications, even data pulled from the organization's own production floor — none of it requires a customer to have picked up the phone. A returned unit that a service technician quietly reworks without the end user ever filing anything is exactly the kind of signal 8.2.1's feedback process exists to catch, and a system that only opens a record when a complaint arrives never sees it at all. The clause's own breadth is the point: it's built to catch the information a narrower, complaint-only channel structurally can't.

Complaints are a subset of feedback, not a synonym for it

Clause 8.2.2 and 8.2.3 take over once feedback turns into a specific kind of report — an allegation of a deficiency relating to a device's identity, quality, durability, reliability, safety, or performance, evaluated against a defined reportability test and, where the test is met, escalated toward regulatory reporting. That's a real and necessary process, but it's downstream of a much larger stream 8.2.1 is supposed to be watching, and treating the complaint log as the whole feedback system mistakes the narrow, formally-triggered branch for the trunk it grows out of. A complaint record's own reportability test only ever runs on the fraction of feedback that arrives already looking like a complaint.

What 8.2.1 actually feeds is the risk file, not just a metrics dashboard

Feedback gathered under 8.2.1 isn't collected for its own sake — it's an input the standard expects to reach the organization's risk management process, the same way a risk management file has to stay current against new information rather than close once a device clears its initial review. A rework pattern nobody outside the production floor ever reports as a complaint can still be the exact signal that should reopen a residual-risk conclusion the file has been carrying as settled. A feedback process that only surfaces complaint-grade events has cut off one of the main channels ISO 14971's own post-production monitoring duty is built to use.

Where this meets the file

A feedback procedure that can name its non-complaint sources by name — which service reports get reviewed, which production data gets monitored, on what cadence — and that shows a documented path from any of them into the risk file, is doing the job Clause 8.2.1 actually describes. A procedure that can only point to its complaint log has built a narrower system under a wider clause's name. A feedback-source worksheet that separates 8.2.1's gathering duty from 8.2.2's complaint-handling duty, with each source's own review cadence named, is previewed in the launch catalog. If your program runs these as one undifferentiated process, the shelf takes that correction directly.