PKPEEK Docs
Docs/Administration

Policies and workflows

Edit agency workflow drafts, test them against synthetic cases, approve changes and transition in-progress work (WF01–WF05).

Delegated workflow administrator · Authorized workflow approver

/pdcc/admin/policies
Live walkthrough · Policies and workflows
/pdcc/admin/policies
/pdcc/admin/policies?screen=WF02
/pdcc/admin/policies?screen=WF03
/pdcc/admin/policies?screen=WF04
/pdcc/admin/policies?screen=WF05

Workflows are agency-owned routes inside inherited limits. Module entitlements and non-delegable authority rules stay locked.

Workflow change lifecycle

  1. 1. Fork a draft (WF02)

    From the active version, e.g. *Market Research review draft 4*.

  2. 2. Define stages

    e.g. technical concurrence → small business concurrence when applicable → authorized CO report decision. Record a change reason (e.g. DEMO-POL-04).

  3. 3. Validate and test (WF03)

    Synthetic cases (e.g. MR-026-014), no live dispatch. A failed required case blocks activation.

  4. 4. Review the change (WF04)

    An independent approver approves the exact tested version with an effective time.

  5. 5. Transition in-progress work (WF05)

    Existing work stays pinned by default.

Editing rules

  • Cycles, unknown role resolvers, arbitrary expressions and removal of inherited locks are rejected.
  • Actual reviewers are resolved for the specific record before submission.
  • Test inputs, rule version and results are saved; test cases are never real decisions.

Approval and transition

Approver
e.g. Avery Chen — independent of the editor.
Effective date
e.g. 15 Oct 2026 09:00 America/Denver.
Existing work
Remain pinned by default.
Rollback
Restore prior configuration for eligible new work.
Heads up — This is configuration approval, not report approval. During a transition no case changes while it is blocked (e.g. a new reviewer is unresolved); decision carry-forward follows policy and prior history is preserved.

Related guides

Policy references and restrictions

Maintain applicable policy sources, preview impact before activation, and explain to users why an action is limited (PO01–PO03).

Module settings and readiness

Inspect the independent gates for each module and activate only delegated agency configuration; pilot and release slices (M07).

Report, preflight, review and CO decision

Assemble the versioned report, run submission preflight, track review, record the CO decision and resolve a returned report (MR13, MR14, MR19–MR21).