Maintenance work order close-out verification
Problem
A leaking tap, a broken door closer or a faulty floodlight gets reported by phone, text or a corridor conversation and logged, if at all, as a line in the maintenance system or a ticket a contractor marks complete. Nobody checks whether the repair held. The same asset fails again three months later and looks like a fresh fault because nothing is coded against it: there is no record that this door, this pump or this light fitting has been fixed twice already this year. The facilities manager finds out a repair failed only when someone complains again, and by then the pattern that would justify replacing the asset instead of patching it again is buried across separate tickets nobody has cross-referenced.
Product idea
A close-out step that sits in front of whatever work-order system is already used. Every asset (a door, a pump, a light fitting, a room) gets a simple record. Closing a job against that asset requires a photo of the completed work and a named sign-off, not just a status change. If a new work order is opened against the same asset within a set window, the tool flags it as a repeat failure and routes it to the facilities manager instead of letting it close quietly as an unrelated ticket. It does not schedule contractors, handle invoicing or replace the work-order system itself: it is the verification and evidence layer sitting on top of whatever is already logging the request.
Who it is for
Maintenance supervisors closing jobs on the ground, facilities managers who need to see which assets keep failing, and estates coordinators. The facilities manager is the natural sponsor, since repeat failures are their budget problem.
Possible first version
A mobile app with an asset register imported from a spreadsheet, a close-out form requiring a photo and named sign-off per job, and repeat-failure flagging when the same asset gets a new job within a chosen window. A single dashboard lists open, closed and flagged-repeat jobs by asset. Version one does not integrate with an existing maintenance and work-order system: jobs are logged directly in the tool or via CSV import, and closed jobs export as a CSV or PDF rather than writing back into another system.
- Build classification
- Workflow application
- Rough effort
- 3-5 week first release
- Roles involved
- Maintenance supervisor, Facilities manager, Estates coordinator
- Relevant to
- Professional club, Venue & stadium operator, Collegiate athletics, Federation / governing body
- Systems in play
- Maintenance and work-order systems, Messaging apps, Building management systems
- Product framing
- Verify or inspect
Questions we get asked
What do we need on day one to make this work?
An asset register, even a rough one: a list of doors, pumps, light fittings and rooms, each with a name that stays consistent over time. If that list does not exist yet, the first weeks of the project are building it, not building software. The tool only earns its value once a fault is logged against a specific asset rather than a free-text description like 'the tap near reception', which will not match whatever gets typed in six months later when the same tap fails again.
Does this replace the maintenance system we already pay for?
No. Job logging, contractor assignment and cost tracking stay wherever they already live, whether that is a dedicated maintenance and work-order system or a phone and a messaging group. This adds one step in front of closure: proof the fix happened and a check for whether the same asset has failed before. If a site has no existing system at all, jobs can be logged directly here, but that is a fallback, not the intended shape.
Our engineers already text 'done' in the group chat. Why would they switch?
They will not switch unless closing a job here is faster than typing 'done', so the form is one photo and one tap, not a page of fields. Some jobs will still get closed by text regardless, and that is a realistic outcome rather than a failure of the tool. What changes is that the jobs that do go through it carry evidence, and the ones that do not are visibly missing it rather than invisibly missing it.
What happens if a flagged repeat failure just sits there?
Then it becomes a well-kept record of a problem nobody acted on, which is an honest risk rather than a hidden one. The flag needs an owner, usually the facilities manager, who decides whether a third failure on the same asset means a different repair, a replacement, or a change in who is doing the work. Without that owner, the tool documents the pattern without changing what happens to it.
Is this your workflow?
Tell us one sports workflow that still runs on paper, spreadsheets, WhatsApp or an outdated system. We will map it and show you what a simpler product looks like.
Tell us about itMore in Venue, facility & ground operations
- Facility booking conflict and capacity monitorA monitor that checks the shared booking calendar for overlapping bookings and capacity mismatches, and alerts a named coordinator before the clash reaches the day itself.
- Life-safety equipment inspection and evidence logA mobile tool that ties fire extinguishers, emergency lighting and fire doors to scheduled checks, so a safety certificate audit can be answered from records instead of a paper folder.
- Maintenance request intake and auto-routing queueA structured intake form that turns phone calls, texts and corridor mentions about broken things into an assigned, escalating queue, so nothing depends on someone remembering to mention it twice.