Policy recommendation lifecycle and conversion flow
Review recommendation rationale, standards context, and convert accepted items into requests or generation jobs.
Summary
- Review recommendation rationale, standards context, and convert accepted items into requests or generation jobs.
- Use this guide to complete the workflow with audit-ready evidence and ownership.
- If you hit a blocker, run troubleshooting first, then escalate with context.
Steps
1. Set scope and owner
Confirm the organization, role, and workflow scope before making changes.
2. Complete required actions in order
Run the in-product steps sequentially and do not skip required confirmations.
3. Verify outcome and capture evidence
Record status changes, blockers, and linked evidence so the next team can proceed quickly.
Verification
- Expected status is visible in the relevant dashboard or API response.
- Required evidence, ownership, and timestamps are present.
- No blocking validation, policy, or governance errors remain.
Troubleshooting
Recommendation was accepted but no draft was created.
Starter/Professional tiers convert acceptance into policy requests. Enterprise high-priority items auto-draft when enabled.
Recommendations look repetitive.
Trigger fingerprints suppress duplicate open items; clear dismissed/converted states and refresh if context changed.
Workflow screenshots
Was this article helpful?
Next article
Pass 1 drafting behavior and inputs
Understand how context and policy intent are used to produce the initial structured draft.
Continue to next guideRelated articles
Understand how context and policy intent are used to produce the initial structured draft.
5 min read
Track each generation pass from draft to compliance validation with transparent status transitions.
6 min read
Set up your first organization with the plan that matches rollout depth and governance needs.
5 min read