Why Most Dispatch Software Evaluations Go Wrong
You've sat through the demo. The interface looked clean, the sales rep answered every question with confidence, and the pricing seemed reasonable. Six months after go-live, your inspectors are still printing paper timesheets, your payroll admin is manually re-keying hours into your certified payroll template, and your HCAI project coordinator is chasing down inspection logs that the system can't format correctly.
This is not an unusual story among California Construction Materials Testing (CMT) and Special Inspection firms. The software wasn't bad — it just wasn't built for you. Evaluating inspection dispatch software without a CMT-specific lens is one of the most expensive mistakes a firm can make, not because the licensing fee is high, but because the hidden costs of a wrong fit compound every single week in the field.
This checklist is designed to help firm owners and operations leaders cut through the demo polish and ask the questions that actually matter.
The Must-Have Checklist: Features That Are Non-Negotiable for CMT Firms
Before you evaluate any vendor, establish your floor — the capabilities without which the software simply cannot function in your environment. For California CMT and Special Inspection firms, that floor is higher than most generic field-service platforms assume.
1. CMT-Specific Dispatch Workflows
General field-service dispatch was designed for HVAC techs, plumbers, or landscaping crews. The workflow assumptions baked into those products — single technician per job, flat service rates, simple job completion states — don't map to CMT operations. You need software that natively understands:
- Inspector type and certification matching (e.g., ICC, ACI, AWS, DSA Special Inspector categories) so a dispatcher can't accidentally assign an uncertified inspector to a job requiring a specific credential.
- Multi-site, multi-trade daily dispatch — a single inspector may cover a concrete pour in the morning and reinforcing steel in the afternoon at two different project addresses.
- Inspection category codes that align with DSA and HCAI documentation requirements, not custom fields you've had to jury-rig into a generic work-order system.
- Sample pickup and lab submittal tracking as a native workflow, not an afterthought add-on.
If a vendor asks you to explain what "DSA" or "HCAI" means during a discovery call, that is a signal worth noting.
2. Certified Payroll Support
California public works projects trigger prevailing wage requirements under the California Labor Code, and certified payroll reporting is a legal obligation — not a nice-to-have. Your construction inspection software checklist must include a clear-eyed evaluation of how any platform handles this.
At minimum, look for:
- Prevailing wage classification fields attached to individual assignments, not just to the project record.
- The ability to generate or export data in a format compatible with DIR-compliant certified payroll reports (California's Department of Industrial Relations requirements).
- Support for split-classification days — common when an inspector performs both regular and prevailing wage work on the same day.
- Overtime calculation logic that accounts for California's daily overtime threshold (over 8 hours) and double-time rules, not just the federal 40-hour weekly standard.
Many firms report spending significant administrative hours each week reconciling dispatch records with payroll because their software lacks this logic. That reconciliation time is a real, recurring cost that rarely appears in a total cost of ownership conversation with a vendor.
3. Mobile Offline Mode
Construction sites are not co-working spaces. Basements, shielded structures, rural grading projects, and underground utilities work all present connectivity challenges. If an inspector's ability to log time, record inspection results, or upload field data depends entirely on a live internet connection, you have a reliability problem that will surface at the worst possible moments.
Ask vendors specifically:
- Does the mobile app store data locally when offline and sync automatically when connectivity is restored?
- Can inspectors complete their full field workflow — check in, log inspection results, photograph, check out — without a connection?
- How are sync conflicts handled if a dispatcher makes a schedule change while an inspector is offline?
A vendor who hedges on offline functionality ("most sites have coverage") has not worked in CMT field operations.
Red Flags: Signs You're Looking at a Repurposed Generic Platform
The dispatch software evaluation process is easier when you know what to look for — and what to walk away from. These are the most common red flags that indicate a platform was built for a different industry and adapted (poorly) for CMT.
No California Compliance Logic Built In
California has some of the most complex labor and prevailing wage rules in the country. If a platform's compliance features are limited to federal FLSA logic, or if "California compliance" means a custom field someone added during onboarding, the burden of compliance will fall entirely on your payroll staff. That is not a software feature — it is a manual process with a software price tag attached.
Inspection Reports That Don't Match Authority Having Jurisdiction (AHJ) Formats
DSA and HCAI have specific documentation expectations. If the platform's inspection report output requires extensive customization to meet AHJ expectations, ask who owns that customization work and what happens when form requirements change. Many firms report being told during sales that report templates are "fully customizable," only to discover post-implementation that meaningful changes require paid professional services engagements.
Weak or Manual Payroll Export
A payroll export that produces a generic CSV file with hours is not certified payroll support. It is a starting point for a spreadsheet exercise. If the export pathway to your payroll system or certified payroll reporting tool requires manual column mapping, rate lookups, or classification cross-referencing every pay period, the software has not solved your problem — it has relocated it.
The Platform Was Originally Built for a Different Trade
It is worth asking vendors directly: "What industry was this platform originally designed for?" Platforms that began as HVAC dispatch tools, property inspection software, or general field-service management systems carry assumptions in their data models that don't always surface in a demo. Those assumptions become constraints post-implementation.
Questions to Ask Every Vendor
Once you've confirmed a platform clears the must-have threshold and hasn't triggered red flags, these questions will separate vendors who understand CMT from those who are learning about it through your RFP.
Integration Surface
- What accounting and payroll systems do you have native integrations with? (Sage, Viewpoint, QuickBooks, and ADP are common in CMT environments.)
- Do you have an open API, and is API access included in standard pricing or gated behind a higher tier?
- How do you handle integration maintenance when a third-party system updates its API?
Data Ownership and Export
"If we decide to leave your platform in three years, what does our data exit look like?"
This question makes some vendors uncomfortable, which is itself useful information. You should expect clear answers on:
- What formats your data can be exported in (CSV, JSON, PDF archives of inspection reports).
- Whether historical inspection records — including photos and signatures — are exportable or locked to the platform's viewer.
- How long the vendor retains your data after contract termination and whether there are fees for a data export at offboarding.
For DSA and HCAI projects, inspection records may need to be retained for the life of the structure. Confirm your data ownership rights are explicit in the contract, not just implied by the sales conversation.
Pricing at Scale
Many platforms offer attractive entry-level pricing that changes materially as your usage grows. Ask:
- How does pricing scale with the number of active inspectors, projects, or dispatched work orders?
- Are there per-inspection fees, storage overage charges, or API call limits that could create unpredictable costs?
- What is the pricing structure for seasonal fluctuation — if you staff up 40% in summer, does your cost increase proportionally?
Implementation Considerations That Drive Total Cost and Rollout Risk
The subscription price is the smallest number in the total cost of ownership equation. Implementation is where CMT firms most commonly encounter unexpected expense and schedule risk.
Data Migration
If you have years of project history, inspector certifications, and client records in a legacy system or spreadsheets, understand exactly what the vendor will migrate and what they will not. Many platforms migrate active records only, leaving historical project data in a system you may have to maintain in parallel.
Inspector Training and Change Management
Field inspectors are not desk workers. Training programs designed around classroom sessions or long video libraries tend to underperform in CMT environments. Ask whether the vendor offers role-specific, mobile-first training materials, and whether they have experience rolling out software to field teams with varying levels of tech comfort.
Configuration Depth vs. Professional Services Cost
Many platforms advertise configurability. What they mean is that configuration is possible — with paid professional services hours. Before signing, ask for a written scope of what is included in onboarding versus what requires a separate statement of work. Common configuration items that surface as surprises include: custom inspection form templates, client portal setup, payroll integration configuration, and report branding.
Go-Live Timing Relative to Project Cycles
Launching new dispatch software at the start of a heavy project season is high-risk. Build implementation timelines that account for your firm's busiest periods, and ask vendors whether their implementation team has capacity commitments or whether your go-live date is subject to their queue.
Putting the Checklist to Work
A structured CMT software buyer's guide approach — defining your must-haves before you see a demo, testing for red flags during the evaluation, and asking the hard vendor questions before contracts are signed — dramatically reduces the risk of a costly platform switch 18 months from now.
The firms that make the best software decisions are the ones who treat the evaluation as a business process exercise, not a product comparison exercise. The question is never "which platform has the best UI?" It is: "Which platform was built for the way CMT operations actually work?"
Inspectra360 was designed from the ground up for CMT and Special Inspection firms — not adapted from generic field-service software. The platform includes native CMT dispatch workflows, California prevailing wage and certified payroll logic, and a mobile-first field experience built for inspectors working in low-connectivity environments. If you're working through a formal evaluation, Inspectra360's team is available to walk through any item on this checklist with specifics.