Independent and not affiliated with the FDA, MHRA, ISPE, PDA, or any agency. Get the appgoutham@madhadi.com
madhadi.comData Integrity & GxP Quality
Browse all topics → Articles Templates & Procedures Learning paths GlossaryScenariosToolsRegulatory ReferencesLearning PathsTopics About Start here
Checklist Plug-and-play starting point Supply Chain & GDP

Checklist: 3PL and Distributor Data Integrity Audit

A plug-and-play audit checklist for assessing a third-party logistics provider or distributor on distribution-record data integrity, system audit trails, logger governance, and excursion authority, with the weak and strong answers to listen for and a filled specimen.

Document type: Checklist

Read and copy the template below into your own quality system. It is a generic starting point for your own internal use, provided as is, with no warranty; see the Terms and License. Adopting it does not by itself create compliance.

This is a ready-to-use audit checklist for a third-party logistics provider (3PL) or distributor, focused on data integrity rather than only the warehouse walk. Use it on qualification and for-cause audits. Mark each item Pass, Fail, or N/A, record the evidence, and route Fails to your finding-classification process. A filled specimen follows. The point of this checklist is to get past the dock: a spotless warehouse can still run on shared logins and editable temperature records.

How to use

  • Sit at the WMS and the monitoring portal, do not rely on a presentation. Pull real records.
  • For each item, capture the actual answer or evidence, not just a checkbox.
  • Treat any Attributable, Original, or Accurate failure as high priority; these break the whole record set.

Section A: Quality system and contract

#ItemPass / Fail / N/AEvidence / answer
A1GDP authorization / registration current where applicable<<FILL>>
A2A written quality / technical agreement exists and addresses data integrity (record access, audit trails, excursion authority, notification, retention)<<FILL>>
A3No onward subcontracting of regulated activity without sponsor approval and flow-down of terms<<FILL>>

Section B: Attributable (who did what)

#ItemPass / Fail / N/AEvidence / answer
B1WMS and monitoring portal use individual named accounts; no shared or generic logins, including night shift<<FILL>>
B2Pull the user list; confirm leavers are deactivated and access is role-based<<FILL>>
B3Custody handoffs identify a person or a scan tied to a controlled device, not “picked up by courier”<<FILL>>

Section C: Audit trail and edit control

#ItemPass / Fail / N/AEvidence / answer
C1Critical fields (lot, quantity, ship-to, condition status) are audit-trailed with user, time, old and new value, and reason<<FILL>>
C2Pull a real audit trail entry on a changed ship-to or lot field and confirm it is complete<<FILL>>
C3Excursion alarms cannot be deleted or silently acknowledged; acknowledgment is attributable and reasoned<<FILL>>

Section D: Logger governance (Original and Accurate)

#ItemPass / Fail / N/AEvidence / answer
D1Raw logger data is retained and exportable; the summary report is derived from it, not the only record<<FILL>>
D2Reusable loggers have a recalibration interval and a control to pull out-of-interval units; ask to see a current certificate<<FILL>>
D3A courier cannot stop and restart a logger without the stop being recorded; the original profile is preserved<<FILL>>
D4Logging interval is fine enough to bound an excursion duration for the products handled<<FILL>>
D5Logger serial on the dispatch record is reconciled against the serial read out at receipt<<FILL>>

Section E: Excursion authority (independence)

#ItemPass / Fail / N/AEvidence / answer
E1The 3PL quarantines a breached shipment but does not self-disposition; sponsor QA decides<<FILL>>
E2Review a recent excursion and confirm sponsor QA, not the 3PL, made the release / reject call<<FILL>>
E3Excursion and data-integrity events (lost logger, corrupted record) are notified to the sponsor within the agreed timeframe<<FILL>>

Section F: Traceability and retention

#ItemPass / Fail / N/AEvidence / answer
F1Run a live traceability test: pick a random lot and trace receipt to dispatch from records alone; time it<<FILL>>
F2Records (including raw logger files) are retained for the required period and remain retrievable, including from a retired platform<<FILL>>
F3The sponsor has the right and the means to access and copy original records<<FILL>>

Signoff

FieldEntry
3PL / distributor<<FILL>>
Site / systems audited<<FILL>>
Audit type (qualification / periodic / for-cause)<<FILL>>
Findings raised (count, by priority)<<FILL>>
Lead auditor (name, signature, date)<<FILL>>
QA approval (name, signature, date)<<FILL>>

Reference: weak versus strong answers to listen for

You askWeak answer (finding)Strong answer
Who edited this ship-to field?”We don’t track that”Audit trail entry: user, time, old value, new value, reason
Do operators share the WMS login at night?”Yes, one shared account”Individual named accounts, role-based
Can a courier stop and restart the logger?”Yes, it just starts a new file”Stop is recorded; original profile preserved and flagged
Where is the raw logger data?”We keep the summary PDF only”Raw data retained and exportable; summary derived from it
Who released this excursion shipment?”Our shift lead released it”Sponsor QA dispositioned; the 3PL only quarantined

References

EU GDP (2013/C 343/01), Chapter 7 (Outsourced activities) and Chapter 4 (Documentation). MHRA GxP Data Integrity Guidance; PIC/S PI 041 (GMP/GDP data integrity). 21 CFR Part 11 / EU GMP Annex 11 for electronic distribution and monitoring systems.

Confirm current versions before relying on this checklist.


Filled specimen

Section B and the signoff completed for an example qualification audit. Illustrative only.

#ItemPass / Fail / N/AEvidence / answer
B1Individual named accounts; no shared loginsFailNight-shift WMS used a shared “warehouse1” account; no individual attribution
B2User list reviewed; leavers deactivated; role-basedPassList current; two leavers deactivated on exit
B3Custody handoffs identify a person / controlled scanPassDriver badge scan at each handoff
FieldEntry
3PL / distributorNorthCold Logistics, Lane EU-NE
Site / systems auditedWMS, cold-room monitoring portal
Audit typeQualification
Findings raised2: one major (B1 shared login), one minor (D2 one logger near interval end)
Lead auditorA. Patel, signed, 16 Jun 2026
QA approvalR. Gomez, signed, 17 Jun 2026

The shared night-shift login (B1) is the classic distribution data-integrity finding: it breaks Attributable for every record touched on that shift, so it was raised as major and the qualification was made conditional on individual accounts before go-live.

Common inspection findings this checklist surfaces

  • Shared logins at the 3PL, breaking attribution for the whole record set.
  • Only summary reports retained, with raw logger data unavailable.
  • The 3PL self-dispositioning excursions the sponsor should decide.
  • A quality agreement silent on data integrity, discovered only for-cause.

How to adapt this checklist

  1. Add lane- or product-specific rows (ultra-cold, controlled substances, DSCSA-scope handling).
  2. Tie the finding-priority scheme to your audit finding classification procedure.
  3. Where a 3PL serves multiple sponsors, confirm segregation of your records and access.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.