Lorixen.
EN

Digital job sheets for a trade business: screen by screen

Short answer: A digital job sheet replaces the carbon-copy book: the office creates a job, the tradie opens it on a phone, records time, materials, photos and notes on site, gets a customer signature, and the completed sheet flows straight to invoicing. The screens that matter are the job list, the job record, materials, photos and sign-off. The design details that decide whether crews use it are speed with gloves on, working without mobile reception, and never losing a photo.

Plumbers, electricians, HVAC techs, builders and handymen across Australia still run on paper job sheets or a text to the office at the end of the day. Paper gets wet, illegible or lost in the ute, and the office retypes everything into the invoicing system. Off-the-shelf field service apps exist and suit many businesses; this blueprint is useful either way, as a checklist for choosing one or a spec for building your own.

Screen 1: Today's jobs

What the tradie sees first when they open the app.

  • List of today's jobs in order: time window, suburb, customer name, job type.
  • Status chips: scheduled, travelling, on site, complete, needs follow-up.
  • One tap to navigate to the address in the phone's maps app.
  • One tap to call or text the customer ("running 20 minutes late").
  • Tomorrow's jobs a swipe away, so crews can check parts the night before.

Design rule: large touch targets and high contrast. People use this in bright sun, with dirty hands, sometimes with gloves.

Screen 2: The job record

Everything about one job on one scrolling screen.

From the office (read-only for crews):

  • customer, site address, access notes ("gate code", "dog in yard");
  • job description and any quote reference;
  • site history: previous visits and what was done.

Filled in on site:

  • Arrival and departure times with a single "start" and "finish" button, editable if they forget.
  • Work performed: free text plus quick-pick options for common tasks, so typing is optional.
  • Findings and recommendations: "hot water unit is 15 years old, recommend replacement quote".
  • Follow-up needed? yes/no, with a reason, which creates a task for the office.

Screen 3: Materials and parts

  • Search or scan items from a parts list the office maintains.
  • Quantity steppers (+/–) instead of number typing.
  • "Used from van stock" vs "purchased for this job", with a place to photograph the receipt.
  • A free-text "other" line for odd items.

Keeping the parts list tidy is the office's job; a messy list makes this screen unusable.

Screen 4: Photos

Photos settle disputes and support quotes, so this screen deserves care.

  • Before, during and after categories, so photos land in order.
  • Take a photo directly from the job. On the web, the file input's capture attribute can request the camera, with values for the user-facing or outward-facing camera. MDN marks it as limited availability, as it doesn't work in some widely used browsers, so the app should still let people pick from the gallery.
  • Captions by voice or quick text.
  • Upload in the background, with a clear "3 photos waiting to upload" indicator and automatic retry. Large photos should be resized on the device before upload to save mobile data.

Screen 5: Sign-off

  • A summary the customer can read: work done, materials, time on site, follow-ups recommended.
  • Signature on screen and the customer's name typed.
  • Option to email or text the customer a copy immediately.
  • If the customer isn't home: mark "left on site" and send the summary by email or text.

Offline: the make-or-break feature

Basements, rural properties, new estates and plant rooms often have no reception. A job sheet app that fails without signal will be abandoned within a week.

What "works offline" should mean:

  • Today's jobs and their details are downloaded in the morning.
  • Everything entered on site, including photos, saves on the phone first and syncs when reception returns.
  • The app clearly shows what's synced and what isn't.

For a web app, web.dev's PWA guide lists the on-device storage options, including IndexedDB for structured data and binary blobs such as photos, and notes that WebStorage (local storage) is synchronous and not recommended for complex data. It also explains that a site can request persistent storage via navigator.storage.persist(), while reminding developers that users can still delete stored data at any time. In plain terms: an offline-capable job sheet stores work properly on the device, asks the browser to keep it, and still syncs as soon as possible.

Office side: what happens after "complete"

  • Completed jobs appear in a review queue.
  • The office checks materials and time, then creates the invoice in your accounting tool through its integration or an export, with no retyping.
  • Follow-ups become tasks or quote requests.
  • Photos and the signed sheet attach to the customer's record.

Choosing or building: questions to ask

  1. Does it work fully offline, including photos?
  2. How fast is it to complete a typical job sheet? Time it with a real tradie.
  3. Can it handle your job types: service, install, maintenance contract, warranty callback?
  4. Does it connect to your accounting tool, or at least export cleanly?
  5. Can you customise fields without a developer?
  6. What happens to your data if you stop using it?

Illustrative example: a hypothetical two-van electrical business in Geelong might only need screens 1, 2, 4 and 5 plus an invoice export; a hypothetical 15-tech HVAC company would add maintenance-contract scheduling and parts stock.

FAQ

Native app or web app for job sheets?

Either works if offline storage and photo handling are done properly. Web apps are cheaper to build and update; native apps can be smoother with cameras and background sync.

Do customers accept on-screen signatures?

Most do. Send them a copy of the summary right away so they have a record.

Can crews use their own phones?

Yes, but agree on it upfront, and make sure the app's data is separate from personal photos and messages.

How long does it take crews to adapt?

It depends on how fast the app is to use. Keep version one simple and get feedback after the first fortnight.

If your job sheets still come back in a muddy carbon-copy book, tell us how a typical job flows from call to invoice and we'll sketch the screens you'd need.

Sources

WhatsAppLet’s talk