A PRACTICAL NOTE · Formatting

How to apply this guide

Write a reusable risk entry that separates what might happen from what has already happened.

Start with

Say what might happen and what would show it is becoming real. For example, “If the review build is still waiting by Thursday, ask the release owner whether the launch date should move.”

Check before you finish

Paste into a working draft and map each item to the appropriate field. Keep dates, triggers and actions distinct in the final record.

Evidence to keep: Compare the source words with the formatted draft and make sure meaning, names, dates and commitments remain intact. This page’s key limit is: Write a reusable risk entry that separates what might happen from what has already happened.

Start here

A useful project risk note names a possible event, an observable trigger and what to do if it occurs. Speak it that way before asking a writing mode to make it easier to scan.

Start with the condition

Say what might happen and what would show it is becoming real. For example, “If the review build is still waiting by Thursday, ask the release owner whether the launch date should move.”

Add the checking step

State the owner and the next check if known. Review the draft so rewritten language stays conditional and never reports a delay as confirmed before it happens.

Put it in the correct tracker

Paste into a working draft and map each item to the appropriate field. Keep dates, triggers and actions distinct in the final record.

Keep exploring