Request Lifecycle
Statuses from submission to closure
Requests follow a defined lifecycle through approval to resolution.
Request Statuses
PENDING
Submitted and awaiting review. Nothing has been approved yet.
REVIEWING
Optional triage step: someone is screening the request before the approval decision.
APPROVED
Approved for action. Approving normally creates the linked work order.
PLANNING
Optional step while the work is being prepared โ budget, parts, scheduling.
ASSIGNED
Assigned to a technician; work has not started yet.
IN_PROGRESS
A technician has started the linked work order.
COMPLETED
Shown as "Completed". The work is finished and the request is waiting for the requester to confirm it, and optionally rate it. This is not the end of the line.
CLOSED
Shown as "Closed". The requester confirmed (or a manager closed it), so the request is finalized and archived. This is the end of the line.
REJECTED
Declined, with a reason recorded.
CANCELLED
Withdrawn before completion.
Completed vs Closed
These two look alike but mean different things. Completed is the maintenance teamโs statement: the work is done. Closed is the requesterโs: they have seen the result and accepted it. That is why a request stops at Completed โ it is waiting for the person who raised it to confirm, from the request page or from the closure link they were emailed. If your team already validates the work inside the work order, an administrator can switch this step off under Company settings โ System; requests then close by themselves when their work order closes.
Tip
Tip
Tip
Tip
Tip
Printing & exporting a request
Open any intervention request and click Print (top right) to download it as a branded PDF. The PDF includes the request details, the requester, the decision (who approved or rejected it, when, and the reason) and any attachment names โ handy for archiving or sharing offline.
Related articles
Was this page helpful?