The variation argument is a fixture of trade work. The customer remembers agreeing to one thing. You remember agreeing to another. It is six weeks later, the wall is closed up, and there is $2,400 between the two accounts.
Most of these are not disputes about honesty. They are two people recalling a conversation that happened on a noisy site while one of them was holding a drill, and human memory is simply not good enough for that. The person who has something written down at the time is not more truthful. They are just better equipped.
This article is about what the Systemise field app captures while the work is happening, and why capturing it at the time is the whole point.
What gets captured
Photos against the job. Taken in the app and attached to the job record rather than sitting in a camera roll with four hundred other pictures. The job is what makes them findable later.
Files against the job. Documents added to the job, so the plan, the spec or the emailed instruction lives with the work rather than in somebody's inbox.
Job sign-off. Recorded when the work is done, at the point the customer is standing there.
Contacts captured on site, including from a photographed business card. The site foreman, the other trade, the property manager who turned up.
Hours and receipts, covered in their own articles, and captured the same way for the same reason.
All of it works without a connection. The app keeps a local copy and holds changes made out of coverage, syncing when the device is back online, which matters because the sites where recording is most valuable are frequently the sites with no signal.
Why the timing is the feature
Storage is not scarce. Everyone has a phone that takes photographs and somewhere to put them. If the value were in keeping images, this would not be worth an article.
The value is in the attachment happening at the moment the context is known.
A photograph in a camera roll is a picture of a wall. The same photograph attached to a job is evidence about that job. The difference is not the image, it is the two seconds where somebody said which job it belonged to, and that is knowledge that decays fast. On the day it is certain. Next week it is probable. In six weeks, at exactly the point you need it, somebody is scrolling backwards through a camera roll trying to work out which Tuesday it was.
The same is true of sign-off. A sign-off recorded when the customer is standing in front of the work means something. A sign-off recorded on Friday from memory is an administrative act.
What to photograph, which is the part nobody tells you
The habit is worth more than the feature, and most crews are never told what good looks like. A workable version is five things.
Before you start. The state you found it in. This is the one that settles arguments about damage that was already there, and it is the one most often skipped because the job has not started yet and nobody is in recording mode.
Anything you are about to cover up. Pipework before the lining, cabling before the plasterboard, the state of a substrate before it goes under something. Once it is closed, the photograph is the only record that it was ever done properly.
Anything unexpected. The thing that was not in the scope. Take the picture before you fix it, not after, because after it is fixed the photograph proves nothing.
The moment a variation is agreed. Photograph what is being changed and note what was agreed while the conversation is still fresh. This is the single highest-value habit in the list.
The finished work. Which is also the one that gets used for something other than arguments.
A rule of thumb that survives contact with a real crew: if you find yourself thinking somebody might question this later, that is the photograph.
Who can see it
Photos, files and job records follow the same permissions as everything else in Systemise. What a person can see and change in the app is set by their role, and financial detail stays limited to the users who are meant to see it.
So a crew member can add photographs to a job without that giving them a view of what the job is making. Those are separate questions and the system treats them separately.
What this is not
This is record keeping. It is not a legal or evidentiary product, and nothing here should be read as advice about what will or will not stand up in a dispute, a claim or an adjudication. Whether a record helps you in a formal process depends on the process, the contract and advice you should get from somebody qualified to give it.
It is also not a guarantee against loss. Records are synced and backed up, and no software should promise you that data can never be lost in any circumstance.
And it does not settle anything by itself. A photograph does not win an argument. It changes the argument from two recollections into one recollection and one record, which is a considerably better position and is not the same as being right.
Where to look next
The field app in general is covered on Jobs and scheduling, and how it behaves without a connection is covered in the article on what happens when the signal drops. Who can see and do what is covered in the permissions article. Receipts captured on site have their own article, as do hours.
If you want to know whether this is worth changing your habits for, think about the last variation you did not get paid for, and ask what you would have needed to have in hand on the day.