WEDNESDAY · 9:23 AM
Facilities & CMMS maintenance scheduling
The chiller in Building C just died during PM week.
A chiller down in Building C, a security-escorted access window, and preventive-maintenance week across twelve buildings. The portfolio didn't slip because your engineers are careless — it slipped because every ticket drags a chain of dependencies: a CFC ticket, a parts pickup, an escort window, a tenant SLA, a fire-inspection date that cannot move. Tools that ignore those chains hand them to a building engineer at 9:23 a.m. Crisphive carries the whole chain instead, so your people don't have to.
This demo replays a real kind of morning: one emergency lands, and every job finds a new slot without breaking a promise. See how it works ↓
Jobs moved: 0Tenant SLAs broken: 0Escalations: 0
Every field service day is a dependency graph. Most software pretends it isn't — and hands the graph to a dispatcher to solve in their head, under pressure, forty times a day. We think the schedule should carry that weight, not your people. That's the whole company.
— Why Crisphive exists
How it fits your day
When the day changes, the schedule keeps up.
Crisphive is the layer that carries your day's dependencies — every work order, tenant promise, and crew constraint — so when a chiller drops mid-PM-week, the plan repairs itself instead of landing on a building engineer at 9:23 a.m.
The day changes
The failure arrives however it comes in — a BAS alarm, a tenant ticket, a 9 a.m. phone call from Building C. The moment it lands, the day is in play.
The schedule recomputes
The schedule re-plans the portfolio against every hard rule — access windows, tenant SLAs, compliance dates, PM frequencies, parts and escort logistics, travel between sites — and returns a new plan plus a backup.
Your team is notified
You confirm once. Your engineers are re-routed, your tenant comms go out, your work orders update — nothing else needed from you.
You never rebuild the day by hand. The schedule recomputes around the disruption, keeps every promise it can, and shows you exactly what moved before anything goes out. Confirming the new plan takes one click.
The rules of your day
Hard rules, not suggestions.
A schedule that ignores these rules isn't scheduling — it's guessing, and a tenant pays for the guess. Every plan Crisphive hands you respects all of them. No exceptions, no "hope the tech makes it."
Site-access windows
Secure floors need escorts; retail floors need after-hours access. Access windows are hard rules per site — a tech who arrives when the door is locked is a wasted trip you still pay for.
Tenant SLA tiers
A critical-environment tenant and a comfort call carry different clocks. Every tenant's SLA tier is built into the schedule, so the chiller outranks the ceiling tile automatically — and everyone can see why.
Compliance dates that cannot move
Fire inspections, elevator certs, backflow tests — some dates are set by regulation. The engine moves everything else around them; they never absorb the slip.
Recurring PM schedules
PM week is a lattice of recurring work. Re-planning reflows it without breaking frequency compliance — the deferred filter route lands inside its tolerance, on the record.
Parts & escort insertion
The chiller repair needs a contactor and a security escort. Both go on the plan with real time attached — visible in the schedule, so nothing gets promised before the part and the escort are actually there.
Technician-to-site travel
Twelve buildings means real windshield time. Travel is counted per leg, so portfolio plans reflect the drive between sites, not wishful adjacency.
Getting started
Up and running in three steps.
Add your engineers and their certs
Sign up and add your engineers with their trades, certifications, and vehicles — CFC, electrical, plumbing, general maintenance. These are the things every plan has to respect.
Bring in your jobs and customers
Bring in the week's work orders and buildings — by import or right alongside the CMMS you already run. Confirmed tenant SLAs and compliance dates come with them.
Let the day run itself
From then on the schedule keeps itself. Emergencies slot in, affected jobs move, and your team and customers hear about it automatically — you just confirm.
⏱ Most teams are live within a week — no technical setup
Outcomes
What changes for you. What your customers feel.
You — running the business
One chiller stops eating your whole Wednesday.
- Your dispatcher gets the morning back. Triaging PM week around an emergency becomes one confirmation click instead of an hour of phone calls.
- SLAs stay kept without heroics. Priority tiers are enforced by the schedule, not negotiated in a hallway while a tenant waits.
- More wrench time, less windshield time. Travel is planned per leg, so engineers spend the day fixing buildings, not driving between wishful adjacencies.
- You always have the answer. When a tenant asks why their work slipped, the plan shows exactly what moved and why their SLA still held.
Your tenants
One chiller stops cascading through twelve buildings.
- Their window is kept. The escort shows up when the plan says, and the after-hours floor is served after hours.
- Their SLA survives the chaos. A critical-environment tenant stays ahead of a comfort call, every time the day recomputes.
- Compliance dates never absorb the slip — the fire inspection happens exactly when it was promised.
- Building C is cooling again by early afternoon — and no other building noticed anything happened.
Running more than one branch?
Set the rules once. They hold across every crew and every building. The access-window, PM, and tenant-SLA logic you set up for one portfolio carries to the next site, the next branch, the next acquisition — so growth stops multiplying dispatcher chaos. Adding buildings adds work orders, not another morning of hand-juggling nobody has time for.
Why it holds up
Built for the days that go sideways.
Re-planning is free
Re-planning is free and unlimited. Portfolio days are volatile by nature — a breakdown, a no-show, a fresh tenant ticket — so re-plan on every disruption without ever watching a bill.
Dependable by design
Schedules come from a deterministic engine, not guesswork — the same situation always produces the same plan. AI helps explain the plan in plain language; it never decides who goes where.
Always a plan B
Every urgent booking comes back with a recommended plan and a backup. If the customer declines the first window, the next-best option is already on the table.
What operators say
Portfolios that keep PM week intact
“An emergency chiller call used to blow up our whole PM week. Now it slots in and the preventive work still gets done. Our SLA numbers have never looked better.”
David Okafor
Facilities Director · Northgate Property Group
“Half my sites need security escorts, and our old system had no idea what that meant. Here the escort window is a hard rule — if the escort isn't booked, the job simply doesn't get planned there. Missed-access callbacks have basically disappeared.”
Sofia Marchetti
Building Engineering Manager · Harborview Commercial
“We folded in two acquired portfolios last year. That used to mean months of dispatcher pain while they learned every building's quirks. We set the rules once — fire-inspection dates, tenant SLAs, access windows — and the board holds. Audit season stopped being scary.”
Greg Lindqvist
Regional Operations Manager · Stonebridge FM Services
FAQ
Questions from the field
Will an emergency work order break our PM compliance?
How are tenant SLA tiers and access windows handled?
Does it work with our CMMS or CAFM?
Can it schedule across a multi-building portfolio?
Our facilities team doesn't write code — who sets this up?
How does pricing work across a building portfolio?
Your schedule should survive a bad morning.
Start free and drop in your worst Wednesday — a chiller down, PM week running, twelve buildings live — and watch the portfolio re-plan itself around every access window and SLA.
Questions? support@crisphive.com · Free to start — no credit card required
See how the scheduling engine worksPricing — pay per job scheduled