The maintenance log that can't be quietly edited.
Work orders, PM, parts and lockout/tagout for manufacturing plants. Operators report problems free.
What breaks today
PMs slip
A preventive maintenance schedule living on a whiteboard or a spreadsheet only works until someone forgets to update it. Then it stops being a schedule.
Parts walk
A tech grabs a bearing off the shelf, fixes the machine, and moves on. Nobody logs it. The count on the shelf and the count in the system stop matching.
The tag ends up in the trash
A lockout tag gets pulled, the job gets done, and the paper trail that proved it happened correctly goes in the bin with the rest of the shift's scrap.
Written once. No edit button.
This is the reason for the name. Once a lockout record is released, it cannot be reopened, back-dated, re-attributed, or deleted. A parts transaction cannot be edited or deleted. The rule does not live in the app. It lives in the database itself, and it holds for every user and every app connection.
- Group lockout, per person
- Every tech on a job gets their own lock. The machine stays locked until every one of them releases theirs.
- Every energy source, verified one at a time
- Electrical, pneumatic, hydraulic, whatever that machine actually has. Each point gets checked off as it is isolated, and the lock does not go on until every one of them is done.
- Force-release needs a reason
- A manager can force a lock open in an emergency, but only by writing down why. That reason is kept permanently.
- A PDF an inspector can keep
- Export the whole lockout history for any date range as a formatted document, with every isolation point and every override reason on it.
No hashing. No blockchain. Just a database that refuses the write.
Tickets that write themselves
A scheduled job runs every night, recalculates every piece of equipment's PM status against its own interval, and opens a work order the moment one comes due. If a ticket is already open for that task, it skips it. No duplicates piling up in the queue.
Current
PM Needed
Overdue
Scan to closed
Anyone on the floor can report a problem in seconds. From there it moves through a work order, a tech clocked in against the machine, and the parts it took to fix it, without leaving a paper trail behind.
Scan a QR code, no login
A code posted at a machine or shared as a link. Operators, contractors, anyone who spots a problem can report it without an account. Spam is filtered with a honeypot and per-IP rate limiting, and every report lands in a queue an admin triages before it becomes a ticket.
The public report form
Short, mobile-friendly, and staged for review before it touches a real work order.
Work orders, clocked labor
Every ticket is tied to the actual piece of equipment, its lock status, and the techs clocked in against it, from open to close. An email goes out when a ticket gets assigned, and again when a PM comes due.
Parts and variance
On-hand counts, reorder points, and an append-only ledger that shows exactly what was required against what actually got used.
The numbers for Monday morning
Labor cost, PM on-time rate, cost by equipment, ticket volume by status and priority. The same questions a plant manager gets asked every week, answered without building a spreadsheet first.
Any date range, drilled down to a single ticket or rolled up across a quarter.
Cost by equipment, maintenance trend over time, and required-versus-actual parts variance, all pulled from the same ledger everything else writes to.
Export the whole ticket detail table to CSV when someone wants the raw rows instead of the summary.
Only the people who fix things pay
One plan, priced per active seat by role, not a tier to pick. Most maintenance software charges the same rate per login whether that person closes ten tickets a day or just checks a dashboard once a month.
Admin & Manager
Reports, cost tracking, approvals, force-release with a written reason.
$29/ user / moTech
Work orders, PM tasks, clock-in labor, parts logging, lockout/tagout.
$15/ user / moOperator
Report a problem. Unlimited seats, never billed.
Free
We're running a limited pilot right now. A small group of manufacturing teams are onboarding directly with us — no self-serve signup today. Invite Managers, Techs and Operators as your team grows — you're only billed for active seats, not for every account you create.
Who built it
Lockledger is built by a solo founder who is also a working Process Improvement Manager at a custom contract packaging and lubricants blending plant. The original version of this system, built in Power Apps, has been running in production there for over two years, tracking the same work orders, PM schedules and lockouts this product handles now.
What it does not do, yet
No customers means no case studies to lean on, so here is what is honestly out of scope today. What it does cover, it covers completely.
Integrations
- No SSO or SAML
- No public API
- No ERP integration
Data handling
- No data residency choice
- No retention guarantee
Coverage
- No native mobile app
- No push notifications
Prove what happened on the machine.
We're onboarding a small group of manufacturing teams directly before opening up to everyone. Tell us about your plant and we'll get you set up — or just leave your email and we'll let you know when it's open to the public.
Just want to know when it's open to everyone?