01 / The buying question
Describe the repeated problem before comparing tools.
“We need a new system” is too broad. Start with one sentence that names what happens now, who handles it and what useful result is missing.
For example: “Our engineers complete service dockets on site, but the office still re-types them into customer reports and chases the related photographs.”
That sentence gives every option the same test. Can it capture the visit where the work happens, keep the evidence with it, support an office check and produce the required customer report?
One useful rule
Choose against one real process—not a long feature list or a general promise to digitise the business.02 / Quick comparison
Three options, three different jobs.
None of these choices is automatically more professional than the others. The right one is the least complicated option that the team will use and that produces the required result reliably.
| Option | Good fit when | What you are taking on | Warning sign |
|---|---|---|---|
| Shared spreadsheet + folders | One list or tracker is enough, record volume is manageable and a named person keeps it consistent. | Designing the columns, permissions, folder rules and everyday discipline. | The real record still arrives through paper, messages and separate attachments. |
| Off-the-shelf field-service software | Several standard processes need one product: jobs, scheduling, forms, customer communication, quotes or invoices. | Configuration, subscriptions, data setup, training and adapting some processes to the product. | The team needs only one narrow fix but must adopt a much larger system to get it. |
| Small custom workflow | One repeated, valuable process has particular hand-offs, approvals or outputs that simpler options cannot fit. | A written scope, build, testing, handover, support arrangements and a clear owner inside the business. | The request starts as “build everything” without one process or measurable result. |
Compare the whole change, not just the licence or build price. Setup time, training, data preparation, support and the time your own people spend changing the process all matter.
03 / Shared spreadsheet
Use a spreadsheet when a clear list solves the problem.
A spreadsheet is a sensible working system when the process is simple, the volume is manageable and the team can agree one shared version.
Current versions of Microsoft Excel support shared workbooks and co-authoring, while Google Sheets supports controlled sharing and simultaneous collaboration. The important question is not whether a spreadsheet can be shared. It is whether the surrounding process stays clear.
The columns are stable, permissions are understood and somebody is responsible for keeping the structure useful.
People mainly need to view, filter, update or export a straightforward set of records.
Site staff send paper, photographs or messages and the office types the important details into the sheet later.
Several linked tabs, fragile formulas and manual status rules are understood by only one person.
Improve the spreadsheet before replacing it.
Remove unused columns, agree the exact status names, keep one shared version and connect each row to its related job folder or document. If that removes the repeated work, stop there.
04 / Existing product
Choose field-service software when you need the standard package.
An established product is usually the stronger option when the business wants several common job-management functions and can work within the product’s way of doing them.
Current field-service products can cover broad areas such as job cards, scheduling, forms, client communication, invoicing, assets and integrations. For one concrete example of that breadth, see this first-party ServiceM8 feature summary. It is an example, not a recommendation or a complete market comparison.
Use the few outcomes the business actually needs, not every feature that appears in a sales demonstration.
Let one office user and one field user complete a normal job on their usual devices.
Check the customer report, handover file, invoice input or other document the process must create.
Understand how your records and attachments can be exported if the product no longer fits.
Include configuration, training, data setup and any work needed to keep existing systems aligned.
If the product’s standard process is clear and suitable, changing an old habit may be better than customising software.
05 / Small custom workflow
Use custom work for a narrow gap with a clear value.
Custom does not have to mean replacing every system. It can mean connecting one repeated process that still depends on copying, chasing or rebuilding information.
The process repeats often
The same inputs, hand-offs and output appear across similar jobs, visits or inspections.
The current cost can be observed
You can count handling time, missing records, corrections, delayed reports or another practical measure.
The result is specific
Everybody agrees what useful record, approval or document should exist at the end.
Simpler options were checked first
The spreadsheet, current system and suitable existing products were considered against the same process.
The first scope can stay small
One process can be built, checked with real examples and accepted before anything wider is proposed.
Custom work is a poor fit for unclear responsibilities, constantly changing processes or decisions that depend heavily on professional judgement. Fixing the process itself may be the better answer.
06 / Worked example
A fictional 20-person service firm compares all three.
The company already schedules work and raises invoices successfully. Its specific problem is that engineers’ service dockets and photographs are re-typed into customer reports after every visit.
A shared visit list, agreed fields and links to one photo folder may be enough if only a few reports are produced each week.
A field-service product may be better if scheduling, job cards, communication and invoicing all need one standard system.
If the existing scheduling and accounts tools work, a small docket-to-report process may avoid replacing them.
Run several fictional or safely prepared sample visits and check the time, corrections and staff effort for each route.
The commercial test
The winning option is the one that removes the repeated handling at an acceptable total cost and that the field and office teams will actually use.07 / Before you buy
Run one process through the decision.
A short practical test will reveal more than a long requirements document written before anybody tries the real work.
- Choose one repeated process and name its owner.
- Collect three to five recent examples, including the final outputs.
- Mark every point where information is copied, chased, corrected or recreated.
- Write down the few results the chosen tool must produce.
- Check whether a cleaner spreadsheet or your current software can already do it.
- Test suitable products with one office user and one field user.
- Consider custom work only for the clear gap that remains.
- Agree how success, ownership, support and exit will be handled before committing.
Map one real record
Use the free job-record template.
Identify the fields, attachments, hand-offs and final output before you compare software.
Open the templateSee the narrow workflow
Try the two-minute example.
Add one fictional record and see its notes and attachments move into a searchable job list.
Try the example08 / Questions
Common questions before changing tools.
When has a spreadsheet become too complicated?
When several people maintain different versions, important evidence sits elsewhere, only one person understands the formulas or the office repeatedly turns rows into other documents by hand.
Should we replace all our systems at once?
Usually not unless the business has deliberately chosen a wider system replacement and can support it. If one repeated process is the problem, test that process first.
How many field-service products should we trial?
Shortlist only products that meet the few must-have outcomes. Trial enough to compare real use, but do not ask the team to test a long list of broadly similar systems.
Is custom software always more expensive?
Not in every case, but it carries its own design, build, testing and support work. Compare the total cost and risk of each option against the same narrow process rather than comparing a subscription price with a build quote alone.
What should we bring to a software conversation?
Bring a few real examples of the current input and output, the people involved, the usual exceptions and any existing systems that must remain. Remove or protect confidential information as appropriate.
This guide is a general framework for comparing administrative tools. It is not a recommendation of a particular product, a complete market comparison or legal, accounting, security, data-protection or procurement advice.