CRA reporting develops through an early warning, a 72-hour notification, and a final report. Article 14 says the later notification and final report do not have to repeat relevant information the manufacturer already supplied.
The safe operational model is one evidence trail with three submission snapshots. A later stage should extend or correct the record without erasing what the team knew earlier.
Give every material fact a history
For each reportable fact, retain the value, source, author, recorded time, and confidence. When it changes, add the new value and explain why. Avoid replacing a product identifier, severity assessment, or mitigation status without leaving a visible correction.
Keep the submitted payload for each stage alongside its receipt or acknowledgement. A live investigation record is not a substitute for the exact content sent to the platform.
Separate four record layers
Use an evidence index for original records, a working assessment for current interpretation, an approved packet for the authorised statement, and a filed snapshot for the external event. Link them with one stable case identifier but do not overwrite one layer with another.
The evidence index should preserve source, collection time, custodian, integrity information used by the organisation, and access restrictions. The working assessment may change frequently. The approved packet changes only through a recorded review. The filed snapshot remains immutable and is linked to completion evidence.
This separation answers different questions. An investigator needs the newest evidence. A reporter needs the approved facts. A read-only auditor needs to reconstruct what the organisation knew and submitted at a particular time.
Reconcile before each submission
Before the 72-hour and final stages, review every earlier field. Mark it confirmed, updated, superseded, or still unknown. Resolve contradictions or escalate them to the named decision owner. Make sure the product and version scope remains consistent with the evidence.
Use a change register for material corrections. Capture the earlier value, current value, source of the change, reason, author, reviewer, and affected submission stage. Do not delete an incorrect early conclusion after it has been filed; show how the later evidence corrected it.
Close each stage with a manifest of the approved packet, filed content, completion evidence, deadline calculation, and open work transferred to the next owner. If a submission attempt failed, retain it as an attempt rather than relabelling it as the filed event.
This continuity makes two things possible: the reporting team can prepare the next stage without reconstructing the case, and a reviewer can see why the organisation’s position changed over time.
Continue this workflow with the incomplete-facts ledger and the stable identifier map.