Maintenance that manages itself
You fix it.Tickover runs the rest.
Maintenance that documents itself. Your team talks about the job the way they already do, and Tickover listens, writes the record and remembers every breakdown and every fix. When something stops, the right person arrives with a plan built from what worked last time. No forms. No new app.
- 1Check the drive-side tension roller2 Nov job
- 2Bring a 13 mm spanner and a lock nut
Ravi - 3Spare roller TR-220 is in bay 3
Sunil
Stopped around 09:08 ±4 min. Priya reported it at 09:12. Ravi was on it by 09:15 and had it running again at 09:41. The drive-side tension roller had worked loose because its lock nut backed off. New nut fitted.
- 1Check the drive-side tension roller2 Nov job
- 2Bring a 13 mm spanner and a lock nut
Ravi - 3Spare roller TR-220 is in bay 3
Sunil
Stopped around 09:08 ±4 min. Priya reported it at 09:12. Ravi was on it by 09:15 and had it running again at 09:41. The drive-side tension roller had worked loose because its lock nut backed off. New nut fitted.
The person who knowswhat happened hastheir hands full.
So what they learned never gets written down. The job closes as “fixed”, the cause is a guess from a dropdown, and the next time it breaks, whoever turns up starts from zero.
Most teams already have maintenance software. The work still happens outside it.
The repair gets done. The record does not. It lives in a WhatsApp group, a phone call and somebody's memory, and the software only knows what someone found time to type in later.
use maintenance software
say the whole team uses it, every time
say people were never properly trained on it
were asked for something that was already in it
Of 686 maintenance and operations professionals surveyed. Limble, 2026 State of Maintenance, as reported by Plant Services and Manufacturing Dive.
The same breakdown, again.
Nobody can see it is the third time, so it gets diagnosed from scratch, again.
Spare parts by guesswork.
You stock what you remember running out of, not what actually fails.
Servicing by the calendar.
Machines get attention on a schedule, whether they need it or not.
Nobody can type with a spanner in their hand.
Every job starts with a plan.And leaves one behind.
Nothing to install, nothing to learn. It starts with whatever your people already do when something stops, and it gets sharper with every fix.
Someone says something.
A message, a voice note, a phone call, or a scan of the sticker on the machine. A few words is enough to open the job.

Nobody opened an app. Nobody started from zero.
Talk it through.The record writes itself.
Tickover listens to the conversation people are already having about the job, and turns it into the record: what broke, why, what fixed it and what was used. People talk like they always do. Tickover keeps the notes.
- Every word, as it is said.
- On a call, in a voice note, or standing next to it. The words appear while people talk, nothing to type.
- Any language, or a mix.
- English, Hindi, Marathi, or all three in one sentence. Names and part numbers it misheard get corrected from context.
- Who said what.
- Voices are told apart, so the first report and the fix land in the right place.
- The recording stays with the job.
- Anyone can play it back later. Tap a line and hear exactly how it was said.
What your team knows, readythe moment something stops.
No new app. People talk the way they already do, on WhatsApp, on a call, on Slack. Tickover keeps what matters as your site's memory, and turns it into a short plan the moment something stops.
- 1Start at the drive-side roller. Check the lock nut.
from Ravi - 2If the belt has drifted left, tension is low.
from Priya - 3Re-tension to the mark. Manual, page 14.
from Mohan - 4If the roller is worn, a spare is in bay 3.
from Sunil
- 1Start at the drive-side roller. Check the lock nut.
from Ravi - 2If the belt has drifted left, tension is low.
from Priya - 3Re-tension to the mark. Manual, page 14.
from Mohan - 4If the roller is worn, a spare is in bay 3.
from Sunil
It talks to each person in the language they use with it, keeps to shifts and quiet hours, and never asks two people the same question. Anything it wrote, you can correct. Your correction becomes a plain rule you can read, or switch off.
Everyone keeps their job.Nobody keeps the paperwork.
Shouts, calls or messages a supervisor, then waits.
Sends one message. Is never asked for more than a few words.
It earns its independence,one approval at a time.
Tickover starts by suggesting. It only does more on its own after you have approved the same kind of thing again and again, and you can pull it back with one tap.
Notices, and suggests.
Decide everything, as before.
It asks. It never promotes itself.
Safety is never assumed.
Whether a machine is locked off and safe to touch is always confirmed by a person, by name, every time.
Every action has a name on it.
What it saw, what it did, and who approved it, kept in a log nobody can rewrite.
It only chases what you choose.
Nobody gets a follow-up until someone taps Chase on that job. Everything else stays quietly on record.
Undo is one tap.
Or one plain sentence, from whichever app you happen to be in.
Maintenance thatmanages itself.
That is the destination: a system that plans, orders, schedules and closes on its own, so your team's whole day is the physical work. It gets there one earned step at a time, and you decide how far.
A day on autopilot
example day- 06:00
Pump 4 service moved into a quiet hour
- 09:12
Conveyor 2 job opened, Ravi sent with a plan
- 09:14

Locked off the conveyor
confirmed by a person
- 09:15–09:41

Fixed Conveyor 2
- 09:44
Record written and filed
- 11:30
Roller TR-220 reordered before stock ran out
- 18:00
Week's summary sent
Plans the work
Builds each person's day around what is due and what just broke.
Orders the parts
Sees what a job will need and has it waiting, within the spend you allow.
Schedules the services
Moves upkeep to when a machine actually needs it, in a quiet hour.
Closes the job
Writes it up, files it, and learns from it.
Example of a site partway there. Each ability is earned separately.
Safety is always confirmed by a person. Autopilot never changes that.
It works on top ofwhatever you use today.
Tickover sits on top of whatever you use today and writes clean records back into it. If that is a spreadsheet, a spreadsheet is fine. Nothing to migrate. Nobody to retrain.
What you already use
Sensors welcome. Never required.
If your machines already report data, it can open a job or pin down a start time. It never closes a job, and it never overrules a person.
Start where it hurts.
One site, one team, one phone number. Add the rest when the records speak for themselves.
The same idea, at any size.
The questionswe would ask too.
No. They message, call or scan a sticker with the phone they already have. The only screen is for whoever approves the records, and that runs in a browser.
Let the workdo the talking.
Start with one site, one team and the phone number everyone already calls. Tickover learns the rest as you work.