The compressor seized on a Thursday in July, eleven months into a fifteen-year design life’s final stretch — early, but not impossibly early. What made the failure a problem instead of a misfortune was the file.

Because the file was perfect. Quarterly PMs, every quarter, signed and dated. Coil cleaning: done. Refrigerant check: done. Belt and bearing inspection: done, done, done — a wall of green checkmarks going back three years. The operations director pulled it expecting vindication and found, instead, a question he couldn’t put down: if all of this was done, how did the bearing fail the way bearings fail when nobody touches them for years?

The teardown answered. Caked coils. A belt worn past any plausible recent inspection. The PMs hadn’t been done. They’d been signed. For three years, by more than one technician, the checkmark had quietly replaced the work.

Pencil whipping is what overloaded systems produce. The individual signature is a symptom. The system that accepts signatures as proof is the disease.

It has a name, and it isn’t an anomaly

The industry calls it pencil whipping — signing off work that wasn’t performed — and the operators we interviewed described discovering it so often that the discovery, not the practice, was the rare event. In most operations, the only way to find out a PM was never done is exactly the way the operations director found out: when the asset fails ahead of schedule, weeks or months after the records went green.

Resist the easy reading, though, because “dishonest technicians” explains almost none of it. Pencil whipping is what overloaded systems produce. The tech has eleven work orders and time for seven; the unit “looked fine last quarter”; the checkbox takes one second and the inspection takes forty minutes; nobody has ever once compared the checkmark to the coil. Every incentive in the system points toward the signature, and not one mechanism points away from it. The individual signature is a symptom. The system that accepts signatures as proof is the disease.

The structural flaw: the record vouches for itself

Here’s the design problem stated plainly: in most maintenance systems, the same instrument that creates the task also certifies its completion — and the certifying party is the performing party. The work order asks, in effect, “did you do this?” and accepts “yes” as evidence. No audit regime in finance would survive that design for a day; self-attestation without independent evidence isn’t a control, it’s a courtesy. Yet it’s the default architecture of maintenance records — which is why a compliance file full of green checkmarks can coexist with three years of unperformed work. The log isn’t proof. It’s a starting point for an investigation.

The consequences stack beyond the failed asset. The compliance exposure: those signed-but-unperformed PMs are now documented misrepresentations sitting in the file an inspector or insurer will read. The data corruption: every analysis built on the records — asset health, replace-versus-repair, vendor performance — inherits their fiction. And the money: the operation paid for the labor twice, once for the work that wasn’t done and again for the failure it caused.

What independent verification actually looks like

The fix is architectural, and the principle transfers directly from financial controls: completion evidence must be generated by something other than the completer’s assertion. In practice, that’s a short list with teeth.

STAGE 1 Visual & Structured Proof

Require timestamped, geotagged photos and specific readings (e.g., exact gauge numbers) at the point of work instead of simple checkboxes.

STAGE 2 Sensor Corroboration

Cross-reference the paperwork against the asset’s own telemetry, ensuring current draw or vibration aligns with the claimed service.

STAGE 3 Verified Payments

Release vendor payment only after completion evidence is objectively verified, turning verification into the economic structure of the transaction.

That payment-on-verification link is exactly how Sweven FM closes work orders, because every operator who told us a version of the July compressor story had the same file: perfect, green, and worthless.

The Evidence Audit

The uncomfortable closing exercise belongs to the reader. Pick your most critical asset and pull its last four PM records. Now ask the question the operations director asked too late: what in this file would survive a teardown? If the honest answer is “the signatures” — you don’t have records. You have testimony, from witnesses with a schedule to protect.

Sources: