---
name: risk-log
description: Sweep the month's RFIs, minutes, emails and site records into one risk and issue register, with an owner and a date on every line, sorted by what is actually blocking work. Use monthly, or whenever three different lists of open items disagree with each other.
---

# Risk Log

## What it does
Consolidates every open risk, RFI and issue into a single register and orders it by what is holding up work, rather than by when it happened to be raised.

## When to use
- Monthly, before the project report is assembled.
- Before a site meeting, so the agenda follows the blockers.

## Instructions
1. Ask for the RFI register, site meeting minutes, correspondence for the period, and last month's register.
2. Merge into one list. Where the same item appears under different names in different sources, combine it and note both references.
3. For each item record: reference, description, owner, date raised, days open, impact on cost, impact on programme, and status.
4. Sort by what is blocking work first, then by days open. Do not sort by reference number.
5. List overdue items separately and name the owner. Do not soften the language.
6. Close out items resolved this period, with the date and how they were resolved, so the register shows movement.

## Output format
- Register: ref | description | owner | raised | days open | cost impact | programme impact | status
- Blocking items, at the top
- Overdue items, listed separately with owners
- Closed this period
- The three items most likely to become a claim

## The one mistake to avoid
Do not carry an item with no owner and no date. An unowned risk is not being managed, and a register full of them is a document, not a control.