Workflow · Moderate effort
Risks and decisions
Turn an unstructured RIDD set into a prioritised register with ownership and escalation logic.
Tool coverage incomplete. The steps identify where a manual approach is needed.
Use the guide to open your own app or workspace. Follow the steps below and return to check your result.
Step by step
Here’s how to do it
Work through these steps in order. Your notes stay on this page until you copy them; nothing runs automatically.
Some steps have no reviewed tool yet. Those steps show a manual approach.
What you’ll need
- raw RIDD items
- project objectives/milestones
- owners where known
- impact/urgency context where known
Collect the items to review
- Copy the risks, problems, dependencies and decisions from your notes into one list.
- Keep each item’s source and any stated owner, impact or due date.
- Start with
- Raw RIDD material.
- You’ll have
- Candidate register.
Label each item
- Decide whether each item is a possible risk, a problem happening now, a dependency or a decision needed.
- Mark unclear items for review instead of forcing a label.
- Start with
- Candidate register.
- You’ll have
- Typed register.
Check for repeated items
- Compare items that describe the same situation.
- Merge only true duplicates and keep all source references. Keep distinct causes or consequences separate.
- Start with
- Typed register.
- You’ll have
- Consolidated register.
Decide what needs attention first
- Read each item against the project goals and upcoming milestones.
- Record the stated impact and urgency. Ask for missing context before assigning a severity score.
- Start with
- Consolidated register plus context.
- You’ll have
- Materiality rationale.
Record the next action
- In your OpenProject project, open the relevant work package and record this step’s reviewed result. Types and fields depend on your project’s configuration.
- Add a confirmed owner and the next action or decision for each important item.
- Leave ownership visibly unassigned when nobody has accepted it; do not invent a deadline.
- Start with
- Assessed register.
- You’ll have
- Owner/next action or ownership gap.
OpenProject’s work-package guide (opens in a new tab) · Checked
Prepare the items needing a decision
- Compare the items with your team’s agreed escalation rules.
- Summarise only those that meet the threshold, with the evidence and the decision or help needed. Review before sending.
- Start with
- Material items.
- You’ll have
- Escalation summary.
0 of 6 step checks complete. Every material item is classified, visible, owned or explicitly unowned, and has a next action or decision path.
Before you share or switch it on
- Compare the result with the brief and the original material.
- Correct errors and check that you have permission to use the result.
- Save a checked version before deciding whether to share or activate it.
03 · Tools used
Tool roles, with choice kept visible
Steps needing another approach
- No currently supported tool covers Structured storage.
- No currently supported tool covers Classification / triage.
- No currently supported tool covers Data normalisation.
- No currently supported tool covers Structured reasoning.
Use a suitable manual approach for these steps. Unqualified tools are not assigned automatically.
Primary Tools
Optional
No optional tool is included in this setup.
01 · What this workflow helps you do
A register with type, description, owner, status, impact, urgency, next action and escalation need.
Clean, classify and prioritise risks, issues, dependencies and decisions so material items receive action.
A register with type, description, owner, status, impact, urgency, next action and escalation need.
Complete when: Every material item is classified, visible, owned or explicitly unowned, and has a next action or decision path.02 · What you need
Start with the available source material
- Raw RIDD Items
- Project Objectives/Milestones
- Owners Where Known
- Impact/Urgency Context Where Known
05 · Human checks
Keep judgement with the person doing the work
- Preserve source references.
- Ambiguous items remain flagged.
- Retain original references where needed.
- Final severity/escalation judgement is human.
- Never invent accountability.
- Human confirms escalation threshold.
06 · Limitations
Where this workflow needs care
- Severity scoring without context creates false precision.
- Owners, deadlines and business impact must not be invented.
- Merging duplicates can lose nuance.
07 · Related workflows