A PR Handover That Works When the Account Lead Is Away

The account lead wakes up ill on the morning a client announcement is due. The covering colleague finds four document links, a long message thread and a note saying the client "mostly approved" the quote. At 9:20 a journalist asks for the final timing, and the cover spends the morning reconstructing the account. A handover that works is a live board, not a history: each open item with its exact version, the next action and owner, and a plain statement of what the cover may decide and what goes back to someone else.

A resilient handover is a control surface for the next person. It identifies the current deliverables, exact versions, open decisions, responsible people and permitted actions. Background belongs there only when it helps the cover understand a decision or relationship boundary.

A live board: each active item with its deadline and time zone, current state, next action, owner and the cost of delay, most urgent first.

At the top, list each active item with deadline and time zone, current state, next action, owner and consequence of delay. Put the closest or most consequential decision first. A label such as “with client” is too vague. Write “Version 5 with client communications director for acceptance; response requested by 10:00; product name remains open.” If a draft is about to go to the client, the cover also needs the pack that travels with a draft sent for client approval.

Link one canonical draft and label older versions as history. Include the current brief, evidence review and approval record through the team’s authorized workspace. Check that the covering person has access before the absence begins. Attachments copied into a handover can drift away from later corrections, so use stable links where possible.

Record external commitments exactly: who expects what, by when, through which channel. Separate a promised update from a promised answer. Include embargo or background terms only when they have been explicitly agreed, and quote the recorded agreement rather than paraphrasing it from memory. The Associated Press tells its reporters↗ to assume an interview is on the record and to negotiate any conditions at the start², so a cover arranging a follow-up call should agree its terms afresh at the outset.

Only what the handover says they may decide: routine coordination, agreed corrections and sending an already authorized version; anything that changes a claim, promise, attribution or channel goes back to its owner.

Map the decisions before the people. Four usually matter. Copy acceptance: who can approve wording for the client or organization, within what limits, on which exact version. Fact resolution: the operational or subject owner who can confirm scope, date and source, who may not be the senior communications contact. Specialist review: when legal, security, investor relations, partner or policy review is required, and who decides that a request falls into that category. Final release: the person authorized to distribute the approved version and the channels they control.

Acceptance of a draft and authorization to publish can be separate decisions, even when they are often made by the same person. Security practice calls the deliberate version of this separation of duty; NIST’s example↗ is that the person who authorizes a paycheck should not also be the one who prepares it³. A decision map for who approves a public statement shows where a small team can combine roles and where it should not. With those four named, the cover’s own limits follow.

QuoteIt keeps that state with the draft rather than in a note about it. The cover opens the current version and sees which claims are checked against their sources, which wording waits for a spokesperson's approval, and which internal and client approvals were given on which version. A fix to one sentence rechecks only what that sentence changed.

It names the canonical version, what has been accepted, what is held and why, the next contact and deadline, and the fallback if nobody answers.

Consider this fictional entry: “Neighbourhood opening release, planned Tuesday at 11:00. Version 5 is canonical. Client accepted the body but asked the founder to approve the revised quote. Location list is supported by operations sheet dated Friday and cleared for this release. The phrase ‘available to every resident’ is held because eligibility remains unconfirmed. Next: Priya, founder’s assistant, expects version 5 in context by 9:30. If no response by 10:15, call client communications director; they decide whether to remove the quote or delay. Cover may correct formatting but may not broaden eligibility wording.”

This example is invented, but its mechanics are reusable. It captures what has been accepted, what remains blocked and who can choose the fallback. A relationship note can add: “The founder prefers one consolidated request; route follow-ups through Priya.” That detail changes the contact plan. A page of impressions about stakeholder personality would be harder to apply and risk inappropriate sharing.

There is a tradeoff between completeness and scan speed. Keep the live board concise, then link to evidence and history. If the cover needs to read every email to understand a condition, the summary is incomplete. If the handover copies every email, the urgent decision disappears inside it.

Name the deputy for each decision, the exact version they may approve, the open facts and the fallback before the team goes offline, in a note short enough to read on a phone. If the account runs crisis work, the cover note should point to the response path agreed before a crisis rather than restate it.

At 6:20 p.m. on a public holiday eve, a journalist asks for a response by 7:00. The usual client approver is travelling. The agency has a list of mobile numbers, but nobody can answer whether the client’s deputy can approve a factual correction, whether legal review is required, or who may authorize distribution. Missing decision design, rather than contact details, causes the delay.

Out-of-hours cover works when it describes authority before a live issue tests it. The same fields apply: the four decisions above, the exact version, the open facts and the person who takes over if a question exceeds the deputy’s remit. Keep the note short enough to read on a phone. For a fictional weekend product update it might read: “Draft v4 is ready for client copy acceptance. Confirmed: launch in two locations on Monday. Open: partner attribution. Release requires client acceptance plus communications director authorization. If no answer by 16:30 IST, hold the partner claim and send the approved core update only.” The fallback is agreed in advance, so the deputy does not have to improvise one.

The cover confirms the live items, raises access or authority gaps at once and records every decision on the same board, so the account lead can see what moved on return.

The covering colleague should acknowledge the live items and raise access or authority gaps immediately. During the absence, update the same board with decisions, versions and commitments rather than starting a private parallel note. Record why a deadline or fallback changed and who authorized it, in the account’s editorial decision log if it keeps one. Decisions a deputy made out of hours go back to the primary team on the next working day, with any temporary restrictions resolved, so they do not remain private messages that later reviewers cannot find.

On return, the account lead should be able to see what moved, what was sent and what remains open. A short debrief can fix weak points in the template, such as missing deputies or unclear client acceptance. The best test is retrieval: a covering colleague should be able to take the stated action from the live board without reconstructing the account from email.