Facilities maintenance app: A field-demo checklist
Your facilities maintenance app needs to help a technician find equipment, report a fault and leave a record the next person can use. If the manager still chases photos by text or copies notes into a spreadsheet, the field crew is doing the same work twice.
If your team covers several buildings, put a real repair through the demo. Use a rooftop air handler in one office building and a similar unit at another site. Follow the issue from the first report through the office’s final view.
What a facilities maintenance app needs to do in the field
Find the right asset and its history
At a hospital, two buildings may both have an “AHU-4.” A technician needs to narrow the record by site, building, floor or room, then see the asset ID and latest service notes. If those details live only in a shared drive, someone may use the wrong instructions.
Have the technician open an air handler from a job, then find it again without that job. Add a similarly named unit at another site. If the vendor offers QR or barcode scanning, use a real label, including one that’s worn or hard to light. The scan needs to open the right record; an unreadable label needs a fallback. Some apps do not offer scanning at all.
Capture an issue where it happens
In a hotel, “water on floor” will not tell the office which fan-coil unit is leaking. The report needs the location, asset, worker’s observation and a photo if the app supports one. A clear priority or safety flag helps the office triage without another phone call.
Keep the form short. If a worker cannot answer a required question at the scene, they may guess. Let the manager add accounting and scheduling details later. Before sending anyone out, see if the office can spot two reports about the same unit.
Assign work and make handoffs visible
At a manufacturing plant, a failed dock-door motor may need an electrician, a part and access from the loading team. The assigned worker needs the fault, location and next step. The manager needs the owner and current status, especially if the job is blocked.
Change the assignee mid-job and watch both views. The first technician’s note should stay with the job, so the next person knows which part is still needed. “In progress” alone tells them very little.
Record inspections without losing the story
If a fire-door closer sticks, the inspector needs a way to record where it happened and who will fix it. Test how the app handles that failed check. Can the team create a repair task, or at least find the exception from the inspection? Checklists and automatic follow-up tasks are vendor-specific.
For routine preventive maintenance, test a planned visit as well as a surprise fault. Have the technician leave a dated note about the work. The manager needs to tell a finished job from a visit that ended with an unresolved defect.
Share the same update with the office
A facilities management app should save the office from calling for a recap. Once a worker adds an observation, opens a follow-up and finishes their portion, have the manager open the job on desktop. The site, owner, timestamps, attachments and next action should all make sense there.
If the phone shows “done” but the office sees an old status, find out why. A basement plant room makes a good weak-signal test: add a note there, then reconnect upstairs. Watch what happens to that note. Offline access and sync rules vary by vendor and plan, so use the crew’s own devices.
Field-demo checklist: one repair, one inspection, two viewpoints
Bring a technician and a manager to the same demo. Pick an asset at each of two sites, plus one repair and one failed inspection check. Time the tasks if speed matters to your crew. Then read the record together: could someone use it to finish the job?
| Test in order | Technician does this on a phone | Manager checks this from the office |
|---|---|---|
| 1. Locate equipment | Find an asset by site and location; try its label if scanning is offered | Confirm the asset ID and site match the physical unit |
| 2. Report a fault | Add a short observation and evidence; submit the issue | See the new issue on the right asset, with enough detail to triage it |
| 3. Assign and hand off | Open the assigned job, add a finding, mark a blocker, then accept a reassignment | See the owner, status and earlier notes without asking for a recap |
| 4. Log an inspection exception | Record a failed check and the action needed | Find the exception and its follow-up without hunting through unrelated notes |
| 5. Finish the work | Record what was done and flag any remaining problem | Distinguish a resolved repair from an open follow-up in the asset history |
| 6. Repeat with poor reception | Attempt a note or photo in a weak-signal area, then reconnect | See whether edits arrive once, in order, with a clear indication of any sync failure |
What makes a mobile record trustworthy?
The work order needs enough detail to help someone later. A study of historical HVAC work orders found that missing key fields affected the ability to identify equipment for further monitoring:
“We demonstrate how incomplete data collection impacts a facility’s ability to use historical MWO data.” – PHM Society European Conference
A clear link to the physical asset. Give each pump an identifier and location. If one moves between facilities storerooms, the team needs its old history under the same record.
A visible trail of work. Keep the fault, assigned task, repair and remaining action together. If a restaurant’s walk-in cooler fails again, the next technician needs to know which part was changed and whether the original fault was resolved. Look at edits and closures too: can you tell who logged the work and who approved it?
Access that fits the job. A contractor may need to update an assigned repair without browsing every building’s equipment. A manager needs a view across locations. Try both roles. Can they do their jobs without changing records they do not own?
One view across locations. Ask the manager to pull up open issues by site, overdue work and repeated faults on one asset. Field updates need to show up there without Friday spreadsheet cleanup. For budgeting, see if the team can connect work history to equipment costs without typing it all again.
If you track tools, vehicles, PPE or furniture alongside building equipment, it helps to keep them together. A team handling mostly tenant requests and property repairs should put the work-request flow through the tougher test.
How an AI-enabled app can help
An AI-enabled facilities maintenance app can also make it easier to get started: import existing spreadsheets or turn checklist documents into digital records that fit your workflows, instead of rebuilding everything by hand. It can cut the admin around a repair, but only if its suggestions stay connected to the right asset and job. Ask the vendor to show how its assistant helps a technician find relevant records or turn field notes into a usable update, then check what the manager sees. Treat generated text as a draft: the technician should confirm the equipment, work done and next action before it becomes part of the record.
For teams managing equipment across sites, AI assistance is most useful when it reduces repeat entry without hiding the source of an update. In the demo, try a vague note and a similarly named asset at another building. Can the worker correct a wrong suggestion, and can the office see who made the final change? Bulbthings includes an AI copilot to simplify your workflows and analytics, so test it with your own maintenance workflow rather than relying on a scripted example.
Roll out the app without making more admin work
Start with one site and a small mix of assets: perhaps a school’s boilers, air handlers and portable ladders. Give each item a clean ID and location. Agree on the statuses the crew will use, who can close work and who fixes duplicate records.
Let technicians use the phone for their daily work: finding an asset, opening a job and leaving notes for the next shift. Managers can route the job and read its history on desktop. If either group still needs a spreadsheet to follow the work, simplify the setup before adding another site.
During the pilot, open a handful of completed jobs with someone who was not there. Ask them which asset got serviced, what changed and whether anyone owes a follow-up. If technicians leave fields blank or enter placeholders, shorten the form or move those fields to the manager’s side.
Before a wider rollout, use your devices and plan to test site permissions, attachments, inspections, scanning, offline behavior and sync conflicts. A phone login alone tells you none of that.
Choose the app that survives a real handoff
A good facility management mobile app lets the next person pick up the job without a call. They can see the equipment, field note and owner; the office sees the same information. Try a messy repair across two buildings before rolling it out to the rest.
Bulbthings is more than a facilities maintenance app: it is an all-in-one asset management platform for buildings, premises, furniture, equipment, tools, vehicles and other physical assets. Supervisors, technicians, logistics managers and finance managers can collaborate around shared inventory, maintenance records and financial information through mobile and desktop access, while an AI copilot helps to execute workflows and analyse resulting data. A team that handles only property work orders should still put its repair and inspection process through the demo. If your teams work from spreadsheets across sites, test the shared record with two real assets.
Start your 14-day free Bulbthings trial and see whether it saves the back-and-forth 🚀