PROJECT RISK REVIEW NOTE
Manual client-delivery planning record. Not a probability forecast, occurred-issue log or specialist assessment. Replace bracketed fields and remove the fictional example before use.

PROJECT AND ENTRY
Client/project: [reference]
Risk entry ID and note date: [reference/date]
Scope of this review: [ordinary delivery commitment]

POSSIBLE EVENT AND CONSEQUENCE
What may happen: [specific possible event]
Affected commitment: [practical consequence]
Information/reference available: [agreed location]
What remains uncertain: [unknowns]
Priority reason: [human judgement and its basis; no invented forecast]

SIGNAL AND PREPARATION
Early signal and when to check: [specific observation/checkpoint]
Preventive action: [what can be done beforehand]
Coordinating owner: [agreed person]
Others helping and approval needed: [people/decision]
Action due date: [agreed date]

IF THE EVENT OCCURS
Response to agree: [current decision/action]
Who can authorise a changed commitment: [agreed role]
Linked issue/action record if event occurs: [reference]

NEXT REVIEW
Next review date and owner: [date/person]
Current state: [possible event / signal checked / occurred issue linked / no longer applies, with reason]
Information changed since last review: [observed evidence]
Decision and reference: [agreement]
Next action and due date: [person/date]

FICTIONAL COMPLETED NOTE
Birch Relay Studio, Tidal Press, Mina, Theo, references and dates below are invented illustrations, not customers or measured results.

Project and entry:
Tidal Press product leaflet, reference TP-LEAFLET; risk DR-01. Current note dated 22 October 2026.
Possible event and consequence:
Approved copy may arrive after the agreed 30 October input date, affecting the first layout planned for 3 November.
Information and uncertainty:
The team has an agreed input date but has not confirmed who will approve the final copy. It does not know how likely a delay is.
Priority reason:
Review this before layout preparation because approved copy is a required input. This is the fictional team's judgement, not a numerical risk rating.
Early signal:
At the 27 October checkpoint, ask whether the client has confirmed the copy approver and whether the agreed input date remains achievable. An unresolved answer calls for discussion; it is not proof of a missed deadline.
Prevention and owner:
Mina will confirm the copy owner and approval route by 26 October. Theo will record the agreed reference in the project notes.
If the event occurs:
If the input date passes without approved copy, record the occurred issue and discuss the affected layout sequence with the client before agreeing a revised commitment.
Next review and current state:
Mina reviews DR-01 on 27 October 2026. Open, response planned; the event has not occurred in this example. No reduction in likelihood has been established.