Complaint Logs Are Not Quality Systems

Complaint Logs Are Not Quality Systems

A complaint log can look very official.

Rows. Dates. Statuses. Owner names. Maybe even a color code if someone got ambitious.

That does not mean the system is working.

It means the company has a list.

And a list is not control.

FDA's recent warning letter to BlephEx, LLC is a useful reminder of something quality leaders already know, but sometimes have to relearn under pressure:

Complaints are not paperwork.

Complaints are signals.

And if those signals do not connect to investigation, MDR evaluation, CAPA, root cause, corrective action, and effectiveness checks, the organization is not learning. It is just collecting evidence that it missed the point.

The Problem Is Usually Not That Nobody Cares

Most teams are not ignoring complaints because they are lazy.

They are overloaded.

Customer service is trying to calm people down. Quality is trying to classify the event. Regulatory is thinking about reportability. Operations is asking whether this is isolated or systemic. Leadership wants to know if shipments are affected, if customers are safe, and if anyone needs to be notified.

Everyone is moving.

That is the trap.

Movement can feel like progress even when the system is not actually connected.

A complaint gets logged.

A procedure gets revised.

A training record gets completed.

A CAPA meeting gets scheduled.

Then six weeks later someone asks the simple question nobody wants to answer:

"What did we learn, and how do we know the fix worked?"

Silence.

The brutal kind.

FDA Looks for the Trail

In the BlephEx letter, FDA cited complaint handling and CAPA issues, including concerns around complaint records, complaint closure, investigation decisions, MDR evaluation, and implementation of CAPA procedures.

Those details matter because they point to a bigger expectation.

FDA is not just asking whether a company has a complaint procedure.

FDA is asking whether the company can prove the procedure works in real life.

Can the team show the complaint was captured?

Was it evaluated in a timely way?

Was reportability assessed?

Was the investigation rationale documented?

Was root cause understood?

Was a CAPA opened when the signal justified it?

Was the corrective action verified or validated?

Was effectiveness checked?

And maybe the most uncomfortable question:

Would the same issue be handled the same way tomorrow?

That is where a lot of systems get exposed.

Not because the company has no documents.

Because the documents do not connect.

Procedures Do Not Run the Business

Procedures matter.

But procedures do not wake up in the morning and make good decisions.

People do.

That is why complaint handling is a leadership system as much as a quality system.

Somebody has to decide what matters.

Somebody has to escalate when a complaint stops looking isolated.

Somebody has to challenge the easy answer.

Somebody has to ask whether the CAPA is actually addressing the cause or just making the file look better.

And somebody has to make sure the team is not confusing "we trained everyone" with "we fixed the process."

Training is often necessary.

It is rarely the whole answer.

If the system design is weak, training just teaches people how to operate a weak system with more confidence.

Fantastic. Now the problem has a certificate.

The Real Test Is Connectivity

Good complaint systems connect the dots.

Not perfectly.

Not theatrically.

Practically.

A strong system can show:

• What signal came in
• How the risk was evaluated
• Why the investigation path made sense
• Whether MDR or other reporting obligations were considered
• What root cause was found or why it could not be confirmed
• What corrective action was taken
• How the team verified the action
• How effectiveness was checked over time
• Whether the issue was trending, recurring, or spreading

That is not paperwork for paperwork's sake.

That is organizational memory.

It is how a company proves it can see problems, understand them, and reduce the chance they happen again.

A CAPA Is Not a Parking Lot

One of the fastest ways to lose control is to treat CAPA like a place where hard problems go to wait.

Open CAPAs do not impress anyone.

Closed CAPAs do not impress anyone either, if they are closed badly.

The question is whether the CAPA did what it was supposed to do.

Did it address the real cause?

Did it change the process?

Did the change hold?

Did the trend improve?

Did the same complaint come back wearing a slightly different costume?

That last one is usually where the room gets quiet.

Because recurring complaints are not just repeat events.

They are feedback.

Sometimes very expensive feedback.

The Operator Takeaway

If you lead Quality, Regulatory, Operations, or the business, do not ask only whether complaint files are current.

Ask whether the system can tell the story.

Pick three recent complaints and trace them all the way through.

Not in a conference room performance.

For real.

Can you follow the signal from intake to risk evaluation to investigation to CAPA decision to effectiveness check?

Can you explain why decisions were made?

Can you show the evidence?

Can the next person find it without calling the one person who "knows where everything is"?

That is the test.

Because inspection readiness is not whether the binder exists.

It is whether the system can stand up when someone starts pulling the thread.

The Work Is Not Glamorous

Complaint handling is not flashy.

CAPA discipline is not flashy.

MDR evaluation is not flashy.

Effectiveness checks are absolutely not flashy.

But this is the work that keeps a quality system honest.

It is where leadership, process, documentation, and decision-making either come together or drift apart.

And when they drift apart, the organization may still look busy.

It may even look compliant from a distance.

But up close, the story does not hold.

The fix is not more theater.

It is connection.

Clear ownership.

Clean escalation.

Better decisions.

Evidence that follows the signal all the way through.

That is how teams move from activity to control.

And that is where the real work starts.

Website Publishing Notes

• Stage as Squarespace draft only.
• Set author to Two Pharma Guys.
• Add source URL in the post settings or internal notes if available.
• Use the hero image above and alt text exactly as provided.
• Do not publish until Micah approves.