Electronic Records and Traceability

Digitising a paper quality form is often the first step manufacturers take toward electronic records, and it’s frequently mistaken for the finish line. A digital form that can be edited freely after submission, with no record of who changed what or when, isn’t a compliant electronic record — it’s a paper form’s problems, still present, just harder to visually inspect for evidence of tampering.

The Standard Regulators Actually Apply

Most electronic record integrity expectations — in pharma explicitly, and increasingly referenced across food, automotive, and general quality management — trace back to a common set of principles, often abbreviated ALCOA+:

Attributable — every record entry tied to a specific person or system that created it, not an anonymous or shared login.

Legible — readable and understandable, for the life of the record, not dependent on a specific piece of software that may not exist in five years.

Contemporaneous — recorded at the time the activity actually happened, not reconstructed or backdated afterward.

Original — the first, genuine capture of the data, not a copy or a transcription that introduces the possibility of transcription error.

Accurate — correct, complete, and reflecting what actually happened.

The “+” extends this to Complete, Consistent, Enduring, and Available — the record has to be retrievable in full, formatted consistently, retained for the required period, and accessible when requested, not just theoretically existing somewhere in an archive.

A record that fails any one of these — an entry made three days after the activity and dated as if it were contemporaneous, for example — is a data integrity finding in a regulated audit, independent of whether the underlying information happens to be correct. Auditors treat the integrity of the record-keeping process as a distinct question from the accuracy of any individual entry.

What This Means for System Design

Capture at the point of activity, not after. A system that only allows entry in real time, or flags entries made significantly after the fact, protects the “contemporaneous” principle by design rather than depending on user discipline alone.

Attribution tied to individual credentials. Shared logins or generic station accounts break the “attributable” principle — every record needs to trace back to a specific, individually authenticated person or system.

Audit trails that capture changes, not just current state. If a record can be edited, the system needs to log who changed it, when, what it said before, and — ideally — why, rather than silently overwriting the original value. This is what makes a record tamper-evident rather than simply electronic.

Electronic signatures where approval is actually required. Batch release, deviation approval, and similar decision points typically need a genuine electronic signature — not just a name typed into a field — meeting the same non-repudiation standard a handwritten signature was meant to provide.

Where This Connects to Broader Traceability

Electronic record integrity isn’t a separate initiative from the traceability work covered in Designing End-to-End Product Traceability — it’s the integrity layer that makes the traceability record trustworthy to a regulator, not just complete. A perfectly connected traceability chain built on records that can be silently edited after the fact doesn’t actually satisfy the audit standard, even though it might look complete on the surface.

Records Designed for Integrity, Not Retrofitted for It

Electronic record integrity is far easier to build in from the start than to retrofit onto a system that was designed for convenience first. SG2’s Manufacturing & Industry 4.0 practice designs quality and traceability capture against the ALCOA+ standard from day one — particularly for Pharma and other regulated environments where this isn’t optional — rather than treating data integrity as a compliance layer added after the system is already built.