The work is finished. The office opens the job record and finds a change mentioned in a message, a photo without context and a note that says “agreed”. Which version belongs in the invoice review?
That is an illustrative situation, not a report about a customer. It highlights a useful distinction: a completed task, an approved change and a reviewed invoice are separate things. A practical review pack connects them without asking the reviewer to reconstruct the whole job from scattered messages.
For a plumbing or heating firm, I would start with a small checklist. Keep the original scope, the exact change, its approval, the relevant completion evidence and one named reviewer together. This is a proposed operating method, not legal advice or a promise about payment.
Start with the agreed scope
Keep the scope or quotation version that the job started from. Give it a clear reference and date. The reviewer needs a baseline before deciding what changed.
Do not quietly overwrite that baseline with the latest description. Keep the relationship visible: original scope, later change and current agreed version. A short reference can be enough, provided the underlying document remains accessible to the people who need it.
If the original record cannot be found, mark that gap explicitly. An empty field should not become an assumed agreement.
Describe the change precisely
“Extra work” leaves too much for the office to interpret. Record what was added, removed or altered, and which job or work area it concerns. Include any agreed price or timing effect when that forms part of the change record.
For example, an illustrative record might say: “Replace the specified radiator with the alternative model recorded in change C-02.” The example is deliberately narrow. The actual job record would need the relevant specification and agreement, not just this sentence.
Separate the requested change from an approved change. A request in a message should not acquire an approved label simply because somebody copied it into a spreadsheet.
Keep approval beside the change
Record who approved the change, what they approved, when they did so and where the supporting record can be found. Use the approval route agreed for that job. A name or a tick on its own does not explain the scope of an approval.
Where the record is incomplete, use a visible status such as “approval evidence missing” and assign someone to resolve it. Keep that status distinct from “approved” and “ready for review”.
This checklist does not decide whether a particular agreement is legally sufficient. It helps the office see the evidence it has and the questions still open.
Attach evidence that explains the work
A completion photo is more useful when the reviewer can tell which job, area and change it relates to. Link relevant photos, notes or other required records to that change instead of dropping everything into a general folder.
The evidence should match the question being reviewed. A photograph may show a fitted item; it does not by itself establish approval of a price change. A note saying “done” does not replace a required inspection or sign-off.
Use your actual job requirements to decide what belongs in the pack. Avoid collecting unrelated personal information or treating extra files as proof of completeness.
Give the review a named owner
The final handoff should say who reviews the pack and what happens if something is missing. A simple pair of states can help: “ready for invoice review” and “needs information”. Neither should mean that an invoice has already been checked or sent.
Before handing over, ask one question: could the named reviewer follow this change from the original scope to approval and completion evidence without guessing?
If the answer is no, record the missing item and its next owner. If the answer is yes, the pack can move to the business’s normal invoice review process. That remains a human decision under the firm’s own commercial and accounting rules.
Test the method before adding software
Try the checklist on one job using the tools you already have. Observe where the record breaks: missing version, unclear approval, unrelated photo or unassigned review. Do not assume a new platform fixes a process that has not been defined.
If existing tools leave a confirmed gap between the office and the field, a custom operations platform may be worth scoping around that specific handoff. The useful starting point is the record and responsibility you need, not an unsupported claim that software will guarantee quicker payment.