Lubrication Route Manager
Turn your machine lubrication routes into a guided checklist techs complete on their rounds, with planner approval, so lube tasks are consistent, complete, and recorded.
A login-protected web app where techs run due lube routes as a checklist, flag missed or abnormal points, a planner approves the completed route, and you export a clean lube-history CSV.
Before you start
- A list of your lubrication routes and points (a spreadsheet is fine)
- Free Vercel, Supabase, and Resend accounts
- Claude Code installed on your machine
The problem this kills
Lubrication is one of the most boring jobs in the plant and one of the most quietly destructive when it goes wrong. A point gets skipped. The wrong grease goes into a bearing. Someone over-greases a motor and blows a seal. Nobody writes any of it down, so when a bearing fails three weeks later there is no record of whether it was ever touched.
Most plants run lube routes off a laminated sheet, a clipboard, or a tech's memory. The route exists in one person's head, the lubricant types live in another spreadsheet, and "done" means a checkmark nobody ever reviews. The result is exactly the failure mode lube programs are supposed to prevent: inconsistent, incomplete, unrecorded greasing.
This plan kills that. It turns each route into a guided checklist that shows the tech every point in order, the exact lubricant and amount for that point, and a clear way to flag anything missed or abnormal. A planner reviews the completed route before it counts as done, and every run is permanently logged.
What you'll build
A small, login-protected web app, tailored to your plant, that lets you:
- Define your routes - the ordered list of points on each machine, with the lubricant type, the amount, and how often each point is due.
- Generate a due route checklist when it's time to run a route.
- Let the tech complete the route point by point, recording what they applied and flagging any missed or abnormal points (wrong fitting, leaking seal, ran dry, couldn't access).
- Send the completed route to a planner who reviews and approves it - including every flagged exception - before it's logged as done.
- Export your lube history and the open issue list as clean CSVs your CMMS or maintenance log can read.
What's inside the Implementation Plan
The plan is a single runbook you paste into Claude Code (an AI coding assistant). It opens by interviewing you about your plant - your machines, how you name assets and lube points, which lubricants you stock, your route frequencies, your peak shutdown volumes, and your real edge cases - and reads back a short spec for your thumbs-up before it builds anything. That means you get a tool shaped around your routes and your naming, not a generic template you have to bend to fit.
From there it walks you step by step through standing up the database, the login, the route definitions, the tech's checklist screen, the planner approval gate, and the CSV import/export - each step ending with a ready-to-paste prompt.
The governance it includes (this is the point)
This isn't a toy. The plan builds in the controls a real maintenance program needs:
- Login so only your team can use the tool.
- Row-level security so a tech only ever sees their own plant's data.
- A complete audit trail - who ran which route, who approved it, and when.
- A human-in-the-loop approval gate - the tech's completed route is a draft until a planner reviews and approves it; only then is it logged as official history.
- Duplicate guards - the same route can't be logged twice for the same run date, so your history stays clean.
Who it's for
Lubrication techs and maintenance planners who want their lube program to be consistent, complete, and recorded - without buying a big CMMS module or waiting on IT. If you can fill in a spreadsheet, you can build this.
You've got this - paste the first prompt and let the agent interview you.