A pre-use inspection checklist is a safety control on paper and a formality in practice. Nothing stops the box being ticked, and nothing stops the equipment being used if it isn't.
An estimated $40,320 a year in labour time saved, by the site's own tracker. Where the figure comes from
$40,320 a year, estimated
The site's efficiency-savings tracker timed this task by hand and again with the software. The labour time saved comes to an estimated $40,320 a year.
| Task | Saved a year |
|---|---|
| Equipment check-out and return at the badge kiosk | $40,320 |
Check-out counts the queue: everyone lined up at the kiosk waits out each check-out ahead of them.
Estimated by the site's own efficiency-savings tracker: each task timed by hand and again with the software, the time saved valued at a fully loaded labour rate over a 252-day working year. Labour time only, to the whole dollar.
Built for the floor operation of a contract-logistics site, covering fall-protection equipment, powered industrial trucks and personal protective equipment.
Tie the checklist to the equipment pool. Every check-out begins at a badge kiosk from the truck picked: a counterbalance truck gets five steps and twelve points, and a cherry picker or turret truck adds the harness and its sixteen. An unticked box counts as a failed point, and a failure locks the item out until an administrator clears it.
Harnesses and forklifts were checked out at a cage on a clipboard. The inspection checklist existed and people ran it, but nothing connected a failed inspection to the equipment actually being taken out of service, and nothing connected an item to the person holding it once the sheet filled up. Fixing it started with moving a clipboard workaround onto a real database.
For a fall-protection harness, that gap is the whole point of the control. A harness with a deployed load indicator has already arrested a fall and must never be used again — but only if somebody notices the tick box and does something about it.
A badge-reader kiosk on the floor, beside the scanners, label printers and other 3PL floor hardware the site already ran. Every check-out starts from the truck, and the truck decides the rest. Pick a counterbalance truck and the session is five steps and twelve inspection points — tyres, leaks, fluids, mast chains, brakes and lights. Pick a cherry picker or a turret truck, the ones that put someone at height, and two more steps appear for the harness and its sixteen: webbing, stitching, hardware, load indicators and labelling. Nobody chooses whether fall protection applies to them.
An unticked box is treated as a failed point, not a blank. That single decision is what makes the checklist mean something.
| Control | Clipboard at the cage (before) | Badge kiosk (after) |
|---|---|---|
| Which inspection runs | A checklist people ran by hand | Set by the truck picked: twelve points, or twenty-eight with a harness |
| An unanswered point | A tick box somebody had to notice | Counted as a failed point |
| A failed inspection | Not connected to taking the equipment out of service | Blocks check-out and locks the item out of the pool |
| Escalation | Up to whoever chose to escalate | Management emailed once the record is committed |
| Who holds an item | Lost once the sheet filled up | Recorded by the nightly sweep before it force-returns the item |
Equipment left checked out overnight is force-returned by a nightly sweep that first records who was holding it, so the trail survives the reset instead of being erased by it.
That record feeds a chain-of-custody exception report: every item returned by someone other than the person who took it, or closed out by the automatic sweep rather than a human, with the duration it was actually held. It answers the question a clipboard never could — not who signed for it, but who had it.
The inspection became a control instead of a formality. Failing equipment leaves the pool automatically, the failure is escalated without anyone choosing to escalate it, and every item has a custody history rather than a signature. The same idea, a record that controls rather than one that only remembers, applies to fire alarm inspection, testing and maintenance records.
Because a blank is how a checklist becomes a formality: nothing stops the box being ticked, and nothing stops the equipment being used if it is not. Treating an unticked box as a failed point means a truck or a harness is released only when every point it carries has passed, and a failure takes the item out of the available pool until an administrator clears it.
Management is emailed the moment an inspection is flagged: the failed points, the reported issue and who was standing at the reader. The email is sent after the record is committed and outside it, so an unreachable mailbox cannot undo the lockout, and the item stays out of the available pool until an administrator clears it.
Because badges get re-issued. A harness assigned to an individual locks to that person's name, so a replacement badge never breaks the assignment. Unknown badges register on the spot and alert leadership, throttled so a badge left on the reader cannot spam anyone.
Client, location, system names and volumes are withheld deliberately; the savings above are the tracker's dollar estimates, with the minutes, rates and headcount behind them left out. We're happy to go deeper on architecture and approach on a call.
Bring decades-old systems into the modern era without a risky rip-and-replace.
See Legacy Modernization & Migrations →Connect aging systems to modern APIs, data platforms, and SaaS tools.
See System Integration →Customer-facing quality audits ran on paper and a survey tool. We built a configurable audit platform with scheduling, escalation, approvals — and a gate that blocks sign-off when the scan doesn't match.
Read the story →End-of-life material left the site on paperwork typed by hand. We rebuilt the chain end to end and added the control nobody had: detection of inventory added after the paperwork was already filed.
Read the story →Access was a boolean column on the user record, so every new screen was a schema change. We replaced it with roles that map to screens, credential checks that verify a second person without elevating the first, and a suspension path that fails closed.
Read the story →Tell us what gets signed out and what the checklist asks before it goes. Talk to an engineer.
Call 832-598-8234 or email msco@stoneagesoftware.com. Houston, Texas — serving Houston, The Woodlands, Conroe, Sugar Land, Katy, Pearland, and the Greater Houston metro.
We read your message, an engineer replies with questions or a straight answer, and if a call would help, we book one. From the first reply on, you're talking to the people who'd do the work.
