Choosing Job Card Software: What Actually Matters

Most field service software demos look impressive. Clean dashboards, colourful charts, a slick mobile app. Six months later the same businesses are back on WhatsApp because the thing did not survive contact with a real job site.

Here is what to actually look at, in rough order of how much it will matter to you.

Ask exactly what happens with no signal

Most products say they work offline. Very few mean the same thing by it. Ask specifically:

• If a technician opens a job card, loses signal, fills it in and takes photos, what happens to that work?
• Does it save on the device, or does it disappear when the app closes?
• Does it sync automatically when signal returns, or does someone have to remember to press something?
• Can they open a job they have not looked at before while offline?

That last one is where most products fall down, and it is worth knowing before you buy rather than after. A basement, a plant room, or a site an hour outside town are not edge cases in this industry. They are Tuesday.

Check whether you can build your own forms

Some products give you a fixed job card and let you rename the fields. That works until you need something they did not anticipate, and then you are stuck typing it into a notes box.

What you want is the ability to build a template from scratch, with the field types your work actually needs: checklists, dropdowns, number fields for readings, photos, signatures. And you want to be able to build several, because a compliance inspection and a breakdown callout are not the same document.

Look closely at how they charge

Per user pricing sounds reasonable until you grow. If you are paying per technician, every hire makes the software more expensive, and you start thinking about whether the seasonal guy really needs an account. That is a bad incentive for a tool that only works if everyone uses it.

Also check what happens at the tier boundaries. Some products put the feature you actually came for two tiers above where your team size sits.

Find out how you get your data out

Your job history is your business record. Ask how you export it, what format it comes in, and whether that includes the photos and signatures or just the text fields.

If the answer is vague, or the export is a paid add on, treat that as a warning. It tells you what the relationship looks like if you ever want to leave.

Try it on the worst phone in your team

Not your phone. The oldest, slowest, most cracked device someone on your team is actually carrying. That is the real test environment. Software that is smooth on a new handset and unusable on a three year old one will not get adopted, and the technician with the old phone is not going to tell you why they stopped using it.

Work out what it costs to get started

Setup time is a real cost. If getting going means recreating twelve forms by hand before anyone can log a job, that is a week you are not billing for. Ask whether there are templates you can start from, whether they will help with the migration, and how long a realistic setup takes for a business your size.

Questions worth asking directly

• What happens to work captured offline if the app is closed before signal returns?
• Can I build a template with my own fields, or only edit yours?
• What is included in the price, and what is charged separately?
• How do I export everything, including photos?
• How many businesses like mine are actually using this?
• Who do I contact when something breaks on a Friday afternoon?

The answers matter less than how readily they are given. A vendor who answers all six directly is a better bet than one with a nicer dashboard.

Opdeck was built for South African field service businesses, with offline support that saves work on the device, templates you build yourself, and flat pricing that does not punish you for hiring. Thirty days free if you would rather test it than take our word for it.