Statuses
Learn about each inspection status, its ID, transition rules, and how inspections move through their lifecycle from creation to completion.
Every inspection moves through a series of statuses from creation to completion. This page covers each status, its API identifier, transition rules, and the overall lifecycle flow.
Status Flow
The typical lifecycle is linear, but inspections can also be canceled at certain stages or move backward when more information is requested.
Statuses
Status | inspection_status_id | Description | Possible Transitions |
|---|---|---|---|
Scheduled |
| The inspection has been created with a future send date. It transitions to Created when the scheduled time arrives and the request is delivered to the customer. Not all inspections use scheduling — you can create an inspection for immediate delivery. | • Scheduled → Created |
Created |
| The inspection request has been sent to the customer via text, email, or both. The customer has not yet interacted with it. | • Created → Started |
Started |
| The customer has opened the inspection link. They have not yet captured any photos, recorded any video, or answered any questions. | • Started → In Progress |
In Progress |
| The customer has captured at least one photo, recorded a video, or answered a question. In Progress inspections cannot be canceled. | • In Progress → Ready for Review |
Ready for Review |
| The customer has submitted the inspection for review, or the inspection expired with at least one image captured or one question answered. It is now waiting for a member of your team to review the results, test outcomes, and captured media. | • Ready for Review → In Progress |
Closed |
| A reviewer has completed their assessment and closed the inspection, optionally assigning an outcome (such as "Approved" or "Rejected"). This is a terminal status. | |
Canceled |
| The inspection was canceled before the customer began capturing. This happens when an administrator or API call explicitly cancels the inspection, or when the inspection expires because the customer never started in time. | • Canceled → Created |
Key Lifecycle Rules
- Inspections can be scheduled for future delivery or created immediately — both paths lead to the Created status.
- An inspection moves to Started when the customer opens the inspection link, and to In Progress once they capture a photo, record a video, or answer a question.
- Only inspections in the Created or Started status can be canceled. Once a customer begins capturing (In Progress), the inspection cannot be canceled.
- If a customer doesn't finish in time, the inspection expires. If they had begun capturing, it transitions to Ready for Review; otherwise it transitions to Canceled.
- A Ready for Review inspection can be moved back to In Progress when you request more photos, videos, or answers from the customer.
- A canceled inspection can be reopened by transitioning it back to Created.
- An inspection must reach Ready for Review before it can be Closed.
Updating Status via the API
Change an inspection's status by sending a PUT request to /inspections/{inspectionId} with the new inspection_status_id value. See Update Inspection for details.
Related Pages
Understand how inspections are composed from teams, lists, templates, and alerts.
Change inspection status and update customer information via the API.
Request additional photos or videos on an existing inspection.
Define and assign outcomes when closing inspections.
Updated about 20 hours ago