Close a PR Project With More Than a Folder of Final Drafts

A month after a launch, a new writer needs a company description. The release says partner-operated facilities, the briefing deck says our facilities, and nobody remembers which discussion settled it. Every final draft is in the project folder. The reason for the wording is in nobody’s.

Close the project with a short ledger beside the final files. Carry forward the few facts likely to recur, each with its source and boundary, the voice examples their owner accepted, and the questions still open with whoever can answer them. Then ask someone outside the project to use it. The next assignment for the same client starts from that ledger, which is why onboarding a client through the first deliverable gets faster the second time.

Keep what the next likely request will need: the few facts that recur, the voice examples their owner accepted and the questions still open, chosen while the people who settled them are still around.

Ask the account lead what is likely to recur: a spokesperson introduction, a service description, a question about coverage, or an explanation of the launch decision. Select material against those uses. A detail that mattered only to a venue booking can stay in the project record. A definition that changed three drafts probably deserves a reusable entry.

Do this while the people who resolved the awkward questions are still available. Ask them to identify decisions a new writer could easily reverse by accident. If the team kept a decision log alongside the drafts, start there. Look through resolved comments as well as the final copy. The final sentence shows what survived; the discussion may explain which tempting alternative was rejected and why.

Keep the selection small enough for someone to review. If the proposed closeout contains dozens of unexamined facts, choose the few most likely to be reused first. The rest can remain discoverable in the project archive without appearing as approved current knowledge. Research the team gathered and never used can be sorted later, as described in giving unused research a second life.

Facts travel with their source and boundary, voice examples travel with the person who owns that voice, and open questions travel with whoever can answer them.

Consider a hypothetical service launch. Its final release describes four partner-operated repair centers. The chief operating officer's accepted quote explains why the company chose local partners. A pricing answer was removed because the commercial team had not settled the terms. Those three outcomes should travel into the next assignment differently.

A fact with a boundary

Carry forward the center description with the operations source, page, service scope and effective date. Preserve partner-operated as part of the meaning. Record who verified the source and who cleared this wording for public use. A published release is useful history, but the underlying operations record is the place to check whether the description still applies. That check belongs in the routine for keeping approved facts current, with this entry's effective date as its trigger.

A voice example with an owner

Propose the accepted quote as an example of this executive explaining a decision in plain language. In QuoteIt a spokesperson’s voice is built from material they approved and kept apart from the organization’s facts, so the quote travels forward as voice and never becomes a company claim. Link the approved wording and the observation it supports. Ask the voice owner to accept that guidance before making it reusable. Keep the organization's partner terminology separate from the person's sentence style; the next spokesperson should inherit the terminology without automatically inheriting the executive's cadence.

An unresolved question with a route forward

Record pricing as unresolved, with the commercial owner and the reason it was omitted. Do not convert the omission into a permanent policy against discussing price. Give the next writer a clear instruction to request a current decision. Store restricted commercial context only where the next authorized reviewer can access it.

Each item gets one line per field: likely reuse, exact wording, entity and period, source location, decision and owner, permitted use and what would trigger a review.

Use this mini-template for each selected item: likely reuse; exact wording or observation; entity and period; source location; decision and decision owner; permitted use; next review trigger. Add a link to the final deliverable where the item appeared. A colleague should be able to reach the relevant passage without opening every file in the folder.

Where an entry already exists, present the old wording beside the proposed addition or replacement. Record whether the owner accepted the change, kept both for different circumstances, or declined it. Preserve the prior entry and its history, with the same care you would give to retiring a company fact that is no longer true. A project ending provides an opportunity to propose knowledge updates, rather than blanket authority to overwrite them.

Separate the client-facing handover from private working material. The client may need the cleared evidence summary and final decisions without receiving internal comments, unrelated drafts or another person's voice references. Check access to linked sources using the intended recipient's permissions before calling the package usable. The PRSA Code of Ethics↗ asks members to safeguard the confidences and privacy rights of present, former and prospective clients¹, and a closeout is where a former client's material is most easily passed to the wrong person.

Ask a colleague outside the project to answer one likely follow-up from the closeout alone; if they have to reconstruct the history, it is not finished.

Ask a colleague outside the project to prepare a short answer to one likely follow-up. Can they find the facility definition, identify what remains current and explain whom to ask about pricing? If they must reconstruct the email thread, improve the transfer note at that point. This is a retrieval exercise, so avoid coaching them through the folder. It is the same test as a handover that works when the account lead is away: the reader should be able to act without calling anyone.

Set a realistic stopping point. Closeout effort competes with other work, and some decisions will have little future value. Preserve required project history within your agreed retention arrangements, but reserve reusable status for material with a clear purpose. A successful ledger answers one recurring question with a complete, reviewable trail and leaves the rest discoverable as project history.