What this is
What is a weekly maintenance schedule, specifically?
What is a weekly maintenance schedule, specifically?
It is the documented commitment of labour hours, parts and access windows to a named set of work orders for one calendar week, agreed with production before the week starts. It is not the backlog, not the PM plan, and not a wish list; it is the subset of work the site has actually committed capacity to deliver.
Why does loading percent matter more than hours scheduled?
Hours scheduled on its own says nothing about whether the plan is realistic. Loading percent compares scheduled hours to available hours, and the template's own guidance is explicit that scheduling to a hundred percent guarantees failure, because it leaves nothing for the reactive work that will inevitably arrive.
What does 'schedule frozen before week start' actually protect?
It protects the plan from being quietly rewritten mid-week every time something more urgent turns up, which is how schedule compliance figures get gamed without anyone intending to game them. A frozen schedule means deviations get tracked as deviations, not absorbed as if they were the plan all along.
Scope
When is a weekly maintenance schedule required?
This plan is the operational centre of the Planned Maintenance programme; using it to record work that has already happened, or work nobody has committed capacity to, breaks the compliance figure it exists to produce.
Use this template when
- The coming week's planned work is being set against labour, parts and access windows before the week starts
- Production sign-off is needed on the schedule before it is frozen
- The workspace is being set up, or the singleton schedule needs its next cycle entered
- You are running the Planned Maintenance programme and this is its weekly planning step
- A linked record needs this one to exist: links Work orders, PM plans
Do not use it for
- Schedule Compliance Review, which reviews what was scheduled against what was actually done, and why the gap exists, after the week has run.
- Maintenance Backlog Review, which reviews outstanding work by age, priority and asset criticality, rather than committing this week's capacity.
- Production Access Agreement, which records the access window agreed for a single job and what happens if it overruns, not the whole week's plan.
- Job Plan, which defines how a specific piece of work is carried out, not when it is scheduled against capacity.
- Anything outside KnowMaintain, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 55001 cl.8.1 requirements does this satisfy?
ISO 55001 cl.8.1 requires operational planning and control over processes needed to meet asset management objectives; the weekly schedule is where that planning becomes a committed, capacity-checked plan rather than an aspiration.
| Clause | Requirement | Where it lands |
|---|---|---|
| 8.1 operational planning | Plan and control operational activities against defined capacity | Capacity |
| 8.1 operational planning | Establish controls to ensure resources, parts and access are available before work proceeds | Readiness |
| 6.1 actions to address risks and opportunities | Ensure statutory and overdue critical work is not displaced by routine planning | Balance |
| 9.1 monitoring, measurement, analysis and evaluation | Determine what needs monitoring and how results feed planning decisions | Result |
| 8.1 operational planning | Retain documented information for confidence processes are carried out as planned | Header |
| 10.1 nonconformity and corrective action | Act on identified planning gaps with a tracked corrective action | Result |
What it does not cover
- Loading Percent, which was recorded above roughly eighty with no corresponding entry under Reserve For Reactive Work, contradicting the template's own guidance.
- All Parts Available, which showed 'No' or 'Most' for work carried into Scheduled Work rows without a corresponding change in Ready To Schedule.
- Overdue Critical Work Included, which recorded 'No' with overdue critical work known to exist, meaning the schedule silently deferred it again.
- Schedule Frozen Before Week Start, which was marked 'Partly' or 'No', undermining any compliance figure calculated against this week's plan.
- Agreed With Production, which was left as 'Partly' with no note explaining what production has not agreed to.
Global
Weekly Maintenance Schedule requirements by country
ISO 55001 sits alongside, rather than replaces, sector-specific statutory maintenance duties; the schedule's consequence differs by how those duties interact with weekly planning.
ISO 55001 alongside statutory inspection and maintenance duties
Regulators expect statutory work to be demonstrably prioritised, not squeezed out by routine planning under capacity pressure.
Statutory Work Included being answered 'No' on a live schedule is evidence a regulator would treat as a planning control failure, independent of ISO certification status.
ISO 55001
Certification bodies increasingly sample weekly schedules directly during surveillance audits, rather than relying only on backlog reports.
A frozen, production-agreed schedule with visible readiness checks is the artefact an auditor expects to see, not a retrospective summary.
ISO 55001 as a customer requirement
Brand owners auditing co-manufacturers often ask specifically how planned versus reactive work is balanced.
The Planned, Preventive and Reactive Work Percent fields are frequently the exact numbers a customer audit will request evidence for.
How to complete it
How to complete a weekly maintenance schedule, step by step
Entering numbers into every field is straightforward; these four judgement calls are what determine whether next week's compliance figure will mean anything.
Reserve For Reactive Work should be sized against the site's actual historical reactive burden, not set to whatever is left over after preventive work is loaded. A reserve that is just the arithmetic remainder is not a planning decision, it is a rounding error being reported as one.
All Parts Available, Job Plans Available and Permits Identified can each independently make a job unready. The judgement call is whether a job with a 'Partly' on any of these should still enter Scheduled Work as Ready To Schedule 'Yes', or whether it should be held back a cycle rather than scheduled and likely deferred.
Agreed With Production 'Yes' should mean production has seen the access windows and line-stop requirements specifically, not that the schedule was emailed and nobody objected. A schedule agreed only in principle will not survive contact with the shift that actually has to give up the line.
Schedule Frozen Before Week Start exists precisely so that mid-week changes are visible as changes. The judgement call is deciding, in advance, what threshold of urgency justifies breaking the freeze, rather than deciding it in the moment for every individual request.
What auditors find
Most common weekly maintenance schedule findings
These are the patterns that show up repeatedly once weekly schedules are checked against their own stated logic rather than just filed.
| Finding | Clause | What fixes it |
|---|---|---|
| Loading Percent consistently near or above a hundred | 8.1 operational planning | Cap routine scheduling against a fixed ceiling (around eighty percent of Labour Hours Available) enforced at the point of entry, not corrected after the fact. |
| Overdue Critical Work Included answered 'No' across consecutive weeks | 6.1 actions to address risks and opportunities | Escalate automatically to the Maintenance Backlog Review when overdue critical work is excluded for more than one consecutive schedule. |
| Ready To Schedule marked 'Yes' despite 'No' or 'Partly' on parts, permits or access | 8.1 operational planning | Make Ready To Schedule a calculated field driven by the readiness answers, rather than a separate judgement entered by the planner. |
| Schedule Frozen Before Week Start recorded 'Partly' with no explanation of what changed | 9.1 monitoring, measurement, analysis and evaluation | Require a linked note or work order reference whenever the freeze is broken, so schedule compliance figures can be reconciled against real deviations. |
| Reactive Work Percent trending up with no change to Reserve For Reactive Work | 6.1 actions to address risks and opportunities | Feed the prior cycle's actual Reactive Work Percent back into the following week's reserve calculation instead of holding the reserve static. |
| Action Required left 'No' despite Result Band showing 'Fail' | 10.1 nonconformity and corrective action | Force Action Required to 'Yes' whenever Result Band is 'Fail', removing the option to record a failing result with no follow-up. |
Case in point
Case in point: the eighty percent line that got ignored twice
A site's planner had been scheduling to ninety-five percent loading for months, reasoning that a well-run team should be able to absorb the odd breakdown. Reserve For Reactive Work was entered each week as whatever hours were left, usually under five percent, and Schedule Compliance had been drifting down for two months without anyone connecting the two numbers.
A gearbox failure on a critical line consumed a full day of the only qualified electrician, and the entire week's preventive schedule behind it cascaded into the following week, which was already loaded the same way. It took a third consecutive low-compliance week before the pattern was traced back to Loading Percent, at which point the reserve was fixed at fifteen percent regardless of how tempting the spare capacity looked on paper.
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.
6 sections
- Reference
- MNT-079
- Archetype
- Plan
- Record ID
- WMS-2026-000
- Scoring
- Schedule compliance
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 55001 cl.8.1
- Links
- Links Work orders, PM plans
- Tags
- Planning
- Sections
- 6
- Fields
- 50
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 3
Header
10 fieldsSchedule ID*
Auto sequence. Format WMS-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*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Schedule Compliance Predicts Breakdowns
Sites that complete what they planned have fewer failures. Sites that plan and then firefight have more. The number is the leading indicator maintenance actually has.
Week Commencing*
Planner*
Agreed With Production*
- Yes3 pts
- Partly1 pt
- No0 pts
Capacity
6 fieldsLabour Hours Available*
Labour Hours Scheduled*
Loading Percent*
Scheduling to a hundred percent guarantees failure. Around eighty leaves room for the breakdowns that will happen.
Reserve For Reactive Work*
Contractor Resource Booked
- Yes3 pts
- Not needed3 pts
- No0 pts
Specialist Skills Available*
- Yes3 pts
- Partly1 pt
- No0 pts
Readiness
6 fieldsAll Parts Available*
A job scheduled without its parts is a job that will be deferred and will consume a slot doing it.
- Yes3 pts
- Most1 pt
- No0 pts
Parts Kitted*
- Yes3 pts
- Partly1 pt
- No0 pts
Job Plans Available*
- Yes3 pts
- Partly1 pt
- No0 pts
Permits Identified*
- Yes3 pts
- Partly1 pt
- No0 pts
Access Windows Agreed*
- All3 pts
- Some1 pt
- None0 pts
Isolations Planned*
- Yes3 pts
- Partly1 pt
- No0 pts
Scheduled work
Repeats9 fieldsWork Order ID*
Links to MNT-002 Work Order ID
Description*
Asset Criticality*
Work Type*
Estimated Hours*
Assigned To*
Line Stop Required*
- No3 pts
- Yes1 pt
Ready To Schedule*
- Yes3 pts
- Partly1 pt
- No0 pts
Priority*
- High0 pts
- Medium1 pt
- Low3 pts
Balance
6 fieldsPlanned Work Percent*
Preventive Work Percent*
Reactive Work Percent*
Statutory Work Included*
- Yes3 pts
- None due3 pts
- No0 pts
Overdue Critical Work Included*
- Yes3 pts
- None overdue3 pts
- No0 pts
Schedule Frozen Before Week Start*
- Yes3 pts
- Partly1 pt
- No0 pts
Result
13 fieldsItems Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Planner*
Signature*
Maintenance Manager*
Second Signature*
MNT-079 · record IDs look like WMS-2026-000 · Links Work orders, PM plans
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping the schedule current, holding the freeze, and reconciling reactive load week over week is the work that actually slips.
Holds the weekly schedule against work orders and PM plans, tracks the freeze, and rolls schedule compliance into the same view as the backlog.
Feeds asset criticality into the scheduled work rows, so line-stop and priority decisions reflect real consequence rather than whoever asked loudest.
Confirms parts availability against the parts request pipeline before a job is marked Ready To Schedule, closing the gap the readiness section depends on.
Coordinates the crew, rolls readiness and loading exceptions into one view, and holds every write for your approval before it touches a record.
This template lives in KnowMaintain — asset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.
Meet KnowMaintain→Glossary
Weekly Maintenance Schedule definitions and key terms
- Schedule compliance
- The percentage of planned work actually completed as scheduled, treated across the industry as the single strongest leading indicator of whether breakdown rates will fall or rise.
- Loading percent
- Scheduled labour hours expressed as a percentage of available labour hours; the template treats anything near a hundred percent as a planning defect rather than efficiency.
- Readiness
- The state of a job having its parts, job plan, permits and access windows confirmed before it is committed to the schedule, rather than discovered missing mid-week.
- Frozen schedule
- A schedule that is locked before the week starts, so any change during the week is visible as a deviation rather than absorbed silently into the plan.
- Reactive reserve
- Labour hours deliberately held back from planned work to absorb unplanned breakdowns, sized from historical reactive load rather than left as whatever capacity remains.
FAQ
Frequently asked questions about weekly maintenance schedule
What is a weekly maintenance schedule?+
It is the plan that sets the coming week of planned work against available labour, parts and access windows, agreed with production before the week starts. It is built against ISO 55001 cl.8.1 and forms part of the Planned Maintenance programme.
Why is this a singleton template?+
There is one live schedule per workspace at a time, superseded each cycle, rather than a new independent record per event. Other templates, including the compliance review, refer back to it.
What loading percent should a site target?+
The template's own guidance points to roughly eighty percent as workable, with the remainder held as reserve for reactive work. A hundred percent loading is presented as a guarantee of failure, not an achievement.
Who has to agree the schedule before it is frozen?+
Production, specifically, because line stops, access windows and isolations affect their operation directly. Agreed With Production is a required field precisely because a schedule agreed only within maintenance rarely survives the week.
What happens if statutory work is left out of a given week?+
Statutory Work Included is scored separately from general loading so that a busy-looking schedule cannot mask a missed statutory obligation; a 'No' here should trigger escalation rather than simply be logged.
Can the template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the links to other templates come with it. Most teams install it as it is, run it for a cycle, then adjust.
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
Maintenance Request
Asks maintenance to look at a problem or carry out a job
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
More in Planning and Scheduling
Schedule Compliance Review
Reviews what was scheduled against what was actually done, and why the gap exists
Maintenance Backlog Review
Reviews outstanding work by age, priority and asset criticality
Production Access Agreement
Records the access window agreed with production for a job, and what happens if it overruns
Maintenance Cost Review
Reviews maintenance spend by asset, type and category over a period
Contractor Maintenance Work Order
Covers a maintenance job carried out by a contractor, holding the scope, permits, supervision and handback
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.8.1 — Operational planning and control
- ISO 55001:2014 cl.6.1 — Actions to address risks and opportunities
- ISO 55001:2014 cl.9.1 — Monitoring, measurement, analysis and evaluation
- ISO 55001:2014 cl.10.1 — Nonconformity and corrective action
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.