Staff requests and fault reports
Around 3 hours a week of 'did anyone sort the van?' gone. Faults and kit requests go in by text and get chased until they're fixed.
Hours back
3
hours a week back, typically
How it runs
What we build, step by step.
This is the usual shape. Yours gets built around how your team actually does the job.
- 01
Requests by text or chat
Staff send a message, voice note or photo to one number: what's wrong, where it is and how urgent.
- 02
Logged and sorted
Each request becomes a line in one list, tagged as vehicle, tools and kit, premises or IT, with the photo attached.
- 03
Sent to whoever owns it
Van faults go to whoever looks after the vehicles, kit orders to the office, building problems to the landlord or your maintenance contractor.
- 04
Safety problems raised at once
Anything that stops a vehicle or tool being used safely goes straight to a manager, not into the queue.
- 05
Chased until it's closed
Open requests get a nudge after a set time, and whoever raised it hears when it's done.
- 06
Servicing on the same calendar
Vehicle and equipment service dates sit alongside the faults, so a knocking engine and a service due next week get booked in together.
Shown with software we see a lot. If your team uses something else, we build it into that instead.
Built for your business
Same job, different business. We build yours.
Two firms in the same trade rarely run a job the same way. Different software, different steps, different people signing off. We build it for your business, around how your team actually does the job.
Your steps
Built around the order your team already works in, odd exceptions included.
Your software
Runs inside the tools you already pay for, set up the way you use them.
Your rules
Your wording, your limits, your sign-offs. Nothing generic goes out in your name.
You sign off
Your team keeps the final say.
A manager decides whether a vehicle or tool comes out of use, and approves every repair or purchase. The system logs, passes on and chases.
What it's worth
What those hours add up to.
3 hours a week, over 46 working weeks, is 138 hours a year. At $50 an hour, that’s
$6,900
back in the business, every year.
Typical, not promised.
Before and after
The job, before and after.
How it runs today
A tech mentions the van's making a noise in the group chat. Someone asks for new boots in passing. The office printer has been broken for a week. Requests land with whoever's nearest, nobody owns them, and the van breaks down on the way to a job.
What we build
- Requests by text or chat
- Logged and sorted
- Sent to whoever owns it
- Safety problems raised at once
- Chased until it's closed
- Servicing on the same calendar
A month in
Every fault has an owner and a date, small van problems get fixed before they turn into breakdowns, and staff stop asking for the same thing three times.
FAQ
Does this replace our fleet or maintenance software?
No. If you already book services in a fleet system, fault reports can be passed into it. Most small businesses don't have one, and a shared list with reminders does the job.
Can it handle building and landlord problems too?
Yes. Building and premises problems go to whoever deals with the landlord or the building contractor, and get chased the same way as van faults.
More for operations
See them all →Next step
Bring this one to a free live build.
Thirty minutes on staff requests and fault reports. We build its elf with you, live, and you keep it.