Gold Standard Practical Case Study 02 | A Print Job and an Outdated Proof

A fictional community group orders 200 brochures for an event. Proof P1 shows the event on Saturday. The customer later corrects it to Sunday in P2 and explicitly approves P2. Designer Noor records the approval. Production operator Ellis receives a job package that still points to P1 and prints that version.

The local rule, V0, requires the approved proof identity to be recorded on the release record and to match the file sent to production. A change after approval must receive a new identity and acceptance before release. This rule belongs to the fictional exercise; it is not a claim that every print business uses the same process.

The scope covers proof approval, production release and collection of this one order. It does not establish colour accuracy, materials performance, accessibility or any other technical requirement. Those would need their own appropriate criteria. The central question here is precise: did the approved content version reach the printed output?

Contents · Next chapter

V1 is the customer’s approval of P2. V2 is Noor’s design note linking the correction and approved file. V3 is the release record, which names P1. V4 is Ellis’s production record, showing P1 printed. V5 is the collected brochure, whose Saturday date matches P1. V6 is the customer’s report identifying the mismatch. All records are simulated for this learning case.

V1 and V2 establish which version was approved. V3 and V4 establish which version was released and used. V5 connects that decision to the delivered content. The failure is supported by a chain of observations; it does not depend on guessing what the operator intended.

A file called final is not an adequate substitute for a stable identity when several files exist. Nor does the customer’s approval of P2 approve P1. The reviewer should compare the identities at the point of release. This is where design acceptance needs to become usable production information.

Contents · Previous chapter · Next chapter

Against V0, controlled execution under GS-R06 is Not met for this release. The required match between approved proof and production file did not occur. The evidence also reveals a failed handoff condition under GS-R07: production received the wrong content identity, even though an identifiable operator took the job.

The quantity and collection-time conditions may have been met. They do not erase the version mismatch. A reviewer can report those positive observations while withholding the broader claim that the agreed brochure order was correctly delivered. The customer needed usable information for Sunday, not merely 200 neatly produced objects.

Do not infer that Ellis lacks general competence from this single record. The record supports an execution and information-transfer finding. Whether training, software selection, workload, ambiguous instructions or another cause contributed needs further examination. Assigning blame before reconstructing the route can leave the wrong file pathway untouched.

Contents · Previous chapter · Next chapter

In the simulated response V7, coordinator Priya asks the customer to stop distributing the remaining incorrect brochures and confirms the approved P2 content. The group reports that no brochures have yet been distributed. Priya agrees a corrected print and collection arrangement with them. This avoids inventing a public correction campaign that the facts do not require.

V8 records a revised production release naming P2. V9 records the replacement batch check against P2 and the customer’s acceptance. The correction can therefore be described as completed for the examined order. The original failed release remains in the history, linked to V7–V9.

Had distribution already occurred, the relevant response would need to account for people who might rely on the wrong date. That is a changed case, not an unstated event in this one. An effective reviewer notices the difference and asks for evidence before expanding the recovery narrative.

Evidence-to-decision register

Contents · Previous chapter · Next chapter

A review meeting reconstructs the release screen. The approved file link sits in the design note, while the production package can retain an earlier attachment. There is no enforced comparison at the release point. This supplied exercise observation, V10, explains a pathway through which the mismatch can occur.

The team proposes C1: place the approved proof identity and production file identity together on one release record, require their match before release, and retain the approver and decision sequence. The process owner can approve that change. The design does not require a particular software product; it requires an effective decision gate.

A reminder saying use the latest file is weaker because latest can mean most recently saved rather than most recently accepted. The proposed control uses acceptance identity. It also allows a legitimate new revision to move through a fresh approval route rather than making every change impossible.

Contents · Previous chapter · Next chapter

V8 and V9 show the corrected customer order. They establish neither that C1 operates reliably nor that all future releases are protected. The initial GS-R10 effectiveness conclusion remains Unknown because no use of C1 is supplied after its adoption.

A useful later trial would deliberately include an obsolete attachment alongside the current accepted proof. The operator should identify the mismatch, stop release and find the correct acceptance route. Another trial should show that a legitimate approved revision can proceed. A control that prevents every release can look strict while failing the service’s purpose.

Any later claim should identify the trials, conditions and limits. Passing one planned exercise provides bounded evidence of the control’s behaviour. It does not prove that every file, person or future workload has been covered. Keep the result proportional to the examination actually performed.

Contents · Previous chapter · Next chapter

Practice question: the batch is delivered on time and corrected the next day. Can the original release be assessed as Met because the final customer outcome was satisfactory? Explain your answer using V0, V1 and V3–V5.

Reasoned answer: no. The original release used P1 while P2 was approved. The later correction can resolve the current order, but it does not change the historical mismatch. A useful account records the failed release, accepted replacement and unanswered effectiveness question separately.

Transfer the lesson to a presentation, instruction sheet or edited document: acceptance and delivery must refer to the same controlled content. Supply the actual domain criteria rather than copying brochure quantities or event-date rules. The enduring skill is to follow a version identity through the decision that turns a file into a promise.

Contents · Previous chapter · Gold Standard hub