Digital Job Cards: Lessons From Building a Field Team App

This year we built a platform to take a field-service company off paper job cards and onto phones. Their technicians do service visits and compliance paperwork on client sites. Before, a job started as a WhatsApp message and ended as a paper card that someone in the office typed up again.

Digital job cards sound simple: put the form on a phone and you are done. The card was the easy part. The hard parts were a technician on a site with no signal, an office that retyped what the card already said, and a certificate that had to look exactly like the old one.

Here is what we learned, with the client's name and details left out, plus a checklist if you are weighing up the same move.

What the day looked like on paper

Every part of a job had its own tool, and none of them talked to each other.

• Dispatch was a WhatsApp message with the address and equipment counts.
• The job card was a printed book. The client's equipment register was built by hand in the office, from a paper slip stuck to the back of each card.
• Invoicing waited until the paper cards came back at the end of the day.
• Certificates were a separate Word document for every job.
• Unfinished jobs were tracked in WhatsApp.
• The service schedule was a colour-coded Excel sheet. When route boundaries shifted from one year to the next, sites were missed.
• Stock lived in a broken spreadsheet with negative balances and #REF! errors (formulas pointing at cells that no longer exist). Nobody could see what was in the vehicles.
• Leave sat in WhatsApp and a paper book, so the office never knew anyone's real balance.

Together they meant one job was written down, passed on and typed again before it became an invoice.

The company had also tried an off-the-shelf app. The technicians stopped using it because of fields that had nothing to do with their work, and connection errors. That shaped two rules for the build. The app must work with no signal. The card must look like the paper card.

What we built for the technician

The technician side is a web app (it runs in the phone's browser). It installs to the home screen, and new features arrive without an app update. A technician sees only their own jobs.

The job card follows the paper card's layout and order, down to the blocks the counts were written in. It saves as the technician types, from odometer readings to parts used and photos. The customer signs on the phone and prints their name.

For a job card, that is generally valid in South Africa. Section 13 of the Electronic Communications and Transactions Act says a signature is not invalid just because it is electronic. This law firm's overview of electronic signatures in South Africa covers the exceptions.

Then there are the parts the paper card never had:

• Proof of visit. The technician photographs the site's own stamp. A signature can be copied. The stamp never leaves the premises.
• A count check. If the units serviced differ from the plan, the technician types a reason.
• QR stickers. The first scan records a unit's details once. Later scans mark it serviced.
• Vehicle and staff admin. Fuel slips, vehicle checks, clocking in, leave with a live balance and policy sign-off, all on the same phone.

Offline decides whether anyone uses it

When a submit fails on a site with no signal and the work is lost, the technician goes back to paper. We treated that as the one failure the app could not have.

While the phone has signal, it saves the day's jobs, their cards and the site registers. With no signal, the technician can still start a job, fill in the card, take photos, get the signature and submit. The card waits on the phone and sends itself when signal comes back.

Three rules sit underneath:

1. Unsent work leaves the phone only once the server (our side of the system) confirms it has it. Delayed is recoverable. Deleted is not.
2. Signing out never deletes unsent work.
3. The app does not trust the phone's "connected" icon. A phone can show signal while nothing loads, so the app checks that the server actually answers.

We also ship updates outside field working hours, because an update clears the saved offline screens until the app is next opened with signal.

What we built for the office

One rule runs through the office side: everything after the job card must be automatic. The office should never build a register by hand again.

• Dispatch board. A Status column shows whose move is next, and new jobs reach the technician's phone with a notification.
• Review. The office approves each card or sends it back with a reason, with everything still filled in.
• Register and certificate. Approval updates the client's equipment register and due dates, and produces the certificate as a PDF in the design the business already used.
• Payment first. Certificates wait until payment is recorded, the client's own rule. A "Send anyway" button records who used it.
• Invoice tracking. Each job holds the invoice number, dates and PDF. It is not a live link into the accounting software.
• Carry-overs. Every morning at 05:00 the system flags unfinished jobs with a reason and sends the office one summary.
• Stock. A ledger (a running record of every change) for the storeroom and each vehicle. Stock used on a card comes off that vehicle automatically, and a shortfall raises a flag for the office instead of stopping the technician.
• Compliance and people. A hub that follows the regulator's audit checklist, plus leave, attendance, policy sign-off and licence expiry dates.
• Numbers. A statistics page that our office guide sums up as "the numbers you used to count by hand at month end."

How we rolled it out

A prototype came first. Work on the real system started in May 2026 and went in phases on made-up test data, then final checks and fixes before launch.

Then we switched to one module at a time (one part of the system, such as stock or leave), with the client:

1. We audit the module against the client's real Excel sheets.
2. The client tests the live product.
3. We refine it and check it again.
4. The client signs it off. Only then does the next module start.

We meet the client on Fridays, and the client sets the pace. Since 21 August 2026, every office module has been live for the client's office.

Our questions for the client lived in the platform, not WhatsApp. We also wrote an Office Guide with one task per page, and a Technician Guide with a tear-out "Your day in 6 steps" card for the vehicle.

For the technicians, the approach is one technician first, on their own phone, with a paper card stocked in the vehicle and a "what annoyed you?" conversation before the other teams join.

Results belong to the client, and we only publish them with their OK.

What we learned about digital job cards

1. Copy the paper card first. Technicians already know where everything is. Improve it once they trust the phone.
2. Design for the worst site, not the office Wi-Fi. Offline is not an extra.
3. Don't let a new check block the submit. Gaps become flags for the office.
4. Enter it once. If the office types what the card already says, the system is not finished.
5. Don't import a broken spreadsheet. Our rule for stock: no import. Day one is a physical count of the storeroom and every vehicle, and that count becomes the opening balance.
6. Keep paper as a spare, not a second system. A job done on paper is photographed and attached to the job, and a person reviews it like any other card.
7. Match the documents people already trust. A certificate that looks like the old one needs no explaining.

A checklist before you switch to digital job cards

If your field team runs on paper and WhatsApp, answer these first:

• Can you list every piece of paper and every message one job creates, from dispatch to paid invoice? If not, map it first. Our workflow digitisation guide and where to start are good first reads.
• Where are your dead zones? Can the app submit a full card, photos and signature included, with no signal?
• Will your technicians recognise the card on day one?
• What happens after the card is signed? Is anything typed again?
• What happens when a phone dies?
• Where will day one's stock numbers come from? A fresh count, or a sheet you already don't trust?
• Which WhatsApp habits stay? Our post on WhatsApp business operations helps you choose.
• Who owns the data and the code? When we build it, you do.
• Which number will tell you it worked, and have you measured it before you start? Here is how we measure success.

Start with how a job moves today

If your team still works off paper cards and WhatsApp, we would like to hear how a job moves through your business today. Take the free AI audit: 9 questions, about 2 minutes, a personalised audit and no sales call. Or send us a message. It goes to both founders, and you get a reply within 24 hours.