
THE FAILURE MODE IS QUIET, NOT DRAMATIC
Incorrect lubrication rarely announces itself. A technician tops up a gearbox with the nearest drum because the correct one wasn't obvious. A grease gun is reloaded with the wrong cartridge because the colour code was never applied at that point. Weeks later, a bearing fails - and the root cause traces back to a five-second decision made without the information to make it correctly.
Regular, structured inspection catches the second half of the problem: machines quietly running low, sight glasses fogged or blocked, and level indicators that were never fitted in the first place. Identification and inspection are two halves of the same discipline - one prevents the wrong lubricant going in, the other confirms the right amount is still there.
FIVE LAYERS OF IDENTIFICATION
Each layer builds on the one before it. Skipping straight to digital integration without the physical layer in place is the most common reason lubrication ID systems fail to stick.
Assign a colour and a shape to each lubricant family, not colour alone — shape coding protects colour-blind technicians and remains legible under poor lighting or on faded tags. Base the scheme on a recognised colour-and-shape identification system rather than inventing one in-house, and apply it consistently across dispensers, storage drums, transfer containers and the application point itself, so the container and the machine are always checked against each other before a drop of oil moves.

Durable, standardised tags at every lubrication point — not just the ones that are easy to reach. Each tag should carry four things at minimum: lubricant type, quantity per application, re-lubrication interval, and a unique point code that ties back to the lube chart and the CMMS asset record. Laminated or engraved tags outlast printed stickers in washdown or high-temperature areas.
A single, centralised chart cross-referencing every machine, its lubrication points, the correct product, and the interval — the master document everything else is checked against.

Linking the physical system to a CMMS or ERP platform (SAP PM, Maximo, or equivalent) is only useful if it's clear what is being tracked. In practice this means three linked records: the asset ID matched to its lubrication points, the lubricant SKU matched to its colour/shape code, and a time-stamped completion log for every application and every inspection. That third record is what turns identification from a labelling exercise into an audit trail — it shows not just what should happen, but what did.
Align the system with the standards that actually govern it, rather than a generic reference. The relevant frameworks are asset-management and contamination-control standards, workplace safety regulation, and, only where food-grade lubricants are in use, food-contact standards specifically.
Identification alone isn't enough. Machines are routinely found running with insufficient lubricant — not through neglect, but because a leak went unnoticed, a sight glass was blocked, or no level indicator existed to check in the first place.
A fixed "daily walk-around for everything" approach either wastes time on low-risk assets or under-inspects the ones that matter. Tier inspection frequency to consequence of failure instead:

The most common gap in an otherwise well-run programme: inspections are completed, findings are noted on a clipboard or a form — and nothing structured happens afterwards. Step 3 isn't finished until a flagged finding automatically becomes a tracked action.

Programmes that stick have a named owner for every inspection point. Programmes that fade usually have a policy document and no one person accountable for walking the route this week.
Machine operators take ownership of daily visual checks on their own equipment as part of autonomous maintenance. Works well for high-frequency, low-complexity checks — level, colour, obvious leaks — because the operator is already at the machine every shift. Requires basic training and a very simple pass/fail check sheet.
A trained specialist runs the full route across multiple assets, including sampling, chart maintenance, and CMMS logging. Better suited to critical assets, deeper diagnostics, and sites where consistency matters more than frequency. Most mature programmes run both models together — operators for daily visual checks, a technician for the structured weekly or monthly route.
Track a small set of numbers so the programme's health is visible before a failure makes it visible instead.
