Insights
Facility Management Software: What "Included" Means
Levaru Operations Team
Say two proposals are sitting on your desk for the same building. Both quote integrated facility management. Both carry a line that reads, more or less: CMMS platform included, no additional software cost.
One of them means your equipment gets tagged into an asset register, your engineer opens and tracks work orders in the system, and on the day the contract ends you can export the whole maintenance history to a spreadsheet.
The other means the provider owns some software, uses it internally to dispatch its own technicians, and will email you a PDF summary on the fifteenth of every month.
Both statements are accurate. Neither provider is lying. They describe completely different products on the same line of the same proposal, and nothing in either document tells you which one you are buying.
This is a buyer’s guide to testing that claim before you sign. We have an obvious stake in it — Levaru builds and operates its own CMMS and includes client access as part of facility management service — so the fair thing is to hand you the tests and invite you to run them on us as hard as on anyone else. Credibility here is not about who says “included” most confidently. It is about who puts the answer in the contract.
What does “CMMS included” actually mean?
There are four distinct things a provider can mean, and they form a ladder. Each rung is meaningfully more valuable than the one below it, and the single word “included” covers all four without distinguishing between them.
Level 1: The provider has software you never log into
The provider runs a dispatch system, a scheduling tool, or a genuine CMMS. It is real software and it genuinely improves their operation.
You never see it. What you get is a monthly report from that system, usually a PDF — better than nothing, and unverifiable, because you are reading a summary authored by the party being summarized. This is probably the most common meaning of “included” in the mid-market. It is not dishonest, just far less than what most owners hear.
Level 2: You get a read-only portal
You get a login. You can see open work orders, recent completions, maybe photos. You cannot create anything, your staff cannot submit requests, and tenant complaints still arrive by email to be retyped by somebody at the provider.
This is a real improvement, because it collapses the reporting lag from thirty days to zero. But it is a window, not a workspace. If the provider’s technicians are the only people entering data, the record reflects the work they chose to log, and you have no way to enter a fact they missed.
Level 3: You get real seats with real data
Your people have accounts. Your engineer submits a request and watches it move through triage, assignment, and closeout. Your property manager pulls up a rooftop unit and sees every visit against it going back to onboarding. Tenants report issues into the system instead of into somebody’s inbox.
This is the level most owners assume they are buying, and it is where software starts changing how the building is run rather than just how it is reported. The test is not whether a portal exists — it is whether the building’s daily work actually happens inside it.
Level 4: You get the data too, and you can leave with it
Everything at Level 3, plus an unambiguous answer to one question: when this relationship ends, what do you walk away with?
At Level 4 the asset register, work-order history, PM schedules, vendor records, and attached documentation are exportable in a standard format, on demand, without a negotiation. The record belongs to the building, not to the contract. Very few proposals address this, and it is the rung that determines the value of every rung below it.
The five questions that tell them apart
All four get described with the same vocabulary, so a capabilities deck cannot separate them. These five questions can, asked in writing before award:
- Do I get a login, and who else on my side gets one? Named seats by role. One shared account for the whole ownership entity is a different product.
- Can my staff and tenants submit and track requests? This is the line between Level 2 and Level 3. If requests get transcribed from email, the system is the provider’s.
- Can I see asset history for work I did not commission? A useful record includes the vendor you called directly last spring.
- Can I export my data, in what format, and how fast? A real answer names both. “We can generate reports for you” is a refusal in polite clothing.
- What happens to the data when the contract ends? Not a policy, not an assurance — a clause.
Ask every bidder, including the incumbent. These sort proposals faster than any feature comparison, because the vocabulary is shared and the commitments are not.
Why does data portability matter more than any feature?
Because it is the only one of the five you cannot fix later.
A missing feature is an annoyance you can work around or wait out. A maintenance history you cannot extract is a switching cost that compounds every month you stay, and it grows fastest exactly when the record becomes most valuable — after three or four years, once asset histories are deep enough to drive capital decisions.
Consider what that record is worth outside the service relationship. A refinancing lender’s engineer wants documented maintenance on major systems. An insurance carrier wants inspection and life-safety records. A buyer’s diligence team wants to know whether that chiller was maintained or merely survived. When a slip-and-fall claim lands, the defensible answer is a timestamped inspection record, not a recollection.
If all of that lives only inside a provider’s system, changing providers means restarting your building’s history at zero — so you end up evaluating not whether the incumbent is good, but whether they are bad enough to justify losing four years of records. That is lock-in, designed or not.
The remedy is not distrust, it is a clause. A provider who treats exported history as leverage is telling you something about the rest of the relationship — and that includes us, so ask us the same question and hold us to a written answer. Our position is that asset records, work-order history, vendor files, and parts data export as ordinary CSV, because a maintenance record only one company can read is not really your record.
What should the CMMS actually be doing for you?
“Included” is only worth something if the thing included is doing real work. If the category is new to you, what a CMMS is covers the fundamentals. Here is what the system should be carrying in a live engagement.
Work order lifecycle. Every request from every source enters as a ticket with a status, an assignee, a due date, and a closeout recording what was found and done. If work happens by phone call and the ticket is filled in afterward, you have a logging system, not a management system.
Preventive maintenance scheduling. PM tasks generate automatically from the asset register on frequency or runtime, not from memory or a wall calendar. This is the highest-value function in the system and the one most likely to be quietly absent. A real preventive maintenance program produces a completion record per task per asset — what an auditor, insurer, or buyer asks to see.
Asset register and per-asset history. Every significant piece of equipment carries an identity, a location, a make and model, and every work order performed against it. This turns maintenance from an expense line into a capital planning input, because you cannot decide whether to repair or replace a unit without knowing what it has already cost you.
Vendor and COI tracking. Which subcontractors work your building, what their certificates of insurance cover, and when those certificates expire. Lapsed COIs are among the most common and most expensive administrative failures in commercial property, and a system that watches dates prevents them.
Parts and inventory. What is on the shelf, what got consumed on which job, what needs reordering. The consumption record is what makes cost-per-asset honest.
Inspections and compliance rounds. Fire and life safety, elevator, backflow, and jurisdictional inspections, with findings captured as structured records that generate follow-up work — not a scanned form in a shared drive.
Reporting that survives scrutiny. The test is not whether reporting looks good in a monthly meeting, but whether it holds up when somebody adversarial reads it: a plaintiff’s attorney, an insurance adjuster, a diligence team. That needs timestamps, photos, named technicians, and an unbroken chain from request to closure that nobody reconstructed after the fact.
Why is software nobody uses worse than no software at all?
A CMMS is only as good as the completeness of what is in it. A half-populated asset register is not half as useful as a complete one — it is worse than a spreadsheet, because it produces confident answers that are wrong.
Picture a system holding forty of your building’s sixty pieces of equipment. Somebody runs annual spend by asset and gets an authoritative-looking number missing a third of the building. Somebody else checks whether the make-up air unit is on a PM schedule, finds no record, and concludes it does not need one — when it was never entered. The gaps do not announce themselves: absence of a record reads identically to absence of a problem.
The two models fail differently. A purchased license fails on adoption: you pay the subscription, your team is busy, nobody owns data entry, and eighteen months later the register is stale and the PM schedules are aspirational. An included CMMS fails on scope: it gets populated, but only with the work that provider performs, and everything else stays invisible.
The structural advantage of the included model is that the people doing the maintenance are the people entering the data, as a condition of the work being complete, so currency is a byproduct of operations rather than a discipline somebody enforces. In the field, QR asset tagging puts capture at the equipment instead of in the truck an hour later. Data recorded at the asset is accurate; data reconstructed from memory is fiction with a timestamp on it.
Either way, ask directly: who enters the data, when, and what happens if they do not? If the answer is vague, assume the register will be half-populated within a year.
Should you just buy your own CMMS instead?
Sometimes yes, and it is worth being straight about when.
Buying your own license and requiring the provider to work inside it is the better answer when you have several providers to see in one place, in-house staff who will own the system, or a wish to keep vendors genuinely interchangeable. That last point is the real argument: if the system of record is yours, changing FM firms is a procurement exercise rather than a data migration.
The costs are equally real and usually underestimated. Standalone products are typically sold per seat per month, tiered by module, with implementation billed separately. But license cost is rarely the number that matters. The dominant cost is labor — somebody has to build the register, tag equipment, define PM schedules, configure workflows, train users, then police adoption forever. That is a project, and the part that most commonly does not get done. Budget for it alongside your facility management cost per square foot planning.
For mid-market DC, Northern Virginia, and Maryland owners too small to justify an enterprise license and too large to run on email and spreadsheets, the middle path is usually best: take the provider’s included platform, and negotiate the export rights that make leaving cheap. You get the populated register without the implementation project, and you keep the optionality owning a license was supposed to buy. Our breakdown of commercial property management fees covers where software sits in a fee structure.
One honest limit on the included model: a platform provided as part of a service relationship is the system of record for work performed under that relationship. It is not a general-purpose license for administering unrelated vendors, and a provider who implies otherwise should be asked to be specific.
What belongs in the RFP to make “included” testable?
Vague requirements produce vague proposals. If your scope says “provider shall include CMMS access,” you will get five bids that all comply and none that are comparable. Our guide to writing a facility management RFP covers the document as a whole; these are the clauses specific to the software claim.
- Named seats. How many accounts, for which roles, and confirmation that there is no per-seat charge — or a statement of it.
- Submission rights. Owner staff and tenants can create and track requests directly, and you are told how tenants reach it.
- Register scope and timing. The register gets built during onboarding, with a definition of what counts as an asset, a completion date, and an answer on equipment the provider does not service.
- Data export. Asset, work-order, PM, vendor, and inspection records in a machine-readable format, on demand, at no charge, with a stated turnaround.
- Termination clause. A full export within a stated number of days of termination, for any reason, not conditioned on final invoice settlement.
- A live demonstration with real data. Not a slide deck — a screen share of a working account, with the bidder opening a specific asset and showing its full history. Ask them to export something while you watch.
That last item settles Levels 1 through 4 in fifteen minutes, because the difference between a system in daily use and a demo environment is obvious the moment somebody navigates it in front of you.
Then ask the same of the incumbent. If you already have a provider claiming an included CMMS, run the export test today rather than during a transition. Discovering the answer while you are trying to leave is the expensive version.
Frequently asked questions
What does “CMMS included” usually mean in a facility management proposal?
Most often it means the provider uses maintenance software internally and will send you reports from it — useful to them, only marginally useful to you. The phrase spans everything from a monthly PDF to named seats with export rights, so it tells you almost nothing until you ask whether you get a login, whether your staff can submit work, and whether you can export the data.
Do I actually get a login with an included CMMS?
Not automatically. Many providers describe reporting as portal access, and some portals are read-only views your staff cannot submit work through. Ask for named accounts by role, confirm whether there is a per-seat charge, and ask whether tenants can report issues directly into the system.
Who owns the maintenance data, me or the provider?
Ownership language varies and is often absent from standard agreements, so do not rely on the default. The practical question is not legal title but access: can you get a complete copy, in a usable format, whenever you ask, including after termination? Put that in the contract — an ownership clause with no export mechanism behind it is not worth much.
Can I get my data out if I switch facility management providers?
Only if you established that you could before you signed. Ask for export in a standard format such as CSV, covering the asset register, work-order history with attachments, PM schedules, vendor and COI records, and inspection results. A provider who can only produce PDF reports is offering you a picture of your data, not your data.
What happens to my asset history when the contract ends?
Whatever your agreement says, which in most standard contracts is nothing. That silence usually defaults to the provider keeping the system and you keeping whatever reports you happened to save. Negotiate a termination export clause with a format, a scope, and a deadline, and make it independent of final invoice disputes.
Should the CMMS be a separate line item on my invoice?
It does not have to be, but you should know which model you are in. A provider who uses the platform to deliver and document the work has no reason to bill it separately, because it is how the service gets performed. A separately billed software fee is not automatically unreasonable, but it should come with genuine seats, submission rights, and export, or you are paying a subscription for a monthly report.