What this is
What is a maintenance request?
What is a maintenance request?
A maintenance request is the intake record that asks maintenance to look at a problem or carry out a job. It is not the job itself. It captures what is wrong, where, and how urgent the raiser believes it to be, and then becomes a work order or is rejected with a reason. A request never converted is still evidence that someone reported a fault.
How does a maintenance request differ from a work order?
A request is a claim about a problem; a work order is a commitment to fix it. The request is owned by whoever raised it and carries their view of priority. The work order is owned by maintenance and carries the agreed priority, plan, parts and labour. Keeping them separate is what lets you measure how long requests sit before anyone triages them.
What does ISO 55001 cl.8.1 require of an intake process?
Clause 8.1 covers operational planning and control: plan, implement and control the processes needed to meet asset management requirements, and keep documented information sufficient to have confidence they were carried out as planned. An intake record capturing the fault, the decision and its author is how that confidence is evidenced for reactive work.
Scope
When is a maintenance request required?
This is the intake step of the Planned Maintenance programme and nothing else. It records that someone asked, not that anything was done. Most maintenance reporting problems come from using intake records as job records, producing a backlog that cannot be aged.
Use this template when
- Someone has noticed a fault, a degradation or a hazard on an asset and needs maintenance to look at it
- A job is wanted that is on no PM schedule — a modification, an improvement or an opportunity for the next shutdown
- An operator needs to flag that an asset is running degraded but has not stopped, so the risk is visible before it becomes downtime
- A hygiene, guarding or corrosion issue may affect product or worker safety and needs a maintenance decision on it
- You need an auditable record that a fault was reported on a given date, independent of whether maintenance accepted the job
Do not use it for
- Work Order, which is the planned job itself — what, where, who and when — created from an accepted request rather than instead of one
- Emergency Work Order, which is used when equipment has already stopped or become unsafe; raising a request first wastes the minutes that matter
- Corrective Work Order, which covers repair of a failure already diagnosed, where no triage decision is outstanding
- Downtime Record, which measures lost production time and is a consequence of a failure, not a request to attend one
- Parts Request, which asks the storeroom for a component against an existing job and needs no maintenance triage
Compliance mapping
Which ISO 55001 cl.8.1 requirements does this satisfy?
ISO 55001 cl.8.1 is the operative clause, but a request touching food contact surfaces or guarding also carries food safety and work equipment obligations. Each is tied below to the section that evidences it.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 55001 cl.8.1 | Plan, implement and control the processes needed to meet asset management requirements, retaining evidence | Header |
| ISO 55001 cl.8.1 | Control planned changes and review unintended ones, acting to mitigate adverse effects | Triage |
| ISO 55001 cl.7.5 | Determine the information needs of the asset management system, including quality and collection method | The problem |
| ISO 45001 cl.8.1.1 | Establish process criteria and control them so health and safety risks are eliminated or reduced | Priority |
| ISO 22000 cl.8.2 | Prerequisite programmes covering equipment maintenance and suitability are established and maintained | Priority |
| PUWER 1998 reg.5 | Work equipment is maintained in an efficient state, in working order and in good repair | Triage |
What it does not cover
- A request with no asset link, which cannot be counted against an asset's failure history, so criticality reviews rest on nothing and the same machine fails repeatedly unnoticed
- A request accepted with no work order ID, which leaves a commitment with no job behind it and makes backlog age meaningless, since the record closes without work
- A rejection with no reason recorded, which reads to an inspector as maintenance declining a reported hazard without explanation — the most damaging pattern in a reactive maintenance file
- Product At Risk answered Yes with no Hold ID, which breaks the chain between the fault and the quality hold, leaving affected product traceable only by memory
- Requested Priority overwritten in place, which erases the raiser's view of urgency and any evidence of disagreement between the floor and the planning office
Global
Maintenance Request requirements by country
The Priority section asks about food safety, worker safety and output. Which carries legal weight depends on where you operate, and that changes what a delayed request exposes you to.
Provision and Use of Work Equipment Regulations 1998, reg.5; retained Regulation (EC) 852/2004 Annex II
The duty to maintain equipment in efficient working order sits on the employer whether or not a request was raised, but a documented request with a triage decision is the primary defence that it was actively managed.
A rejected or deferred request on a guard or safety device is the record the HSE reads first. Reason For Priority and Rejection Reason carry the reasonableness argument.
Regulation (EC) 852/2004, Annex II Chapter V; Directive 2009/104/EC on use of work equipment
Food business operators must keep equipment clean and maintained so as to avoid contamination risk; the work equipment directive imposes a parallel duty for worker safety.
Hygiene or corrosion under Problem Type is a food hygiene matter, not just an engineering one, and should route to quality as well as maintenance.
21 CFR 117.35 and 117.40; OSHA 1910.212
The preventive controls rule requires equipment to be kept in adequate repair to prevent contamination; OSHA requires machine guards in place and effective during operation.
A request flagging a missing or damaged guard cannot be deferred on cost grounds. Safe To Continue answered No should stop the asset, not merely raise its priority band.
How to complete it
How to complete a maintenance request, step by step
Filling the fields is trivial. These four judgements decide whether the record survives an investigation.
This field decides whether an asset keeps running. If the raiser is an operator under output pressure, With restrictions becomes the default and the record loses its value. Decide in advance whether their answer is advisory or binding, and if advisory, make Triage re-answer it explicitly rather than inherit it silently.
Downgrading is legitimate — raisers overstate urgency. But a downgrade from Emergency or Urgent to Routine with no note is where most disputes originate. Require Reason For Priority on any downgrade of two bands or more, and review those cases together at the Backlog Review.
Accepted By Maintenance offers three outcomes: Yes, Merged, and No. There is no fourth state, intentionally. If your reality includes requests parked pending information, add that state explicitly with an owner and review date, or they will sit as Open indefinitely and corrupt every backlog figure you publish.
Merging is the most abused option because it closes a request without visible work. It must carry the Work Order ID it merged into, and that job's scope must actually cover the reported fault. A merge into an unrelated job is a rejection without a reason.
What auditors find
Most common maintenance request findings
These recur whenever a maintenance request log is examined properly, with the clause each engages and the change that closes it.
| Finding | Clause | What fixes it |
|---|---|---|
| A large share of requests sit at Open with no Triaged By and no triage date, some for months on end | ISO 55001 cl.8.1 | Set a triage service level in working hours and report Open age, not Open count. A count is flattered by closing old records; an age distribution is not. |
| Requested Priority is Emergency on a sizeable minority of records; Agreed Priority almost never is | ISO 45001 cl.8.1.1 | Publish what each band means in response time and reassess. Persistent mismatch means the bands are not understood on the floor, not that raisers are wrong. |
| Product At Risk is answered Yes but the Hold ID field is empty on most of those records | ISO 22000 cl.8.2 | Make Hold ID required when Product At Risk equals Yes, and route those records to quality on submission rather than at triage. |
| Photographs are absent from most requests despite the field existing and the guidance encouraging it | ISO 55001 cl.7.5 | Check the mobile capture path on the devices people actually carry. Missing photographs are almost always a device or permissions problem, not a behavioural one. |
| Asset and Asset ID hold a generic line or area entry rather than the specific machine | ISO 55001 cl.7.6 | Filter the Asset picker to the selected site and active assets only, and audit the register for catch-all entries. A Line 3 pseudo-asset guarantees unusable failure history. |
| Rejection Reason is present but is one word — duplicate, invalid — on nearly all rejected records | PUWER 1998 reg.5 | Require a reference on a duplicate rejection — the request or work order it duplicates — and sample rejected records at Backlog Review, not only accepted ones. |
Case in point
Case in point: the seal that was reported four times
A chilled ready meals site had a chill store door seal reported as damaged in March, with a photograph, Problem Type of Hygiene or corrosion, Product At Risk of Possibly and Requested Priority of Urgent. Triage downgraded it to Routine with no reason recorded, on the reasonable-sounding basis that the door still closed. It was raised again in April, May and June by different operators and downgraded the same way, because nobody triaging saw the earlier records — the asset link pointed at a generic Chill Store entry, not the door.
In July a swab found Listeria on the door frame. The investigation pulled four requests with photographs showing progressive seal degradation, all downgraded without explanation. The engineering failure was minor and cheap; the finding was that a food safety concern had been raised four times by the people closest to it and the system could not see the repetition. Two changes closed it: a specific asset per chill store door, and a triage flag on any request whose asset already carries an open or recently rejected request of the same problem type.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- MNT-001
- Archetype
- Record
- Record ID
- MREQ-2026-000
- Scoring
- Priority band
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 55001 cl.8.1
- Links
- Links Asset; feeds Work Order
- Tags
- Maintenance, Intake
- Sections
- 4
- Fields
- 31
- Follow up fields
- 4
- Repeating sections
- 0
- Links out
- 4
Header
11 fieldsRequest ID*
Auto sequence. Format MREQ-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Asset*
Asset ID*
Format AST-0000.
Links to FDN-002 Asset ID
Under A Minute
A photo and a location beat a long description. If it takes more than a minute, people stop reporting and problems get worse quietly.
The problem
8 fieldsWhat Is Wrong*
Photograph
Problem Type*
Still Running*
- Yes, normally3 pts
- Yes, degraded1 pt
- No0 pts
Safe To Continue*
- Yes3 pts
- With restrictions1 pt
- No0 pts
Product At Risk*
- No3 pts
- Possibly1 pt
- Yes0 pts
Hold ID
Links to QUA-003 Hold ID
Case ID
Thread key
Priority
5 fieldsRequested Priority*
- Emergency0 pts
- Urgent1 pt
- Routine2 pts
- Opportunity3 pts
Reason For Priority
Affects Food Safety*
- No3 pts
- Possibly1 pt
- Yes0 pts
Affects Worker Safety*
- No3 pts
- Possibly1 pt
- Yes0 pts
Affects Output*
- No3 pts
- Reduced rate1 pt
- Stopped0 pts
Triage
7 fieldsAccepted By Maintenance*
- Yes3 pts
- Merged with existing work order2 pts
- No0 pts
Agreed Priority
- Emergency0 pts
- Urgent1 pt
- Routine2 pts
- Opportunity3 pts
Rejection Reason
Work Order ID
Links to MNT-002 Work Order ID
Triaged By
Requester*
Signature*
MNT-001 · record IDs look like MREQ-2026-000 · Links Asset; feeds Work Order
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The record is the easy part. What slips is triage within the day, repeat faults on one asset being noticed, and a food safety flag reaching quality before the shift ends.
Holds the request against the asset register, filters the picker to active assets at the selected site, and ages untriaged requests separately from accepted backlog.
Picks up requests where Safe To Continue is No or With restrictions, or Affects Worker Safety is Yes, and treats them as hazard reports rather than waiting for a planner.
Routes Product At Risk and Affects Food Safety to the hold process, links the Hold ID back onto the request, and keeps the fault visible in the product investigation.
Flags repeat requests on the same asset and problem type, chases records untriaged past the service level, and holds every write for approval before it lands.
This template lives in KnowMaintain — asset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.
Meet KnowMaintain→Glossary
Maintenance Request definitions and key terms
- Triage
- The maintenance decision on whether to accept, merge or reject a request, and at what priority. Distinct from planning the job, with its own owner and timing.
- Priority band
- The scoring on this template. Emergency, Urgent, Routine and Opportunity carry ascending scores because high is good here — an Opportunity job scores well precisely because it carries no immediate risk.
- Backlog age
- How long accepted work has been outstanding, measured from acceptance rather than raising. Untriaged requests never appear in it, which is why untriaged volume is reported separately.
- Hold ID
- The reference to a quality hold on product possibly affected by the fault. It appears only when Product At Risk is answered Yes.
- Merged request
- A request closed by attaching its scope to an existing work order. Legitimate when that job genuinely covers the fault, a silent rejection when it does not.
FAQ
Frequently asked questions about maintenance request
Should everyone on site be able to raise one?+
Yes, and restricting it is the most common way sites break their own intake. The record is deliberately short because the value comes from volume and immediacy. Gatekeeping through supervisors adds a day and loses the photograph.
What is the difference between Requested Priority and Agreed Priority?+
Requested Priority is the raiser's view, captured at observation and never edited. Agreed Priority is maintenance's view, set at triage. Keeping both preserves the disagreement, the most useful signal this form produces.
Does a maintenance request always become a work order?+
No. It becomes one when Accepted By Maintenance is Yes, capturing the Work Order ID. It may also be merged into an existing work order, or rejected with a written reason. All three are complete outcomes; only an untriaged request is incomplete.
How is this template scored?+
As a priority band where high is good. Benign answers — running normally, safe to continue, no product at risk, opportunity priority — score highest. A low aggregate is the signal to act now rather than next planning cycle.
Why does the form ask about food safety on a maintenance record?+
Because the person raising it is usually the only one who knows. Affects Food Safety and Product At Risk let the record route to quality at the moment of raising rather than after a planner has read it, changing who sees it within minutes.
Can the template be changed?+
Every field, option, score and conditional rule is editable, and the links to Asset Register, Work Order and the quality hold come with it. Resist adding fields to the intake sections — each one reduces faults reported.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Planned Maintenance
Asset Register
Holds every piece of equipment, machine, vehicle and tool you track
Tool and Equipment Register
Holds portable tools, gauges, lifting accessories and small equipment that sit below asset level but still need control
Work Order
The main record for a planned maintenance job, covering what, where, who and when
Corrective Work Order
Covers a repair to fix something that has already failed or degraded
Emergency Work Order
Covers urgent work where equipment has stopped or become unsafe
Work Order Closeout
Confirms the job is finished, the area is safe and the equipment is fit to run
More in Work Orders
Work Order
The main record for a planned maintenance job, covering what, where, who and when
Corrective Work Order
Covers a repair to fix something that has already failed or degraded
Emergency Work Order
Covers urgent work where equipment has stopped or become unsafe
Work Order Closeout
Confirms the job is finished, the area is safe and the equipment is fit to run
Job Plan
Sets out the steps, parts, tools, permits and time needed for a repeatable job
Permit Linked Work Record
Connects maintenance work to the safety permits it requires, such as isolation, hot work or confined space
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 55001:2014, cl.7.5 and 8.1 — Asset management systems, requirements
- ISO 45001:2018, cl.8.1.1 — Operational planning and control
- ISO 22000:2018, cl.8.2 — Prerequisite programmes
- Provision and Use of Work Equipment Regulations 1998, reg.5 — Maintenance
- 21 CFR 117.35 and 117.40; OSHA 29 CFR 1910.212 — Sanitation and machine guarding
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.