A protocol-to-eCRF traceability matrix connects each required assessment to the exact form and field used to record it. It should also document timing, source provenance, data checks and analysis use so missing capture is discovered before build or first patient.
Reusable decision and evidence template
Begin with the most consequential control and the evidence needed to resolve it. The following matrix connects each decision to records and an accountable action, rather than treating the list as a generic compliance checkbox.
| Control / question | Evidence to examine | Sponsor action |
|---|---|---|
| Protocol requirement | Section, assessment, endpoint and schedule line | Assign stable traceability ID |
| Capture location | eCRF form/field, visit and conditional logic | Verify each requirement has a home |
| Origin and owner | Site source, central lab, ePRO or safety provider | Avoid conflicting authoritative sources |
| Validation and use | Edit check, coding, SAP/analysis variable | Test that recorded data supports decision |
| Change history | Amendment ID, impacted fields, regression test and approval | Keep traceability current |
For teams that need support implementing this across functions, BioBoston CRO eCRF Design and Review can help adapt the controls to the study, vendors, and decision calendar.
Working through the controls
1. Protocol requirement
Evidence: Section, assessment, endpoint and schedule line. Decision: Assign stable traceability ID. Record the responsible function and the approved source version, and keep any remaining exceptions visible to the sponsor before this item is closed.
2. Capture location
Evidence: eCRF form/field, visit and conditional logic. Decision: Verify each requirement has a home. Record the responsible function and the approved source version, and keep any remaining exceptions visible to the sponsor before this item is closed.
3. Origin and owner
Evidence: Site source, central lab, ePRO or safety provider. Decision: Avoid conflicting authoritative sources. Record the responsible function and the approved source version, and keep any remaining exceptions visible to the sponsor before this item is closed.
4. Validation and use
Evidence: Edit check, coding, SAP/analysis variable. Decision: Test that recorded data supports decision. Record the responsible function and the approved source version, and keep any remaining exceptions visible to the sponsor before this item is closed.
5. Change history
Evidence: Amendment ID, impacted fields, regression test and approval. Decision: Keep traceability current. Record the responsible function and the approved source version, and keep any remaining exceptions visible to the sponsor before this item is closed.
Red flags that should change the plan
- Requirements mapped only at form level.
- Derived endpoints with missing source components.
- Amendment updates not reflected in traceability.
Decision gate and governance
Choose a critical endpoint and reconstruct its path from protocol text through collection, transfer, analysis and final interpretation. The control owner should record the decision, evidence version, date, residual uncertainty and next re-review trigger. Where delegated providers perform the work, the sponsor should retain the relevant oversight and acceptance evidence.
Regulatory note: Determine which electronic records and signatures are regulated before applying 21 CFR Part 11 controls; FDA guidance supports risk- and intended-use-based implementation.
Need practical support?
Use BioBoston CRO eCRF Design and Review to review the evidence, define decision rights, and build a study-specific action plan for the next milestone.
