Skip to content
PCProject Controls Assistant
← All resources

Practical guide

Risk register vs issue log: differences and examples

An issue describes a condition that already exists. A risk describes an uncertain event or condition that could affect delivery. Keeping them distinct makes the response and reporting clearer.

Start with what is known today.

Ask whether the condition has already occurred or is still uncertain. If a supplier has missed an agreed date, record the missed delivery as an issue. If the supplier may miss the date, describe the uncertainty as a risk.

A current issue can also create a separate future risk. An unavailable test environment is an issue today; a possible delay to acceptance testing is a future consequence you may need to manage as a risk.

A useful writing pattern

Issue: “The test environment is unavailable, preventing planned testing.”

Risk: “If access is not restored by Friday, acceptance testing may finish late.”

Classify the situation, then choose the response.

SituationClassificationPractical response
A key specialist may be unavailable during cutover.RiskConfirm availability and prepare cover before the cutover window.
The specialist is unavailable and cutover preparation is blocked.IssueAssign cover and assess the immediate effect on the plan.
A supplier has missed the interface delivery date.IssueAgree a recovery plan and record the revised forecast.
The missed interface delivery may shorten end-to-end testing.Related riskAssess the remaining test window and agree a contingency.
“Please confirm supplier delivery by Tuesday.”ActionName an owner, set the due date and track the response.

What belongs in each log?

For a risk register

Record a reference, the cause or trigger, the uncertain event and the potential effect on objectives. Add an owner, likelihood and impact assessment, response, review date and current status. Use your organization's agreed scoring method.

For an issue log

Record a reference, the condition that exists, when it was identified and its current effect. Add an owner, severity or priority, resolution plan, target date, status and closure evidence.

Assign follow-up work to action records where useful. A log entry explains the condition; the action explains who will do what and by when.

What to do when a risk happens.

  1. Confirm the event. Check what happened and when. The actual effect may differ from the original forecast.
  2. Record the issue. Describe the current problem and its observed impact, with an accountable owner and a response.
  3. Update the risk. Record that it occurred and reference the related issue. Reassess any uncertainty that still remains.
  4. Reconcile the report. Explain the change without counting the same exposure twice or implying that creating an issue resolved the problem.

Keep a traceable reference between related records using the fields or description available in your project system.

Review the wording against the evidence.

“Testing is late” does not explain the cause, impact or response. “Testing is one day behind the approved plan after late supplier files; the test lead is confirming recovery options” gives the team a condition it can discuss and manage.

Project Controls Assistant proposes risks and issues from your updates for review. Confirm the classification and details before adding findings to the official logs.

Explore risk and issue tracking →

From update to reviewed report

Put your next project update to work.

Try Project Controls Assistant with your own project. Review every finding before it enters your logs.

Start a free trial 14-day trial · No payment card required