Skip to main content

Set up a recurring process

Create separate runs for work that repeats on a schedule.

Use a recurring process for work such as weekly safety meetings, daily inspections, or monthly accounting. Each run has its own tasks and completion record.

Before you begin: Use desktop with Editor or Administrator access and a published Playbook process.

Choose the destination and schedule

  1. Open the process in Playbook and choose Use process.

  2. Select the project or operation. For a project, select the phase or phases where this work belongs.

  3. Choose Recurring.

  4. Choose the frequency and the required days or dates.

  5. Confirm with Add to project or Add to operation.

Choose a frequency

  • Every workday: follow the company's working days and skip company holidays.

  • Weekly: choose the weekdays when the process should run. Company holidays are skipped.

  • Monthly: choose dates, the last day of the month, or an occurrence such as the first Monday.

  • Annually: choose a month and day.

Monthly and annual schedules follow their selected dates. Do not assume they skip holidays in the same way as Every workday or Weekly.

Understand project phases

A recurring process assigned to a project phase waits for that phase to start. The phase's milestone date and the following phase or project end can limit when runs are generated. Check milestone dates if expected work has not appeared.

Find the setup and each run

Find the recurring setup in On deck. Review its runs in the project or operation as work becomes active and is completed. Complete the individual run, rather than treating the recurring setup as a single checklist to finish forever.

Change the schedule or start an extra run

  1. Open the On deck setup and its more-actions menu.

  2. Choose Activation settings, adjust the schedule, and select Save changes.

  3. To start an additional run when needed, use Activate now where offered.

Review team assignments and due-date rules on the resulting work. Changing the schedule does not mean that earlier completion records should be reused as the next run.

Did this answer your question?