ALCOA+ supports bench data integrity by defining what every recorded value has to be: attributable, legible, contemporaneous, original, accurate, complete, consistent, enduring and available. In a pharma QC lab it only holds at the bench when those attributes are built into the work itself. That means results captured directly from the instrument, analysts guided through the approved procedure, and records that are audit-ready as they are created. Manual transcription and after-the-fact review are where it most often fails.
Ask anyone in a pharmaceutical QC lab about ALCOA+ and they will spell out the acronym without hesitating. Ask how it is guaranteed for a single weighing on a busy Tuesday afternoon, and the answer gets less certain. It depends on the analyst, the worksheet, the printout and, eventually, the reviewer.
That gap is what this article is about. ALCOA+ is well understood as a principle. Making it hold at the bench, every time, for every value that ends up on a certificate of analysis, is a different matter.
ALCOA+ describes nine attributes of trustworthy data. The original five, ALCOA, are attributable, legible, contemporaneous, original and accurate. They are about how a value is recorded. The four additions, complete, consistent, enduring and available, are about what happens to it afterwards: whether it is kept in full and in sequence, survives the retention period, and can be found again when QA or an inspector asks for it.
The FDA’s 2018 guidance on data integrity and compliance with drug CGMP expects CGMP data to be ALCOA. PIC/S PI 041-1 (2021) and the WHO guideline on data integrity (TRS 1033, Annex 4, 2021) spell out the four additional attributes, and the MHRA’s GxP data integrity guidance makes clear that its expectations are the same whichever acronym you use.
None of this is new. What has changed is where inspectors look. The final record still matters, but so does the route a value took from the instrument to the certificate of analysis, who touched it along the way, and whether anything would have caught a mistake.
In most labs the problem is not intent. It is hand-offs. Take a typical assay. The analyst reads a weight from the balance, writes it on a worksheet, types it into LIMS or a spreadsheet later, a formula turns it into a concentration, and a reviewer checks the lot. Each of those steps is a place where one of the principles can slip.
The cost is not only compliance risk. Because the process can’t be trusted on its own, QA checks everything by hand. That takes time and money, and problems still surface late.
Three things move ALCOA+ off the training slide and into the work itself.
Connect the balance, pH meter, titrator or spectrophotometer, and let the result go straight into the workflow along with the instrument ID, calibration status, timestamp and unit. Nobody types it, so nobody can mistype it. It also settles a question that comes up in almost every data integrity discussion: which record is the original?
Turn the SOP into steps on a screen at the bench. The analyst signs in. Before the weighing starts, the system has already checked that the balance is calibrated and the reference standard is in date. Steps run in the approved order, and a value outside its limits is flagged while the analyst is still at the bench, not three days later in review. Attribution, consistency and completeness no longer depend on memory.
If every action is time-stamped, tied to a named user and stored in a controlled system, the record is created as the work is done. Changes need a reason and keep the old value. Audit trails can be searched. This is what lets QA move to review by exception: look closely at what the system flagged instead of re-checking every line.
If you want a checklist, here it is: each principle, the question it raises at the bench, and how a connected workflow answers it.
| Principle | The question at the bench | How a connected workflow answers it |
|---|---|---|
| Attributable | Who did it, and on which instrument? | Personal logins and e-signatures on each step; instrument ID recorded automatically |
| Legible | Will someone understand it in five years? | Structured records with units, method and context. No handwriting to decipher |
| Contemporaneous | Was it recorded when it happened? | Timestamp set at the moment of capture, not when someone gets round to typing it in |
| Original | Is this the first capture? | The value comes straight from the balance or meter and is stored as the original record |
| Accurate | Is it right, and are changes justified? | No transcription; limits checked in the step; edits need a reason and keep the old value |
| Complete | Is anything missing? | Repeats, failed runs and aborted steps stay in the record |
| Consistent | Was the approved sequence followed? | The guided SOP enforces the order; deviations are flagged and documented |
| Enduring | Will it last the retention period? | Controlled, backed-up storage rather than printouts and local files |
| Available | Can QA and inspectors find it? | Searchable records and audit trails |
Weighing is a good place to start. It happens constantly, and the result feeds straight into the assay calculation that decides whether a batch is released.
On paper, integrity depends on the analyst writing the right number in the right place at the right time, and on the reviewer spotting it if they don’t. In the connected version the chemistry is exactly the same. The weight comes directly from the balance, is linked to the analyst, sample and standard lot, is checked against tolerance and goes into a validated calculation. The reviewer opens a complete record with the exceptions already highlighted.
Good data integrity shouldn’t depend on someone having a good day.
This doesn’t need a big programme. Pick one method, get it right, then copy the pattern. If you are still deciding which system should own bench execution, our decision guide on LIMS, ELN or LES compares the options for regulated labs.
The regulatory direction points the same way. On 7 July 2025 the European Commission opened a consultation on revised EU GMP Chapter 4 and Annex 11, together with a new Annex 22 on AI. The draft Annex 11 says data transfer should, where possible, be based on validated interfaces rather than manual transcription, and expects audit trail review before batch release unless a later review can be justified. The final texts had not been published at the time of writing, but taking manual hand-offs out of the process now is unlikely to be wasted effort.
ALCOA covers five attributes: attributable, legible, contemporaneous, original and accurate. ALCOA+ adds complete, consistent, enduring and available, which deal with the rest of the data lifecycle rather than the moment of recording. Some guidance goes a step further. The EMA’s 2023 guideline on computerised systems and electronic data in clinical trials lists ten attributes, adding traceable, which is often called ALCOA++. That guideline is written for clinical trials, but the idea applies just as well in a QC lab.
What are the most common ALCOA+ failures in a QC lab?Most come from manual hand-offs rather than bad intent: values transcribed from an instrument display or printout, entries made after the fact, shared logins, unvalidated or unlocked spreadsheet calculations, users with rights to delete or alter raw data, and repeat or failed runs that never make it into the record. Each one breaks a specific attribute, usually original, contemporaneous, attributable or complete.
Is a balance printout an original record?It can be, as long as it is the first capture and is reliably linked to the sample, the analyst and the time. The trouble is that printouts get separated, reprinted or stuck in later. Capturing the value directly from the instrument, with its metadata, removes the ambiguity. Either way, decide per method what the original record is, and write it down.
Does ALCOA+ mean we have to go paperless?No. The principles apply to paper and electronic records alike. In practice, though, paper-based bench work leans heavily on the analyst’s discipline and on review after the fact. Connected, guided workflows take a lot of that weight off people.
How does ALCOA+ relate to 21 CFR Part 11?They answer different questions. ALCOA+ describes the attributes trustworthy data must have. 21 CFR Part 11 sets the FDA’s requirements for the electronic systems that hold that data, including system validation, access controls, secure time-stamped audit trails and electronic signatures. A system that meets Part 11 gives you the controls; ALCOA+ is what those controls are meant to protect. For how this works in practice, see 21 CFR Part 11 workflows in LabOperator.
How does ALCOA+ relate to the EU GMP Annex 11 revision?The European Commission’s consultation on revised Chapter 4 and Annex 11, together with a new Annex 22 on AI, ran from 7 July to 7 October 2025. The draft Annex 11 refers to ALCOA+ directly, asks for data transfer to be based on validated interfaces rather than manual transcription where possible (section 10.2), and expects audit trail review before batch release unless a later review can be justified (section 12.8). The final texts had not been published as of October 2026, so check the adopted version for your own obligations.
ALCOA+ isn’t new. What is changing is how labs meet it: less documenting after the fact, more building it into each step. That is what LabOperator is for. It connects lab instruments, guides analysts through approved workflows and produces records that are ready for review. If you’d like to see what that looks like for one of your own methods, get in touch.