Template: GDP / 3PL Data Integrity Quality Agreement Addendum

This is a ready-to-use addendum that bolts the data-integrity-specific obligations onto a standard distribution or logistics quality agreement, which is usually written around handling, liability, and service levels and rarely names audit trails, raw record access, or excursion authority explicitly.

Attach it to your existing quality agreement rather than rewriting the whole agreement.

Replace every <<FILL: ...>> placeholder. A filled specimen of the key clauses follows. This content is educational and general, not legal advice; route it through your own legal and procurement functions before use.

Cover block

1. Purpose

This addendum states the data-integrity obligations that apply to any GxP-relevant record the contract acceptor creates, stores, or processes on behalf of the contract giver under the parent quality agreement referenced above.

Where this addendum and the parent agreement conflict, this addendum governs for data-integrity matters.

2. Record ownership and access

• The contract giver retains ownership of, and has the right to access, copy, and retain, all original distribution and monitoring records generated under this agreement, including raw logger data, not only summary reports or PDFs.
• The contract acceptor will provide access in the format specified: <<FILL: live system query access / periodic export / on-request within N business days>>.
• Raw records will not be deleted, overwritten, or allowed to expire before the retention period in section 7 without the contract giver’s written agreement.

3. Audit trail and system controls

• Any computerized system used to create, modify, or store GxP records under this agreement must have an enabled, unalterable audit trail covering creation, modification, and deletion events, with user identity and timestamp.
• Individual, named user accounts are required for all personnel with access to GxP-relevant systems; shared or generic logins are not permitted for any activity that creates or modifies a GxP record.
• Critical fields (lot number, quantity, ship-to address, condition/disposition status) must be role-restricted so only authorized personnel can edit them, and every edit must be captured with a reason.

4. Excursion and quality-event handling

• The contract acceptor will notify the contract giver of any temperature excursion, deviation, system failure, or data-integrity event (including a lost, damaged, or malfunctioning logger, or a corrupted or incomplete record) within <<FILL: number>> hours of discovery.
• The contract acceptor will place any shipment or lot associated with a quality event into quarantine and will not release it to saleable stock, further distribution, or disposal.
• Final disposition of any quarantined shipment or lot is the contract giver’s decision. The contract acceptor does not self-disposition a quality event.

5. Right to audit

• The contract giver has the right to audit the contract acceptor’s facilities, systems, and records relevant to this agreement, including audit trails and access-control configuration, on a routine schedule (<<FILL: frequency>>) and for cause, with <<FILL: notice period, or "no notice required for cause">>.
• The audit scope explicitly includes system-level review (pulling an audit trail, reviewing the user list for shared accounts, testing traceability of a sample lot) and is not limited to a physical facility walkthrough.

6. Subcontracting

• The contract acceptor will not subcontract any activity covered by this agreement to a further third party without the contract giver’s prior written approval.
• Any approved subcontractor is bound by data-integrity terms equivalent to this addendum, flowed down in the subcontract, and the contract acceptor remains accountable for the subcontractor’s performance.

7. Retention and return

• Records will be retained for <<FILL: retention period, e.g. product shelf life plus applicable regulatory minimum>>.
• On expiry, termination, or transition of this agreement, the contract acceptor will return or, at the contract giver’s direction, securely destroy all records, with records first confirmed transferred and readable by the contract giver before any destruction.

8. Acceptance criteria for this addendum

• Every clause has a filled, specific value; no clause is left as a placeholder in the executed version.
• The retention period in section 7 is not shorter than the applicable regulatory minimum for the product’s markets.
• The notification timeframe in section 4 is short enough that the contract giver can make a timely disposition decision.
• Legal and procurement have reviewed and countersigned before use.

9. Approvals

Filled specimen

Key clauses completed for an illustrative cold-chain 3PL relationship.

The specimen shows the addendum doing its job: the parent quality agreement covered handling and liability, and this addendum is what actually gives the sponsor a contractual right to pull an audit trail, see raw logger data, and demand a 4-hour excursion notification, none of which a generic logistics contract would include on its own.

Common inspection findings this addendum prevents

• A quality agreement that covers service levels and liability but never mentions audit trails, raw record access, or data-integrity expectations.
• No defined notification timeframe, so an excursion is discovered by the sponsor days after the fact.
• No confirmed right to audit systems, only facilities, so a shared-login or audit-trail gap goes undetected until an inspector finds it.
• Subcontracted activity with no flow-down of the same data-integrity terms, so a fourth party handles GxP records under no contractual obligation at all.

How to adapt this addendum

1. Attach to your existing quality agreement rather than renegotiating it from scratch; reference the parent agreement number in the cover block.
2. Set the notification timeframe in section 4 against how quickly your team needs to act on an excursion, not against what is administratively convenient for the 3PL.
3. Confirm the retention period in section 7 against every region the product ships to, and use the longest applicable requirement.
4. Route through legal and procurement before execution; this addendum states data-integrity obligations, not indemnification, liability, or commercial terms, which stay in the parent agreement.