Who Approves a Public Statement? A Decision Map for Small Teams

A five-person communications team has a statement ready at 4:40 on Friday. The operations lead approved the facts in a chat, the managing director rewrote the quote in the document afterward, and the client contact replied "fine by me" to an earlier PDF. Everyone took part, and nobody can say whether the current version may be published. The answer is not more approvers. It is a one-page map of four separate decisions: who confirms the facts, who approves words attributed to a person, who accepts the deliverable and who authorizes release.

Small teams rarely need a heavy committee for every statement. They do need a map of distinct decisions. The map prevents seniority, speed or silence from becoming accidental authority, and it shows when one person legitimately holds several roles.

Four different decisions, which may sit with one person or four: the fact owner confirms substance, the speaker approves attributed words, the client accepts the deliverable and the release owner authorizes publication. Security teams call the underlying rule separation of duty↗: one person should not both prepare and authorize the same action¹. PR teams want the same line for automation: in Muck Rack's State of AI in PR 2026↗, 89% of PR professionals said they want clear human approval before an AI agent publishes or sends anything².

Put decision types in rows and, in columns, the named owner, deputy, evidence needed, deadline and escalation route.

Use rows for decision types and columns for primary owner, deputy, evidence needed, deadline and escalation route. Add the scope of each person’s editorial discretion. Deputies outside office hours need the same clarity, so arrange approval cover for evenings and holidays before it is needed. For example, the account editor may fix punctuation after client acceptance but must return any changed date, promise, attribution or geographic scope.

Write names rather than departments. “Legal if needed” leaves the trigger and the requester uncertain. Define which content requires specialist review and who decides when the trigger applies. The map should also state what happens if the reviewer disagrees with the fact owner or cannot respond. Silence should remain an open decision unless the organization has explicitly adopted another valid rule.

Keep access in mind. A reviewer can only own a check if they can inspect the material needed to make it. Provide a cleared extract when a source contains unrelated private information, and preserve the original in its authorized location.

QuoteIt records these decisions as separate steps. Internal review, client review through a review link and release are each recorded with who decided, on which version and when. Wording that gives a spokesperson a view stays marked as proposed until that person approves it, and an edit after approval shows which sentences changed so they go back to the person who approved them.

It reads as a short sequence of named decisions on numbered versions, so a late change goes back only to the person whose decision it touches.

Imagine a fictional community transport service responding to a route suspension. The service manager confirms the affected route and start time. The customer lead checks notification wording. The director approves the explanation attributed to them. An agency client lead accepts version 7 subject to the route time being updated. The organization’s communications head has release authority.

When the service manager changes the time, the writer creates version 8 and flags the changed sentence. The client owner confirms that the condition is satisfied. Because the director’s quote refers only to the reason for the suspension, it remains unchanged under the agreed review boundary. The communications head authorizes version 8 for the website and reporter response at a recorded time.

This process adds several explicit decisions, yet most are short. The cost is visible coordination. The benefit is that nobody has to interpret a vague reply after publication. For a low-risk diary notice, the same map might assign all decisions to one communications manager, with a deputy for absence.

Whenever roles, agencies or risk categories change, and whenever a test with a routine announcement or an urgent correction shows a bottleneck or an unreachable deputy. An approval map is one of the standing records behind enterprise reputation management, and in a crisis it becomes the response path agreed before the crisis.

Review the map when roles, agencies or risk categories change. Test it with a routine announcement and an urgent correction. Look for bottlenecks, unavailable deputies and decisions that regularly arrive through informal channels. Record valid chat or verbal approvals in the statement’s review history with the exact version and scope, and where approval comes by email, ask for a reply that names the exact copy being approved.

Do not solve every delay by adding another approver. Remove duplicate reviews when one accountable owner can cover the decision, and add specialist review only where its trigger is clear. The map is complete when each named person recognizes the decision assigned to them, the deputy can reach the evidence, and the release owner can see every open condition.