Methodology · v2.1 · Last reviewed May 16, 2026
How we score FSM software
Every product review on this site is scored against the same five weighted criteria. The rubric below is the contract — what we measure, how the weights combine, and the bar each platform has to clear to score 8+.
The rubric
Five criteria. Same five. Every platform.
Each criterion is scored 0–10 and weighted as shown. Weighted scores sum to the Editor's score chip you see on every review.
- 25% 01
Usability
Cold-start task completion by real operators, not trained staff.
- 25% 02
Feature depth
Native coverage of the full FSM workflow without third-party glue.
- 20% 03
Pricing
Transparent, predictable cost from headline rate to all-in.
- 20% 04
Integrations
Breadth and reliability of the connectors that actually matter.
- 10% 05
Support
How fast a real human resolves a problem during a dispatch window.
The math
How a score is calculated
The Editor's score on every review is a weighted sum — no manual adjustments, no brand-reputation bonus points, no score floor.
Editor's score = (Usability × 0.25)
+ (Feature depth × 0.25)
+ (Pricing × 0.20)
+ (Integrations × 0.20)
+ (Support × 0.10) See a worked example (illustrative numbers, not a published score)
| Criterion | Score | Weight | Contribution |
|---|---|---|---|
| Usability | 8.0 | 25% | 2.00 |
| Feature depth | 9.0 | 25% | 2.25 |
| Pricing | 7.5 | 20% | 1.50 |
| Integrations | 8.5 | 20% | 1.70 |
| Support | 7.0 | 10% | 0.70 |
| Editor's score | 8.15 → 8.2/10 | ||
Scores are not adjusted for company size, industry, or price point. A platform's weakness in any criterion drags down the aggregate regardless of its strengths elsewhere — the goal is honest comparison, not promotional scoring that makes every product look like a winner.
In depth
The five criteria, spelled out
Each card lists what we measure and the bar a platform has to clear to score 8+ on the rubric.
-
01 Usability
25%Usability measures how quickly real people — technicians and dispatchers, not software trainers — can complete core tasks after a cold start. A dispatch board that takes a week to learn costs real money in productivity and onboarding overhead.
What we measure
- Time-to-first-job: minutes from a fresh account to a scheduled work order.
- Click depth: screens a dispatcher touches to book, assign, and close a job.
- Mobile parity: whether a tech can complete the same workflow on a phone as on a desktop.
- Error recovery: how gracefully the app handles a double-booked tech or a mis-entered address.
What an 8+ looks like
A new dispatcher can build a route in under 15 minutes without trainer assistance, and a tech can complete a service ticket in three taps from the mobile home screen.
-
02 Feature depth
25%Feature depth rewards platforms that cover the full field-service workflow without requiring a separate point solution for every job stage. A platform that does everything adequately scores higher than one that does two things brilliantly and outsources the rest.
What we measure
- Quoting and estimates — from customer inquiry to approved quote.
- Job scheduling and dispatch — recurring jobs, dynamic re-routing, crew management.
- Time tracking and payroll integration — GPS verification, overtime rules.
- Invoicing and payment collection — in-field card acceptance, automated follow-ups.
- Customer communication — automated appointment reminders, on-my-way SMS, review requests.
What an 8+ looks like
Native support for quoting, scheduling, dispatch, time tracking, invoicing, and customer comms — no third-party plug-in needed for any standard FSM workflow. Vertical-specific reviews also need the relevant compliance and asset tracking covered natively, not retrofitted.
-
03 Pricing
20%Pricing transparency is a proxy for how a vendor treats customers after the sale. Software that hides its pricing behind a 'contact us' form almost always has a more complicated cost structure than software that publishes it openly.
What we measure
- Whether per-user, per-tech, or flat rates are publicly listed without a demo call.
- All-in cost at 5, 20, and 50 seats — does it scale linearly or with surprise add-ons?
- Whether onboarding, training, and module fees are disclosed before the demo.
- How the pricing model scales — per-user, per-tech, flat rate, or usage-based.
What an 8+ looks like
Per-user or flat rates published on the marketing site without a lead form. Onboarding fees disclosed before the demo call. Cost at 20 seats lands within 15% of the headline number — no surprise modules required to reach feature parity with the demo.
-
04 Integrations
20%No FSM platform is an island. Every field service business already has an accounting system, a CRM, or a payment processor. Integrations score both the breadth of the ecosystem and the reliability of the connections that matter most.
What we measure
- QuickBooks integration — tested hands-on for two-way sync accuracy.
- Stripe / Square / payment processing — in-field and office payment capture.
- CRM connections — Salesforce, HubSpot, or the platform's own customer records.
- GPS and routing — whether the platform connects to a real routing engine or relies on manual scheduling.
- API availability — whether the platform exposes a documented public API.
What an 8+ looks like
Two-way QuickBooks sync that survives 30 days without manual reconciliation. A documented public REST API. Native CRM, payment-processor, and routing connections that the vendor maintains directly — not third-party Zapier glue.
-
05 Support
10%Support quality only matters when something breaks — and in field service, software problems during a dispatch window have direct revenue consequences. We score support on accessibility (can you reach a human quickly?) and resolution quality (does the human actually resolve the issue?).
What we measure
- Live chat first-response time, measured during business hours.
- Email support response time, measured over 5 business days.
- Phone support availability and wait time.
- Documentation quality — current, searchable, accurate.
- User community — active operator-to-operator help.
What an 8+ looks like
Live chat first response under 5 minutes during business hours. Email response within 4 business hours. Phone support reachable in under 2 minutes of wait time. Documentation covers the full product surface with version-current screenshots.
Commitments
What we don't do
- No pay-for-placement. A vendor cannot pay to appear in a best-of list, to receive a higher score, or to have negative content removed.
- No vendor-controlled review. Vendors may correct factual errors, but they do not approve copy, preview scores, or influence the final verdict.
- No score floor. A weak criterion drags the aggregate down regardless of brand reputation or relationship with the vendor.
- No anonymous authorship. Every review and comparison carries Chip's name, photo, and credentials. Readers can verify his experience and contact him directly with corrections.
- Test conditions are disclosed per review. Where vendor trial or sandbox access is available, scoring is hands-on. For platforms that gate access to enterprise buyers, scoring draws on product documentation, verified buyer reviews on third-party platforms, and analyst sources, and the review states so. A vendor demo alone is not the basis for a published score.
Update policy
How we keep reviews current
Each review carries two dates: Published (original publication) and Last reviewed (the most recent re-evaluation). These are different, and both matter.
The 12-month freshness rule: any review whose "Last reviewed" date is more than 12 months in the past is flagged as potentially stale in the site's build pipeline. Flagged reviews are prioritised for re-review. FSM software changes substantially in 12 months — pricing, core features, and support quality are all moving targets.
Vendor-driven re-reviews: when a vendor ships a major feature update (a new dispatch board, a pricing model change, a new integration), Chip re-reviews the affected criteria rather than waiting for the 12-month cycle. Vendors may notify us of major changes at the contact page, but re-reviews are conducted independently — not in coordination with the vendor.
Correction policy: factual errors (wrong pricing, a feature that no longer exists, an incorrect spec) are corrected as soon as verified. Corrections are noted at the bottom of the affected review. Score changes are noted with the date and a brief explanation.
Have a correction?
If you find a factual error in a review — incorrect pricing, a feature description that no longer matches the current product, or a spec we got wrong — please let us know. Corrections are taken seriously and published promptly. Reach Chip via the contact page.