A risk register that names what could go wrong, scores it, gives it an owner, and comes back to you on a schedule instead of dying in a kickoff document. Describe the engagement and a Taskade Genesis app builds the register: risk, cause, likelihood, impact, mitigation, owner, review date, and current status.
The Monochrome Project Dashboard is a live Taskade Genesis app embedded on this page. It tracks project items with a status and a severity, which is one step away from a register, so use it as the starting point: try it here, then click "Use this app" to clone it in about ten seconds and describe your own engagement so the rows become scored risks with owners, triggers, and mitigations.
The point of a risk register is not prediction, it is pre-agreement. When a risk you named in week one materializes in week six, the conversation is about the mitigation you already agreed rather than about whose fault it is. Workspace DNA keeps it alive. Memory holds what went wrong on comparable engagements, so the register starts from experience rather than imagination. Intelligence, backed by 15+ frontier models from OpenAI, Anthropic, Google, and open-weight providers, proposes the risks your scope implies, scores them consistently, and drafts mitigations. Execution reviews the register on the cadence you set and escalates anything that moved.
The register renders in every layout you need:
- Table view for the scored grid with likelihood, impact, and mitigation owner
- Board view for grouping risks by status: open, mitigated, materialized, closed
- Calendar view for review dates and mitigation deadlines
- List view for the readable summary that goes in the steering pack
- Plus the rest of the 7 project views
Automations make the register a habit. Connect Taskade automations so a fortnightly review opens with only the risks that changed, any high-scoring risk without a mitigation owner escalates, and a risk that materializes creates the response tasks immediately. With 100+ bidirectional integrations, your delivery records and Gmail pull signals in while Slack pushes escalations to the right person.
The AI agents inside the app carry 34 built-in tools including persistent memory, web search, file analysis, custom slash commands, and multi-agent collaboration. Ask the agent to write the pre-mortem, imagining the engagement failed and explaining why, and you will get a better register in five minutes than an hour of polite brainstorming produces.
Clone it, share it with the client where appropriate, and the register is yours. Across engagements it becomes a pattern library of how your kind of work actually goes wrong.
Build your own register in Taskade Genesis, see live tracking apps in the Community Gallery, or learn scheduled reviews in Learn. Feed it from Scope and Price a New Engagement, and connect it to the plan through Build an Engagement Roadmap With Phases and Milestones.
Frequently Asked Questions
How do I score risk without pretending to be precise?
Use a simple scale for likelihood and impact and be consistent rather than accurate. The value is in the ranking, not the number. The agent applies the same scale across every risk and every engagement so a high score means the same thing in January as it does in June.
Should the client see the risk register?
Usually yes, at least in part, because a shared register is how client-side risks get owned by client-side people. Keep commercial risks such as margin or team availability in an internal view, and share the delivery risks that need joint mitigation.
What risks do consultants most often miss?
The ones that involve people rather than tasks: the sponsor moving on, a key interviewee refusing access, an internal team that sees the project as a threat, and decisions that need a committee nobody scheduled. The agent proposes these because they appear repeatedly across engagement types.
How often should the register be reviewed?
Often enough to catch movement, which is usually fortnightly on a normal engagement and weekly on a compressed one. The automation opens the review with only what changed, so the meeting takes ten minutes instead of an hour.
What is the difference between a risk and an issue?
A risk might happen, an issue already has. The register tracks both, because the moment a risk materializes it needs an owner and a response, and being able to show it was identified in advance changes the tone of that conversation entirely.
Can it draw on what went wrong before?
Yes, and that is where it gets genuinely useful. Feed it your retrospectives and the agent proposes the risks that actually bit you on similar work, which beats a generic risk taxonomy every time. Run a Post-Engagement Retrospective supplies that material.
Is a register worth it on a six-week project?
Yes, in a lighter form. Five named risks with owners and one review at the midpoint is enough to catch the common failures, and it takes fifteen minutes to set up from the scope you already wrote.
Who should own a mitigation, me or the client?
Whoever can actually act. Assigning a client-side risk to yourself is how mitigations quietly fail, because you have no lever to pull. Where the risk sits inside the client organization, name the person who can address it and agree that in the room rather than in a document they never read. The app tracks the owner and the review date, so an unowned high-scoring risk becomes visible within a fortnight instead of surfacing as an issue in month three.
