Scheduled maintenance & parts

How recurring maintenance and spare-parts requests are kept under control.

Recurring maintenance runs itself

Instead of relying on someone to remember that an asset is due for servicing, CAFM Cloud tracks a maintenance schedule per asset — how often it needs attention, what checklist to follow, and who normally handles it. When maintenance comes due, a job is created automatically and assigned to the right technician.

From there, it's treated exactly like any other job — see How a job moves through CAFM Cloud — so technicians and supervisors don't need a separate process for "scheduled" versus "reported" work.

When a job needs parts

If a technician doesn't have what they need on hand, the job doesn't stall — it pauses as "waiting on parts" while the request works through:

  1. Request — the technician requests the parts they need, linked to the job that's waiting on them
  2. Approval — if stock is available, it's issued directly; if not, a purchase is raised for approval
  3. Ordering — an approved purchase becomes an order sent to the vendor
  4. Receiving — parts are received and stock is updated, and the job automatically becomes available to resume
💡

Because the job is linked to the request the whole way through, nothing gets lost between "we're waiting on a part" and "the part arrived, back to work."

What to do next