Build a repeatable plan for client work, then publish a version your team can run.
Availability: This guide applies only to accounts included in an approved Playbooks release. If Playbooks is unavailable, contact your administrator or ScalePad Support.
Before you begin
You need permission to create Playbooks. Editing and publishing require update permission as well as read access. Starting Runs requires separate permissions.
Create a Playbook
- Open Playbooks and select New Playbook.
- Enter a useful name and summary, such as Quarterly client review. Add a description or tags to help your team find it.
- Add actions for the work you want to repeat. Supported action types include Tasks, Meetings, Assessments, Deliverables and Roadmap reviews.
- Give each action a title. Add instructions, its schedule and any prerequisite work.
- Select required templates and responsibility. Assessment and Deliverable actions need a template and a responsible person or role. Task and Meeting actions can use templates or their own content.
- Review recurring dates and any occurrence limit. Meeting actions also need their intended time and duration.
- Save your draft. You can return to an unfinished draft before publishing.
Publish a version
- Review all actions and resolve missing required details or unavailable dependencies.
- Publish the Playbook. Publishing creates a numbered version with the action content and dependencies fixed for that version.
- Use the published version when preparing a client Run.
Editing a draft does not rewrite an existing published version or Run. Publish a new version when future Runs should use changed content.
Archive and troubleshoot
Archive a Playbook when it should leave the default library. Published versions remain available for history; they cannot be permanently deleted through the normal definition lifecycle.
If a publish check fails, correct the highlighted action or dependency and review again. If another person changed the draft, reload the latest version and reconcile your edits.
Creating or publishing a Playbook does not itself execute client work. A Run has its own client, permissions, preview and confirmation.