Guide

Everything that happened on a job, in one place

Last updated 29 August 2026

Ask most businesses what happened on a job six months ago and the answer is a search party. Photos on one phone, a delivery docket in a ute, the variation agreed in a phone call nobody wrote down, the hours in a book. The work was done properly. Proving it is the problem, and proving it is what gets you paid.

Why it scatters

Nobody decides to keep records badly. It scatters because each piece is captured by a different person, on a different device, at the moment it happens, and the moment it happens is never a convenient moment to file anything. The sparky photographs a dodgy switchboard because he needs to show someone, not because he is building a file. The apprentice texts the boss about the delivery. The variation is agreed standing in a driveway.

Each of those is the right thing to do in the moment. The failure is that none of them land anywhere connected to the job, so recombining them later means remembering they exist at all.

What a complete job record actually holds

If you were designing it from scratch, a job would carry all of this, and all of it would be reachable from one screen:

The commercial facts, who the customer is, what was quoted, what was agreed, what has been invoiced, and what is still owed.
The costs as they land. Materials used, supplier bills, purchase orders raised against it, and labour hours. Not at the end of the month. As they happen, while somebody still knows what they were for.
A day-by-day record of the work, who was on site, what they did, what held them up. This is the single most valuable thing in a dispute and the most commonly missing.
Photos, attached to the job rather than to a phone. Before, during, after, and every surprise found in a wall.
The conversation. The back and forth about this job, kept with the job instead of in a group chat that has moved on to three other sites.
Documents. Plans, spec sheets, dockets, the certificates the work required.
Variations. Priced, approved, and separated from the original scope so the final bill can be explained line by line.
Defects and the punch list. What was found, who fixed it, when it was signed off.
Safety records. The SWMS, the site sign-ons, the toolbox talks, the incidents.
Proof of completion. The customer's sign-off on the day, with their name and the date attached to it.

Read that list and notice something: almost none of it is extra work. It is all already happening. The only question is whether it lands somewhere useful or somewhere it can be lost.

The test of a job record is not how tidy it looks. It is whether a stranger can reconstruct the job from it. If you were hit by a bus tomorrow, could someone else pick up this job, bill it correctly, and answer a customer's question about week two? If the answer is no, the record is decorative.

When it earns its keep

Four moments, and every one of them costs real money:

The customer disputes the bill. The final invoice is more than they remember agreeing to. A record with the variation, the date it was approved and the photos of why it was needed ends that conversation in a minute. Without it, you either discount or fight.
You need to know whether you made money. Quoted against used. If materials and hours are only reconciled at tax time, you find out you underquoted a type of job about eleven months too late to stop doing it.
Someone leaves. The leading hand who knew the job goes on holiday, or leaves altogether. Everything he knew is either in the job or in his head.
Something goes wrong later. A failure, a claim, an insurer, a regulator. What you can prove about how the work was done is what protects you, and memory is not proof.

How to keep one without adding paperwork

The trick is not discipline. Discipline fails on a wet Thursday. The trick is to make the record a by-product of work people already do:

Capture at the point of doing. The photo is taken on site, so it should attach on site, in two taps, not be emailed to the office to be filed.
Make it work with no signal. Half of Australia's job sites have no reception and every basement has none. If the app needs bars, the record has a hole in it exactly where the hard jobs are.
One place, not five. If chat lives in one app, photos in another and hours in a book, nobody reassembles them. The reassembly is the work, and nobody has time for it.
Write the diary the same day. A diary written on Friday for the whole week is fiction with good intentions. A prompt at knock-off beats a policy.

The admin dividend

A complete job record is usually sold as protection, which undersells it. The bigger win is that the admin at the end stops being a job of its own. Invoicing a job whose costs are already on it is a check and a send, not an evening of reconstruction. Paying a supplier bill is matching it to a purchase order that is already there. The month-end that eats a Sunday is almost always the cost of information that was captured somewhere it could not be used.

This is the shape Jobdeck is built in. Every job carries its own overview, costs, files, notes, site diary, photos, chat, variations, defects and safety records. Ten tabs on one job, on the phone and in the web dashboard. The site diary works with no signal and syncs when you get bars back. Materials, supplier bills and purchase orders land on the job as they happen, so quoted-versus-used is a screen rather than an exercise. The customer signs off on your phone at handover, and that signature stays with the job.

Start a free trial. 14 days, no card needed.