Property Maintenance Software Demo Script: What to Test Before You Buy
By Alex Jordan on June 12, 2026
The average property management team sits through 4–7 software demos before making a decision — and 68% of buyers later discover that a feature they assumed was included either doesn't exist or requires an "enterprise tier" upgrade. The problem isn't bad software. It's bad demos. Vendors show you their product's best-case scenarios, not your actual workflows. They demonstrate work order creation on a clean test account, not with your 3,000-unit portfolio's data volume. And they rarely let you touch the mobile app yourself. OxMaint's demo process is designed differently — we run your actual workflows on your actual data volume, let your team drive the mobile app themselves, and provide a sandbox account for independent testing. Use the script below to test any vendor — and hold them accountable for what they claim.
PROPERTY MAINTENANCE · CMMS DEMO · 2026
Property Maintenance Software Demo Script: 32 Things to Test Before You Buy
Work order creation, PM scheduling, mobile app offline mode, reporting, API integration, data import, user roles, approval workflows — a complete demo script that separates real capability from sales fluff.
68%Of buyers discover post-purchase that a key feature requires an upgrade tier
4–7Demos attended before purchase — but most test the wrong things
12 minAverage time vendors spend on "your workflows" vs. their pre-built demo script
32Specific test scenarios — use this checklist on any vendor
Phase 1: Work Order Creation & Management (8 Tests)
Work orders are the core transaction of any CMMS. If creation is slow, if required fields are missing, or if the mobile experience is clunky, your team will resist adoption. Test these 8 scenarios in every demo — and insist on using your own property names, unit numbers, and asset types, not the vendor's sample data. OxMaint's demo sandbox lets you create work orders on your actual property structure before you commit.
1. Create a work order in under 60 seconds
Speed Test
Start a timer. From login to work order creation — how many clicks? How many required fields? Can you duplicate a previous work order? Can you create from a template?
2. Attach photos to a work order
Documentation
Take a photo on your phone during the demo. Can you attach it to the work order immediately? Does the photo resize automatically? Is there a storage limit? Who owns the photo data?
3. Assign a work order to a specific technician
Routing
Can you see technician availability? Can you assign based on skills (HVAC vs. plumbing vs. electrical)? Does the technician receive an instant notification? Can they accept or reject?
4. Set priority levels (emergency/urgent/routine)
Triage
Are priorities configurable (custom labels and colors)? Do high-priority work orders appear differently in dashboards? Can you set SLA response times per priority?
5. Add parts to a work order from inventory
Parts Tracking
Can you select parts from a dropdown? Does inventory quantity auto-decrement? What happens if part is out of stock — can you create a purchase order from the work order?
6. Add labor time and complete the work order
Completion
Can technicians log time in minutes/hours? Can they add completion notes? Can they capture tenant signature? Does completion auto-notify the requester? Can they add "before/after" photos?
7. Reopen a completed work order
Revision
If a repair fails or a tenant reports the issue again, can you reopen the work order? Does it retain history? Is there a revision count? Can you link the new work order to the original?
8. Search for a work order from 6 months ago
History
Use a real example from your current system (e.g., "water heater repair at unit 203 last November"). How many clicks to find it? Does the search work by unit number, asset, date range, and technician?
Preventive maintenance is where CMMS ROI comes from — but only if scheduling is automatic and flexible. Test PM setup on your actual assets (HVAC filter changes, pool chemical checks, elevator inspections) — not on the vendor's sample "oil change" task. OxMaint's PM module supports both calendar-based and meter-based triggers, with automatic work order generation at the correct frequency per asset.
Create a preventive maintenance schedule for a real asset in your portfolio — not a demo example.
9. Calendar-based PM (e.g., every 30 days)
TestSet up filter change every 30 days
Does it generate work orders automatically on day 30? What if day 30 falls on a weekend?
10. Meter-based PM (e.g., every 500 hours)
TestPool pump service every 1,000 hours
How does the meter reading get updated? Manual entry? API from BMS? Can you set a trigger threshold with lead time?
11. Seasonal PM (e.g., spring/fall HVAC)
TestBoiler tune-up before heating season
Can you set PM by date range (Oct 1–Nov 15) rather than fixed interval? Does it repeat annually?
Can you attach a detailed checklist to the PM work order? Are checklist items trackable (pass/fail/NA)?
13. Automatic work order generation
TestCreate PM today → due date 7 days from now
Does the work order appear automatically on the due date? At what time? Can you set a lead time for planning?
14. Missed PM alerting
TestWhat happens when a PM is past due?
Does the system alert supervisors automatically? Can you set escalation rules (e.g., alert manager after 7 days overdue)?
Phase 3: Mobile App Functionality (4 Tests)
If your technicians won't use the mobile app, your CMMS implementation will fail. Test the mobile experience on your own phones — not on the vendor's demo device. Insist on offline mode testing, photo capture, and signature capture. OxMaint's mobile app works offline, syncs automatically when connectivity returns, and includes barcode scanning for asset lookup — no hidden "premium mobile" tier.
15
Offline mode
✓ Put phone in airplane mode
✓ Open work order list — does it load cached data?
✓ Complete a work order offline
✓ Add photo and signature offline
✓ Restore connectivity — does it sync automatically?
If offline fails, eliminate vendor
16
Photo capture & storage
✓ Take a photo from within the app
✓ Annotate or mark up the photo
✓ Add multiple photos to one work order
✓ View photos on desktop version
Cloud storage? Photo limits?
17
Barcode/QR scanning
✓ Scan an asset barcode (use a real asset)
✓ Does it pull up asset history?
✓ Can you create a work order from scan?
✓ Can you complete PM from scan?
Essential for unit turns
18
Signature capture
✓ Capture tenant signature on completion
✓ Signature stored with timestamp
✓ Exportable with work order PDF
✓ Legal admissibility?
Liability protection
Phase 4: Reporting & Dashboards (5 Tests)
If you can't report on it, you can't manage it. Test reporting on your actual data volume — not on a sample database with 50 work orders. Generate the reports you currently run manually (monthly maintenance summary, cost per unit, turn cycle time, PM compliance rate) and time how long each takes. OxMaint's reporting engine generates any report in under 60 seconds, with scheduled delivery to executive inboxes and export to Excel, PDF, and CSV.
Reporting Tests — 5 Essential Reports to Generate in the Demo
19.
Monthly maintenance summary by property
Work order count, completion rate, average response time, average resolution time, cost summary per property. Can you filter by date range? Compare month-over-month?
20.
Cost per unit report (last 12 months)
Total maintenance cost ÷ total units. Can you break down by category (labor, parts, contractor)? Can you compare cost per unit across properties?
21.
Unit turn cycle time report
Average days from notice-to-vacate to ready-to-lease. Can you filter by unit type, property, season? Can you identify slowest and fastest turns?
22.
PM compliance report
Percentage of scheduled PM tasks completed on time (by asset category, property, month). Can you drill down into missed tasks? Can you export to Excel?
23.
Technician productivity report
Work orders completed per technician, average completion time, overtime hours, cost per work order by technician. Can you compare across technicians?
Phase 5: Integrations & Data (5 Tests)
Your CMMS does not operate in isolation — it must integrate with your PMS, accounting software, and building systems. Test integration claims with specific scenarios, not general promises. OxMaint's open API includes pre-built connectors for Yardi, RealPage, Entrata, ResMan, AppFolio, SAP, QuickBooks, and Xero — with unlimited API calls and no integration surcharge.
Test Scenario
What to Ask
Red Flag
24. PMS integration
"Can a tenant maintenance request from our PMS create a work order automatically?"
"Export CSV and import" — not real integration
25. Accounting integration
"Can work order costs post to QuickBooks/Xero automatically?"
"Manual export" or "separate license required"
26. API access
"Do we get API access in the base plan? Any call limits?"
"Enterprise tier only" or per-call pricing
27. Data import from current system
"Can you import our existing asset list, work order history, and PM schedules?"
"Manual entry" or separate migration fee
28. Data export (when you leave)
"Can we export all our data in standard format? Any fees?"
Export fee or no structured export
Phase 6: User Roles, Workflows & Approvals (4 Tests)
Your CMMS must support different user types — property managers who need dashboards, technicians who need mobile access, regional directors who need portfolio views, and vendors who need limited portals. Test role configuration with your actual job titles, not generic "admin/user" samples. OxMaint's role-based access control includes unlimited custom roles, configurable permissions per module, and vendor portal access — all in the base plan.
29
Create a custom role
✓ "Property Manager — can see own properties only"
✓ "Regional Director — can see all properties, cannot create work orders"
✓ "Vendor — can see only assigned work orders"
✓ "Technician — mobile-only, no desktop access"
Role testing takes 5 minutes
30
Approval workflows
✓ Create a purchase order for parts >$500
✓ Does it route to property manager for approval?
✓ Can you set approval thresholds per role?
✓ Can approvers review and approve from mobile?
Essential for cost control
31
Notification rules
✓ Can you set different notifications per work order type?
✓ Emergency → SMS + email + push
✓ Routine → email only, daily digest
✓ Can users customize their own notification preferences?
Alert fatigue prevention
32
SLA tracking & escalation
✓ Set SLA: P1 emergency → 2-hour resolution
✓ Does the system track time-to-acknowledge and time-to-resolve?
✓ Does it escalate automatically when SLA breached?
✓ Can you generate SLA compliance reports?
Tenant satisfaction
The Demo Scorecard — 32 Tests, 3 Pass/Fail Thresholds
Use this scorecard during every vendor demo. Score each test as Pass, Partial, or Fail. Any vendor with 5+ Fails or 10+ Partials should be eliminated from consideration. OxMaint passes all 32 tests in the base plan — no enterprise tier required, no hidden upgrade, no "we'll build that for you in phase 2."
Demo Scorecard Summary — Track Results per Vendor
Pass
Works as described, no workaround required, included in base plan
Partial
Works but requires workaround, enterprise tier, or custom development
Fail
Does not work, vendor cannot demonstrate, or not available at any tier
Elimination thresholds: 5+ Fails = eliminate immediately. 10+ Partials = proceed with caution, require written commitment before signing.
"
We sat through 6 demos before we started using this script. The first vendor we tested with the script got 11 Partials and 3 Fails — all features they had promised in the sales pitch but couldn't demonstrate. The second vendor got 5 Fails and we eliminated them. The third passed 29 of 32 tests and we signed. Using a structured demo script saved us from making a $24,000 mistake on software that wouldn't have worked for our portfolio.
Director of Operations — Multifamily portfolio, 2,200 units, US Southwest
Frequently Asked Questions
How long should a proper software demo take?
A serious demo for enterprise property maintenance software should take 90–120 minutes. The first 30 minutes: vendor presentation (watch for fluff). The next 60 minutes: you run the 32 tests from this script on your actual workflows. The final 30 minutes: Q&A and pricing discussion. Any vendor who rushes through your test scenarios or insists on using their sample data is hiding limitations. OxMaint's demos are 90 minutes — 60 minutes of your tests, 30 minutes of Q&A.
Should we get a sandbox environment before purchasing?
Yes — insist on a free sandbox account where you can test the software on your own data, at your own pace, without the vendor controlling what you see. A 14–30 day trial with your actual property structure, asset list, and work order volume is standard for enterprise software. Any vendor who won't provide a sandbox before contract signature is hiding poor performance or missing features.
What questions should we ask about pricing during the demo?
Ask four specific questions: (1) "What is the all-in monthly cost for our portfolio size — including all users, all features, and all integrations?" (2) "Is there a per-user or per-unit surcharge?" (3) "What is the annual price escalation policy — is it fixed in the contract?" (4) "What are the data export fees if we leave?" Get answers in writing. If the vendor deflects or says "it depends," eliminate them.
How many vendors should we demo before deciding?
Demo 3–5 vendors maximum. More than 5 leads to decision paralysis. Start with your shortlist based on portfolio size and feature requirements. Use this script on the first vendor as a learning experience, then refine your questions. Demo vendors 2 and 3 with the refined script. If none pass, consider vendors 4 and 5. More than 5 demos usually indicates unclear requirements — not vendor problems.
Skip the Script — Test OxMaint on Your Actual Workflows.
No sample data. No sales fluff. No enterprise tier for essential features. Free sandbox account — test all 32 scenarios yourself.
.png)
.png)