A template gives you the right fields to assess a risk. The harder part is reassessing as the project moves. Husn reads the work and keeps each rating reflecting current reality.
A risk assessment is a snapshot of judgment at one moment. You score likelihood and impact at kickoff, assign an owner, write a mitigation, and then the project changes around the assessment while the numbers stay where you left them. By the time someone revisits the sheet, the highest scored risk is often no longer the one that matters most.
Scores are set early and rarely revisited, so a risk that has grown more likely still reads the same as it did at kickoff.
Mitigations get written once and not tracked, so the sheet says handled while the underlying issue is still live.
Owners move teams or leave, and the assessment keeps pointing at someone who no longer holds the risk.
Why this gets hard at scale
Why a template alone is not enough
01
Assessment is continuous work. Likelihood and impact change as the project moves, but a static sheet captures only the day it was filled in.
02
The evidence that should change a score lives in the work. A slipped ticket or a worried thread should raise a rating, but nothing connects them to the sheet.
03
As a portfolio grows, reassessing every risk by hand becomes impossible, so the assessment decays exactly when accurate scoring matters most.
How Husn helps
Step 01Husn reads Jira, Slack, and your docs and fills the assessment fields automatically, so each row arrives with its source attached.
Step 02It identifies risks from tickets, threads, and updates as they form, then flags when likelihood or impact has changed since the last score.
Step 03Mitigation status stays honest, because Husn notices when the work behind a mitigation has stalled even though the sheet still says it is in progress.
Husn reads and reasons, and never changes your tools.
What is inside
The sections, in the order leaders read them.
01Risk description: a plain statement of the risk and the assumption it threatens.
02Category and likelihood: where the risk sits and how probable it is on your scale.
03Impact and score: the cost if it lands and the combined rating that ranks it.
04Owner: the single person accountable for tracking and responding.
05Mitigation: the action in flight to reduce likelihood or impact.
06Status: open, mitigated, accepted, or closed, kept current against the work.
Set likelihood and impact at kickoff and let Husn flag when the work has moved the rating, so you reassess what actually changed.
Honest mitigations
See when a mitigation marked in progress has gone quiet in the tickets, before a review assumes it is handled.
Owner continuity
Catch risks whose owner has moved on, so no high impact item sits with someone who no longer holds it.
Who this is for
Built for the people who have to keep it all straight.
Project and program managers
Delivery and engineering leads
PMO and risk owners
Chiefs of staff
FAQ
Questions, answered.
What fields does the template include?+
Risk description, category, likelihood, impact, a calculated score, owner, mitigation, and status. Enough to assess a risk fully without becoming a form no one fills in.
Does Husn fill it in for me?+
Yes. Husn reads Jira, Slack, and your docs, populates the fields, and flags when a score or mitigation no longer matches the work behind it.
Will Husn change my tools?+
No. Husn reads and reasons only. It never posts, edits, or moves anything in Jira, Slack, or your documents.
Can I keep my own scoring scale?+
Yes. The template uses standard likelihood and impact fields, and Husn maps the work into whatever scale your organization already uses.