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. Her 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. The cover’s first task becomes reconstructing the account instead of moving the work forward.

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.

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.”

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.

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 her 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.

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.

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.