Biological Evaluation Plan (BEP) for Medical Devices

What a Biological Evaluation Plan Is

The Biological Evaluation Plan, usually shortened to BEP, is the document that sets the biological evaluation strategy under ISO 10993. It should define how the finished device will be represented, which endpoints matter, what evidence already exists, where new testing might be needed, and where test waivers or chemistry-based reasoning may be appropriate.

That means a BEP is not the final conclusion document. It is the planning document that should make the later Biological Evaluation Report (BER) easier to defend instead of harder to repair.

What a BEP Needs to Do Under ISO 10993

A strong BEP usually needs to do five things well:

• Describe the actual finished device: not a vague summary detached from coatings, sterilization, packaging, manufacturing, or real patient-contact conditions.
• Classify contact correctly: because endpoint selection only makes sense if contact nature and duration are framed correctly from the start.
• Set a defendable endpoint strategy: including which endpoints need direct support, which may rely on existing evidence, and where chemistry or toxicology may drive the logic.
• Explain waiver or evidence logic clearly: especially when the plan relies on literature, prior testing, material history, or extractables and leachables reasoning.
• Stay aligned with the wider file: the BEP should support risk management, chemistry, supplier reality, and the regulatory pathway rather than living as an isolated document.

What Reviewers Usually Notice First

Reviewers often spot BEP weakness before they even start debating test data. Weak plans tend to show one or more of these patterns:

• endpoint tables that look copied from a standard without device-specific reasoning
• contact classification that does not fully reflect the actual finished device or intended use
• waiver statements without clear scientific support
• chemistry or toxicology assumptions that are never defined up front
• device changes, sterilization changes, or supplier changes that the plan no longer reflects

Where Teams Commonly Get Stuck

Many teams know the device well but still struggle to convert that knowledge into a structured BEP. The problem is often not lack of effort. It is the missing bridge between device reality, ISO 10993 endpoint logic, chemistry expectations, and reviewer-facing wording.

Product-specific files can also contain more than one exposure route. The medical-wipe BEP template structure, for example, shows how patient contact, applicable user exposure, wipe chemistry, transferred residues and a processed device may need separate but connected evaluation logic.

Another common problem is timing. A weak BEP can look survivable early, but later it creates BER gaps, chemistry misalignment, or reviewer questions that are much more expensive to fix once the file is already moving. Use the free BEP–BER evidence traceability diagnostic when the immediate concern is whether planned questions still connect to executed evidence and report conclusions.

When You Need BEP Drafting vs BEP Review

If the plan does not exist yet, or the current draft is too generic to repair efficiently, the right path is usually the BEP drafting service. That is the fit when the strategy needs to be structured clearly from the device and evidence base upward.

If a draft already exists and the main question is whether the contact logic, endpoint strategy, waiver rationale, or reviewer-facing structure are strong enough, the better fit is often the BEP review service. That is the faster path when you need a specialist check before submission or before more internal drafting time is spent.

When the Problem Is Broader Than the BEP

Sometimes the plan is not the only issue. The real weakness may span the BEP, BER, TRA, chemistry rationale, reviewer comments, and the wider submission narrative together. When that is the case, it is usually better to start with a submission gap review or the broader biocompatibility consulting overview instead of treating the whole file as if it were just a BEP question.