---
key: review-work-order-booking-and-checklist-automation
title: Review work order, booking and checklist automation
audience: staff
section: operations
routes: ["/work-orders/lifecycle", "/bookings/lifecycle", "/checklists/lifecycle"]
permissions: ["lifecycle_automation.view"]
since: 0.0.1
updated: 0.0.1
status: published
summary: Use the lifecycle hubs for work orders, bookings and checklists to see which automated reminders and follow-ups are running, pause or stop one, and clear what waits for approval.
keywords: [lifecycle hub, automation, reminders, follow-ups, review requests, appointment reminders, checklist nudges, automated messages]
related: [review-work-automation, review-account-automation, use-the-automation-center, work-on-a-work-order]
---

In the sidebar, open **Automation**, then **Overview**. Under **Domain automation hubs**, press **Work Orders**, **Bookings & Activities** or **Checklists**. The page addresses are `/work-orders/lifecycle`, `/bookings/lifecycle` and `/checklists/lifecycle`. From a work order, **Automation details** at the bottom of its **Lifecycle** tab opens the work order hub.

A lifecycle hub watches the automated sequences for one kind of record: the reminders, follow-ups and review requests Nova sends or does on its own. Each hub is the same page, filtered to its records:

- **Work Order lifecycle hub**: service reminders, post-service follow-ups and review requests. Its shortcuts start from the **Work order reminders** and **Post-service reviews** presets.
- **Booking lifecycle hub**: reminders before an appointment or activity, follow-ups after it, and review requests. Its shortcut starts from **Activity follow-ups**.
- **Checklist lifecycle hub**: nudges when evidence is due, follow-up on failed items, and completion reminders. Its shortcut starts from **Checklist remediation**.

## Before you start

- Opening a hub needs permission to read that kind of record; seeing anything on it also needs permission to view lifecycle automation. Without it the page says **Lifecycle access is unavailable**.
- Pausing, stopping, reviewing approvals and creating automations each need their own permission.

## Steps

1. Read the tiles at the top: **Visible automations**, **Pending approvals** and **Open enrollments** (records currently inside a sequence), with the next due action.
2. Under **Actionable enrollments**, each row is one record inside a sequence, with its **Status**, **Subject**, **Current step** and **Next due** time.
3. To hold a sequence for that record, press **Pause lifecycle sequence**; press **Resume** later.
4. To end it for good, press **Suppress future actions** and confirm in **Suppress future lifecycle actions?**. Nothing further runs; the history stays.
5. Press **Why this happened** to see why a step ran or was held, or **Open record** to jump to the work order, booking or checklist.
6. Under **Pending approvals**, press **Review approval** on a step that waits for a person, or **Review next approval** under **Quick actions**.

## What you see

- **Active automations** lists the automations for this kind of record, with their **Journey**, **Scope** and when they were **Updated**.
- **Interventions and holds** collects steps that were blocked, held or failed.
- The recent activity and analytics sections show what ran lately and how it performed, when your role can see analytics.
- The buttons at the top open the records (**Open work order queue**, **Open Schedule** or **Open checklist reports**) and **Open control plane**, the organization-wide Automation Center.

## If something looks different

- **Lifecycle analytics are unavailable**: your role cannot see automation analytics; the rest of the page still works.
- Nothing is listed under **Active automations**: none has been set up for this kind of record. **Create work order automation**, **Create booking automation** or **Create checklist automation** starts one; building automations is an admin task ([[use-the-automation-center]]).
- To stop messages for one work order only, choose **Turn off** under **Customer messages** on its **Lifecycle** tab instead ([[work-on-a-work-order]]).