How to submit a plan version for review
Submit a draft so the Studio validates it. Blocking findings stop it; warnings must be acknowledged one by one before it can move to review.
Have questions or need step-by-step guidance on this topic?
Step-by-Step Procedure
Open the version
Select the plan and the version. Read the "Validation findings" list: each line shows a level (BLOCKING, WARNING or INFO), a code and a message.
Fix every BLOCKING finding
Blocking findings must be fixed in the definition or the composer, then saved. The version cannot reach review while one remains.
Acknowledge each WARNING you accept
For a WARNING on an editable version a checkbox labelled "acknowledge" appears. Tick it only after you have understood the warning.
Click "Submit for review"
The Studio sets the state through VALIDATING and recomputes findings and the content hash. The message "Submitted: see the findings and state." appears. If everything passes, the state becomes IN REVIEW.
Check the required approvals
Under "Approvals required" the panel lists the categories still "pending". A financial version is flagged "financial · dual approval" and needs FINANCE, COMPLIANCE and PLAN_APPROVER; any other version needs PLAN_APPROVER.
The version is IN REVIEW with a list of pending approvals, or it is FAILED VALIDATION with a clear reason you can fix and resubmit.
Troubleshooting & Failure Modes
Was this guide helpful?
Help us refine our platform documentation