Get Marketing Insights First
Subscribe to receive actionable strategies, growth tips, and industry insights delivered straight to your inbox.
The Risk Signal
· Construction control briefing
Issue 03 · Living register
Jira risk register for construction
See the risk before it becomes the issue
A practical blueprint for building a living construction risk register in Jira—connecting uncertainty, named ownership, treatment action and executive visibility before cost or schedule exposure materializes.
Read the control brief
13-minute read · ISO 31000 aligned
Control principle
A risk is a possible future event—not a defect already found.
Risk management starts before failure
Jira should preserve the line between anticipation and response while keeping both sides traceable.
Risk
An uncertain event that could affect cost, schedule, quality, safety or project objectives.
- Probability and impact are assessed.
- A named owner monitors a trigger.
- Mitigation changes residual exposure.
Realized issue
A defect, NCR, incident or change that now requires operational response and verified closure.
- Actual consequence is recorded.
- Corrective workflow is activated.
- Delivery or service teams resolve it.
When a risk materializes, create and link the operational issue. Do not convert or overwrite the original risk record—the comparison between forecast and outcome is valuable evidence.
The risk record
Capture the event, exposure and response
A useful register is more than a red–amber–green list. Its fields must support a clear risk statement, defensible prioritization and accountable treatment.
Frame the uncertainty
- Permanent risk ID
- Cause → event → consequence statement
- Category, project and affected phase
- Observable trigger point
Quantify the exposure
- Probability and impact score
- Cost: minimum / likely / maximum
- Schedule: minimum / likely / maximum
- Inherent and residual rating
Make response accountable
- One named risk owner
- Avoid / transfer / mitigate / accept
- Treatment actions and due dates
- Contingency plan and review date
Probability × impact
The 5×5 heat map
| Probability | 1 · Negligible | 2 · Minor | 3 · Moderate | 4 · Major | 5 · Severe |
|---|---|---|---|---|---|
| 5 · Almost certain | 5 | 10 | 15 | 20 | 25 |
| 4 · Likely | 4 | 8 | 12 | 16 | 20 |
| 3 · Possible | 3 | 6 | 9 | 12 | 15 |
| 2 · Unlikely | 2 | 4 | 6 | 8 | 10 |
| 1 · Rare | 1 | 2 | 3 | 4 | 5 |
1–4 · Watch
Monitor through the normal review cadence.
5–10 · Manage
Assign an owner and confirm proportionate action.
12–16 · Escalate
Active treatment and project-manager visibility.
20–25 · Intervene
Senior attention, response assurance and trigger monitoring.
Illustrative bands based on the supplied study. Calibrate thresholds to the organisation’s risk appetite, contract and assurance model.
The operating workflow
Make the lifecycle mirror the risk process
A generic To Do / In Progress / Done flow hides the decisions that matter. The status model should show how understanding, treatment and residual exposure are changing.
Identified
Capture cause, possible event, consequence and initial owner.
Under analysis
Score probability and multi-dimensional impact.
Evaluated
Compare the rating with appetite and escalation thresholds.
Treatment planned
Select the response and approve actions, dates and contingency.
Treatment active
Execute linked mitigation tasks and remove blockers.
Monitoring
Reassess residual risk and watch the trigger point.
Closed / accepted
Record the decision, approval and final residual position.
Materialized
Preserve the risk and create a linked operational issue.
!
Materialized is a controlled handoff, not an endpoint
Automation can create and link the relevant Jira Software change, JSM defect/NCR or safety incident while retaining the original forecast, owner, trigger and treatment history.
A risk register is only live when the field can change it.
Monitoring and review
Build a cadence that prevents stale certainty
Risk information decays. Review dates, reminders and named owners turn the register into a working control rather than a one-time workshop record.
Notify before the review date
Give the owner enough time to reassess the trigger, probability, impact and treatment progress.
Flag stale risks
Surface entries that have exceeded the agreed cadence—often 30 days for active project risks.
Escalate high exposure
Route overdue high-rated items to the project manager or risk coordinator automatically.
Record residual movement
Show whether treatment is actually reducing probability, impact or total portfolio exposure.
Decision-ready reporting
Put exposure, age and action on the same page
Every dashboard should answer a decision question. Use Jira filters, gadgets and marketplace extensions to combine live risk data into views for project teams and executives.
Heat map
Where are current risks concentrated across the 5×5 matrix?
Top risks
Which open items require steering-committee intervention now?
Category exposure
Is uncertainty clustering in design, ground, procurement or HSE?
Cost and schedule
What probability-weighted contingency is the portfolio carrying?
Review compliance
Which risks are stale, overdue or missing an accountable owner?
Treatment tracker
Which mitigation actions are overdue, blocked or reducing exposure?
Realized trend
Which forecast risks became issues, and what was the consequence?
Residual trend
Is total post-treatment exposure reducing across the project?
Named accountability
One owner per risk, several expert contributors
A department cannot watch a trigger or approve a response. Assign one accountable person while drawing analysis from the disciplines that understand the exposure.
Risk manager / coordinator
Owns the register model, workshops, matrix and review discipline.
Project manager
Approves treatments, accepts exposure and escalates high-rated risks.
Named risk owner
Monitors the trigger, delivers mitigation and updates residual assessment.
Commercial / QS
Validates three-point cost ranges and contingency implications.
Planner / scheduler
Maps schedule impact to activities and validates time ranges.
Design, HSE and site leads
Own category-specific analysis and related treatment actions.
Executive sponsor / client
Approves formal acceptance of high residual exposure.
Jira administrator
Configures fields, workflows, automation, permissions and integrations.
A practical start
From workshop spreadsheet to living Jira register in 90 days
Start with one project, one calibrated matrix and a disciplined weekly review. Add quantitative complexity only after the team trusts the core record.
Define the control model
- Appoint the risk coordinator and pilot project.
- Agree categories, 5×5 scoring and appetite bands.
- Configure the Risk work type and core fields.
- Import and clean the current register.
Make review unavoidable
- Launch the ISO-aligned workflow and owner views.
- Add review reminders and high-risk escalation.
- Link treatment actions to Jira delivery tasks.
- Run the weekly meeting from the live register.
Report and calibrate
- Publish heat map, ageing and treatment dashboards.
- Add residual, cost and schedule exposure reporting.
- Test the materialized-risk handoff end to end.
- Refine permissions and create the program template.
The value is not the number of risks logged. It is the exposure changed.
Measure whether treatments reduce residual risk, whether owners review on time and whether anticipated events are handled before they become expensive surprises.
Key sources and further reading
Editorial note
This newsletter is an editorial adaptation of the supplied “Jira Risk Register – Detailed Use-Case Construction Risk Management” study. Scoring bands, review intervals, access controls and acceptance authorities should be calibrated to each organisation’s risk appetite, assurance framework and contracts.
Photography: Umut Karabulut / Pexels and Israel Torres / Pexels . Product interface image: Atlassian .
Jira and Atlassian are trademarks of Atlassian. This independent use-case study is not sponsored by, endorsed by or affiliated with Atlassian.
Important updates waiting for you!
Consectetur eget cras neque augue malesuada urna urna hendrerit tellus.