Policy generation job lifecycle and pass states
Track each generation pass from draft to compliance validation with transparent status transitions.
The UI shows named stages, not "Pass 1/2/3"
The current engine (V3) runs a 12-stage pipeline shown on /dashboard/policies/generation-progress as plain-language steps: Build organization profile, Check policy readiness, Build standards context, Build policy blueprint, Validate blueprint, Draft policy sections, Assemble draft, Check consistency, Repair draft, Run review gate, and Save draft bundle. You will not see "Pass 1", "Pass 2", or "Pass 3" anywhere in the current product; that numbering belonged to the deprecated V2 engine.
Summary
- Track each generation pass from draft to compliance validation with transparent status transitions.
- 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. Start a job from /dashboard/policies/new
Choose a policy category and start generation. This queues a V3 job and takes you to /dashboard/policies/generation-progress?job=[id].
2. Watch the stage list advance
Each stage shows Pending, Current step, or Completed. The active stage shows a short narrative and how long it has been running.
3. Handle a pause or quarantine if one occurs
If the job status becomes Paused for a few follow-up details or Needs manual review, use the primary action button rather than waiting or restarting.
4. Open the reviewer memo when complete
A completed job produces a reviewer memo, including the standards scorecard when standards are mapped, visible from the policy detail page.
Verification
- The stage list on the progress page shows named build/validate/draft steps, never a numbered pass.
- A completed job produces a reviewer memo you can open from the policy detail page.
- A stuck or blocked job shows a clear next action rather than a bare status code.
Troubleshooting
A job has been sitting in one stage for a long time.
Open the job detail. If it shows Paused for a few follow-up details, answer the follow-up questions; if it shows Needs manual review, use the quarantine recovery steps instead of waiting.
Workflow screenshots
FAQ
How long are the AI working files behind a draft kept?
For 12 months after the draft finishes, then they are stripped. These are the organisation profile snapshot the draft was generated from and the in-progress data from each generation step. Files still in use are kept while they are needed: the snapshot a current policy was drafted from, the document-control details printed on an exported policy version, and drafts still awaiting a decision, such as an open revision. The policy itself and its version history are always kept, and answers you give to a draft’s follow-up questions are kept with the draft so they can be offered again when the policy is redrafted. The Privacy notice and the sub-processors page state the same period.
Was this article helpful?
Next article
Policy recommendation lifecycle and conversion flow
Review recommendation rationale, standards context, and convert accepted items into requests or generation jobs.
Continue to next guideRelated articles
Review recommendation rationale, standards context, and convert accepted items into requests or generation jobs.
6 min read
Set up your first organization with the plan that matches rollout depth and governance needs.
5 min read