The Agency-to-Client Approval Handoff: What to Send with the Draft

"Looks good from our side." The account lead forwards the reply to distribution. The client had been reading version two. Version four, the one that went out, carried a partner quote nobody on the client side had seen.

Send every draft with a handoff note tied to one version: what you are asking for, what changed and what supports it, which decisions are open with a named owner and deadline, and who authorizes release. Record client acceptance and release authorization as two decisions, even when one person makes both. Clients expect that line to hold when tools are involved too: in Muck Rack's State of AI in PR 2026↗, 89% of PR pros said clear human approval before publishing or sending would make them more comfortable trusting AI with PR work¹.

Take a fuller version of that thread, also fictional: "Looks good from our side. Please check the partner quote." The account lead has a positive response and an unresolved instruction. Can the release go out? Which version did the client read? Does the partner check require a wording change or permission to use the quote? The email alone cannot settle those questions.

Name them at the brief: the agency editor, the client decision owner, the fact owners, any specialist reviewer, a deputy and the person who authorizes release.

At the start of the assignment, name the agency editor, the client decision owner, the fact owners, any required specialist reviewer, a deputy for absences and the person authorized to release the material. One person may hold several roles, and mapping who approves each kind of public statement is a quick way to agree them before the first draft.

The CIPR Code of Conduct↗ describes good practice as making sure clients and colleagues are fully informed about what can be delivered and what other parties must do to enable the result². In a handoff, that means telling the client plainly which of their people must act, on what, and by when.

Ask what each decision covers. An executive can approve their attributed quote while an operations owner confirms availability. The client contact may accept the copy subject to those decisions, and a communications lead may control the publication timing. Preserve those distinctions in the handoff rather than translating every positive comment into a single approval status.

Agree on the review scope, deadline and time zone. If a required reviewer cannot meet the deadline, identify who can authorize an alternative reviewer or change the schedule. An unanswered request remains unresolved. Avoid a default rule that turns silence into consent simply because the distribution slot is approaching. A launch that lands on a weekend or a public holiday, like an account lead going on leave, needs cover arranged in advance, with the account's decisions intact.

Some announcements need a specialist sign-off that the client contact cannot give. For a US company that reports to the SEC (the rule does not cover foreign private issuers), Regulation FD↗ applies when the company, or a person acting on its behalf, discloses material nonpublic information to certain outsiders such as market professionals, and the company must then make that information public, at the same time for an intentional disclosure³. If a release may carry results, guidance or other price-sensitive news, ask whether investor relations or counsel must clear it and how it will be published, and name that person in the handoff. This is general guidance, not legal advice; check the rules that apply to your organization with counsel.

Four things, tied to one version: what you are asking for, what changed and what supports it, which decisions are open, and what happens after the reply.

The following is an illustrative template, not a record of an actual client approval. Replace the bracketed fields and remove any instruction that does not fit the assignment. Keep the note short enough to read beside the draft. Link to supporting detail through the team's approved sharing method, with access checked before sending, and keep embargoed material out of the wrong review link when the draft carries news that is not yet public.

Review request

Please review [deliverable and title], version [identifier], for [audience and channel]. The proposed publication time is [date, time and time zone], subject to release authorization. We need [named client owner] to accept this version, request changes or decline it by [review deadline]. The current document is [link]. Earlier attachments are retained as history and should not be used for this decision.

What changed and what is supported

Since [previous version], we changed [specific wording or sections] because [reason]. The agency editor has reviewed [scope]. Factual support is recorded at [review sheet], including source passages and relevant dates. The executive quote has [current approval state]. The person and organization voice references used for this draft are [approved references]. These checks cover the current wording described here.

Open decisions

[Issue identifier]: [exact claim or decision]. Evidence currently establishes [limited conclusion]. We still need [missing evidence or permission] from [named owner] by [deadline]. Until then, [affected wording] is held. Proposed fallback: [remove, narrow or delay], requiring [decision owner]. Repeat for each unresolved issue so a conditional acceptance cannot conceal a release blocker.

What happens after your response

Please identify this version in your decision and state any conditions explicitly. [Agency owner] will reconcile requested changes and return material revisions for review. Client acceptance will be recorded separately from publication authorization. [Release owner] will authorize the final version, channel and timing once the required decisions are complete. The agency will distribute only within that authorization.

The review sheet referred to in the template is the one built during a claim-by-claim fact check of the release, and the quote's approval state comes from the speaker's own review of a quote written to add something to the story. The handoff does not repeat that work; it points to it.

Ask for the reply in the same terms. A client's "approved" is only as useful as its scope, so make the email approval specific to the copy by naming the version, the conditions and the decision the reply covers.

Give each reviewer one question they own, such as confirming the launch scope or accepting the quote in context.

A request to review everything can leave ownership unclear. Ask the operations owner to confirm the launch scope against the attached source. Ask the executive approver to accept the quote in context. Ask the client decision owner to resolve the campaign position. Let reviewers raise concerns outside their assigned area, while keeping the required decisions attached to the appropriate people.

Where reviews are independent, they can happen concurrently. Where one decision changes another reviewer's task, make the dependency visible. A new launch date may require another availability check and a revised quote. Parallel review is useful only if everyone can identify the current draft and see when a change affects the work they already completed.

Record the condition in the client's own words, hold the wording it affects, and send conflicts to the owners who can resolve them.

Return to the fictional partner quote. Record the client's response as acceptance with an open partner condition, using the client's own wording. Ask the partner owner whether the exact quote and attribution are cleared for the intended use. If the partner supplies different wording, preserve the original, record the replacement and recheck any changed factual claims.

When two reviewers request incompatible edits, present the conflict with its consequence. For example, one may want to describe national availability while another confirms only selected locations. The account lead should ask the responsible fact and communications owners to resolve that discrepancy. Combining the edits into vague language can leave the same unsupported implication in place. When several reviewers disagree at once, sort the decisions behind the conflicting feedback before producing another version.

Separate preferences from changes in meaning. A punctuation correction may fit the team's agreed editorial discretion. A changed scope, promise, attribution or publication date should return to the relevant approver, including a number the client changes after approving the draft. Record that review boundary at the start so the account team can make routine corrections without guessing which decisions remain valid.

Software can record each decision against the version it covered. Making the decisions stays with the people named in the brief.

QuoteIt records internal, client and release decisions separately, each tied to a version, so a reply to an old attachment cannot pass for approval of the current draft. A drafted line that gives a spokesperson a view is marked as proposed until that person approves it. The claim review the handoff points to sits beside the draft: each claim next to the passage it came from, with unsupported claims flagged. If you are comparing it with a PR suite your agency already uses, how QuoteIt compares with Prowly and the comparison of AI tools for PR professionals set out the differences.

The accepted version, each required approval, the resolved conditions, who authorized release, the permitted channel and when it actually went out.

Keep a final record containing the accepted version, required approvals, resolved conditions, release authority, permitted channel and actual distribution time once known. Preserve the source references and earlier decisions in the authorized workspace. Share only the supporting material each recipient is permitted to see; a client-facing summary can point to a cleared extract while private review history stays restricted. The PRSA Code of Ethics↗ asks members to protect privileged, confidential or insider information gained from a client or organization⁴, which applies to review history as much as to the draft. A short log of the editorial decisions behind each change kept through the project makes this record quick to assemble.

This adds some preparation to the handoff. For a small routine update, the note may be a few lines with a linked review sheet. For a disputed launch, it needs more detail. Scale it to the decisions at stake. The person receiving the draft should be able to tell what they are accepting and who takes responsibility for the next step.