Use casesProject risk register

Build your project risk register.

Keep project risks, response plans and review dates separate from actual issues.

How to build your project risk register

  1. Describe the job

    Keep project risks, response plans and review dates separate from actual issues.

  2. Review the first version

    Choose how the risk owner records the risk and how the project reviewer reviews the next step.

  3. Refine the views

    Ask First to adjust the fields and views for the people who will use the app.

  4. Test before sharing

    Walk through the process with a sample record and check who owns the next action.

A project risk register example

A forecast delay may affect a roof delivery.

Illustrative workflowProject risk register

Project risk register example

Record
Project risk register · 01
Owner
Risk owner

Current stage · Risk owner

Open the risk

A forecast delay may affect a roof delivery.

Read the full walkthrough
  1. Open the risk

    A forecast delay may affect a roof delivery.

    Record:
    Project risk register · 01
    Owner:
    Risk owner
  2. Review the issue reference

    Record a risk response before a delay occurs; if the delivery misses its date, link an actual issue without deleting the original risk assessment.

    Stage:
    Review pending
    Owner:
    Project reviewer
  3. Link the actual delay to the original risk

    Link the actual delay to the original risk without erasing the earlier assessment.

    Next action:
    Link the actual delay to the original risk without erasing the earlier assessment.
    Owner:
    Project manager

What to include in your project risk register

  • Keep the risk in context

    Keep risk, cause, possible effect, owner, response, review date and issue reference together so the next person can understand the request or record.

  • When the next step needs a decision

    A forecast delay may affect a roof delivery. Record a risk response before a delay occurs; if the delivery misses its date, link an actual issue without deleting the original risk assessment.

  • Keep issue reference visible

    Link the actual delay to the original risk without erasing the earlier assessment.

  • Choose what each person needs

    Give the risk owner a working view and the project reviewer a review view. Keep risk and cause attached to the decision as the work moves between them.

Questions about project risk register

Start with risk, cause, possible effect, owner, response, review date and issue reference. Describe who enters the information and who reviews the next step.

Build your project risk register.

Start with your workflow and make it yours.

Get started