After an authority acts: rebuilding the product file, the supplier checks and the routine

The first job after an action is to translate the official wording into a plain list of weaknesses. An action may cite a missing document, a failed test, a label gap, or a traceability hole, and each one points at a different fix. A seller who treats the action as a single verdict, rather than a list, will fix the headline and miss the smaller findings that will resurface at the next check.

The list should separate product faults from paperwork faults, because they need different owners. A product fault goes to design or supplier work. A paperwork fault goes to the file routine. Illustration: a seller of garden kneelers receives an action citing a missing batch code on packaging and a stitching failure, and correctly treats those as two jobs, not one.

Product fixes follow the fault mechanism, not the finding's wording. If a test failed, the seller needs to understand whether the failure came from design, materials, production variation, or a test method mismatch, and each cause leads somewhere different. A design cause needs redesign and retesting. A production variation cause needs tighter process control or inspection. A test mismatch needs a conversation about method, with evidence, not a quiet redesign of a sound product.

The fix should be verified before the product returns to sale in full volume. A trial batch, tested under the conditions that failed before, gives the seller something to show an authority that asks what changed. Selling the old stock while hoping the fix works invites a second action on the same product, which is harder to explain than the first.

A file that failed an authority check usually failed in a specific place: a missing test report, an outdated risk assessment, a supplier document never collected, or a batch record that could not be traced. Repair means filling that exact gap with genuine evidence, not padding the file with unrelated documents. An authority returning for a follow up will look at the gap first, and a padded file that still lacks it will be judged harshly.

File repair also means fixing the routine that let the gap form. If test reports were filed by email and lost, the routine should move to a single file location with a named owner. If the risk assessment was never updated after a design change, the routine should link design changes to assessment updates. The gap and the routine are two halves of the same repair.

Where a supplier contributed to the finding, the seller needs a documented response: what the supplier says changed, what evidence supports it, and what incoming checks will verify it. A supplier who cannot explain the lapse or show corrected controls should lose safety critical work until proof exists. A supplier who explains promptly and accepts verification may be retained, with the new terms written into the file.

The seller should also review whether other products share the supplier or the component. An authority action on one product often reveals a weakness that touches a family, and a seller who checks the family voluntarily will find problems before the next authority visit does. That wider check belongs in the post action plan, with its own date.

Routines reopen gaps when they depend on memory or on one person. The redesigned routine should name who updates the file, who reviews complaints, who checks incoming batches, and who prepares for authority contact, with deputies for each. It should also set a rhythm: complaint review weekly or monthly depending on volume, file review when a product changes, and a periodic self check against Safety Gate alerts for the product type.

A simple calendar of these rhythms, visible to the team, does more than a policy document nobody opens. The calendar turns good intentions into dates, and dates turn into completed reviews. The seller should also keep a log of authority contacts, so the next contact starts from the history rather than from scratch.

Showing change means evidence, not assurance. A short closing message to the authority, where appropriate, can list the product fix with its test evidence, the file gaps filled, the supplier terms changed, and the routine now in place. That message should be factual and brief, and it should not claim more than the evidence supports, because an overstated claim invites a verification visit.

Over time, the proof becomes the record itself: steady inspection results, complaint patterns that no longer show the old fault, and a file that answers questions promptly. A seller who can show that trajectory has turned an authority action from a setback into a visible improvement, and that trajectory is worth more than any single letter.