Starting and managing a Playbook Run

Brandon Peterson
Brandon Peterson
  • Updated

Use a Run to apply a published Playbook to one client and track the resulting work.

Availability: Playbooks must be available for your account. Your client access, client eligibility and Playbook Run permissions also apply.

Preview and start

  1. Select a published Playbook version and the intended client.
  2. Choose the start date and the schedule day where the Run should begin. Review the Run timezone and intended outcome.
  3. Resolve required people or roles and review any overlapping active Runs.
  4. Open the preview. Check the schedule, skipped earlier work, responsibilities and client eligibility. Preview does not create work.
  5. If you change setup, refresh the preview before confirming Start.
  6. Confirm Start once. Open the resulting Run and check its status and generated work.

Runs keep their selected published version and timezone. Later template edits do not rewrite a Run. Assessment actions create evaluations; Deliverable actions create drafts that still need the normal review and publication workflow.

Manage an active Run

  • Pause: stops new work from being created. Existing linked work remains.
  • Resume: keeps the schedule's dates. Missed work is not automatically caught up; review any explicit catch-up options.
  • End: requires a reason and suppresses work that has not been created. It does not delete existing Tasks, Meetings or other linked records.
  • Reinstate: where permitted, returns a closed Run to Paused. Review missed dates before resuming. Completed Runs cannot be reinstated.

Handle attention and recovery

Open an action's workflow controls and review its reason before retrying, catching up, skipping or changing responsibility. These controls depend on the action's state and your update permissions.

If work may already have been created, inspect the linked destination before retrying. An uncertain creation needs reconciliation; a missing or deleted record is not automatically recreated.

Reassigning upcoming work changes eligible remaining occurrences for that action. It does not rewrite work already created or resume a paused Run.

If the Run remains blocked, contact ScalePad Support with the Run and action details. Do not start duplicate Runs solely to recover a slow or uncertain creation.

Was this article helpful?

Yes! No