Definition
A work request formally asks for maintenance work once a need has been identified (often following a maintenance notification) with enough scope and priority information for a planner to evaluate it. Approval and scheduling turn it into a maintenance work order; it is not yet the authorized, planned task itself.
Key facts
- Represents a defined ask for work, more specific than a raw observation but not yet approved or scheduled.
- Often originates from an evaluated maintenance notification, adding scope, priority, and justification.
- Reviewed by planning or supervision, which approves, rejects, merges, or converts it into a work order.
- Distinct from a maintenance work order, which carries the approved schedule, resources, and completion record.
What information does Work request preserve?
A work request states that maintenance work is needed on a specific asset, with enough detail (scope, reason, urgency) for planning to assess it, prioritize it against other demand, and decide whether and when it becomes an authorized job.
How do maintenance teams use Work request?
A maintenance notification is an unfiltered observation awaiting evaluation; a work request is what that evaluation can produce once a genuine need is confirmed: a defined ask, not yet approved. A work order is the next and final stage: the request has been approved, scheduled, assigned, and will be closed with a documented outcome.
FAQ
Frequently asked questions
How is needed maintenance work requested?
It is submitted as a work request with the asset, scope, and reason for the work, so planning can evaluate, prioritize, and (once approved) convert it into a scheduled maintenance work order.
Last reviewed: