ISO 10993 tells you what the biological evaluation should say. ISO 13485 governs how that evaluation is created, reviewed, approved, versioned, and changed inside the quality system.
If the BEP and BER are scientifically solid but poorly controlled, weakly approved, or disconnected from design change processes, the file can still create audit and submission problems.
One of the most common mistakes is treating biological evaluation as a technical writing exercise that lives outside the quality system. In practice, BEPs and BERs are controlled design documents whose lifecycle should reflect the same rigor as other critical development records.
ISO 13485 and Biological Safety Documentation
ISO 13485 governs how biological evaluation is planned, documented, reviewed, approved, revised, and retained. It does not replace ISO 10993, but it determines whether the biological evaluation process is being run under an acceptable quality-system structure.
Biological Evaluation as a Design Control Activity
Under design and development controls, the BEP should appear at the right stage of product development, the BER should function as a controlled design output, and any updates triggered by material, process, or indication changes should flow through the formal change process rather than informal edits.
- BEP timing: planning should happen early enough to influence study strategy and evidence planning.
- BER approval: final conclusions should be reviewed and approved under controlled workflows.
- Change-trigger handling: device changes should explicitly trigger review of whether the existing biological evaluation still applies.
- Revision history: updated rationale, new evidence, and changed assumptions should be traceable across versions.
What Good Document Control Looks Like
A controlled biological evaluation file should have clear ownership, version numbers, approval signatures or equivalent approval records, change history, and a way to identify which version was in force for a given submission or design state. That sounds basic, but it is often where the QMS breaks down.
Common ISO 13485 Audit Findings Around Biological Evaluation
- BEP or BER outside document control: missing revision history, approval trace, or controlled release.
- Weak approval logic: waiver justifications or endpoint decisions are present but not clearly reviewed by the appropriate functions.
- Missed design changes: material or process changes happen without formal reassessment of biological safety documents.
- Poor risk linkage: the biological evaluation is not visibly connected to the ISO 14971 risk-management file.
- No defined procedure: the organization lacks a clear SOP for when biological evaluation starts, who owns it, and what triggers re-evaluation.
Why This Matters Before Submission
Even when the science is acceptable, weak control over the documents can erode reviewer confidence. A file that looks current, internally coherent, and properly governed signals a stronger overall regulatory operation than one where biological evaluation appears to have been assembled ad hoc.
The Practical Role of an SOP
A simple biological-evaluation procedure can remove a surprising amount of chaos. It should define when a BEP is required, how approvals work, what evidence belongs in the BER, who reviews waiver logic, how document changes are controlled, and what events trigger reassessment.
If your team cannot quickly answer who owns the BEP, who approves the BER, what triggers re-evaluation, and where change history is controlled, the QMS layer around biological evaluation is probably too loose.
What Good Integration Looks Like
The strongest systems connect ISO 13485 process control, ISO 14971 risk logic, and ISO 10993 biological evaluation into one auditable workflow. That means the science, approvals, design history, and change triggers all tell the same story.
Need help tightening the QMS layer around your biological evaluation documents before an audit or submission?
Discuss Your Project Back to Insights