Constraints
Documents fixed constraints — regulatory, technical, budgetary, or organisational — the solution must operate within.
AI in this module
How AI suggestions work
Click "Get AI Suggestions" to have the AI draft or improve the constraints table in one pass, grounded in the DRP's other content and any AI Knowledgebase documents. The suggestion appears as a single card — click "Apply" to replace your current table with it.
This module is the exclusive home for constraints in a DRP — every other module's AI drafting is told not to restate a specific constraint (including its actual timeframe, target, or limit) under any heading, and to reference this module by name instead if it's relevant.
Quality checks
What "Check Quality" looks for here
Genuinely non-negotiable. Flags anything that reads like a disguised risk, assumption, or preference that could actually change.
What it captures
Fixed constraints the solution must operate within — regulatory, technical, budgetary, or organisational.
Using this module
This module is a single table: one row per constraint, with a Type — Business or Technical; a regulatory or resource constraint is a business constraint — and a Description of the constraint itself.
- 1Use "+ Add row" to add a constraint, and the ✕ on a row to remove one.
- 2Only list things that are genuinely fixed — see the tip below on where a "soft" constraint actually belongs.
Review and approval
Reviewed as a whole — the Overview and the Constraints table together, not row by row. Once submitted it is read-only; to change it, press "Reopen to edit", which cancels the round and returns it to In progress.
This DRP's Review Assignments tab shows the module as one row, like any other, with its own review level, reviewers and approver — inherited from the project until you change them here.
Tips
- "Export CSV", at the top of the page, downloads this table as a spreadsheet file — handy for sharing it with someone who works in Excel.
- A constraint is non-negotiable by definition — if something could reasonably change, it belongs in Solution Scope or the RAID Log's assumptions instead.