The receipt-process end-to-end flow

01"Taking delivery" is not "accepting"

In everyday use the words blur together, but for the owner's accountability they are distinct. Delivery acceptance means a file has physically and formally arrived in your hands. Formal acceptance means you, the owner, have confirmed the deliverable meets the order specification and regulatory requirements, and you declare yourself answerable for that judgment. The first is clerical. The second is adjudication.

As argued in installment 2, "Where moral responsibility remains," outsourcing production to a vendor does not move the responsibility for what you put into internal review and out into the world. Process receiving as clerical work and the moment for shouldering that responsibility disappears. Design receiving as adjudication and the moment to discharge it is created. This article makes that moment visible as a flow.

02The whole flow — five gates

Design the path from receiving to filing for internal material review as five gates. Each gate has an input (what you receive), checks, an artifact (what you keep), and a pass condition. You cannot advance without clearing the prior gate. Receiving thus becomes a sequence of verification points, and you can always trace where it stopped.

Note that the G3 regulatory screening does not replace internal material review. The owner's first-pass screening exists to stop obvious deviations before review and to hand the review function a clear statement of what the owner has and has not verified. Final conformance rests with the review function and the supervising pharmacist.

03G0: Intake & identification — fix what arrived

The first gate is unglamorous, but skip it and everything downstream wobbles. Establish which order, and which version, the deliverable corresponds to. Verifying against an ambiguous version and later discovering it was a different one is a common, avoidable waste.

• Match the PO/SOW number to the deliverable
• Record version, delivery date, and vendor contact
• Confirm attachments are present: source list, reference PDFs, the vendor's own check records, revision history

Do not accept a deliverable missing its attachments, above all the vendor's check records and source list. In the sister series "Production Quality Management" these are positioned as artifacts the vendor must prepare. The owner is entitled to demand them as a given. If they are missing, that is legitimate grounds to halt receiving.

04G1: Formal conformance — match against the order spec

At G1 you confirm the deliverable meets the items agreed in the SOW. This gate looks not at whether content is correct but at whether it was built as promised. Where there is a spec deviation, separate an agreed change from an unauthorized one.

Examples of formal items to check:

• Material type (oral-explanation / hand-out / web) matches intended use — change the use and the applicable regulation changes
• Mandatory entries present: product name, indication, dosage, warnings/contraindications, company name, date of creation
• Audience (healthcare professional / general public) matches — for the general public, efficacy appeals for prescription drugs are not permitted
• Consistency with approval information (package-insert version)

Formal conformance looks mechanical, but mixing up use and audience leads straight to a regulatory violation. If material ordered for oral explanation is delivered in a hand-out format, it fails the entry requirements for distributed material and the scope of the MSA Guidelines shifts. Checking form is a precondition for verifying content, not an optional step.

05G2: Evidence verification — map each claim to its source

G2 is the core of the receiving flow. For each claim in the material, confirm one by one that a source or data backs it. Much of the exaggerated advertising under Article 66 arises from expressions lacking evidence, or sources that do not support the claim. "The vendor attached a source, so it's fine" will not do. The owner has a duty to read the source and confirm it actually supports the claim.

Do not confuse Article 66 (exaggeration) with Article 68 (pre-approval). Overstating an approved indication is an Article 66 matter; suggesting an unapproved or off-label use is an Article 68 matter. They are separate articles with different judgments and remedies. See Basics of the Pharmaceutical Affairs Act and the Standards for Fair Advertising.

06G3: Regulatory screening — a first-pass filter before review

G3 is the owner's first-pass filter, stopping plainly risky expressions before review under the Act, the fair-advertising standards, and the MSA Guidelines. Again, this does not replace internal material review. The owner's first-pass screening has two aims: stop obvious deviations early, and hand the review function a clear "verified / unverified" statement.

Items the owner should screen at minimum:

1. Suggestion of indications or uses outside the approved scope (Art. 68)
2. Superlatives or absolutes lacking evidence ("the most," "certainly") (Art. 66)
3. Understated safety (improper downplaying of warnings, contraindications, side effects)
4. Unapproved information or misleading expressions against the MSA Guidelines (bearing on the Art. 68-2 duty of effort in information provision)
5. Format or expression contrary to the JPMA Code and creation guide

For concrete MSA-G judgments, the MSA Guidelines commentary and its Q&A help; for code conformance, the JPMA Code and creation guide. Where a screening judgment is uncertain, do not force a conclusion as the owner — record it as "needs confirmation" and pass it on to the review function. This is the key to leaving no blind spot.

07G4: Filing decision & record — close with an acceptance decision

At the last gate the owner judges "may this deliverable go to internal material review" and keeps that judgment as a document. Make the decision a three-way choice, to forbid a vague "good enough."

The artifact that supports the decision is the acceptance decision record. At minimum include:

• Deliverable identification (SOW number, version, receipt date)
• Pass records for each gate (who confirmed what, and when)
• The G2 claim-to-source mapping table
• The G3 screening result and "needs confirmation" items forwarded
• The decision category and the signature of the decision maker

This document plays two roles: hand-off material to the review function, and evidence that discharges accountability against later audit or findings. Without the acceptance decision record, the owner cannot later prove what was checked. Systematic design of documentation is covered in installment 10 (in preparation).

08Three design principles that turn receiving into verification

Lining up gates alone leaves them hollow. To make the flow function as live verification, embed three principles at the design level.

First, write down the pass conditions. "I checked it" is not verification. State for each gate what must be satisfied to pass, in concrete criteria. Reduce checks to objective yes/no and gaps become visible regardless of an individual's experience.

Second, treat rejection as a normal option. In a culture where rejection is an exception or a problem, the floor rushes to pass things. Rejection is normal action that protects quality, and the organization should agree that there are moments where it outranks the deadline. The rejection rate is not a failure metric; it is also evidence that verification is working.

Third, leave a trail of verification. If there is no record of who checked what, verification decays into "we'll say we did it." Make the acceptance decision record and per-gate records mandatory artifacts, and design it so you cannot advance without them. Records serve not only audit response but as a structural brake against skipping verification.