Use casesRecurring task checklist

Build your recurring task checklist.

Keep each repeat task's occurrence, owner and completion evidence distinct.

How to build your recurring task checklist

  1. Describe the job

    Keep each repeat task's occurrence, owner and completion evidence distinct.

  2. Review the first version

    Choose how the operations coordinator records the recurrence and how the request owner reviews the next step.

  3. Refine the views

    Ask First to adjust the fields and views for the people who will use the app.

  4. Test before sharing

    Walk through the process with a sample record and check who owns the next action.

A recurring task checklist example

The monthly filter check is completed in June but missed in July.

Illustrative workflowRecurring task checklist

Recurring task checklist example

Record
Recurring task checklist · 01
Owner
Operations coordinator

Current stage · Operations coordinator

Open the recurrence

The monthly filter check is completed in June but missed in July.

Read the full walkthrough
  1. Open the recurrence

    The monthly filter check is completed in June but missed in July.

    Record:
    Recurring task checklist · 01
    Owner:
    Operations coordinator
  2. Review the missed reason

    Store two occurrences so June's evidence cannot satisfy July's checklist; keep the missed occurrence visible.

    Stage:
    Awaiting request owner review
    Owner:
    Request owner
  3. Leave the missed occurrence visible

    Leave the missed occurrence visible when the next scheduled task is created.

    Next action:
    Leave the missed occurrence visible when the next scheduled task is created.
    Owner:
    Team lead

What to include in your recurring task checklist

  • Keep the recurrence in context

    Keep recurrence, occurrence, due date, assigned owner, completion evidence and missed reason together so the next person can understand the request or record.

  • When the next step needs a decision

    The monthly filter check is completed in June but missed in July. Store two occurrences so June's evidence cannot satisfy July's checklist; keep the missed occurrence visible.

  • Keep missed reason visible

    Leave the missed occurrence visible when the next scheduled task is created.

  • Choose what each person needs

    Give the operations coordinator a working view and the request owner a review view. Keep recurrence and occurrence attached to the decision as the work moves between them.

Questions about recurring task checklist

Start with recurrence, occurrence, due date, assigned owner, completion evidence and missed reason. Describe who enters the information and who reviews the next step.

Build your recurring task checklist.

Start with your workflow and make it yours.

Get started