Risk Register
Keep every risk the team is tracking in one editable sheet -- for the whole project, an area, an activity or a task chain -- then read what has already landed.
Not assignedEvidence detailsChecking
Risk Register content
What needs a decision before work proceeds?
Capture what was known, assign a response, and retain each decision. These are team assessments, not schedule facts or permission to execute.
Choose an authorized review in the workspace header.
Sample candidates are synthetic and are not adopted automatically. Working sheet edits and this journal remain separate; old trimmed cell history cannot be reconstructed.
Evidence when assessed and current context
Record an assessment or decision
Durable decision history
Recorded time is when the decision was captured; Data Date belongs to its schedule evidence. Earlier assessments are not rewritten.
The page’s PDF and Excel downloads include the complete verified decision journal: captured evidence, responses, acceptance and revision history. Each download captures its own point in time; later decisions do not rewrite it. CSV remains the working sheet only.
Type straight into the grid the way you would in Excel, or use the line below. A risk belongs to the whole project -- a noise or traffic complaint, a permit condition, a utility outage -- unless you name an area in Applies to or link it to activities or a task chain in the schedule.
By area and by owner
Open and mitigating risks by where they sit -- the ISA-95 area an IFC tag declares on the linked work, else its top WBS level, else what Applies to says -- and by who owns them. A risk linked to work in several areas counts in each, so the areas do not add up to the register.
Types of risk response
Every risk takes one of four responses. The control measures say what will be done; the action steps say who does it and by when.
- Reduction
- Put control measures in place to reduce the risk exposure to an acceptable threshold or level (mitigation).
- Avoidance
- Put control measures in place to eliminate or remove the risk.
- Sharing / Transfer
- Move the risk to a third party -- for example insurance cover or a liability clause in the contract.
- Acceptance
- Accept that the risk is unavoidable, but put the necessary contingency measures in place. Acceptance does not mean doing nothing.
Does the matrix earn its colours?
The colours are a screening device: they get risks named and argued about. They are a poor ranking instrument -- a likelihood-by-impact grid tiles the square with rectangles while equal-risk lines are curves, so a higher colour can hold a smaller risk (Cox 2008, “What's wrong with risk matrices?”). Write down what each level means in numbers and the register tests its colours, and ranks your risks by expected days instead.
Contingency against expected exposure
The contingency the project holds for each category of risk, set against what the open and mitigating risks are expected to cost: probability times estimated cost, as entered. A risk without both is named and not counted. This is declared arithmetic, not a simulation.
Start from common risks for this job
Tick the ones that apply to this job and add them in one go. They arrive unrated, so the team sets its own likelihood and impact. Risks under From the schedule are offered because the newest schedule still has that kind of work to do; each says which activities it was read from.
IFC tags: ISA-95 and the supply chain
Write the IFC class and tag of what an activity builds into its name -- for example Set IfcPump P-101 on plinth -- and every other activity that names P-101 joins it. Each tagged element is walked to its ISA-95 level, its supply category and the supply stages the schedule shows for it. A stage not shown is not missing work: the schedule may simply not model it. The tables are declared product conventions, not the plant's own equipment hierarchy.
Your columns
Add free-form columns for anything your team tracks -- a neighbour contact, a permit reference, a trigger to watch for. Removing a column hides it; what was typed in it is kept.
Double-click or start typing to edit. Alt+Enter adds a line inside a long text cell. Paste a block copied from Excel to fill cells, or paste a whole sheet with its header row to add every row at once. Likelihood and impact are your own 1 to 5 ratings: their product ranks the sheet and is not a probability, and the estimated days and cost are the team's estimates, not a computed slip.
Select a row to write its preferred mitigation in full and to read or add notes.
A risk has not happened and carries probability times impact. An issue has, and carries a severity. A shock came from outside the project. Nothing here infers a cause.
Observed records carry a source. Modelled records are plausible reconstruction, not evidence. Counts are separate; register totals include both lanes and are not observed-only findings.
Probability times impact across all supplied risk statuses, including realized and retired. Largest exposure first. This weighting is not forecast delay.
Choose a project.
Front-days are working days lost on the affected front. A front holding float can lose days without the project moving, so this is a workload figure and never a schedule variance.
Choose a project.
A shock is dated and hits named fronts. That an issue followed one is a sequence, not a cause.
Choose a project.
The share of issues carrying a risk link. It is not a grade or proof of prior anticipation: chronology is not checked.
Choose a project.
Review status and evidence steps
Steps of the decision on this page.
