Evidence-backed project assurance
A RAID log grounded in what the project actually knows
Reqify generates a live Risks, Assumptions, Issues and Dependencies register from your project context — owners, mitigations, status, review dates, and an audit trail of every change.
- Owners assigned automatically
- Probability × impact scoring
- Review-date reminders
- Excel export
Most RAID logs are a single workshop, then a stale spreadsheet
Every project starts a RAID log. Few have one a month in that anyone trusts. The pattern is familiar: a workshop fills a spreadsheet, ownership is "PM" by default, scoring is "high/medium/low" with no rubric, and three weeks later half the risks are obsolete and the new ones never made it in. By the time of the steering committee, the PM is rebuilding the log the night before from Slack threads.
The reason is not that PMs are lazy. It is that RAID logs are operational artefacts: they have to absorb new information continuously, retain history, and surface what changed since the last review. A static spreadsheet cannot do this. A live register inside a tool can.
Generic AI document generators will produce a one-off RAID log that looks fine and goes stale immediately. That is the wrong shape of solution.
How Reqify keeps a RAID log honest
Reqify generates the initial RAID log from your discovery files, transcripts, business case, and risk-register history — with an owner pulled from your stakeholder context, a probability and impact score against a documented rubric, a mitigation or contingency, and an explicit review date. Each entry has a stable ID so it can be referenced from minutes, status reports, and other Reqify artefacts.
The log is then a living register. Update an entry and the audit trail records what changed, when, and by whom. The next status report is generated against the current RAID state, so risks that have actually changed are surfaced — not just whatever the PM remembers in the meeting.
When the model is unsure — an unowned risk, a dependency with no target date — it flags the gap inline rather than guessing. You see what is grounded versus what needs a PM decision.
Why this RAID log is different
Real scoring rubric
Probability × impact with a documented rubric — not arbitrary high/medium/low. Heat-map view by category.
Owners pulled from context
Reqify proposes owners based on stakeholder context (RACI, project sponsor, workstream leads). Re-assign with one click.
Review-date reminders
Each entry has a next-review date. Notifications fire before steering committees so nothing goes stale silently.
Audit trail per entry
Every change is logged with who, when, and why. The steering pack can show "movement since last meeting" automatically.
Mitigation and contingency
Each risk carries a mitigation (reduce probability) and a contingency (response if it materialises). No more empty cells.
Feeds your status reports
When Reqify writes a status report, it pulls from the current RAID state — so the RAG status is grounded, not vibes.
From discovery files to a maintained register
- Step 1
Add your project context
Discovery files, business case, stakeholder register, prior risk logs. Reqify indexes them against the RAID schema.
- Step 2
Generate the first cut
Under a minute. Reqify emits initial Risks / Assumptions / Issues / Dependencies with owners, scoring, and mitigations.
- Step 3
Tune the rubric
Confirm or adjust the probability × impact rubric for your organisation. Categories and severity bands are configurable.
- Step 4
Maintain in the editor
Update entries as the project moves. The audit trail captures changes. Review-date reminders fire automatically.
- Step 5
Report and export
Excel and PDF export. Heat-map view. Movement-since-last-meeting view for steering packs.
Built for project governance that holds up
- Programme PMs running multi-workstream delivery
- PMOs standardising RAID rubrics across projects
- Senior BAs feeding risk into BRDs and business cases
- Consultancy PMs reporting weekly to a client steering committee
- Bid PMs writing RAID into proposals
- Audit and assurance teams who need a defensible risk register
RAID log generator FAQ
What does RAID stand for here?+
Risks, Assumptions, Issues, and Dependencies — the four categories tracked in the same register. Reqify keeps them in one log with category filters, because risks become issues and dependencies become risks, and you want the trail in one place.
How is scoring done?+
Probability and impact each scored 1–5 (configurable), with a documented rubric so the scores are comparable across projects. Heat-map view groups entries by score band. Reqify proposes scores; you adjust.
Will the owners be accurate?+
Reqify proposes owners from your stakeholder context (RACI table, project sponsor, workstream leads). When ownership is ambiguous it flags the entry as unowned rather than guessing — so the register stays honest.
Can I export to Excel?+
Yes — one-click .xlsx with the same column structure your PMO already uses, plus PDF for steering packs. Filters and the heat-map view export too.
Does this integrate with anything?+
Team plan includes Jira and Confluence integrations. RAID entries can mirror as Jira issues or Confluence-table content. Slack notifications for review-date reminders are configurable.
How is this better than a spreadsheet?+
Spreadsheets are great for editing but terrible for governance: no audit trail, no review reminders, no link from a risk to the BRD assumption it came from, no movement-since-last-meeting view. Reqify gives you all of that without taking the spreadsheet ergonomics away.
Related governance artefacts
AI Business Case
Risks roll up from the RAID log into the business case automatically.
AI Project Charter
High-level risks for the charter pulled from the RAID log.
Reqify for PMs
Status reports, change requests, and the rest of the PM suite.
AI BRD Generator
Assumptions in the BRD feed the RAID assumptions track.
A RAID log that earns trust, not eye-rolls
Generate the first cut in a minute. Keep it alive with audit trails, review reminders, and steering-ready exports.