At 8:10 on a Monday morning, a gearbox on Line 2 is due for grease.
The work order is closed ten minutes later. On the screen, the task is green. At the machine, the fitting is difficult to reach, the grease gun is not clearly identified, and nobody checks whether old grease has somewhere to escape.
The schedule says the work happened. It cannot tell you whether the right product reached the right point in the right amount.
This is how a plant can have hundreds of lubrication tasks and still live with hot bearings, contaminated oil, repeat top-ups and failures that seem to arrive without warning.
The missing piece is control: who owns the decision, which product is approved, how the work is performed, what evidence is recorded and what happens when reality does not match the plan.
This framework applies to both grease-lubricated and oil-lubricated assets. The controls differ, but the principles do not: verified product identity, clean handling, usable instructions, representative condition data and clear decision ownership.
Ninety days will not transform an entire site. It is enough time to take one important area, find the weak links, build a method people can follow and see whether that method holds up during normal operations.
A green work order proves that someone clicked complete. It does not prove that the machine received the right care.
By Day 90
What the pilot should leave behind.
Not a presentation. A set of controls, records and decisions that can be inspected in the field.
- A defined pilot boundary and accountable owner
- A verified register of critical lubrication points
- An approved lubricant matrix
- A documented lubricant path from receiving to application
- Field-tested work instructions
- Controlled storage and transfer practices
- Representative sampling procedures
- A working exception and closure process
- A baseline and final performance scorecard
- A documented decision to scale, revise or repeat the pilot
Why a lubrication schedule is not a lubrication program
A lubrication route controls timing. A lubrication program also controls the product, method, cleanliness, evidence and response to abnormal conditions.
A due date can remind someone that a bearing needs grease. It cannot confirm that the gun holds the approved product, the fitting was cleaned, the quantity was right or the bearing had a safe path to purge.
Once that distinction is visible, the weak points stop looking random. Engineering chooses a product. Stores receives it. Maintenance applies it. A laboratory reports on its condition. If those decisions live in separate files and separate conversations, the machine becomes the place where every gap finally meets.
ICML 55.1 reflects this wider view through twelve connected areas of lubrication management. ISO 55001:2024 places the same emphasis on defined decisions, responsibility, review and improvement within an asset management system.
A useful 90-day pilot starts small. Its job is to find where the work loses information, cleanliness or ownership while the scope is still manageable enough to repair.
The difference
A schedule controls timing. A program controls the work.
- Due date
- Assigned person
- Completion status
- Approved product and specification
- Controlled storage and transfer
- Defined safe method
- Competent execution
- Recorded evidence
- Representative condition data
- Named decision owner
- Verified closure and management review
The complete roadmap
Three phases, each with an exit test.
The next phase begins only when the current one has produced evidence the team can inspect.
| Phase | Objective | Core activities | Required outputs | Exit test |
|---|---|---|---|---|
| Days 1 to 30 | Verify | Verify the field reality |
|
| Every critical point is verified or formally marked unresolved. No assumption is treated as fact. |
| Days 31 to 60 | Standardize | Convert findings into controlled work |
|
| A trained person who did not write the method can perform it correctly without guessing. |
| Days 61 to 90 | Test | Run the method under normal operating conditions |
|
| The method works across shifts, supervisors can verify it, and exceptions stay open until evidence confirms closure. |
Week by week
A 13-week rhythm the plant can actually run.
- Week 1Select the area, define the boundary and assign ownership
- Week 2Verify assets, points, products, quantities and methods
- Week 3Audit receiving, storage, transfer, application and sampling
- Week 4Record gaps and establish the baseline
- Week 5Rewrite critical work instructions
- Week 6Correct identification, storage and transfer controls
- Week 7Validate sample locations, methods and test requirements
- Week 8Run the night-shift test and competency checks
- Week 9Begin live execution during normal operations
- Week 10Observe tasks and record deviations without blame
- Week 11Correct recurring access, tooling and ownership problems
- Week 12Compare execution and condition evidence with the baseline
- Week 13Decide what to scale, revise or repeat
Days 1 to 30: verify the field reality
With the scope chosen, resist the urge to begin by cleaning the spreadsheet. Start with shoes on the plant floor and one production area where the consequence of poor lubrication is easy to understand. Give one person enough authority to bring maintenance, operations and stores into the same conversation.
Define what is inside the pilot before the work expands on its own: the area, asset families, lubrication points, shifts, lube-room locations and condition-monitoring processes. State what is outside the boundary too. The owner must be able to resolve conflicting information, stop the use of unidentified products, escalate unsafe tasks and require evidence before an exception closes.
Begin at the machine. Find every critical lubrication point. Confirm the product, quantity, method, interval, operating condition, access requirement, tool and responsible role. If a value is unknown, mark the uncertainty. A blank is safer than a confident guess copied from the machine next door.
Now walk upstream. Follow the lubricant from the machine back through the grease gun or transfer container, the lube room, receiving and the supplier label. Then walk downstream through sampling, used-oil handling and disposal. The lubricant needs an unbroken chain of identity, much like a passport. At every handoff, ask whether the product could be contaminated, confused or quietly substituted.
Establish the baseline now, not after the changes begin. Record schedule compliance, unidentified-product findings, instructions that require interpretation, access problems, uncontrolled transfer equipment, abnormal consumption, laboratory exceptions, closure time and repeat defects.
- Can a technician identify the exact point and approved product without guessing?
- Is the quantity defined, or is the approved method for determining it clear?
- Can the work be performed safely under actual access and machine conditions?
- Are containers sealed, identified and supported by dedicated clean transfer equipment?
- Does each sample point represent the machine condition the team needs to understand?
- Would a supervisor know what evidence proves correct execution?
Pilot charter, verified point register, approved-product matrix, lubricant-path audit, gap register and baseline scorecard.
Every critical point is verified or clearly marked unresolved. No assumption is silently treated as fact.
Days 31 to 60: standardize and validate the work
After a month of walking the path, the team should know where the work depends on memory, luck or the one person who has been at the plant for twenty years. Days 31 to 60 turn those discoveries into a method other people can use.
Every critical instruction should name the exact point, approved product, quantity or level, method, machine condition, required tool, contamination-control step, stop condition, evidence and exception owner.
Use the night-shift test. Hand the instruction to a trained person who did not write it. That person should be able to identify the point, select the correct product and tool, perform the task safely, record the evidence and escalate an abnormal condition without calling the author.
The lube room needs the same clarity. Keep lubricants closed and identified, quarantine damaged or uncertain containers, protect clean transfer devices and connect receiving records to the approved specification. Color or symbols can help, but written identity remains the control.
Sampling deserves the same validation. Define the location, machine state, method, purge practice, cleanliness requirement, test slate, intended failure modes and the person who owns an abnormal result. A repeatable sample is still misleading if the location does not represent the condition being investigated.
- Pass: the task is completed correctly without help
- Pass with correction: the method works after a documented change
- Fail: the instruction, tool or competency is inadequate
- Unsafe to perform: access or machine condition prevents safe work
- Unresolved: product, quantity or decision ownership is still unclear
Field-tested instructions, lube-room standard, sampling procedure, competency record and escalation workflow.
A trained person who did not write the method can perform it correctly without guessing.
Days 61 to 90: test the method under normal operating conditions
In the final month, the plant gets to test every assumption the team made indoors. Run the pilot during normal operations, including awkward access, shift changes, urgent work and the tasks with a history of deviation.
Do not observe only easy or well-prepared work. Select critical tasks across different shifts, lubricant types and operating constraints. Record the point, product, tool, access, method, quantity control, contamination controls, evidence, deviation, system cause, action owner and closure evidence.
When someone misses a task or invents a workaround, do not begin with blame. Ask whether the point was accessible, the instruction was clear, the right tool was available and the escalation path made sense. The workaround is evidence about the process.
Bring oil-analysis findings into the same review. A laboratory result creates value only when a named person interprets it in machine context, decides the next action and verifies closure.
Use a fixed weekly review for new critical exceptions, overdue actions, repeat findings, abnormal consumption, laboratory findings, failed instructions and access problems. The team should leave knowing what changed, who owns the next action and what evidence will close it.
- A corrected and field-validated instruction
- Correct lubricant identification or dedicated equipment in place
- An access modification or repeat task observed successfully
- A follow-up sample or consumption record showing the condition changed
- Supervisor verification and similar assets checked where relevant
Observation records, exception-closure log, final scorecard, management review and scale decision.
The method works across representative shifts, supervisors can verify it, and exceptions remain open until evidence confirms closure.
Decision ownership
Name the person who can move the work forward.
A task without a decision owner can remain technically complete and operationally unresolved.
| Role | Accountability |
|---|---|
| Site sponsor | Approves the boundary, resources and final scale decision |
| Pilot owner | Accountable for the complete 90-day result |
| Maintenance planner | Maintains accurate tasks, instructions and frequencies |
| Technician | Validates whether the method works in the field |
| Maintenance supervisor | Verifies execution quality and manages field exceptions |
| Stores or lube-room owner | Controls receiving, identification, storage and issue |
| Operations representative | Coordinates access, machine state and production constraints |
| Reliability or lubrication specialist | Supports product, method, sampling and failure-mode decisions |
| Named machine decision owner | Decides and verifies the response to a confirmed condition exception |
- Who approves a lubricant change?
- Who prevents an unidentified product from being used?
- Who decides whether a task can be deferred?
- Who owns the response to an abnormal laboratory result?
- Who verifies that an exception is genuinely closed?
Schedule compliance is only the first measure
Schedule compliance is necessary, but it does not prove correct execution. Review it alongside method conformance, product control, lubricant condition, abnormal consumption and exception closure.
Read execution and machine condition together. Did the task happen as designed? Did the lubricant remain protected? Did abnormal consumption change? Were confirmed exceptions acted on before the next sample or failure?
Keep the scorecard small. Every measure should lead to a defined conversation, decision or action.
Establish the baseline before announcing a target. Asset criticality, operating conditions and the maturity of the current program all shape what useful improvement looks like.
Program scorecard
Measure execution, condition and response separately.
Each measure should lead to a defined conversation and action.
| Measure | Definition | Evidence source | Review | Action when outside control |
|---|---|---|---|---|
| Schedule compliance | Due critical tasks completed within the approved window | Work-management system | Weekly | Correct capacity, planning or scheduling |
| Method conformance | Observed tasks completed to the field-validated method | Field observations | Weekly | Correct the instruction, competency, tool or access |
| Product-control exceptions | Wrong, mixed, substituted or unidentified lubricant findings | Stores and field inspections | Weekly | Quarantine, identify or review the product |
| Contamination-control exceptions | Findings outside asset-specific cleanliness, moisture or ingress requirements | Inspection and sample results | Per event | Filter, seal, handle or investigate |
| Abnormal lubricant consumption | Top-up or grease use outside the established asset baseline | Usage and work records | Weekly or monthly | Investigate leaks, seals, over-lubrication or equipment |
| Exception closure time | Time from confirmed exception to verified closure | Action register | Weekly | Escalate delayed or unowned actions |
| Repeat exception rate | Closed issues that recur on the same or similar assets | Exception register | Monthly | Review the root cause or wider control |
| Instruction validation | Critical instructions successfully tested in the field | Validation records | Monthly | Prioritize procedure revision |
Read the first weeks carefully. An increase in recorded exceptions during the first weeks may mean the pilot is finally making hidden problems visible. Judge the program by severity, recurrence, ownership and closure, not only by the number reported.
Use your own evidence
A credible pilot result is specific about what remains unresolved.
This is a reporting template, not a success story. Fill it only with verified site data.
| Report line | What to record |
|---|---|
| Pilot boundary | Area, asset family, critical-point count and shifts included |
| At baseline | Unresolved quantities, identification gaps, shared transfer devices, unsafe tasks, sample points under review and current closure time |
| By Day 60 | Instructions validated, storage or transfer controls corrected, sampling methods standardized and competencies demonstrated |
| By Day 90 | Change in method conformance, repeat exceptions and closure time, followed by the scale, revise or repeat decision |
| Still unresolved | One honest limitation, unsafe condition or decision that remains open |
Common mistakes
Ten shortcuts that weaken the pilot.
- 01
Cleaning the CMMS before verifying the field reality
- 02
Copying a quantity from a similar machine without confirming it
- 03
Relabeling containers before resolving the approved specification
- 04
Treating training attendance as proof of competence
- 05
Treating schedule compliance as proof of task quality
- 06
Buying software before defining accurate data and ownership
- 07
Closing a laboratory exception when the report is forwarded
- 08
Expanding site-wide before the pilot survives different shifts
- 09
Blaming technicians before checking access, tools and instructions
- 10
Setting site-wide targets before establishing the baseline
The Day 90 gate
Scale, revise or stop.
A formal decision prevents an unfinished pilot from quietly becoming the site standard.
Expand the controls that hold up
- Critical points and products are verified
- Instructions work across shifts
- Storage and transfer controls are followed
- Sampling is representative and repeatable
- Closure evidence is routinely available
- Remaining gaps are understood and controlled
Correct the method and repeat the pilot
- Instructions still depend on local knowledge
- Repeat deviations remain high
- Access or tooling creates workarounds
- Exception closure is inconsistent
- Product or sampling information remains unreliable
- The scorecard cannot be interpreted confidently
Do not expand yet
- Tasks cannot be performed safely
- Product identity remains unresolved
- Critical exceptions have no owner
- Condition findings are forwarded but not acted on
- Completion records are the only evidence
- Representative shifts and constraints were not tested
By Day 90: decide what to scale, revise or repeat
By Day 90, the team should have something more valuable than a launch presentation: evidence from real shifts, real constraints and real machines.
The review should not be a victory lap. Walk the pilot with the technician, supervisor, stores representative and analyst who lived with it. Ask what became easier, where people still improvised and which machine conditions actually changed.
Some findings will justify hardware, filtration or software investment. Others will be solved by a label, a sample port, a clearer job plan or a named decision owner. The pilot helps the plant spend money where the work has already shown a need.
Ninety days does not finish a plant-wide program. It earns the right to take the next step with less guesswork.
The goal is not a perfect lubrication slide. It is a machine that receives the same correct care on a quiet morning, a busy afternoon and a short-staffed night shift.
Readiness review
What should be auditable before the pilot expands.
Each check needs an evidence source and a person accountable for keeping it current.
- 01Pilot boundary and ownershipEvidence
Approved pilot charter with named sponsor and owner
OwnerSite sponsor - 02Critical points and productsEvidence
Verified point register and approved-product matrix
OwnerPilot owner - 03Storage and transferEvidence
Inspection records showing identified, sealed and controlled equipment
OwnerStores or lube-room owner - 04Work instructionsEvidence
Signed field-validation records across representative shifts
OwnerMaintenance supervisor - 05SamplingEvidence
Approved sample locations, methods, operating states and test requirements
OwnerReliability specialist - 06Exception closureEvidence
Action register with owners, dates and closure evidence
OwnerNamed machine decision owner - 07Scale decisionEvidence
Management review separating scale-ready controls from unresolved gaps
OwnerSite sponsor
Common questions
Questions teams ask before they start.
Can a machinery lubrication program really be built in 90 days?
Not across an entire plant. Ninety days is enough to build and test a controlled pilot in one clearly defined area. The pilot should verify lubrication points and products, establish storage and transfer controls, field-test work instructions, define exception ownership and compare results with a baseline. The outcome is evidence showing what is ready to scale, what needs revision and what should not yet expand.
What is the first step in improving a lubrication program?
Select one important but manageable operating area and name one accountable owner. Then walk the lubricant path from receiving and storage through transfer, application, sampling and disposal before rewriting procedures or cleaning work-management data. Existing records may contain quantities, products, intervals or methods that have never been verified at the machine.
Do we need lubrication-management software before starting?
No. A pilot can begin with controlled registers, forms, labels, inspection records and a disciplined review process. Software becomes valuable when point data, product specifications, work methods, ownership and closure requirements are already accurate. Automating an unverified process does not create control.
Which training supports lubrication-program implementation?
Machinery Lubrication I supports foundational capability in selection, handling and contamination control. Machinery Lubrication II suits teams developing precision lubrication and program design. Machinery Lubrication Engineer supports leaders responsible for governance, strategy and plant-wide improvement. Match training to the decisions each role must make rather than assigning the same course to everyone.
Standards and primary references
Editable workbook
Microsoft Excel | 10 worksheetsTake the 90-day plan into the field.
Define the pilot, verify each point and product, observe the work, manage exceptions and record the Day 90 decision.
Download field packPlan
- Pilot charter
- Point verification
- Product matrix
Verify
- Lubricant-path audit
- Instruction validation
- Task observation
Control
- Exception register
- KPI scorecard
- Readiness review
- Scale decision
New field notes
Get one practical lubrication field note each month.
Clear guidance on lubrication, oil analysis and reliability improvement. No daily emails.
