How to write a briefing note that prepares the reader to act

Stefan Weiss, Co-Founder & CEO

Stefan Weiss

How to write a briefing note that prepares the reader to act

To write a briefing note, identify who will read it and what they need to understand or do. Put the current issue first, include only the background needed to interpret it, explain the implications and finish with the required next step. Check the facts and label anything that remains a proposal or an uncertainty.

A briefing note is not a compressed transcript. Its job is to prepare a particular reader for a particular situation. That might mean understanding a developing issue, attending a meeting or making a decision. The Canadian government’s guidance on briefing notes recognises these different purposes and recommends clear, concise, fact-checked writing.

This guide follows a practical sequence from assignment to review, then shows a complete fictional note. Follow your organisation’s required format where one exists; there is no single heading scheme that suits every briefing.

Before writing: establish the purpose and source material

Start with the reader, the occasion and the question the note must answer. “Brief the operations director before Thursday’s supplier meeting” is more useful than “summarise the supplier project”. It gives you a deadline and a reason to choose some details over others.

Gather the latest relevant records before drafting. These may include an approved plan, figures from their owner, correspondence and notes or recordings of earlier conversations. Identify which version is current. A recent comment can explain why a plan is changing without itself approving the change.

Keep a small evidence list as you work: the claim, its source and the check still needed. You do not need to put that whole working list in the finished note. You do need a way to verify important dates, quantities, commitments and recommendations before someone relies on them.

Step 1: state what the reader needs from the note

Decide whether the note is mainly for information, meeting preparation or a decision. More than one purpose is possible, but make the immediate purpose explicit.

For information, lead with what has changed and why the reader needs to know. For meeting preparation, add the likely discussion points, the position the reader is authorised to take and any questions they should ask. For a decision, state the choice, the options and the recommendation, together with the evidence and consequences.

Queen’s University’s GovTalk introduction distinguishes briefing-note purposes and structures. The useful principle is to let the assignment shape the note rather than treating every briefing as an approval request.

A note prepared for a meeting can say “No decision is requested in this note.” That prevents a proposed position from looking like an approved one. If a decision is needed, name who needs to make it and by when instead of hiding the request at the end.

Step 2: define the issue in one clear sentence

Write the issue before you write the history. Make it specific enough that the reader knows why this briefing exists now.

Weak: “There have been several conversations about the pilot.”

Stronger: “The supplier’s proposed delivery change would leave the pilot team without the equipment needed for its first training session.”

The second sentence identifies a proposed change and its consequence. It does not claim that the change has been accepted. It also gives you a relevance test for the rest of the note: does this detail help the reader understand the delivery issue or respond to it?

If you cannot state the issue clearly, resolve the assignment before collecting more prose. You may be dealing with two separate issues that need different readers, evidence or decisions.

Step 3: select background that changes the reader’s understanding

Include the context needed to interpret the issue: the existing agreement, the relevant dependency and the reason the matter has become timely. Leave the full chronology in supporting records unless the sequence itself is central.

For the pilot example, useful background might establish that the training date is already agreed and equipment is needed beforehand. A detailed account of every planning meeting is less useful unless one of those meetings changed the agreement.

Explain specialist terms and avoid assuming that the reader shares the team’s working knowledge. A short note still needs enough context to stand on its own. If removing a sentence makes the implication impossible to understand, you have probably cut too far.

Separate established facts from reported accounts. “The supplier proposed Friday delivery” is different from “Friday delivery is confirmed”. If you only have an account of what someone said, keep that distinction visible until you inspect the relevant correspondence or obtain confirmation.

Step 4: explain implications and options fairly

Move from “what happened” to “why it matters”. Identify the effect on the reader’s responsibilities, the project’s immediate objective or the people affected. Be specific about the condition under which a consequence would occur.

“Training may be affected” is vague. “If the equipment arrives after Wednesday, the team cannot use it in Thursday’s scheduled training” explains the dependency. If the delivery date is uncertain, say so rather than turning a possibility into an inevitable outcome.

Where there are options, compare them using the same relevant criteria. For example, keeping the training date with loan equipment and postponing training can both be assessed for availability, cost, disruption and the approval each requires. Do not describe your preferred option in detail while reducing the alternative to a dismissive phrase.

You do not need to invent a recommendation for an information-only note. You may instead identify the question the next meeting must resolve. If you recommend an option, connect it to the evidence and keep any conditions attached: “Use loan equipment if availability and cost are confirmed” is a conditional proposal, not an unconditional instruction.


A single orange cloth balance scale with empty cream cloth pans at equal height

Step 5: make the next step unambiguous

Finish with what needs to happen after the reader has been briefed. This might be a decision, a question to ask, a proposed position to confirm or a follow-up owned by someone else.

Distinguish the reader’s role from the team’s work. An operations director might need to confirm a negotiation position while a project lead checks the equipment list. Listing both as “next steps” without owners makes the briefing harder to act on.

If an owner or date has not been agreed, write “owner to confirm” or “date to confirm”. A neat-looking note with an invented assignment is less useful than a note that exposes the gap.

Step 6: write the opening summary after the substance

Once the issue, implications and next step are stable, write the short opening that a busy reader can scan first. Include the point that would matter if they read nothing else, together with any qualification that changes its meaning.

The Canadian writing guidance advises writing the summary after the content and putting important information early. Apply that as an editing sequence, not a reason to delay clarifying the purpose.

Use direct sentences and concrete dates. Replace “in due course” with the date needed, or mark the date as unknown. Replace a string of internal abbreviations with the plain meaning. Remove repeated background before removing the caveat that makes your recommendation accurate.

A complete fictional briefing note

The following example demonstrates the structure. The organisation, dates and events are invented; they are not a customer story or a tested Weeve output.

Supplier delivery proposal before the pilot review

Purpose: Prepare the operations director for the supplier meeting on 12 November. No approval is requested through this note.

Issue and current position: The supplier has proposed moving equipment delivery from 17 November to 20 November. The pilot team’s training is scheduled for 19 November. The revised delivery date has not been accepted.

Background: The agreed pilot plan places equipment training before the first live session on 23 November. The project lead has asked the supplier whether a partial delivery could arrive in time for training. No written answer has yet been received.

Implications: If all equipment arrives on 20 November, the team cannot use that equipment in the planned training session. Training with loan units may be possible, but availability, compatibility and cost remain unconfirmed. Moving training could reduce the time available to resolve problems before the live session.

Position to confirm before the meeting: Seek delivery of the training-critical equipment by 18 November. Do not commit to extra cost or accept the revised schedule without the relevant approval.

Questions for the supplier: Which items can arrive by 18 November? What is the earliest confirmed date for the remaining items? What would a partial delivery change in cost or support arrangements?

Follow-up: The project lead will check the revised equipment list against the supplier’s written response. Ownership of any additional-cost approval must be confirmed before a commitment is made.

Why this example works

The note opens with the situation the reader must handle. The background establishes the dependency without replaying the project’s history. The implications explain why the proposed change matters, and the unresolved questions remain unresolved rather than disappearing into a confident summary.

Its proposed meeting position also has a boundary. Asking for an earlier partial delivery does not authorise an extra-cost agreement. That distinction matters more than making the note sound decisive.

The finished version would still need factual review. Someone would need to check the actual approved plan, the supplier’s proposal and the authority to accept a change. Good structure does not establish that those facts are correct.

Use conversation evidence without letting it become the whole briefing

When relevant context is spread across saved conversations, use a bounded review to identify changes and unanswered questions. In Weeve’s chat with recordings, start with the relevant project and conversations. Ask what changed about the issue, which commitments were explicit and which points need confirmation, with citations to the passages.

The genuine product composer illustrated here contains a synthetic demonstration question about changes across recent meetings. It shows the kind of review request you can make; it is not a completed briefing note or evidence that a supplier change was approved.

Read the cited material before drafting. Check who made each statement, whether a proposal was later revised and how much of the relevant material was reviewed. A missing mention in retrieved passages does not prove that something never happened.

A project-brief workflow can help with a different task: setting out a project’s purpose and boundaries. For a briefing note, organise the material around this reader’s current issue instead. Check budgets, delivery records and approvals against their authoritative sources outside the conversation.


Genuine Weeve Chat composer with a synthetic question about changes across recent meetings and Local mode selected

Review the note from the reader’s position

Read the opening without the background. Can you identify the issue, its importance and the reader’s next step? Then check whether the body supports each part of that opening.

Trace the important facts back to sources. Verify dates and version status, distinguish requested actions from agreed commitments and check that recommendations stay within the reader’s authority. Ask a colleague unfamiliar with the discussion to flag unexplained context or jargon.

Finally, make sure the note is current for the occasion. If a supplier response arrives after drafting, update the issue, implications and opening together. A polished note based on yesterday’s uncertainty may misbrief today’s reader.

The target is a short document that preserves the information needed for sound judgement. Brevity comes from selecting and organising the right evidence, not from hiding uncertainty or removing the detail that changes the decision.