Documenting moral responsibility and retaining records

01Why document the judgment

The moral responsibility discussed in Part 2 cannot be tested as long as it stays an abstract mindset. An owner may claim to have "checked properly," but without a record of what was checked, a third party has no way to judge whether that claim is true. The absence of a record is outwardly indistinguishable from never having checked at all.

Documentation serves three functions. First, reproducibility: capturing the facts checked and the grounds so anyone reaches the same judgment. Second, explainability: being able to explain later, in an audit, regulatory inquiry, or internal incident review, why the material was cleared. Third, learning: accumulated rationale keeps judgment consistent across similar materials.

02Five things to record

The trail the owner must keep extends beyond the deliverable itself. Include every element that makes up the path from receipt to release.

Receipt-flow design was covered in Part 3 (receipt flow). This installment focuses on how to structure and retain the trail generated at each of those steps.

03A template for the judgment record

The judgment record is the core of the trail. At minimum, fit the following on a single sheet. A fixed format keeps record quality steady even when the decider changes.

• Material ID / name / version — uniquely identify which deliverable is being judged
• Vendor / order number — link the producer to the order
• Items checked and results — clear/hold against Pharma Act applicability, ad standards, the MSA guidelines, and code compliance
• Findings and remediation status — points raised in verification and their resolution
• Judgment — clear / conditional / returned
• Rationale — why this judgment was reached (1–3 free-text sentences)
• Decider, date, signature — locus of responsibility

04How to write "why it was cleared"

When the rationale becomes hollow, the whole record stops working. Conclusion words alone — "checked," "appropriate" — turn the substance of the check into a black box. Write the rationale as a bridge between the facts checked and the norm referenced.

Concretely, fit three points into one sentence: (1) what was checked (target), (2) which standard it was tested against (norm), and (3) the resulting judgment (conclusion). "The efficacy statement (target), tested against the approved scope and the Standards for Fair Advertising (norm), shows no deviation (conclusion)" lets a third party re-verify from the same material.

On points open to differing readings, address the interpretation you did not adopt. "There is room to read it as suggesting comparative superiority, but the trial conditions stated alongside mean it does not amount to exaggeration (Pharma Act §66)" shows the judgment was made with the issue in view. This is precisely what future inquiries probe hardest.

05Retention — period, medium, access

A record is not finished when made. It becomes a trail only when it can be retrieved when needed and is assured against tampering. Decide retention along three axes.

06Preparing for audit and regulatory inquiry

Regulators and auditors do not ask only about the polish of the deliverable. They ask by what process you reached the decision to release it. What you can present at that moment is the trail built up in this installment.

Three failures typically stall an inquiry: (1) inability to identify which version went to review, (2) no record of the facts checked, and (3) rationale consisting of conclusion words only. All are prevented by fixing the record format and rigorously linking from the point of receipt. Reconstructing records after an inquiry arrives is close to back-filling an absent trail, and it erodes credibility.

1. From the material ID under inquiry, can you instantly bundle and present receipt, verification, judgment, basis, and change history?
2. Does the rationale read as a bridge between facts checked and norms referenced?
3. Is the record's creation timestamp consistent with the judgment moment, with no sign of after-the-fact alteration?

07Connecting to the vendor's trail

The owner's record becomes a full picture only when joined to the vendor's quality records. The vendor-side production, proofing, and check trails covered by the sister series "Production Quality Management" become inputs to the owner's verification record. The owner does not take them at face value but separately records the facts re-verified from its own vantage point.

Agreeing at the contract stage on the scope and handover format of the trail the vendor must keep makes post-receipt connection smoother. This links to Part 9 (contracts and the responsibility boundary) (in preparation).

08Making records a culture

Even with a tidy format, records go hollow if they decay into "paperwork to pass review." The rationale becomes copy-and-paste every time and drifts from the reality of the check. What prevents this is operating with the record as part of the judgment itself.

The decider writes the rationale in their own words. Findings and fixes are kept, not skipped. Points where judgment was split are written honestly. These take effort — and that effort is the very evidence of accepting moral responsibility. The quality of the record mirrors exactly how seriously the owner engaged with the material.

The series comes down to one thing. Even when production is delegated, responsibility for the released material stays with the owner. The final means of making that responsibility visible is the record. It makes past judgment explainable into the future and turns the owner's judgment into an asset of the organization.