All posts
AFFiNE
Toeverything·Originally published Aug 22, 2026 · Updated Oct 5, 2026
Project risk register for a fictional store replatform: five rows with IDs, likelihood × impact scores from 16 Critical to 9 Medium, owners and next review dates, one risk moved to the issue log, beside a small 5 × 5 heat map of eight open risks

Risk Register Template for Projects: Free Example and Guide

A project risk register is the one place where a team writes down what could still go wrong, how likely and how damaging it would be, what will warn them early, and who will act. This guide gives you a free template in three formats, a fully worked ten-risk example, a scoring scale you can adopt as is, and the review routine that keeps the register alive.

Quick answer

A risk register is a living table of uncertain future events that could affect a project's objectives. Each row records the cause, the event and its effect, a likelihood and impact rating, a trigger that signals the risk is starting to happen, the planned response, one named owner, a status, a next review date and the risk left over after the response (residual risk). The Association for Project Management describes the register as the place to document risks, their analysis and responses, and to assign clear ownership of actions (APM).

Use one whenever a project has a fixed date or budget, depends on vendors or other teams, or runs longer than a few weeks. Things that have already happened are issues, not risks; they belong in an issue log.

Free downloads (fictional example included, no sign-up):

  • Excel workbook (.xlsx): blank register with score, priority, residual score and overdue-review formulas, dropdowns, the worked example and the scales.
  • Blank CSV and example CSV: the same 24 columns, for Google Sheets or any tool that imports CSV.
  • Markdown copy (.md): the blank table and scales for a document or wiki.

Risk register template you can copy

Paste this into any document or spreadsheet. The downloads split some cells into separate columns (cause, event and effect; residual likelihood and impact) and add date raised, escalation and notes.

IDCause → event → effectL (1–5)I (1–5)Score / priorityTriggerMitigation (now)Contingency (if triggered)OwnerStatusNext reviewResidual L × I
R-01Because … , … may happen, leading to …OpenYYYY-MM-DD
R-02Because … , … may happen, leading to …OpenYYYY-MM-DD

Put three lines above the table: the project name, the register version and data-as-of date, and the role that maintains it. Then paste the scoring scale directly under the table, so a "4" means the same thing to everyone who opens the register later.

What each field is for

FieldWhat to writeRule that keeps it useful
Risk IDR-01, R-02 …Never reuse an ID, even after a row closes.
Cause → event → effectBecause [fact], [uncertain event] may happen, leading to [effect on an objective].One event per row. The cause is a fact today; the event is uncertain.
Likelihood (L)1–5 from the agreed scaleRate the evidence, not the mood of the meeting.
Impact (I)1–5 from the agreed scaleRate the worst effect on one objective: date, cost or scope.
Score and priorityL × I, then the priority bandA sorting aid, not a measurement (see scoring).
TriggerAn observable threshold with a date"More than 2% of records fail on Nov 20", not "if data looks bad".
MitigationWhat you do now to lower the likelihood or the impactA concrete action with a date and an action owner.
ContingencyThe fallback you run if the trigger firesAgreed in advance, with any money or time it needs.
OwnerOne named role accountable for the rowIndividual actions can have other owners.
StatusOpen, Mitigating, Accepted, Escalated, Materialized, ClosedA fixed list, so the register can be filtered.
Next reviewA dateBlank or past dates mean the row is stale.
Residual riskL × I expected after the mitigation is doneIf it is still above tolerance, escalate.

The UK government's project delivery guidance describes the same building blocks: each register entry describes the risk "in terms of cause, event and impact", has a named risk owner who plans, implements and monitors the response, and assigns tasks to named action owners (Government Project Delivery Framework, "Teal Book", chapter 20). HM Treasury's Orange Book lists early warning indicators and contingencies as parts of a risk treatment plan, which is why the trigger and contingency columns earn their place (Orange Book, 2023).

Annotated anatomy of example risk R-01: a cause, event and effect statement; a current rating of 16 Critical; mitigation leading to a residual rating of 8 Medium; a trigger leading to the contingency and the issue log; and the owner, status and next review date
One row, read as a system. Mitigation changes the odds now; the trigger decides when the contingency starts; the owner checks all of it by the review date.

Worked example: a project risk register with 10 risks

The register below is a fictional example written for this article. The bookseller, its store replatform, the roles, dates and numbers are invented; they are not an AFFiNE customer or a real project. It is the same data as the example sheet in the downloads.

Project: online store replatform for a fictional bookseller · Go-live: 2027-02-15 · Register: v1.3, data as of 2026-10-05 · Maintained by: project manager · Scales: the 5 × 5 scale below

Assessment

IDCause → event → effectL × I = scorePriorityTriggerOwnerStatusNext review
R-0114 years of legacy order history with inconsistent customer records → the trial migration fails validation → go-live slips 4+ weeks past Feb 154 × 4 = 16CriticalMore than 2% of records fail validation in the Nov 20 trial migrationData leadMitigating2026-10-12
R-02The new payment provider requires a merchant risk review → approval is not granted before the Dec 15 code freeze → checkout cannot take card payments at go-live3 × 5 = 15CriticalNo approval decision from the provider by Dec 1Finance leadEscalated2026-10-12
R-07Product URLs change format on the new platform → redirects are incomplete at launch → search and bookmarked links break and uncovered categories miss launch3 × 4 = 12HighRedirect map covers less than 95% of the top 2,000 URLs at the Jan 15 crawlMarketing leadMitigating2026-10-12
R-04Marketing asks for loyalty-program features mid-build → change requests are accepted without re-planning → the release slips 2 to 3 weeks or testing is cut3 × 3 = 9MediumMore than two unplanned change requests in one sprintProject managerMaterializedTracked as issue I-03
R-06The agency's fixed-price quote excludes data cleanup → cleanup needs more than 15 agency days → the budget overruns by 3 to 5%3 × 3 = 9MediumCleanup estimate above 15 days after the Oct 30 data profilingVendor managerOpen2026-10-19
R-03Only one developer knows the legacy inventory integration → that developer is unavailable during the cutover window → cutover stalls and go-live slips about a month2 × 4 = 8MediumLeave, illness or resignation notice before Jan 31Tech leadMitigating2026-10-19
R-05Caching on the new platform is untested at peak traffic → the load test at 3x average traffic shows slow pages → launch is postponed by about a month2 × 4 = 8Mediump95 page load above 3 seconds in the Jan 10 load testTech leadOpen2026-10-19
R-09The platform vendor freezes releases from Dec 15 to Jan 5 → a patch we need is not released before the freeze → integration testing slips 1 to 2 weeks4 × 2 = 8MediumAny open vendor ticket of severity 2 or higher on Dec 1Vendor managerAccepted2026-10-19
R-08Warehouse and support staff are trained only on the old admin → training is not finished before cutover → order processing slows and overtime adds 3 to 5% to the budget2 × 3 = 6MediumLess than 80% of staff complete sandbox training by Feb 1Support leadOpen2026-10-19
R-10The freelance copywriter is booked for only 40 hours in January → rewritten category pages are not ready → 12 categories launch with old copy2 × 1 = 2LowDrafts for fewer than 6 categories by Jan 10Marketing leadClosedClosed 2026-09-30

Responses and residual risk

IDResponseMitigation (now)Contingency (if triggered)Residual L × IEscalation / notes
R-01MitigateProfile and clean the top five error types before the trial; run a dedupe script on customer recordsMigrate the last 3 years of orders at launch; keep older history read-only in the legacy system2 × 4 = 8 (Medium)Re-rated from 3 × 4 to 4 × 4 on 2026-09-28 after a sample export showed 3.1% validation failures and 6% duplicate customer accounts. Sponsor informed 2026-09-30 (Critical)
R-02MitigateSubmit all merchant documents by Oct 20; weekly check-in with the provider's account managerKeep the legacy payment integration behind the new storefront for 60 days2 × 5 = 10 (High)Escalated to sponsor 2026-10-02: approve 60-day legacy gateway extension? Decision due 2026-10-09
R-07MitigateBuild the redirect map from analytics top URLs; automated crawl test every sprintHold launch of uncovered categories and serve them from the legacy site1 × 4 = 4 (Low)—
R-04MitigateChange-control rule: every new request must swap out planned work of equal sizeMove loyalty features to a phase-2 release in Apriln/aTrigger fired Oct 2 (three requests in sprint 4); contingency invoked; tracked as issue I-03
R-06MitigateDo the profiling in-house first; cap agency days in a contract amendmentDraw from the 8% contingency reserve; sponsor approval needed above 5%2 × 3 = 6 (Medium)—
R-03MitigatePair a second developer on the integration and write a cutover runbook by Nov 30Integration partner contractor on 48-hour call-off2 × 2 = 4 (Low)—
R-05MitigateConfigure the CDN and run an early load test in the first week of DecemberKeep the legacy site live for two more weeks and switch traffic gradually1 × 4 = 4 (Low)—
R-09AcceptRaise all known vendor tickets before Nov 30Use one week of the schedule buffer for extra testing4 × 2 = 8 (Medium)Accepted by project manager 2026-09-28; within schedule tolerance
R-08MitigateThree sandbox training sessions in January with sign-off per personTwo temporary support agents and extended hours for the first two weeks1 × 3 = 3 (Low)—
R-10AcceptPrioritize the 6 highest-traffic categoriesLaunch with old copy and update after go-liven/aClosed 2026-09-30: all 12 drafts delivered early, so the trigger can no longer fire

Read the register the way a reviewer would:

  • Two Critical rows get weekly attention. R-01 and R-02 are reviewed on 12 Oct, and the sponsor already knows about both.
  • R-02 is escalated, not just high. Even after its mitigation, its residual score is 10 (L2 × I5). That reaches this project's escalation threshold (a residual of 10 or more), so the sponsor must decide whether to fund the 60-day legacy gateway fallback.
  • R-04 shows a risk becoming an issue. Its trigger fired on 2 Oct. The contingency started and issue I-03 was logged. The row stays, marked Materialized, so the history is not lost.
  • R-09 is accepted on purpose. Its residual equals its current score because the team chose not to spend more on it. The contingency (one week of schedule buffer) is still ready.
  • R-10 is closed with a date and reason. It stays in the register.

How to score risks: a 5 × 5 scale you can copy

Agree on the scale with the project sponsor before anyone rates a risk. The impact thresholds below are written for a six-month project with a fixed launch date; change the numbers to fit your project, then keep them fixed for the life of the register.

RatingLikelihood: evidence that fitsImpact: worst effect on one objective
1Rare. No precedent on comparable projects and no warning signs.Minimal. Under 1 week of slip, under 1% of budget, no visible scope change.
2Unlikely. Happened once on comparable work; no current warning sign.Minor. 1–2 weeks of slip, 1–3% of budget, or an internal feature trimmed.
3Possible. Happened on several comparable projects, or one warning sign is present.Moderate. 2–4 weeks of slip, 3–5% of budget, or a planned feature deferred.
4Likely. Happened on most comparable projects, or two or more warning signs are present.Major. 4–8 weeks of slip or a fixed date missed, 5–10% of budget, or a key launch feature deferred.
5Almost certain. Trigger conditions are already forming.Severe. Over 8 weeks of slip, over 10% of budget, or a core objective fails.

Priority bands and review cadence

PriorityScore (L × I)ReviewEscalation in this example
Critical15–25WeeklyTell the sponsor within 2 working days.
High10–14, or any impact of 5WeeklyEscalate if the residual score stays at 10 or more.
Medium5–9Every two weeksOwner manages within tolerance.
Low1–4MonthlyClose when the trigger window passes.

The "any impact of 5 is at least High" rule is deliberate: without it, a rare but project-ending risk (L1 × I5 = 5) would sit in the same band as a frequent nuisance.

One worked score: R-01

  1. Likelihood = 4 (Likely). Two warning signs are present: a 5,000-record sample export shows 3.1% of records failing the new platform's validation rules, and a duplicate check flags 6% of customer accounts. That matches "two or more warning signs". The trigger itself is measured on the 20 Nov trial, so it has not fired. The row was re-rated from 3 to 4 on 28 Sep for this reason.
  2. Impact = 4 (Major). A failed trial means a second clean-up and a second trial, estimated at 4–6 weeks, so the fixed 15 Feb go-live would be missed.
  3. Score = 4 × 4 = 16, so priority is Critical (15–25). Consequences: weekly review, and the sponsor was told on 30 Sep, two working days after the re-rating.
  4. Residual = 2 × 4 = 8, Medium. If the clean-up brings the sample error rate below 1%, likelihood drops to 2. Impact stays at 4: if the trial still fails, the slip is just as long. Only the contingency (migrating three years of orders first) would shrink the impact, and it is used only if the trigger fires.

Why the score is a prioritization aid, not a probability

The numbers 1 to 5 are ordered labels. They are not measurements, so arithmetic on them has limits:

  • 16 is not "twice as risky" as 8. Nothing guarantees that the step from 3 to 4 equals the step from 4 to 5. The Teal Book notes that "scales do not need to be linear".
  • The same score can hide very different risks. In the example, R-03 (L2 × I4) and R-09 (L4 × I2) both score 8. One is unlikely but damaging, the other likely but mild, and they need different responses.
  • Matrices can rank risks wrongly. Louis Anthony Cox Jr. showed that risk matrices compress very different risks into the same cell and can even rate a smaller risk higher. He recommends using them with caution and explaining the judgments built into them (Cox, Risk Analysis, 2008).

In practice: publish the scale inside the register, read likelihood and impact separately (not just the product), look at proximity (a Medium risk whose trigger date is next week may need attention before a High one that is months away), and when a decision depends on money or dates, estimate the days or cost directly instead of arguing whether a score is 12 or 15. When the choice is mainly about money over several years, a cost-benefit analysis template puts those estimates into NPV and payback.

Five by five likelihood and impact heat map of the example project’s eight open risks, with R-01 at 16 Critical and R-02 at 15 Critical, and every cell labeled with its score and priority band
The heat map shows where open risks cluster. Each cell also prints its score and a band letter (L, M, H or C, explained in the legend), so the chart does not rely on color alone.

Text version of the heat map (open risks only; R-04 materialized and R-10 is closed):

Open risksLikelihood × impactScorePriority
R-014 Likely × 4 Major16Critical
R-023 Possible × 5 Severe15Critical
R-073 Possible × 4 Major12High
R-063 Possible × 3 Moderate9Medium
R-03, R-052 Unlikely × 4 Major8Medium
R-094 Likely × 2 Minor8Medium
R-082 Unlikely × 3 Moderate6Medium

How to manage a risk register, step by step

The UK government's project delivery standard asks that risks be identified, given an owner and assessed for impact, likelihood and proximity, then monitored until they are resolved and closed (GovS 002 Project delivery, clause 7.6). Here is that loop as a working procedure.

  1. Identify. At kickoff, at every phase gate and after any scope change, walk the schedule milestones, the assumptions list, the dependencies and vendor contracts, and lessons from similar projects. A useful prompt: "It is launch day and we missed it. Why?" Write each answer as cause → event → effect. If you run the session on sticky notes, group the notes with an affinity diagram before writing rows.
  2. Assess. Rate likelihood and impact with the published scale. When people disagree, record the higher rating and the reason, then revisit it once there is evidence.
  3. Respond. Pick a response type: avoid (change the plan so the event cannot happen), mitigate (reduce likelihood or impact), transfer (move the impact to someone else, for example through a contract), accept (do nothing more, on purpose), or escalate (it is outside the project's authority). Write the mitigation with a date, the trigger, and the contingency.
  4. Assign. Name one risk owner per row and an action owner for every task in the response. Set the next review date from the priority band.
  5. Monitor. In each review, check triggers first, then whether the mitigation work is actually done, then re-rate L and I and update the residual risk. Change the next review date last.
  6. Close or convert. Close a row when the trigger window has passed, the cause has been removed, or the control is no longer needed, and record when, why and by whom. If the trigger fires and the event happens, run the contingency, log an issue and mark the row Materialized. The Teal Book says closed risks should stay on the register with that information.
  7. Escalate. Raise a risk to the sponsor when its residual score stays above tolerance, when the response needs money, people or scope changes beyond the owner's authority, or when the contingency itself would breach tolerance. GovS 002 says risks an owner cannot resolve should be escalated or reassigned. Record who it went to, the decision and the date.
Risk lifecycle loop of identify, assess, respond, assign and monitor, with exits to escalate, materialize or close, above a bar chart of residual risk in which R-01 falls from 16 to 8 and R-02 stays at 10 and is escalated
Every row loops through review until it closes, materializes or escalates. Residual risk is what remains after the response, and it decides whether the row can stay with its owner.

A 20-minute review agenda

  1. Rows with an overdue next review date (the workbook's Review flag column lists them).
  2. Triggers that have fired or will be checked in the next 7 days.
  3. Critical and High rows: is the mitigation work done? Re-rate and update the residual.
  4. New risks from changes since the last review: scope changes, new dependencies, assumptions that turned out false.
  5. Escalations waiting for a decision, and the date they are needed by.
  6. Rows to close, each with a date, reason and name.

Risk vs. issue: when a row leaves the register

A risk might happen. An issue has happened, or is happening now, and needs action rather than monitoring. The Teal Book puts it plainly: "If a risk happens then it becomes an issue".

RiskIssue
TimeFuture and uncertainPresent and certain
Main questionHow likely, how bad, what will warn us?Who fixes it, by when?
ResponseMitigation now, contingency readyResolution actions now
Where it livesRisk registerIssue log
ExampleR-04: change requests may swamp sprint capacityI-03: three unplanned requests landed in sprint 4

When a risk materializes, keep the register row, set the status to Materialized, and write the issue ID in the notes. That link is how a team learns whether its triggers and contingencies worked.

Where the risk register fits in a RAID log and other project documents

A RAID log tracks risks, assumptions, issues and dependencies side by side, usually with one or two lines per item. The risk register is the detailed version of its "R": the place for scoring, triggers, contingencies and residual risk. Small projects can keep everything in a RAID log; once you have more than about ten live risks or need scores and escalation rules, keep a separate register and link to it from the R section. That threshold is an editorial rule of thumb, not a standard. See our guide on how to run a RAID log.

The other items in a RAID log feed the register. An assumption that turns out false becomes a risk or an issue. A dependency on another team that might slip becomes a risk row with that team's delivery date as its trigger. Before a project is funded, the top risks usually appear first in the business case, and the register takes them over once work starts.

DocumentQuestion it answersRelationship to the register
RAID logWhat risks, assumptions, issues and dependencies are live?Summary view; the register holds the detail on risks
Issue logWhat has gone wrong, and who is fixing it?Receives materialized risks
Risk assessmentHow exposed is an activity or site at a point in time?Findings with a project impact become register rows
RACI chartWho is responsible, accountable, consulted, informed?Helps choose risk and action owners
Lessons learnedWhat should we repeat or avoid next time?Closed rows and materialized risks feed it; it seeds the next register

A project risk register is not a workplace hazard assessment or a security risk assessment. Those follow their own legal and industry rules; if that is what you need, start with risk assessment templates for hazards and point-in-time checks.

The register is also one of the core outputs of planning, alongside the schedule, budget and communication plan; see the other project planning phase deliverables. Treat it like any controlled project document, with an owner, a version and a review date, following the same project documentation practices for ownership and version control.

Common mistakes that make a register go stale

  • Writing worries instead of events. "Vendor issues" cannot be rated or reviewed. "Because the provider requires a merchant review, approval may not arrive before Dec 15, so checkout cannot take cards" can.
  • Logging tasks or issues as risks. "Write the test plan" is a task. "The server is down" is an issue.
  • "The team" as owner. If nobody will own a row, the project has accepted the risk without saying so.
  • Monitoring with no trigger. Without a threshold and a date, reviews turn into opinion.
  • Mitigation without residual. If you never re-rate after the work is done, you cannot tell whether the response worked or whether to escalate.
  • Deleting closed rows. You lose the evidence that the risk was managed, and the input for lessons learned.

Keeping a risk register in AFFiNE

AFFiNE does not offer a ready-made risk register template, and its database columns do not calculate formulas. So the most practical setup is the downloaded workbook for scoring, and AFFiNE for the living register, the evidence behind each row and the discussion around it. The steps below use features described in AFFiNE's documentation, release notes and source code as of v0.27.4; we did not test this setup in the app for this article.

  1. Create a page for the project and add the header lines: project, register version, data-as-of date and maintainer.
  2. Insert a database in table view. Use the title for the risk statement, Number columns for likelihood, impact and score (type the score yourself), Select columns for category, priority, response type and status, a Date column for the next review, and Text columns for trigger, mitigation, contingency, owner and residual.
  3. Open any row as its own page to keep the evidence behind a rating, the escalation decision and links to meeting notes.
  4. Add a kanban view grouped by status for review meetings, and a calendar view on the next review date (calendar view was added to databases in AFFiNE v0.27.0, July 2026). Filter the table view to Critical and High before each weekly review.
  5. Use the Edgeless whiteboard for the identification workshop: one sticky note per worry, grouped, then rewritten as rows. Paste the scoring scale into the same page so it travels with the register.

Limits worth knowing as of AFFiNE v0.27.4 (August 2026): database columns have no formulas, so scores do not recalculate; there is no person column, so owners are typed as text; AFFiNE does not send reminders when a review date passes; and its import options include Markdown files but not CSV. If you import the Markdown download, check how its table arrives before you rely on it; we did not test that import.

Sources and method

This page replaces the version published on 2026-08-22. That version used a 3 × 3 scale and leaned on cybersecurity and workplace-safety references. This refresh adds downloadable files, a 5 × 5 scale with a worked score, contingency, escalation and residual risk in the template, and project-delivery sources.

  • How the example was made. The bookseller and every row of its register are fictional, written for this article; no client data or customer outcomes are reported. The example tables on this page, the example sheet in the workbook and both CSV files are generated from one data file, and an automated check compares the values drawn in the four figures with that file.
  • How the files were checked. We opened and recalculated the workbook in LibreOffice 26.8 and Apple Numbers and ran a separate formula evaluator. In all three, every score, priority, residual score and review flag in the example matched the published CSV, and blank rows stayed empty. The file also stores those results, so previews that do not calculate (such as macOS Quick Look) show the same values. We did not test it in Microsoft Excel or Google Sheets.
  • Search intent. We reviewed the current results for "risk register template", "what is a risk register" and "project risk register template" on 2026-10-05. Most offer a download plus a field list; few show triggers with thresholds, residual risk, escalation rules or a warning about multiplying ordinal scores, which is what this page adds.
  • AFFiNE claims were checked on 2026-10-05 against AFFiNE's documentation, GitHub release notes and source code up to v0.27.4. AFFiNE is our product; we kept the claims to what those sources support.

References (all accessed 2026-10-05):

FAQ

Should a risk register be a spreadsheet or a document?

Use a spreadsheet when you want scores and review flags to calculate themselves, and a document or database when the discussion, evidence and decisions behind each risk matter more. Many teams use both: the workbook for scoring and a shared page for the living record.

How many risks should a project risk register have?

There is no standard number. Keep only risks that someone will act on or watch, and close or merge the rest. As a rule of thumb, if you have more than about 30 live rows, split the register by workstream and roll the Critical and High rows up to one summary for the sponsor.

Who owns the risk register?

The project manager usually maintains the register and runs the reviews, while each row has its own risk owner who is accountable for the response. The sponsor sets the tolerance that decides when a risk must be escalated.

Can a risk register include opportunities?

Yes. A risk can be positive: an uncertain event that would help the project, such as a vendor delivering early. Log it with the same cause, event and effect structure, rate it, and plan how to make it more likely or more valuable.