Describe the finding precisely
Record job, item, site, batch or version reference and the actual difference from the accepted requirement. Include observation date, responsible checker and useful permitted evidence. A report such as poor quality can start a conversation but does not identify what must be corrected. Separate content, dimensions, construction, appearance, damage and quantity where they have different owners. Keep the original accepted requirement available for comparison.
Contain the affected work
Identify which items or decisions are affected and ask the responsible provider what can safely continue under the actual scope. Do not assume every batch failed because one item is wrong. Equally, do not dismiss a repeated issue because one sample looks acceptable. Record held work, open deliveries and customer impact as facts. A proposed remake, repair or accepted exception needs responsible review and must remain distinguishable from a completed remedy.
Agree action and confirmation
Name who will perform the remedy, what result is expected and when a responsible recheck is needed. Use the actual contract or accepted scope to settle obligations rather than inventing an automatic guarantee. Record the provider response and buyer decision. If the remedy changes material, artwork or delivery, route those changes through the relevant approval gates. Completion requires a real result and confirmation within the agreed check scope.
Worked example — fictional
A fictional retail campaign receives one variant with incorrect opening times. The coordinator identifies the affected file and branches, preserving that their boxes were delivered but content remains unacceptable. The supplier and buyer agree replacement from corrected proof version 5. The content owner approves that version, the provider accepts production and the site confirms actual receipt and installation later. The original finding remains linked to the replacement and outcome. Other site variants are checked against their own records rather than all being marked failed or complete together.
Common pitfalls
A new scheduled date is not evidence that corrective work happened. Deleting a finding after remedy prevents useful analysis of recurring issues. An assumed cause can distract from the actual defect, so distinguish observation from investigation conclusions. Avoid blaming a person publicly or publishing confidential customer evidence when the task needs a private attributable resolution.
Learn from the actual result
Use the readiness or discrepancy record to connect finding, accepted action, performed work and recheck. Review whether briefing, version control, packing or inspection could prevent recurrence. Record an improvement with an owner and a measurable task rather than a promise of no future mistakes. The next campaign should inherit the useful lesson and current specification, while its actual quality still requires appropriate checks. Give the next coordinator enough context to identify a resolved issue without reopening it unnecessarily. The record should distinguish the original finding, accepted remedy and actual confirmation dates clearly.
Take this to the next job
- Identify the accepted requirement and deviation
- Define affected scope
- Agree responsible corrective action
- Confirm actual remedy and recheck
- Preserve lessons without erasing history
