Skip to main content

Set how senior a playbook stage is

Seniority decides which model tier a stage's runner gets: Junior runs on the Low tier, Mid on Standard and Senior on High. A higher tier costs more and handles harder judgement. Set one default for the whole playbook, then raise or lower single stages: a Plan or Architect stage shapes everything after it and is worth Mid or Senior, while a routine stage may do well on Junior.

Who can do this: changing a playbook needs the Owner or Admin role in your organization, and Playbooks must be included in your plan. Built-in playbooks are read-only; duplicate one first, as in Create a playbook.

  1. In the sidebar, select Settings, then Playbooks under Customize.

  2. Under Your playbooks, select the playbook's ⋯, then Edit. For a new playbook, select New playbook instead.

  3. On the Playbook tab, pick Default seniority: Junior, Mid or Senior. Every stage uses it unless it sets its own. A new playbook starts on Mid.

    A new playbook's Playbook tab: Name, Full Auto, Default seniority and Description, with the chain below

  4. Select the Stages tab, then ▸ at the start of a stage to open its card.

  5. In Seniority, pick Junior, Mid or Senior for this stage alone, or leave Playbook default.

  6. Check the tier the stage will run on, worked out from its own seniority and the playbook default: the card's header names it, such as Low tier, and so does Model tier under Set by the deliverable.

  7. Read any warning on the card. A Plan stage, or an Architect stage, at Junior gets one, because its output decides what every later stage builds. A warning doesn't stop you saving.

    An Architect stage set to Junior: its header and Model tier read Low, under a warning that it runs the Architect at Junior seniority

  8. Repeat steps 4 to 7 for each stage you want to change, then select Save.

To see the effect before saving, select Preview prompt on the stage's card: the model tier is named at the top.