By Michael Kovalcik

18 Nov 2026 6 min read

Share this post

Sign up to our newsletter

Subscribe to receive the latest blog posts to your inbox every week.

By subscribing you agree to with our Privacy Policy.

A vendor closes the work order at 2:10 p.m. Five minutes later, the rooftop unit is still in alarm. The CMMS shows the job as complete, but the BMS continues to report the fault. The mismatch remains hidden until a store manager calls or the same alarm generates another ticket.

Work order governance means checking each work order against the equipment it was written for. KODE OS now does that check automatically, using real-time FDD signals and the status your CMMS reports back.

Answer Card (TL;DR)

Work order governance in KODE OS keeps every FDD-generated work order tied to the alarm and equipment that triggered it. Five Event Triage Rules compare the live alarm with the status recorded in your CMMS. Depending on the result, KODE OS can reopen a work order, link repeat alarms to the existing ticket, hold low-priority work until a site visit is warranted, or cancel a job that is no longer necessary.

Why do closed work orders keep coming back?

A CMMS records the reported status of a job: dispatched, in progress, or closed. On its own, it cannot confirm what is happening at the equipment. The BMS and FDD provide that equipment context but have no visibility into the work order. When the systems are not connected, someone has to reconcile them manually, often after a complaint.

That gap shows up in the same few ways at almost any portfolio that sends outside trades through a CMMS:

  • A vendor closes a work order while the alarm is still active. The invoice gets paid for a fault that wasn’t fixed, and someone is dispatched again.
  • The alarm returns a few days after closure and opens a new work order. One failing unit now has its history split across several tickets, and the vendor who closed the first one isn’t tied to the second.
  • An alarm clears during overnight setback and comes back at occupancy. Each cycle opens another ticket for the same fault.
  • A low-priority alarm sends a truck on its own. The visit isn’t worth its cost until something more urgent needs attention at the same site.
  • A transient alarm clears itself and the dispatch goes ahead anyway. You pay a trip charge, or lose an engineer’s time, for a condition that no longer exists.

In an occupied building there’s a second cost. The tenant, the employee or the store manager calls before the technician arrives.

What is work order governance in KODE OS?

KODE OS gives you one owner-controlled model of your portfolio, built on the systems you already have. In that model, each alarm is linked to the equipment it came from and to the work order raised for it. The work order’s status stays in sync with your CMMS, so KODE OS knows when a vendor marks a job dispatched, in progress or closed.

With both facts in one place, the comparison is simple. If the CMMS says closed and the equipment is still in alarm, the work isn’t finished. Work order governance in KODE OS is a set of five Event Triage Rules that act on that comparison, so nobody has to open two systems to check.

The rules are part of FDD and apply to events, the conditions your FDD routines detect on equipment in real time. They work with any CMMS that has an API for updating work orders, once it’s connected to KODE OS.

How do the five work order governance rules work?

Each rule watches for one kind of mismatch between an alarm and its work order.

  1. Bad closure. The CMMS reports the work order closed, and the alarm is still active once the grace period ends. KODE OS reopens the work order and tags it Bad Closure. The vendor gets the same ticket back, with its history intact.
  2. Recurrence reopen. The work order is closed and the alarm did clear, then the same alarm returns inside the recurrence window. KODE OS reopens the original work order, so there’s no second ticket and the unit’s history stays in one place.
  3. Self-resolving cancellation. The alarm goes inactive and stays that way for the hold time, before anyone has acted on the work order. KODE OS cancels it. If the alarm comes back first, the timer resets and the work order stays live.
  4. Hold and release. Work for low-priority routines is held instead of going out on its own. When a high-priority routine fires at the same building, KODE OS releases the held items as work orders. The low-priority work then goes out alongside a visit that’s already justified.
  5. Carry forward. The work order is still open and the same device alarms again, for example at the start of the next occupied period. KODE OS attaches the new alarm to the open work order instead of opening a new ticket.

The rules cover work orders your team creates from an event in KODE OS, as well as the ones KODE OS creates automatically.

Visual showing KODE OS dashboard Duct Static High with the details and the Work Order

How do you set up work order governance?

Event Triage Rules sit in FDD, under Settings and then Triage Rules. You choose which rules are on and set the timings that fit how your buildings and vendors work.

Event Triage Rules: settings and defaults
Rule What you set Default
Bad closure Grace period after the CMMS closes the work order 0 minutes
Recurrence reopen Recurrence window after closure 7 days
Self-resolving cancellation Hold time the alarm must stay inactive 24 hours
Hold and release Which priorities trigger the release P1 and P2
Carry forward Nothing to set On

The defaults are a starting point. A grace period of zero reopens the work order as soon as the CMMS closes it while the alarm remains active. A longer period gives equipment time to settle after a repair, which can be useful when an alarm takes time to clear after a unit restarts.

The recurrence window determines how long a closed work order remains linked to the fault it was intended to fix. The hold time controls how long a self-clearing alarm must remain inactive before the work order is canceled. A longer hold provides greater confidence that the alarm has cleared permanently.

Once set, the rules run in the background across the portfolio. They need a work order connector on the building, because without one there’s no CMMS status to compare against.

Visual showing the Event Triage Rules of KODE OS

What work order governance changes across retail, CRE, corporate and government

The rules are the same everywhere. Which ones matter most depends on how you dispatch.

  • Retail, facilities director with vendor-dispatched maintenance. Every visit carries a trip charge, so the rules that prevent a dispatch do the most: self-resolving cancellation, carry forward, and hold and release. Reopened work orders also show which closures didn’t hold.
  • Commercial real estate, chief engineer or property manager. When a comfort alarm outlasts its work order, the tenant notices first. A bad closure reopen puts the job back with the engineer or vendor without waiting for that call. Recurrence reopen keeps one unit’s history on one work order, which helps when the question becomes repair or replace.
  • Corporate, head of facilities across offices, branches or campuses. In-house engineers stop being sent to alarms that have already cleared. Repeat alarms stop adding tickets to the queue your FM provider reports against.
  • Government, facility manager. Each fault keeps one work order through reopenings and repeat alarms, which makes contractor performance easier to review.

What to track once the rules are on

Four counts tell you what the rules are doing each month: work orders reopened as bad closures, work orders reopened on recurrence, work orders canceled as self-resolved, and alarms carried forward onto open work orders. 

Canceled and carried-forward work orders represent tickets that might otherwise have been raised or dispatched. Multiply those counts by your average trip charge to estimate potential savings. Reopened work orders provide a measure of closure quality and are worth reviewing with each vendor.

See it on your own work orders

With Event Triage Rules on, your work orders update as the alarms do. Repeat alarms go to the same ticket, and your team is only dispatched when the job is still open.

The full settings reference is in the KODE OS documentation.

Work order governance FAQ
What is work order governance?

It is the practice of checking each work order against the live state of the equipment it was raised for, and correcting the work order when the two disagree. In KODE OS, Event Triage Rules do this automatically.

What happens when a vendor closes a work order and the alarm is still active?

Once the grace period ends, KODE OS reopens the same work order. The default grace period is zero minutes.

How does KODE OS stop duplicate work orders from repeat alarms?

Two rules handle it. Carry forward attaches a repeat alarm to a work order that is still open. Recurrence reopen brings back the original work order when the alarm returns within the recurrence window, which is seven days by default.

What happens to a work order when the alarm clears on its own?

If the alarm stays inactive for the hold time, 24 hours by default, and nobody has acted on the work order, KODE OS cancels it. If the alarm returns first, the timer resets.

Does this replace my CMMS?

No. Vendors and engineers keep working in your CMMS. KODE OS reads the work order status from it and keeps that work order in line with the alarm.

Which CMMS platforms does it work with?

The rules apply to any building in KODE OS that uses a work order connector. That includes common CMMS platforms such as ServiceChannel, IBM Maximo, Corrigo and Prism.

Can I change the timings or turn rules off?

Yes. You choose which rules are on and set the grace period, recurrence window and hold time in FDD settings.

Share this post

Michael Kovalcik

Product Management, KODE Labs

Sign up for our newsletter

News, insights and resources from the world of smart building management.

By clicking "Sign Up" you're confirming that you agree with our Terms and Conditions.

Resources

Related posts

View all
What Should You Check Before Connecting Existing Building Systems?
Building Operations

What Should You Check Before Connecting Existing Building Systems?

Hearing “Yes, we can integrate with your BMS” is a good starting point when you evaluate a building platform. However,…

Read more

Fix Tenant Comfort Before the Complaint: A Connected Approach to Workplace Experience
Building Operations

Fix Tenant Comfort Before the Complaint: A Connected Approach to Workplace Experience

Your tenant already knows there’s a problem. Why don’t you? A conference room slowly warms throughout the morning. CO₂ levels…

Read more

Building Cybersecurity Is a Procurement Problem, Not a Hiring One
Industry Thought Leadership

Building Cybersecurity Is a Procurement Problem, Not a Hiring One

Originally posted on Mann Report Ask your facility manager how many vendors currently have remote access to your building. Most…

Read more

Don’t let your buildings get left behind

Request a demo