Use decisions in Playbooks

🚧

Beta

Playbooks are available to selected workspaces while we continue to improve them. Contact your V7 account team if you need access.

A decision step chooses the next path from stated conditions. Use decisions when the process must handle different document states, risk levels, approvals, or outcomes.

Define a clear condition

State the evidence the Playbook must inspect and the path it must choose for each result. For example, a Playbook can request human review when a required document is missing or continue when all required evidence is present.

Every decision and selected path is recorded in the run. This makes the process auditable and helps teams find rules that need improvement.

Repeated and delegated work

A Playbook can repeat work for a set of submitted items. Advanced designs can also delegate bounded work to other Playbooks. Use these patterns only when each responsibility and handoff is clear.

Technical notes

Define branches that are mutually exclusive and cover every expected result. When a process splits into parallel paths, define how those paths return to one next step. Playbooks can also include loops, but every loop needs a clear condition that ends it.