Write a weekly launch risk note that a founder can read in five minutes
A compact launch risk note that names the decision at risk, the evidence, the owner, and the next checkpoint.

Lead with the decision at risk
A founder reading a launch note wants to know which decision is now harder. Start with one sentence that names the decision and the risk. For example, the launch may still proceed, but the sales team cannot promise the migration timeline until the technical review closes. That sentence tells the reader why the note matters before any status detail arrives.
Keep the opening to one decision. A note that lists five risks in the first paragraph forces the reader to rank them alone. If several risks are active, choose the one that most affects the launch date, the buyer promise, or the revenue plan. Put the others in a short section below. The first paragraph should earn the next four minutes of attention.
Quantify only what is measured
Use numbers only when the team has a source for them. A count of open approval requests, a percentage of assets reviewed, or a date from a dependency tracker is useful. A phrase such as most of the work is done is not a measurement. If the team has no number, say the status is unknown and name the check that will produce one.
Put the number beside the decision it affects. A completion count without a threshold does not tell the reader whether the launch is ready. Write the threshold the team agreed on and the current value. If the threshold changes, say who changed it and why. A measured risk note lets the reader compare this week with last week without opening a dashboard.
Name one owner per risk
Each risk needs a person who can move it, not a department. Write the owner's name and the action they have agreed to take. If the risk depends on a decision from someone else, name both the owner and the decision maker. A risk assigned to a team without an individual contact tends to wait for the next meeting. The note should make the next conversation obvious.
Separate the owner from the person who reports the risk. The reporter may be a coordinator who tracks the dependency, while the owner is the manager who can resolve it. Record both roles so the reader knows who to contact for status and who to contact for a decision. This distinction prevents the coordinator from being blamed for a delay they cannot control.
Separate new risk from known risk
Label a risk as new only when it appeared since the last note. A known risk that has not moved belongs in a separate section with its age and the reason it is stuck. Mixing the two makes the note look more volatile than the launch actually is. It also hides the risks that are quietly getting older while the team reacts to the newest item.
Give each new risk a first-seen date and each known risk an age in days. Review the known risks first in the reader's mind by placing them before the new items if they are more serious. The order should follow decision impact, not novelty. A founder should be able to see whether the same issue has been open for three weeks or three hours.
Show what changed since last week
Add a short change section with three lines: what moved, what did not, and what the team learned. Keep each line tied to a risk or a decision. This section replaces a general status narrative and gives the reader a way to check progress. If nothing moved, say so plainly and explain why. A note that reports activity without movement trains the reader to skim.
Use the prior note as the comparison point. Carry forward the risks that are still open and close the ones that have a documented resolution. Do not delete a closed risk from the record; move it to a resolved list with the date and the evidence. The change section should be readable on its own, even if the reader did not open last week's note.
End with the next checkpoint
Close with the date and purpose of the next checkpoint. Name what the team expects to know by then and who will provide it. A vague next update invites the reader to ask for status before the team has anything new. A specific checkpoint tells the reader when to expect a changed decision and what would cause it.
Keep the note to one page and send it at the same time each week. A predictable rhythm is more useful than a polished report that arrives at random. Save each note in the launch record so the team can trace how a risk evolved. The archive also helps a new owner understand why a decision was made without reconstructing the entire launch history.