Your Yard Is the Least-Governed Part of Your GxP Supply Chain

There is a line at every pharmaceutical site where governance quietly stops. Inside the warehouse door, every movement of every pallet is on a validated system with an audit trail, a signature and a retention period. Step outside, and the same product sits in a trailer for four hours in a yard where the authoritative record is a paper book, a WhatsApp message to a supervisor, and a driver's word about what the reefer was reading when he set off.

That line used to be invisible. It is not any more. Questions about seal integrity, temperature at the yard boundary, contemporaneous gate records and carrier qualification now turn up in the same conversation as batch documentation — and the honest answer at most sites is a description of a process rather than a record.

Why the yard is where the chain breaks

Three structural reasons, none of them anybody's fault:

• The yard was never anybody's system. The WMS owns inside. The TMS owns the road. The gate owns the barrier — usually with a clipboard. Nobody's validated system covers the ground in between, so the records that get created there are informal by default.
• The evidence is perishable. A seal is only evidence if an expected number existed beforehand and someone compared it. A temperature is only evidence if it was read before the vehicle was accepted. Both facts have a shelf life of minutes, and if they are not captured at the barrier they cannot be reconstructed afterwards.
• The people at the boundary are not quality people. A gate operator managing a queue of six trucks in the rain is not thinking about ALCOA+. If capturing the record is not the fastest way to do the job, the record loses.

So we wrote the checklist we wanted to have

We build yard-management software for GMP sites, so we had to work this boundary out clause by clause for our own quality system — an Annex 11 and 21 CFR Part 11 implementation, a validation approach, a data-integrity policy. Along the way it became obvious that no single document walked the *yard* against that guidance. Everything published assumes you are validating a warehouse system. So we wrote the yard version.

It is 101 checks across 12 domains, each mapped to EU GMP Annex 11, 21 CFR Part 11, the EU GDP guidelines or the MHRA data-integrity guidance. Every check has Yes / Partial / No columns and an evidence column, because the useful question is never "do you do this" — it is "could you put the evidence in front of someone within the hour".

The twelve domains: vehicle and visit records · seal integrity and tamper evidence · temperature-controlled handling at the yard boundary · driver and carrier qualification · documentation control at the gate · electronic records and electronic signatures · audit trail and ALCOA+ · access control and segregation of duties · computerised-system validation and change control · deviation, incident and CAPA handling · retention, archive and retrieval · and supplier qualification of your yard system vendor.

Four checks worth doing before you download anything

If you only have ten minutes, walk to the gate and test these four. They are the ones that most often come back Partial, and each is cheap to fix now and expensive to fix retrospectively.

Is the gate terminal on a shared login? If the answer is yes, every record that account has ever created is unattributable — retroactively, with no remediation available for the history. This is the cheapest fix on the list and the most damaging omission.

Did an expected seal number exist before the truck arrived? Verifying a seal against nothing is theatre. The expected value has to come from the booking or the despatch advice, and the comparison has to be recorded with an outcome.

When was your audit trail last reviewed? Annex 11 §9 expects the trail to exist *and* to be reviewed, with a defined scope and frequency. "We can pull it if there's a problem" is a different sentence from "we review it", and an inspector will hear the difference.

Has anyone signed the §11.100(c) certifications? If your team applies electronic signatures to release decisions, the FDA expects a written certification that those signatures are the legal equivalent of handwritten ones. It is a one-off administrative task, it takes an afternoon, and it is almost universally skipped.

What software can and cannot fix

Being straight about this matters more to us than a longer list of features. Most of the checklist is process and evidence, and it is yours: no platform creates a carrier qualification file, signs a Part 11 certification, or reviews an audit trail on your behalf.

But several of the domains are structural — properties of the system you run the yard on, not of how diligently your team uses it. Contemporaneous capture at the barrier rather than at end of shift. Attributability without shared logins. A seal chain that lives in one record instead of three systems. An audit trail that no administrator can switch off. A vendor who can evidence their own compliance position rather than assert it. Those you either have or you don't, and no amount of discipline compensates.

Domain L is the one people find most uncomfortable, because it points at the vendor. It asks whether you hold a documented supplier assessment of your yard system provider, whether they can produce a QMS index and a GAMP categorisation, whether their certification status is known rather than assumed, and whether data residency is contractually stated and technically enforceable.

We publish our own answers to all of it. The YARDtwin Vendor Assurance Pack is a free download with no form — including a full list of the controls we do not yet have.