A RAID log is easy to start and hard to keep honest. Husn reads the work and keeps risks, issues, assumptions, and dependencies reflecting what is actually open.
An open issue on the log was resolved in a ticket six days ago, but the row is still flagged red.
Changed
A new blocker has been live in Slack for two days and is not on the log yet.
Risk
A dependency row still shows a date that moved last week, so two teams read it differently.
Watch
1 resolved not closed - 1 missing item - 1 stale date
The problem
Risk and issue log template
A risk and issue log starts clean and slowly stops being trusted. Risks get added but rarely closed, issues get resolved in a thread without anyone updating the row, and dependencies sit on the log long after they have shifted. Within a few weeks the log is a mix of stale and live items, and no one is sure which is which.
Items go on the log and never come off, so it fills with closed work that no one had time to clear.
An issue gets resolved in Slack or a ticket, but the row stays open because updating the log is a separate chore.
Risks and issues blur together, so the log cannot tell you what is a present problem versus a future threat.
Why this gets hard at scale
Why a RAID log decays
01
A log is a side artifact. The real work happens in Jira and Slack, so the log lags whatever it is supposed to track.
02
Closing items is invisible work. There is no prompt when an issue is resolved elsewhere, so the row stays open by default.
03
As scope grows, the log grows faster than anyone can groom it, so trust in it erodes exactly when you need it most.
How Husn helps
Step 01Husn reads Jira, Slack, and your docs and keeps each log entry current, opening new items and flagging ones that look resolved in the work.
Step 02It identifies risks and issues from tickets, threads, and updates as they form, then sorts them into the right RAID category with a source attached.
Step 03Dependencies on the log stay accurate, because Husn notices when a linked date or owner has moved even if the row was never touched.
Husn reads and reasons, and never changes your tools.
What is inside
The sections, in the order leaders read them.
01Risks: future threats with likelihood, impact, owner, and mitigation.
02Assumptions: stated beliefs the plan depends on, flagged when they break.
03Issues: present problems that are already affecting delivery, with status.
04Dependencies: cross team links with the date and owner they rely on.
05Owner and status fields: kept current against tickets and threads.
06Source and last changed: the work behind each row and when it last moved.
Keep risks, assumptions, issues, and dependencies in one place that Husn grooms from the work, so the log stays worth opening.
Nothing falls off
Catch the blocker discussed in a thread that never made it onto the log, before it becomes the reason a date slips.
Clean closure
See items that look resolved in the work but are still open on the log, so the RAID reflects what is actually live.
Who this is for
Built for the people who have to keep it all straight.
Delivery and program managers
PMO and project leads
Technical program managers
Chiefs of staff
FAQ
Questions, answered.
What does the template cover?+
Risks, assumptions, issues, and dependencies in one RAID style log, each with owner, status, source, and a note on what changed.
How does Husn keep it current?+
It reads Jira, Slack, and your docs, opens new items as they appear in the work, and flags rows that look resolved or out of date so the log stays honest.
Does Husn modify the log in our tools?+
No. Husn reads and reasons only. It surfaces what changed and never posts, edits, or moves anything in Jira, Slack, or your documents.
Can it tell a risk from an issue?+
Yes. Husn separates present problems from future threats and files each item in the right RAID category, so the log reflects what is happening now versus what might.