Biological Evaluation Plan (BEP) Service
ISO 10993 planning support for medical device teams that need a scientifically defensible endpoint strategy, clear waiver rationale, and a submission-facing BEP that fits the actual device.
Endpoint Strategy
Risk-based endpoint planning tied to contact nature, duration, and final device configuration.
Waiver Rationale
Clear justification for endpoints addressed by existing data, chemistry, or material knowledge.
Device Representation
Materials, coatings, sterilization, packaging, and process context framed correctly from the start.
Submission-Ready Format
BEP structure designed to support EU MDR, FDA, and deficiency-response contexts.
Best for teams that need the right biological evaluation strategy before the file becomes expensive to fix
A strong BEP is where the submission path starts to become clear. It sets the device representation, endpoint logic, existing-data strategy, chemistry expectations, and the scope of any new biological testing. When that first document is weak, everything built after it is harder to defend.
First Serious Submission Program
You have a real device, known materials, and a regulatory path, but not yet a structured biological evaluation strategy.
Need to Avoid Unnecessary Testing
You want to identify where existing data, chemistry, or device knowledge can support endpoint waivers before defaulting to a broad test plan.
Materials or Design Are Still Evolving
The BEP needs to reflect the actual finished device and stay aligned with supplier, coating, process, or sterilization changes.
Current BEP Is Too Generic
You already have a draft, but it reads like a template and does not clearly explain the real endpoint logic or waiver basis.
What a serious BEP actually needs to cover
A BEP should explain why the endpoint strategy makes sense for the actual device. It should not read like a standard copied into a template.
Contact Classification
Correct contact nature and duration framing, because that decision shapes the entire endpoint table and downstream evidence plan.
Material and Process Context
Finished-device materials, additives, coatings, manufacturing state, sterilization, and packaging relevance set out clearly.
Endpoint Logic
Endpoints selected and prioritized based on actual biological hazards instead of a generic copy-paste list.
Existing Evidence Pathway
Literature, prior testing, chemistry, predicate knowledge, or material equivalence assessed as part of the plan rather than after the fact.
Waiver Justification Strategy
Endpoints that may be addressed without new testing are identified early, with the scientific basis spelled out clearly.
Reviewer-Facing Framing
The BEP is structured so it can later support the BER, the technical file, and any reviewer questions more cleanly.
Projects where BEP quality matters most
These are the situations where a good planning document usually saves the most time, testing cost, and remediation effort later.
New Class II or Class III device programs
When the first formal biological evaluation plan will shape both the testing budget and the future submission narrative.
Polymeric and coated devices
Where chemistry and toxicology questions often need to be anticipated at the planning stage.
Implants and prolonged-contact devices
Longer-contact categories need a more careful balance of endpoint expectations, existing evidence, and residual-risk framing.
Teams trying to reduce unnecessary testing
When the goal is to justify the right evidence set, not simply run every endpoint by default.
Files with inconsistent material information
Where supplier, coating, additive, or sterilization details are fragmented and need to be pulled into one coherent plan.
Legacy plans that no longer reflect the device
Where the current BEP is outdated, too generic, or no longer aligned with the actual finished device and pathway.
How a BEP scope is usually structured
The work starts with the actual device and ends with a plan that can support both execution and reviewer-facing documentation.
Review Device Inputs
Device type, materials, contact profile, process details, sterilization state, and target pathway are reviewed together.
Set the Endpoint Strategy
The likely endpoints, evidence pathways, and chemistry needs are mapped in a way that fits the device rather than a template.
Draft the BEP
The plan is written with clear justification language, reviewer-facing structure, and practical next steps for the team.
Refine and Finalize
The draft is aligned to your final device state, internal comments, and the broader submission or remediation timeline.
Questions teams usually ask before starting a BEP
Do we need all test reports first?
No. The BEP is usually created before all testing is complete. Its job is to define the evidence path and justify what should or should not be done next.
Can a BEP support test waivers?
Yes. That is one of its most important functions, as long as the rationale is device-specific and supported by the right evidence base.
Is this useful for FDA and EU MDR both?
Yes. The same underlying endpoint strategy often supports both pathways, even when the final presentation differs.
Can you revise an existing BEP instead of rewriting it?
Yes. If the current plan has the right basic structure, the work can focus on updating device framing, endpoint logic, and weak justifications instead of starting from zero.
Need a BEP that sets up the rest of the file properly?
Send the device type, materials, contact profile, pathway, and current challenge. I will review the likely scope and tell you the best next step.