You know the moment. The auditor leans across the table, looks at the production lead you’ve grabbed off the line for an interview, and asks, “How does the company communicate the effectiveness of the quality management system to you?”
The production lead pauses. Looks at you. Looks back at the auditor. Says, “I think there’s a poster in the break room?”
That’s §5.5.3 in action. Or rather, it’s §5.5.3 not in action, which is exactly what auditors are listening for.
What §5.5.3 Actually Says
This clause is, by ISO 13485 standards, almost cruelly short. The entire requirement boils down to two things top management must do:
- Make sure appropriate communication processes are established within the organization.
- Make sure communication actually happens — specifically, communication about the effectiveness of the QMS.
Two ideas. One short paragraph. And yet this is the clause that quietly trips up companies who otherwise have their act together. The reason is that it’s not asking whether people talk to each other. People talk to each other constantly. Slack channels are full. Hallway conversations are happening. Production meetings cover yields and downtime. None of that necessarily satisfies §5.5.3.
What §5.5.3 wants is communication about the QMS itself — and it wants it to be planned, intentional, and reaching the people who need to hear it.
What “Effectiveness of the QMS” Means in Plain English
This is the part most companies skip past. “Effectiveness of the QMS” is not a vague feeling about quality. It’s specific things, like:
- Whether the quality policy and quality objectives are being met
- Results from internal audits
- Status of corrective and preventive actions (CAPAs)
- Customer complaints and how they’re trending
- Nonconformities — what’s been caught, what’s been fixed
- Outputs from management review
- Changes to regulatory requirements that affect the work
Internal communication under §5.5.3 means making sure the people who do the work actually know how the system around them is performing. The technician on the line should know that complaint rates are up this quarter. The shipping clerk should know there was a CAPA on labeling errors. The design engineer should know the audit found a gap in design verification records. You can’t fix what you don’t know is broken, and you can’t reinforce what’s working if nobody knows it’s working.
What “Appropriate Processes” Looks Like in Real Life
The standard doesn’t dictate how you communicate. It just says the processes have to be appropriate to your organization. A 12-person startup in one room communicates differently than a 400-person manufacturer with three shifts and a remote design office. Both can comply. Neither can comply by accident.
Here’s what “appropriate processes” tends to look like in companies that pass audits cleanly:
- Defined channels. Quality dashboards posted somewhere people actually look. Standing items on team meeting agendas. Quarterly all-hands segments dedicated to QMS metrics. Quality bulletins or newsletters. Toolbox talks before shifts.
- Two-way flow. Communication isn’t just top-down. There has to be a defined way for staff to raise quality concerns, suggest improvements, and report problems. Suggestion systems, anonymous reporting channels, tiered huddles, and skip-level meetings all count.
- Tied to roles. Different people need different information. The CFO doesn’t need every nonconformity report. The line operator doesn’t need the regulatory landscape briefing. Define who hears what.
- Evidence. Meeting minutes, training records, dashboard screenshots, posted bulletin photos, attendance lists, intranet logs. If you can’t show it, the auditor will conclude it didn’t happen. (See also: every other clause of ISO 13485.)
The Common Traps
A few patterns that show up over and over in audit findings:
The one-channel trap. “We have a monthly all-hands.” Great. What about the people on second shift who don’t attend? What about the contract manufacturer’s staff who never get the email? Communication that doesn’t reach the people who need it isn’t communication. It’s a bullet point on a slide.
The product-vs-system confusion. Daily production huddles about scrap rates and downtime are operational communication, not QMS communication. They might overlap, but they don’t replace it. §5.5.3 is asking specifically about the system that governs quality — its objectives, its performance, its audit results, its corrective actions.
The “we tell management” trap. Sharing QMS performance only with the leadership team and forgetting to cascade it down satisfies none of §5.5.3. The clause is about communication within the organization, which means the people doing the work, not just the people in the corner offices.
The undocumented town hall. “Oh, we covered that at the all-hands in March.” Show me. No agenda, no minutes, no attendance list, no slides. The auditor isn’t being unreasonable — they’re being a normal auditor.
The Bottom Line
§5.5.3 is one of those clauses that takes about ninety seconds to read and about ninety days to do well. The fix isn’t complicated. Decide what QMS information needs to flow, decide who needs it, decide how it gets there, and keep evidence that it actually did. Then ask a few people on the floor what they know about how the QMS is performing. If they can give you a real answer, you’re in good shape. If they reach for the break-room poster, you’ve got work to do.