Handling an Authority Request: The First 72 Hours and Everything After

An authority request is a project with an external deadline and an unforgiving paper trail, and it should be run like one from the hour it lands: a matter file opened, a single owner named, the request logged verbatim (products, documents, deadline, legal basis as stated), and the response clock managed visibly. Most operators' outcomes are decided less by the underlying facts than by the professionalism of these mechanics - because the authority forms its view of the operator's whole system from the one interaction it can see.

This guide is the protocol, written to be followed under pressure.

Day one: acknowledge in writing, naming the contact and confirming the deadline as understood (or seeking clarification of scope where the request is genuinely ambiguous - asked once, precisely). Open the matter file; freeze the relevant records (production, artwork, data versions) against routine deletion; alert the RACI's consulted rows (legal, the category owner, leadership proportionate to the request's scope). Days two and three: assemble the production set from the documentation system; run the gap check (what the file does not contain, with remediation started and noted); decide the response's posture with legal - the facts produced completely, any interpretation argued precisely, any defect volunteered with its remediation where the surveillance guide's logic applies. The deadline is met or an extension is sought before it expires, with reasons; silence is the only unforced error.

Everything produced is logged (document, version, date, recipient) and produced once, consistently - the version sent to the authority, the version in the customer conversation and the version in the internal file are the same document, because parallel narratives are discovered and read as intent. Translations are the producing party's problem, solved properly. Personal data and commercially sensitive material beyond the request's scope are handled under advice - produced where the duty runs, protected where it does not, with the distinction recorded rather than improvised. And the production set is reviewed before sending by someone who did not assemble it: the second pair of eyes is the protocol's cheapest control and its most skipped.

Expect follow-ups and treat each as the same matter, same owner, same log - authorities test consistency across rounds, and the operator who answers round two as if round one had not happened fails a test it set itself. Closure, when it comes, is recorded with its terms (any corrective actions, dates, reporting duties diary-noted into the audit programme). Then the matter's final product: the lessons entry - what the request revealed about the system (a data gap, a slow file, an unclear position) converted into an audit finding with an owner, so the matter pays rent after it closes. The file is retained with the technical documentation's clocks; it is, among other things, the next request's rehearsal.

The protocol's last lesson is that composure under an authority's deadline is not a personality trait; it is the visible surface of the systems beneath - files that exist, owners who know, logs that run. Managers inherit the composure their operation built in peacetime, and no performance in the first 72 hours substitutes for it. Build the systems, and the letter, when it comes, is an administrative event with a deadline. The business has those every week.

A mid-size producer's first request under the framework named twelve SKUs and their substance evidence, thirty days allowed. The matter file opened the same morning; the production set - declarations, substance inventories, two supplier files reformatted - was assembled by day nine from the documentation system, with one genuine gap (a legacy adhesive's declaration) identified, its remediation (screening commissioned, supplier pressed) described in the response itself. The authority closed the matter with the screening result filed six weeks later, no measure, and a note of the operator's cooperation that sits in the file like a small bond. Nothing in the story is heroic. That is the story's point.