Work orders

A work order should end when the problem does.

Requests, alarms, and detected problems become one queue. Edviro drafts the order; a person approves it; the building data confirms the fix.

Use Edviro as your work-order system, or connect the one you already run.

Book a demoReplace or integrate your CMMS
  1. Staff text: Room 214 is freezing again. Kids are in coats. Can someone look at it?
  2. Edviro: On it. Room 214 is served by RTU-3 in Building B. Checking its history and this morning’s schedule.
  3. Edviro drafts work order WO-2418, "RTU-3 heating stage not firing — Room 214", priority High, trade HVAC. Evidence: Supply air 58°F vs 92°F expected; Third occurrence in 30 days; Zone scheduled occupied since 7:00.
  4. D. Park, Facilities Director, reviews and approves the work order at 9:47 AM.
  5. Edviro: Approved. Luis M. (HVAC) is on the way, ETA about 45 min. I’ll text you when the room is back to setpoint. Assigned to Luis M. (HVAC).
  6. Staff text: Any update? Still pretty cold in here.
  7. Edviro: Luis is at RTU-3 now replacing the igniter. You should feel heat in about 15 minutes; I’ll confirm once the room holds 70°F. Work order updated: On site, replacing igniter.
  8. Verified 11:20 · supply air 91°F, room 70°F. Edviro: Room 214 is back at 70°F and holding. Closing this out. Thanks for flagging it.

The lifecycle

Seven steps, one record.

Review is a step, not a setting: nothing is dispatched until a named person says so.

  1. IntakeA request, alarm, anomaly, or inspection finding opens the record.
  2. TriageSite, likely asset, related history, and proposed priority are drafted.
  3. ReviewA named person approves, edits, or rejects before anything is dispatched.Human approval
  4. DispatchThe technician gets location, asset history, and steps on their phone.
  5. Field updatePhotos, readings, parts, and notes come back from the site.
  6. ClosureLabor, parts, and cost land on the asset’s service history.
  7. VerifyBuilding data confirms the condition stopped, or the order reopens.

One queue

Requests and detections, side by side.

A “too hot” request and a stuck damper detected in the data are usually the same problem. Edviro matches them and proposes the priority.

  • Priority proposed from comfort, safety, cost, occupancy, and asset history
  • Duplicates of open work are surfaced instead of becoming a second ticket
  • Repeat failures on the same asset are flagged for a repair-or-replace review

Illustrative product views with fictional data.

Replace your work-order system, or connect Edviro to it.

Everything on this page is native to Edviro. Keep your CMMS and you still get the diagnosis, the routing, and the verification.

Replace or connectYour choice, changeable later
Edviro finds and diagnosesMeter data, alarms, and staff requests become a likely cause, a priority, and a drafted work order.
ReplaceEdviro is your work-order systemNative work orders, assets, inspections, and mobile field workflows. Your lists and open work are imported first.
ConnectKeep your work-order systemEdviro routes the work into it and reads the outcome back. Integration scope is confirmed system by system.
Same verified fix, same recordBuilding data confirms the fix either way; the history feeds preventive maintenance and the capital plan.
Compare with a traditional CMMS →See the full platform →How verification works →

For K‑12 and higher education

Running a school district?

The same lifecycle, written for maintenance and operations teams: campus intake, district-wide review, and verification across every site.

Questions

Work-order software FAQ

How do requests reach Edviro?

Through the app and by email today. Text-message intake is shown on the site as an illustrative scenario and is not yet live. Edviro also opens work itself from a detected problem, so the queue is not only what people remembered to report.

Does anything get dispatched without a person approving it?

No. Edviro drafts the work order with a proposed priority, trade, and assignee, and a named reviewer approves, edits, or rejects it. The same applies to emails, schedule changes, and setpoint changes: every side effect waits for approval.

How does Edviro verify that completed work fixed the problem?

Every work order is tied to the signal that created it or the asset it concerns. After closure, Edviro watches the relevant building and energy data against the learned baseline. If the condition returns, the order is reopened with the evidence attached.

Can Edviro work with the CMMS we already use?

Yes. Edviro can detect and diagnose the problem, route the resulting work into your existing CMMS, and read the outcome back for verification. Integration scope is confirmed system by system. Teams that would rather consolidate run work orders and assets in Edviro directly.

Can technicians use Edviro in the field?

Yes. Technicians receive assignments and priority changes on a phone or tablet, open the asset record and last service notes, follow an inspection checklist where one applies, attach photos and readings, and mark the work complete from the site.

See what Edviro finds in your buildings.

Connect your sites. Find the problems. Close the loop.

Book a demo