Equipt (CMMS)

Work Orders & Maintenance Requests

How a Work Order actually moves through status, how a Maintenance Request gets triaged into one, and what really happens to parts inventory along the way.

Work Order vs. Maintenance Request

A Work Order is the actual job record — assigned, worked, and tracked for labor and parts cost. A Maintenance Request is a lighter-weight intake form for reporting a problem, meant for triage before it becomes a real Work Order — useful when whoever spots the issue shouldn't (or can't) create a full Work Order themselves. Both live under CMMS in the sidebar — Work Orders and Requests respectively.

Creating a Work Order

Click + New Work Order. Fields: Title (required), Priority (Low / Medium / High / Critical — not “Urgent”), Type (Reactive / Preventive / unspecified), Category (multi-select), Asset or Vehicle, Scheduled Date (hides the work order from lists until that date arrives), Assigned To (multi-select), Due Date, Description, and an optional Recurrence (Daily / Weekly / Biweekly / Monthly / Quarterly / Yearly — see Recurring work orders).

Selecting more than one Asset/Vehicle creates a parent + sub-work-order structure — one parent Work Order plus one sub-Work Order per asset, each carrying its own parts and status. This is the same pattern PM Schedules use when generating for a multi-asset schedule.

Work Order status

StatusMeaning
OpenNewly created, not started.
In ProgressWork has started.
On HoldPaused — reachable from Open or In Progress.
DoneComplete. A parent work order can't reach Done until every sub-work order is Done or Skipped.
SkippedIntentionally not done this time. Available on sub-work orders (one asset of a multi-asset job), on a single-asset PM work order, and on a recurring work order. Any parts the work order had already deducted go back to inventory (once), at the cost they were used at; reopening it deducts them again. Parts added or changed while it is skipped are recorded but not taken from stock until it is reopened. A skipped work order counts as closed — it isn't open or overdue anywhere in the app.

Both Done and Skipped can be reopened back to Open with a single click if something was closed by mistake.

Open means Open, In Progress or On Hold everywhere — the dashboard, the reports, the Overdue filter and the notification bell. A work order is overdue when it is open and its Due Date is before today on your organization's calendar (its timezone, not your computer's).

Recurring work orders

When a Work Order with a Recurrence is marked Done — or Skipped — the next one is created automatically, whether it was closed from the web app, the crew app, the API, or an automation. A “Next work order scheduled for …” message confirms it when you close it in the web app, and the new one appears in the list right away. Skip an occurrence you won't do (say, a weekly check during a shutdown week): the series carries on from the same calendar.

  • Due date: follows a fixed calendar set by the series' first due date, so it never drifts. A monthly series first due on the 31st stays on the 31st (clamped to Feb 28/29 in short months and back to the 31st afterwards). Completing late doesn't move the schedule, and any occurrence that has already passed in your organization's timezone is skipped rather than creating a work order that is overdue the moment it appears. If you deliberately change a work order's Due Date to a different day, the series follows the new day from there. If the first one had no Due Date, the schedule starts from the day it was completed. The Scheduled Date keeps its original lead time before the new Due Date.
  • What carries over: title, description, priority, type, categories, asset or vehicle, assignees, and the recurrence itself. The new one starts at Open with its own work order number.
  • What doesn't: parts, labor, and vendor charges on the Costs tab. Parts are left off on purpose — adding a part deducts it from inventory, and the next occurrence may be weeks away. Add parts when the work is actually done.
  • Multi-asset work orders recur as a whole: completing the parent creates a new parent with a fresh sub-work order for each of its assets. A recurring parent can be skipped once all of its sub-work orders are done or skipped.
  • One next occurrence per work order. Reopening a completed (or skipped) recurring work order and closing it again doesn't create a second copy, and neither does re-completing one whose next occurrence you deleted.
  • To end a series, edit the current work order and set Recurrence to “Does not repeat” before completing it. A deleted work order never generates a next one.
Work orders generated this way don't send a “new work order assigned” notification. For recurring maintenance with more control — such as generating work orders ahead of the due date with an automation — use a PM Schedule instead.

Maintenance Requests

There are two separate ways a request gets created — worth knowing both:

  • In-app, for anyone who can submit requests (including Requestors and Purchasers): CMMS > Requests > + New Request — title, priority, optional asset/vehicle, description. The request is credited to whoever is signed in.
  • A no-login submission path — the actual “anyone can flag a problem” story. A branded public form (linked by your org's own slug) and an internal field-repair-request page both feed the same submission handler, requiring no CMMS access at all. Typing the exact name of one of your assets or vehicles links the request to it, so converting it later attaches that asset or vehicle to the work order. New submissions email your org's admins/managers automatically (if that notification preference is on) — except the person who submitted it.
  • Crew logins use the internal field repair-request page. It lists your active assets and vehicles by name; that list and the crew's own requests are all a crew login can see in Equipt. A crew's request always starts as Open.

Who can change a request. Admins, managers and staff triage requests: they move it through the statuses below and can edit any request. Requestors, Purchasers and crew logins can edit only their own requests — title, description, priority and asset/vehicle — and only while the request is still Open; the same goes for deleting it. Once someone starts reviewing it, it's locked for them. Editing a request keeps the equipment name it was submitted with unless you pick a different asset or vehicle, and the description is optional when editing.

Status buttons only act on the status you're looking at: if someone else changed the request in the meantime you'll see “This request changed — refresh and try again” and nothing is saved. Once a request is linked to a work order its status can no longer be changed.

StatusMeaning
OpenJust submitted.
In ReviewA manager/admin has picked it up to triage.
ApprovedConfirmed as real, legitimate work. Only status the Convert button appears on.
RejectedNot going to be actioned. Can be reopened back to Open. Open requests for an asset or vehicle that is deleted, disposed or sold are closed as Rejected automatically, with a note added to the description.
Converted to WOTurned into a Work Order. Terminal — read-only from here.

Converting a Request to a Work Order

The Convert to Work Order button only appears once a request reaches Approved — that's the real triage gate. Converting creates a new Work Order (typed Reactive, or Preventive when a meter rule raised the request) carrying over the title, description, priority, and asset or vehicle link, and flips the request to Converted to WO, a terminal state with a link back to the resulting Work Order.

Where PM Schedules fit in

Planned, recurring maintenance programs are driven by PM Schedules (CMMS > PM Schedules) — a work order's own Recurrence setting is the lightweight alternative for a single repeating task. See the Preventive Maintenance Schedules guide for the full mechanics. In short: generating work orders from a schedule is a manual button click by default, but an Automations rule can make it fire automatically ahead of the due date without anyone clicking anything.

Labor tracking

A Work Order's Costs tab has a Labor section: technician name (free text, not linked to a user account), a description, hours, and an hourly rate — each entry rolls up into a running labor total for the work order.

Users with the Requestor role don't see the Costs tab: work-order parts, labor and vendor charges are hidden from them, along with part costs, purchase orders and receiving. Viewers and Purchasers still see costs.

Parts, inventory, and the clamp-at-zero behavior

Adding a part to a Work Order's Costs tab decrements that part's quantity on hand immediately — this is the normal, expected way stock goes down, independent of (and usually before) any formal receiving. Removing a part restores the quantity; editing the quantity applies the difference. Using a part on a Work Order also auto-links it to that asset going forward, so it shows up as a “commonly used” part the next time.

Using more than you have doesn't error — it clamps at zero. If you add more of a part to a Work Order than is actually in stock, quantity on hand is set to 0 instead of going negative, with a toast telling you how many you were short. Nothing blocks you from doing this; it's a warning, not a hard stop. The part's history records what was really taken, for example “used 1 on WO-… (2 short)”.

The shortfall isn't forgotten. The work order line remembers how many units it actually took out of stock, so the gap (“used 3, only 1 was on hand”) is tracked. This is the usual case when a Work Order is built before the Purchase Order for the part has been received. Three things happen:

  • The part shows an amber “N used before received” badge in the Parts list and in its detail sheet, where a notice lists which Work Orders are short and by how much. The Parts list also has a “Used before received” stock filter to see every affected part at once.
  • Admins, managers, and purchasers get an in-app notification (Part Used Before Received) so someone can check the count or chase the open PO. The person who added the part is not notified of their own action.
  • When the part is later received, the short units come straight off the incoming stock (oldest Work Order first), so quantity on hand ends up correct without anyone adjusting it by hand. Each one is recorded in the part's audit trail as “used N on WO-…”, and the badge clears.

Deleting the line, or lowering its quantity, only returns the units that were really taken from stock — never the full quantity. Returned units go back at the line's own unit cost (what the work order was charged), not at the part's price today.

Parts not tracked as inventory (“Track as inventory item” is off on the part) can still be added to a Work Order for costing, but they never move stock: nothing is deducted or returned, there is no “short” warning, and they never show as used before received.

A physical shelf count on the part (see the Parts guide) also clears its shortfalls: the counted number already reflects the parts used, so the next delivery won't take them again.

Deleting a Work Order

Use the trash button on the work order. Deleting it also deletes every sub-work-order under it, and can't be undone from the app.

  • Open, On Hold, In Progress or Skipped: the parts each line took from stock go straight back on hand. You aren't asked.
  • Done (the work order itself, or a sub-work-order under it): the delete dialog asks “Did the parts go back on the shelf?” Choose Yes, return them to stock only if the parts were never fitted and are back in stock; choose No, they were used to leave stock as it is. Delete stays disabled until you answer.

Only what each line really took is returned (never more than was deducted), and the linked Products-catalog item's stock follows automatically. Work orders can only be deleted this way: they are never removed outright, so their history stays in reports and the audit trail.

Requesting parts via a Requisition

A Requisition can be linked back to the Work Order that needed it — but today that link only gets created through the public API or a Zapier automation, not from a button inside the Work Order screen itself. If you're creating requisitions by hand from inside a Work Order's detail panel, there's currently no field to set that connection; the underlying data model supports it, the in-app form just doesn't expose it yet.

Gotchas

  • A parent Work Order can't be completed until every sub-work-order is Done or Skipped. If a multi-asset Work Order won't let you mark it done, check for an open sub-work-order first. A PM schedule's master work order completes itself when its last asset work order is done or skipped (it is marked Skipped if every asset was skipped).
  • Priority is Low / Medium / High / Critical — if you're looking for an “Urgent” option, it doesn't exist; Critical is the top tier.
  • Work Order, Maintenance Request, and Requisition numbers all use different prefixes (WO-, MR-, REQ-). Work order numbers count up per organization each year (WO-2026-000123). If a number is already taken (for example by a work order numbered by hand), generating from a PM schedule moves on to the next free number.
© 2026 Landscapt. All rights reserved.