How to Evaluate a Field Service Platform: 12 Questions and a Scorecard

Most field service evaluations end the same way. Three vendors show three demos, every feature list gets a check mark, and the shortlist comes down to price and who the sales rep was.

The trouble is that every vendor checks every box. Work orders, dispatch, invoicing, a mobile app: they all have them. What separates the tool that still serves you in three years from the one you're replacing is what happens between the features. Whether the invoice builds itself from the job. Whether a price change reaches a technician's phone or waits for someone to update a second list.

Below are twelve questions, and each one comes with something to ask the vendor to show you live. Ask the demo request before you score the answer. A vendor can say yes to any question. Showing it is harder.

How to use this guide

Score each vendor from 1 to 5 on every question. The weights are set for you (High for most, Medium for one) and you can change them to fit your operation. Score after the demo, not before.

Use it on every platform you evaluate, including ours. The scorecard near the end has a column for MangoApps, and we suggest you leave it blank until you have watched us run the demos.

One record

The first two questions test whether the platform keeps one record of a job or several copies that have to be reconciled. Everything else in this guide gets easier or harder depending on the answer.

Question 1. Does the invoice generate from the work order, or does someone re-key it?

Ask the vendor to show you: a completed job and the invoice ready, with nothing typed in between.

This is the most useful single question in field service software. If the invoice is built from what the technician logged (labor, parts, materials, travel, at the price list's rates), then days-to-invoice depends on when the job closes. If someone types it from a paper ticket or a photo of one, days-to-invoice depends on how busy the office is that week.

Watch for the demo that "auto-creates" an invoice and then needs a person to add the parts. That's a draft, and the work of finishing it is the gap. It's also the first of the six places facts get lost that we describe in the six information gaps behind every field service problem, and the work order lifecycle walks through what should happen at each hand-off.

Question 2. Does the customer portal read the same job record, or a copy of it?

Ask the vendor to show you: change a status on the work order, then refresh the portal.

A portal that reads a copy of the job is a second system with a lag. It works until the dispatcher reassigns a technician at 2:00 and the customer is still looking at the 8:00 schedule. Then the customer calls, and the portal has produced the exact phone call it was bought to prevent.

The test takes ten seconds and settles it. For more on what the portal has to read, see when the customer's only status channel is the phone.

Pricing

Question 3. When you change a price, when does the technician's app show it?

Ask the vendor to show you: change a price, then show it on a technician's next estimate.

If pricing lives in a separate list, or in a PDF, or in a tech's memory, two technicians will quote the same job differently forever. The office bills one number and the field quotes another. The right answer is "on the next estimate, without anyone touching a second system."

Ask, too, whether the price list keeps a history of what was in effect on what date. You'll want that the first time a customer disputes a charge. The full argument is in the price depends on which technician showed up.

Frontline access

Question 4. What does a technician with no company email see on their own phone?

Ask the vendor to show you: the onboarding flow, not the app.

A lot of field technicians have no company email and would rather not use a personal one for work. Many don't carry company hardware either. If the sign-in flow starts with a corporate email address, a directory entry or a VPN, those technicians are locked out on day one, and the office ends up running the old process alongside the new one "just until everyone's on it."

Look for an invite by text message or a QR code, an app that installs on a personal phone, and no password or corporate email to remember. Then ask to see it on a phone, not a slide. Why technicians work around the tools is the long version of this question.

Question 5. Can a technician build, price and close an estimate on site, and does it convert to a work order without being retyped?

Ask the vendor to show you: an estimate built on a phone, approved, and turned into a work order.

Speed matters here because urgency fades. A customer who hears "we'll send you a quote" on Tuesday has often called someone else by Friday. Ask whether the customer can approve on the technician's device or in a portal, and count the number of times anyone has to re-enter something between "approved" and "scheduled."

Recurring work

Question 6. Does a maintenance agreement generate its own scheduled visits, or does someone remember to create them?

Ask the vendor to show you: the work order an agreement created on its own.

If the answer is a calendar reminder, the agreement is a document, not a system. Recurring revenue is the steadiest money in field service, and it's also the easiest to lose, because nothing fails loudly when a visit is missed or an invoice goes out late. The revenue just doesn't arrive.

Ask whether the agreement also bills on its own cycle, whether renewals surface ahead of expiry, and whether the price on a covered visit comes from the same list as everything else. Recurring revenue that schedules itself goes through each of those.

Compliance

Question 7. Can an expired certification block a dispatch automatically?

Ask the vendor to show you: expire a certification in the demo, then try to assign that technician.

In licensed trades, the HR record is an operational record. A technician whose credential lapsed last Tuesday is, on Wednesday, a liability who happens to be nearest to the job. If credentials are tracked in one system and assignments made in another, nothing connects the two except a person's memory.

The demo is decisive. Either the board refuses the assignment, or it doesn't. Watch for the answer that involves an alert email: an alert informs someone, and it doesn't stop a dispatch. We take the whole argument apart in why an expired certification should block dispatch automatically.

Question 8. Whose permissions does the AI inherit?

If the answer is anything other than the caller's own, the AI can surface data the person asking isn't allowed to see. A technician asks a pricing question and gets a margin they were never supposed to see, because the assistant had broad access to answer quickly.

The right answer is that every request runs as the person who made it, returns nothing they couldn't already see, and is logged. Ask where a prompt goes, what is retained, and whether any of it trains a public model. See whose permissions does the AI inherit for the full set of questions.

Integration

Question 9. Which accounting and HR systems sync two ways, by name?

Ask the vendor to show you: an invoice posting to your accounting system and a payment coming back.

"We integrate with accounting" tells you nothing. Get the names of the systems that sync in both directions, ask what moves (customers, invoices, payments, completed jobs and their costs), and ask to see one round trip. Ask the same about payroll and your HR system if technician time and credentials matter to you, and they do. For reference, ours is two-way sync with QuickBooks, Sage, NetSuite and other accounting and ERP systems, and with Workday, UKG, ADP, Paylocity, BambooHR and Rippling on the HR and payroll side.

Keep the systems you depend on. A good platform connects to them once instead of asking you to replace them mid-season. If the answer to "what happens to our accounting system" is a migration project, that's worth knowing before you sign.

Security

Question 10. Which security certifications does the vendor hold on one system, not across acquired products?

Certifications only mean what they say if they cover the product you're buying. Ask whether the attestation covers the platform your technicians will use, or a parent company, or a different product in the family.

For a platform that carries employee records, customer sites and AI, the bar we'd set is HITRUST CSF, SOC 2 Type II and ISO 27001 together, on one system. Ask about FedRAMP authorization if you sell to or operate in the U.S. public sector, HIPAA with a signed BAA if health data is involved, and GDPR if you have staff or customers in Europe. Then ask how the product deploys: SaaS, Private Cloud, Customer VPC or On-Premise are the four options worth knowing about, and a 99.9% uptime SLA is a reasonable thing to see in writing.

Expansion and adoption

Question 11. Can you start with one gap, or does the vendor require an all-at-once rollout?

Field service companies don't replace accounting, payroll and identity in one project, and they certainly don't do it in peak season. A vendor that needs everything to go live on the same Monday is asking you to take a risk that has nothing to do with your business.

The healthier answer is to close the gap that costs you the most first, keep what works, and add the rest when you're ready. If you're worried about the tool you just bought, we just bought an FSM tool: are you asking us to throw it away? answers that directly.

Question 12. What is your adoption rate at 90 days, and do you back it with anything?

Adoption is the number that decides whether any of the other eleven answers matter. A platform that's perfect on paper and unused in the truck is a parallel process with a monthly bill.

Here is ours, stated as a fact: 90%+ adoption within 90 days, including workers with no company email. And if employees don't adopt after launch, you don't pay. Ask every vendor the same thing and see what they put in the contract. The way to earn that number is in your first 90 days.

The scorecard

Score each vendor from 1 to 5 on each row and tally at the bottom. The weights are a starting point.

A note on the rows: they run in a different order from the twelve questions above, because the scorecard groups by the decision a buyer has to make, and the questions group by what to ask. Copy the table into a spreadsheet and add your own columns.

Five demo requests to send before the meeting

If you only do one thing after reading this, send these five to every vendor on your shortlist a week before the demo. Copy and paste them as they are.

1. "Show me a completed job and the invoice ready, with nothing typed in between."
2. "Change a price, then show me it on a technician's next estimate."
3. "Build an estimate on a phone, approve it, and turn it into a work order."
4. "Expire a certification, then try to assign that technician."
5. "Show me the work order an agreement created on its own."

Sending them ahead does two things. It gives the vendor time to prepare a real answer, and it tells you a great deal about how they respond to being asked to show rather than tell.

A vendor that runs these live has nothing to hide behind

A vendor who will run all five demos live, on your data and your service lines, has nothing hiding behind the feature list. One who redirects, or shows a slide, or promises a follow-up, has told you something too.

We'll run all five on your service lines. Schedule a demo and bring your hardest scenario, or start with the Field Service Suite if you want to see what we're evaluating you against.

If you'd like the twelve questions, the scorecard and the five demo requests in a form you can hand to a colleague, they're in the Field Service Management guide, a free download with no email required.

Frequently asked questions

What is the most important question to ask a field service software vendor?

Ask whether the invoice generates from the work order or whether someone re-keys it. Have the vendor show a completed job and the invoice ready, with nothing typed in between. It tests whether the platform keeps one record of the job or several copies, and every other capability (billing accuracy, pricing consistency, customer visibility) depends on the answer.

How do you test whether field service software works for technicians without company email?

Ask to see the onboarding flow on a phone, not the app on a slide. A technician with no company email should be able to install a branded app on a personal phone, get invited by text message or QR code, and get to their work orders without a corporate email address, a directory entry or a VPN. If any step needs one of those, the software wasn't built for that technician.

Should field service software integrate with accounting? Which systems?

Yes. Invoices, payments and completed jobs should move in both directions so the back office reviews exceptions instead of retyping records. Don't accept "we integrate with accounting" as an answer. Ask for the named systems that sync two ways, and ask to watch an invoice post and a payment come back. MangoApps syncs two ways with QuickBooks, Sage, NetSuite and other accounting and ERP systems.

What security certifications should a field service platform have?

For a platform that holds employee records, customer data and AI, look for HITRUST CSF, SOC 2 Type II and ISO 27001 together on one system. Depending on your customers, also ask about FedRAMP authorization for U.S. public sector work, HIPAA with a signed BAA for health data, and GDPR compliance. Ask which deployment options are offered: SaaS, Private Cloud, Customer VPC or On-Premise.

What adoption rate should you expect from field service software?

Ask each vendor for their adoption rate at 90 days and what they back it with. MangoApps customers typically see 90%+ adoption within 90 days, including workers with no company email, and if employees don't adopt after launch, you don't pay. Whatever a vendor tells you, get the number in the contract.