Skip to content
PCProject Controls Assistant

Project risk and issue tracking

See what has happened. Prepare for what might.

Use project updates to identify current problems and future uncertainty. Review each finding, then maintain separate issue and risk logs with the context your team needs.

14-day trial · No payment card required

THE WORKFLOW
  1. Describe the situation

    Record what happened, what may happen and the effect on delivery.

  2. Check the classification

    Review proposed findings and correct their wording, ownership or classification.

  3. Maintain the logs

    Track approved records and update them as the project situation changes.

A risk and an issue need different responses.

A late supplier delivery is an issue when it has already happened. A possible delivery delay is a risk while the outcome remains uncertain. Keeping the distinction clear helps you discuss today's impact separately from the exposure you are trying to prevent.

Review risk records in a dedicated log with ownership and priority.
Review risk records in a dedicated log with ownership and priority. Actual application screen with fictional project data. Open image to enlarge ↗

A worked example

One update. An issue, a risk and an action.

PROJECT UPDATE

The test environment is unavailable today. If access is not restored by Friday, the acceptance test window may slip. Jordan is coordinating restoration with the infrastructure team.

AFTER REVIEW
Issue
The test environment is currently unavailable, preventing planned testing.
Risk
If access is not restored by Friday, the acceptance test window may slip.
Action
Jordan to coordinate restoration of the test environment with the infrastructure team.

The issue, risk and action are related and should be reviewed together. Confirm the likelihood, impact and response using your project's actual evidence.

Before you start

Useful details.

Read the risk register vs issue log guide ↗
Do AI findings enter the official logs immediately?

Proposed findings go to the Review Queue. You can approve, edit or reject them before they become official control records.

Can I maintain records manually?

Yes. Project logs support manually created records as well as approved findings. Keep ownership, impact, response and status current as new information becomes available.

What happens when a risk becomes an issue?

Review the original risk, record the event as an issue and update the risk's status and context as appropriate. Do not assume the original exposure and the resulting problem have identical wording or ownership.

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