You fix it.Tickover runs the rest.
Tickover remembers every breakdown, every fix and every quirk of your equipment. When something stops, the right person arrives with a plan built from what worked last time, and the follow-ups, write-ups and planning take care of themselves. 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.
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.
It is not a discipline problem. 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.
Said anywhere. Remembered.Ready when 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
In their language.
It talks to each person in the language they talk to it in.
At a decent hour.
It knows shifts and quiet hours, and it does not call at night.
Asked once.
It never asks two people the same question.
Yours to correct.
Edit anything it wrote. 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.You hold the keys.
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.
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.
Keep what you have.Or start with nothing.
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 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.
- Nothing to install
- Works with what you have
- Your data stays yours