Prepare an announcement brief before writing the release

The blank release document is often a sign that the team has started writing too soon. One person knows the product, another owns the timing and a third expects the announcement to support a business goal nobody has written down. Before shaping a headline, collect those decisions in a short announcement brief. The brief gives the writer a place to test the story and the approvers a shared reference.

This method is intended for an ordinary organizational announcement, such as a new service, a research finding or an operational change. It is a working preparation approach, not a requirement to use the same template for every situation. Adjust the depth to the subject and bring in the appropriate specialists where the announcement involves sensitive or regulated information.

Write the change in one sentence

Begin with what is changing, who it affects and when it happens. Avoid the organization’s preferred adjectives at this stage. “The service will be available to regional customers from next month” is a usable factual starting point. “An exciting new chapter” leaves the writer with the same unanswered questions as before.

If several people describe different changes, record the disagreement. It may mean the announcement contains two stories or that the underlying decision is not settled. Resolving that question early saves time later. A release is a poor place to discover that the product team and commercial team have different understandings of what is launching.

Identify the audience's practical question

The audience needs a reason to care about the change. Write the question they might reasonably ask: what becomes available, what must they do differently or what does the finding explain? Keep the answer tied to the subject. The internal importance of a launch does not automatically make it useful to an outside reader.

For a hypothetical service announcement, the question might be whether customers can now complete a task in their region. The brief would then need the service boundary, availability date and instructions. That is a more productive writing guide than a general ambition to raise awareness. It tells the writer which facts must appear near the beginning.

Separate facts from interpretation

Create a simple evidence list with three fields: assertion, supporting source and person responsible for checking it. Include ordinary details such as dates, names, product availability and geographic scope. Small errors can survive because everyone assumes someone else has already checked them. Assigning an owner makes the final review more deliberate.

Interpretation belongs in the brief too, but label it. A team may believe the change will make a process easier. What can it demonstrate today? What remains an expectation? The PRSA Code of Ethics provides useful professional context for accuracy. In practice, the writer needs language that matches the evidence rather than a stronger sentence approved through repetition.

Decide who can answer follow-up questions

A named spokesperson should be able to discuss the announcement beyond the prepared quote. Ask which parts of the subject they own and where a specialist needs to join the conversation. A product lead may explain how something works but need another colleague to answer availability questions. Put those boundaries in the brief.

Prepare a few difficult questions before drafting a reassuring answer. What has changed from an earlier plan? Which customers are excluded? What is still uncertain? The goal is to find the questions that need a real decision or more evidence. A question-and-answer document becomes useful when it exposes gaps rather than smooths them over.

Give the quote a job

A quote should add a point of view or explain a decision. It does not need to repeat the opening paragraph in more enthusiastic language. Ask the spokesperson what they would say to a colleague about why the change matters. Their answer may reveal a useful explanation that the draft has not yet made clear.

Avoid drafting a long quote before checking that the spokesperson agrees with its meaning. A short conversation can settle the central thought, after which the writer can prepare wording for review. Keep approval focused on accuracy and the speaker’s intended position. The quote should remain something that person could reasonably say aloud.

Record the timing and dependencies

An announcement date may depend on a customer notice, an internal briefing or a product becoming available. List those dependencies and the person responsible for each. The release schedule should follow the real sequence. A planned date is not confirmation that the underlying step has happened.

Also record the source of truth for the final version. If several teams keep separate copies, the wrong file can reach the website or a spokesperson. Choose one controlled document and a clear approval owner. Mark substantial changes after approval so the team knows when a fresh check is needed. These are small habits that prevent avoidable confusion on a busy morning.

Plan the material a reader will need

An announcement may lead to questions that the release cannot answer alone. Decide whether a product page, research note, diagram, image or technical explanation is needed. Check that each item will be available at the stated time. A link in a draft is not enough; someone should inspect the actual destination before publication.

Image rights and captions deserve the same attention as the main text. Identify who supplied each asset, what permission covers its use and what the caption needs to explain. A photograph should not imply a customer relationship or an event that did not happen. Clear supporting material makes the announcement easier to understand and use.

Define a useful result before counting activity

Write down what the communications work is intended to support. An objective might concern awareness of a new service among a defined group, understanding of a change or use of a new information resource. The AMEC Integrated Evaluation Framework offers a structure for connecting objectives with evaluation. It helps the team decide what information to collect before the work starts.

Keep activity measures in their proper place. Publishing the release and sending relevant pitches describe work performed. They do not, by themselves, show that the audience understood the announcement. The brief can state which later observations would help answer that question. This keeps the eventual report connected to the original purpose.

Use the brief in the review meeting

A useful final review asks whether the draft says what the brief establishes. Read the opening against the change sentence. Check every strong claim against its source. Confirm the dates, links, spokesperson and dependencies. If a reviewer introduces a new fact, add its source and owner before accepting it into the text.

The brief should be short enough to consult and specific enough to resolve a disagreement. Once the announcement is complete, note what changed during the process and why. That record can make the next preparation meeting more efficient. The practical outcome is a writing team with fewer hidden assumptions and a release built from decisions everyone can identify.