Fig. 1 Step 1
Where do problems come from?
Three places: a building system that detects a fault, an alarm email or text from equipment that already sends them, or a person on site who taps "report a problem" and picks the location and unit. All three become the same kind of work order.
Fig. 2 Step 2
What does the operator see?
A plain-language description of what's wrong and why it matters, at the top of the work order. The technical detail from the building system is one tap away, never in the way.
Fig. 3 Step 3
Who approves the work?
A person on your team, with one tap, from a phone. You can set a not-to-exceed amount so routine jobs approve themselves. Nothing is dispatched without that yes or that rule.
Fig. 4 Step 4
How does the contractor get the job?
The job goes straight to the contractor's phone. They see the site, the unit, the problem, and the not-to-exceed amount. They accept or decline, give an ETA, mark arrival, and close out with photos and a quote. No app, no account, no fees.
Fig. 5 Step 5
How do you know it's actually fixed?
If the building system that reported the problem can see it clear, FluxOps confirms the fix automatically. If not, someone on your team confirms with one tap. Either way, the work order isn't done until the fix is.
Fig. 6 Step 6
What happens to the record?
Every alert, approval, contractor update, photo, quote, and confirmation stays attached to that unit forever. Muted and declined problems are kept too, so the history is complete.