Common BEP Mistakes That Trigger Reviewer Questions

Why reviewers focus so much on the BEP

The BEP is not just an administrative precursor to the BER. It is the document that shows whether the biological evaluation was actually planned around the finished device, the true patient-contact profile, the likely hazards, and the evidence pathway that will be used to address each endpoint. If that planning document looks weak, the rest of the file starts under pressure.

Mistake 1: Contact classification is stated, but not really justified

A surprising number of BEPs list contact type and duration without showing how those conclusions were reached. That usually means the endpoint strategy rests on a fragile base from the first page onward.

What this looks like in practice

• The contact category is copied from a previous device without checking whether the intended use really matches.
• Duration language is broad or contradictory.
• The device description does not clearly explain where, how long, and in what condition the patient-contacting part is used.

If the contact classification is weak, the endpoint table will almost always be questioned too. That is why the first useful cross-check is often the contact-classification logic, not the endpoint list itself.

Mistake 2: The BEP does not represent the finished device clearly enough

Reviewers do not evaluate an abstract product concept. They evaluate the finished device state that reaches the patient. When the plan is vague about materials, additives, coatings, sterilization, packaging, or process-relevant residue sources, the endpoint strategy starts to look disconnected from the real device.

• Material names are too broad to be useful.
• Coatings or adhesives are omitted because they look secondary.
• Sterilization is named but not connected to possible chemistry or residue implications.
• Packaging or process changes that affect the final state are left out.

A strong BEP makes the finished-device representation visible enough that the endpoint strategy feels inevitable, not improvised.

Mistake 3: The endpoint table looks copied from a template

This is one of the fastest ways to trigger reviewer skepticism. If every endpoint appears by default, with no clear prioritization or scientific logic, the plan looks like a standard checklist rather than a device-specific evaluation strategy.

Typical warning signs

• Endpoints are listed with no explanation of why they apply.
• The plan does not distinguish between endpoints likely addressed by testing versus existing data or chemistry.
• No line of reasoning connects the materials, contact profile, and biological risks to the selected endpoints.

The goal is not to make the table look shorter. The goal is to make every endpoint decision look scientifically grounded.

Mistake 4: Waiver language is asserted, not argued

A weak BEP often says an endpoint will be waived, but does not explain what evidence will actually support that waiver when the file is reviewed later. That creates a gap between the planning language and the evidence path the team will eventually need to defend.

• Existing data is mentioned, but not described.
• Chemical characterization is assumed rather than scoped.
• Literature is referenced generically, with no relevance conditions.
• The BEP does not say what type of scientific rationale will connect the device to the waiver.

The right planning question is not just "Can this endpoint be waived?" It is "What exact evidence path will make that waiver credible later?"

Mistake 5: Chemistry and toxicology triggers are missing from the plan

Even when teams know that chemistry or TRA may matter, the BEP sometimes treats those activities like optional later tasks rather than part of the planning logic. That can make the file look incomplete when the endpoint strategy depends on chemistry-driven reasoning.

A better BEP shows where chemical characterization, toxicological review, or exposure logic may become central to the evaluation path. It does not need to present final conclusions yet, but it should show that the planning logic already anticipates them.

Mistake 6: The BEP is not aligned to the real regulatory path

Sometimes the science is mostly fine, but the plan is still weak because it reads like it was written for a different market, a different device version, or an earlier stage of the program. That usually happens when a legacy BEP is reused without checking whether the intended route and file context are still the same.

• The text reads like an EU MDR plan with FDA language added later.
• The plan does not reflect how the eventual summary or technical-file presentation will be structured.
• The regulatory path changed, but the BEP did not.

That does not mean the science must change completely. It means the plan should be written so the evidence pathway still makes sense in the file the reviewer will actually read.

Mistake 7: The BEP is not updated after meaningful device changes

Even a well-written plan becomes weak if it no longer matches the device. Supplier changes, formulation changes, new coatings, sterilization adjustments, process changes, or packaging changes can all make the original planning logic incomplete.

When those changes happen, the BEP should be reviewed and updated rather than left in place as a historical artifact. Otherwise the file starts to look internally inconsistent before the BER even begins to explain the evidence.

A fast self-check before the file moves forward

• Does the device description clearly represent the finished patient-contacting configuration?
• Is the contact classification obviously linked to the intended use?
• Does each endpoint look device-specific rather than copied from a template?
• Is there a credible planned evidence path behind every proposed waiver?
• Does the plan show where chemistry or toxicology may become important?
• Does the document still match the current device version and pathway?

What to do if the current BEP already has these problems

Not every weak BEP needs to be thrown away. In many cases, the core structure is usable and the real task is to repair the device representation, clarify the endpoint logic, and make the waiver pathway more explicit. That is exactly where a focused gap review is often the fastest first step.