Maintenance · Executable work record
A named job, a named site, a named assignee, an SLA clock, the gates it has to clear, and the evidence it has captured so far. All on one record.
The timeline is the page. Scroll the record.
09:14 UTC
originating ticket TK-2026-4521
Site · Asset
Block A Rooftop · Plant Room 2
Chiller Unit 4 · AST-2026-0047
Scheduled 2026-04-25 09:00-13:00 UTC
Assignees
Mike J. · HVAC · In-house Resolution target
At risk2h 18m remaining
Gates on the card
Gate enforcement
Three gate pills on the card. The system refuses the transition to In progress until the upstream pieces are in place. The error message names the gate so the operator knows who to chase.
Choreography
Permit choreography on permit-to-work. Quotation choreography on service-catalog. What happens on the WO is the enforcement line.
Activity feed
Activity timeline
On WR-2026-0847
Every motion on a work order writes an entry. Status change, assignment change, attachment added, comment posted, part issued, permit approved, form submitted. Over twenty distinct event types, each carrying actor, timestamp, and a short content line. System events are tagged as system, not as a person. A human is never impersonated by the platform.
Work order created · SLA response deadline set to 09:29
Assignment set · Mike J. (In-house) + Meridian HVAC (crew of 3)
Mike J. status · Accepted Accepted the job · first-response captured
Permit PTW-2026-0412 approved · gate cleared
Mike J. status · In progress permit verified, quotation approved
Mike J. attachment · 3 photos rooftop-approach.jpg, coil-inspection.jpg, pressure-gauge.jpg
Priya S. comment Mentioned Mike J. · 2 reactions (thumbs-up, check)
SLA warning · 75% of resolution window consumed
Mike J. materials issued 2 × refrigerant filter, 1 × belt set · from Parts Room 2
Mike J. form submitted Chiller servicing SOP v3 · 12 of 12 checklist steps complete
Assignment + routing
Assignment
Mixed assignment is the default. Team-only runs through a different notification path than mixed or user-only, so member preferences are honoured. The author of a comment is always excluded from their own notification.
Assignees on WR-2026-0847
Mike J.SLA
Response + resolution
Deadlines are calculated at creation based on priority. First-response is captured the moment the status leaves open. Breach is a flag, not a guess. Reopen counter increments every time a completed or closed job is reopened.
Response · 15 min
MetActual 09:18
4 min after open
Resolution · 4 hrs
At riskElapsed 3h 34m
remaining 26m
Business hours
07:00-19:00 UTC · Mon-Sat
Reopen counter
Reopened once
2026-04-22 by David M. · customer reported recurrence
Recurrence
Recurrence
Daily, weekly, monthly, and yearly. When the current occurrence is marked complete, closed, or skipped, the next is generated automatically. Authoring lives on preventive.
Previous
ClosedWR-2026-0412
Chiller 4 quarterly
Closed 2026-04-22 16:14 by Priya S.
Next
AutoWR-2026-0847
Chiller 4 quarterly
Scheduled 2026-04-25 09:00 UTC · materials reserved
Integration surface
Integration surface
Every creation, update, status change, and completion publishes a webhook. Four event types, full structured payload. External systems subscribe. The platform delivers without scraping the interface.
BI dashboard sync
events: created, status.changed, completed
Last delivery 2026-04-25 14:23
Requester notification service
events: status.changed · filter: priority=High
Last delivery 2026-04-25 12:41
Payload excerpt
workorder.status.changed · 2026-04-25 14:05:12 UTCdisplay number: WR-2026-0847status: In progress · previous: Acceptedlinked asset: AST-2026-0047assignees: Mike J. + Meridian HVAC End of trail
The work order is the record. Every move has a reason, an actor, and a timestamp.
See the platform
30-minute demo. Your work types, your priorities, your SLA template. Real motion on a real record.