How to Evaluate a CMMS Proposal

A capability may look convincing in a comparison or demo, yet the commercial offer may describe a different edition, module, number of users or implementation service. Before deciding, reconcile the solution you evaluated with the one actually proposed.

The proposal should describe the same solution you evaluated.

The proposal should describe the same solution you evaluated

A proposal defines an offer: its software, services, quantities, responsibilities, assumptions, costs and terms. It does not prove a capability works. Use the evidence already obtained during evaluation to establish what happened, then check whether the offered scope would reproduce it under the material conditions of your operation. This is CMMS Buyer’s Guide editorial methodology, not a procurement rule imposed on every buyer.

Bring forward the requirements, claims, dependencies and open questions from CMMS Software Comparison. Bring forward what was stated, shown, tested, supported or left unresolved from CMMS Demo Evaluation. This page checks whether those findings match the offer; it does not repeat either evaluation.

Requirement ↓ Evidence ↓ Included Scope ↓ Dependency ↓ Responsibility ↓ Cost ↓ Commercial Term ↓ Gap

Record the difference first. Then decide whether it matters. A missing line or unclear assumption is a question to clarify, not automatically evidence of a vendor failure.

Why the quoted price is only one part of the comparison

A low quoted amount is difficult to interpret when the buyer does not know what is included, excluded, assumed or separately priced. An unpriced integration cannot be counted as free; an optional module cannot be assumed to be in the base offer. Do not infer the total cost of operating a system from one number on the first page of a proposal.

Alexandria Renew Enterprises’ CMMS solicitation used a cost form with separate lines for software licensing, third-party components, hosting, planning, configuration, data loading, potential integrations, testing, training, go-live and support; it also requested yearly and five-year totals and an explanation of assumptions. That is one public buyer’s specified format, not a universal template for private purchases. [1]

For a deeper look at pricing units, read How CMMS Pricing Works; for the boundary of a written offer, see what should be included in a CMMS quote.

Carry evidence forward before reading the offer as a decision

For each material requirement, write down the vendor claim and the evidence obtained. Keep the remaining uncertainty visible. A successful demonstration shows what happened in the demonstrated setup; the proposal must identify whether the modules, services and conditions needed to reproduce it are included. A proposal sentence about future capability does not replace a test, technical document or other appropriate proof.

Requirement → Vendor claim → Evidence obtained → Remaining uncertainty → Proposed scope → Commercial boundary → Gap / follow-up

This continuity is a way to keep a material requirement’s history intact as the buying process moves from demo to proposal. It is not a scoring system or a requirement to document every minor feature.

The five reconciliations

Use the five checks below for material requirements. They connect observed capability with included scope, delivery responsibility, cost and terms. Record what differs before making a judgment. Not every condition applies to every CMMS or proposal.

1. Capability reconciliation

What would we need in order to reproduce exactly what we just saw? Is everything required to reproduce it included in what we are being offered?

Check whether the evaluated capability is included under the same material conditions: edition or plan, module, user type and quantity, configuration, integration, add-on, custom development, implementation service, third-party product, and buyer-provided preparation or infrastructure where relevant. If the demo used sample data or a configured environment, ask which work makes that setup operational for your team.

For instance, if the mobile CMMS workflow was tested using a mobile application and preloaded records, reconcile the application entitlement and the work needed to configure that record availability. Record any untested conflict behavior as unresolved even if offline work appears in the offer.

2. Scope reconciliation

Identify what the offer actually includes: software or subscription, modules, implementation, configuration, integrations, data migration or conversion, training, support, go-live assistance, stabilization or post-launch service, and optional services where relevant. Separate an item being described from a commitment to deliver it.

The AlexRenew solicitation separated configuration, data loading, potential integrations, system testing, pre-go-live training, go-live, and ongoing support. It said integration choices would be made after selection. [1] Gwinnett County’s Maximo cloud migration solicitation separately described configuration changes, integration support, administrator training, hosting and ongoing support. [2] These are examples of how two public buyers specified project components; they do not establish what any particular private vendor includes.

When data or connected systems are material, use CMMS data migration and CMMS integrations to define the work being discussed.

3. Responsibility reconciliation

An included capability may still need decisions and work before it is operational. Record which tasks belong to the vendor, an implementation partner if one is involved, your team, and a third party where applicable. Name who provides source data, mapping decisions, test cases, access, devices, configuration sign-off and support handover when those tasks matter.

In Gwinnett County’s solicitation, the county owns the test plan and procedures while the provider contributes technical services and training. [2] AlexRenew instead assigned the offeror system configuration and data loading, including reviewing data gaps. [1] Those allocations are specific to those solicitations; use your own written scope to determine who will do each task.

See the CMMS implementation plan for sequencing responsibility and what to expect during CMMS implementation for the work that follows selection.

4. Cost reconciliation

Separate one-time, recurring and optional amounts. Depending on the offer, implementation, migration, integration, training and support may be bundled, separately priced or left for a later scope decision. Record unknown amounts as unknown. Identify quantities or triggers that may change cost—users, user types, sites, assets, modules, usage or volume, subscription tier, term, and renewal or escalation provisions—only where the vendor’s proposal uses them.

Tacoma Public Utilities’ CMMS solicitation requested distinct price lines for installation/configuration, data migration, system integration, customization and project management. [3] AlexRenew’s form requested yearly and five-year totals. [1] These public requests illustrate different disclosure structures; neither proves a common pricing model across vendors.

Use CMMS licensing models to interpret proposed quantities and CMMS renewal costs to check later-term terms. For the price boundary across different offers, see how to compare two CMMS proposals.

5. Term reconciliation

Surface material assumptions, exclusions, constraints, quantities, dependencies, renewal conditions, escalation provisions, implementation assumptions and acceptance conditions where relevant. Obtain written clarification for ambiguous terms. Do not treat a term as agreed merely because it appears in an example, sales presentation or earlier draft.

AlexRenew’s solicitation asks offerors to list and explain cost assumptions and specifies a particular process for renewal price adjustments. [1] Cleveland Public Library’s CMMS solicitation distinguishes required single sign-on from optional integrations and identifies post-go-live support as a project phase. [4] Both are buyer-specific examples of why scope and terms deserve a separate read.

Material contract language may need review by the appropriate legal or procurement professional. This guide does not interpret or advise on the legal effect of any term.

CMMS Proposal Reconciliation Sheet

Copy these eleven fields for each material requirement. Keep the observation and the proposed commercial boundary in separate fields. This sheet exposes differences and uncertainty before a decision; it is not a vendor scorecard. Blank or unclear fields should become questions, not implied commitments.

Requirement

What the operation needs

Evidence obtained

What was observed or documented, with test conditions

Proposed solution

The offering named in the proposal

Included scope

Modules, quantities and services explicitly included

Dependency

What must be in place to deliver the capability

Vendor responsibility

Work the vendor commits to perform

Buyer responsibility

Work the buyer must perform

One-time cost

Quoted one-time amount or “not established”

Recurring cost

Quoted recurring amount or “not established”

Commercial boundary

Assumptions, exclusions, quantities and terms that bound the offer

Gap / follow-up

Difference or remaining uncertainty and how to resolve it

Worked example: an offline work order

The following record is wholly illustrative. It does not describe a real vendor, an actual purchase, a standard number of mobile licenses or a universal pricing practice. It carries the offline scenario from the demo through the commercial offer without treating the demo as proof of the commercial scope.

Requirement

Technicians must complete work without connectivity

Evidence obtained

Offline workflow tested; synchronization observed in the tested setup

Proposed solution

Mobile technician capability

Included scope

75 mobile users in this illustrative offer

Dependency

Required records must be available on the device before connectivity is lost

Vendor responsibility

Configure mobile workflows

Buyer responsibility

Provide devices and provision users

One-time cost

Included in the illustrative implementation package

Recurring cost

Included for 75 licensed mobile users in this example

Commercial boundary

Additional mobile users would be separately priced in this example

Gap / follow-up

Conflict handling remains unresolved; request a controlled vendor sandbox test

Observation: labor and a photo synchronized after reconnecting in the defined test. Interpretation: the offer may support the required offline workflow if the included setup and device preparation reproduce those conditions. Conflict handling remains open until a suitable test or other evidence resolves it.

What a proposal cannot settle

Language in an offer does not turn an untested claim into observed performance. Depending on the unresolved question, ask for written clarification, a revised proposal, an implementation scope, technical documentation, a security review, a sample migration, a proof of concept, a comparable customer reference or contract review. Choose the method that fits the claim; no buyer needs every method for every proposal.

Keep the evidence status and the commercial status separate: a capability might be tested but excluded from the offer, or included in the offer while its behavior remains untested. Both situations need attention for different reasons.

What to do with gaps

• Write the precise difference between the evaluated solution and the offer before interpreting it.
• Ask for a written clarification or revised scope when an inclusion, quantity, responsibility or price boundary is unclear.
• Assign a suitable evidence method and an owner to any material technical or operational uncertainty.
• Check the clarified scope against the proposal version and the comparison record; keep unanswered items unresolved.
• Decide whether each remaining difference is acceptable for the operation, with appropriate procurement or legal review where needed.

Missing information is a reconciliation issue first. An unresolved item is neither an automatic rejection nor an implicit yes. Its importance depends on the requirement, the available evidence and the buyer’s ability to accept or resolve the uncertainty.

From proposal reconciliation to the final decision

Bring the reconciled record back to the decision: what your operation required, what was established, what is included, what each party must do, what it costs under the stated terms, and what remains open. The proposal should describe the same solution you evaluated. If it does not, make the difference explicit and resolve or consciously accept it before committing.

Review what the demo actually proved →

Use your CMMS Requirements Tool to keep your own needs and open decisions together as you prepare the final review.

Next: How to Make the Final CMMS Decision →