Feature Focus

Finishing the Work and Proving It Are Two Different Jobs

Zigaflow2 September 20266 min read
Invoices3 overdue
Acme Merchandise Ltd£12,480Paid
BlueSky Promos£3,760Sent
Horizon Events£8,940Overdue
Vertex Group£5,120Ready to Invoice
Promo World Ltd£2,380Sent

Work ends with a verbal thumbs up and a job sheet that arrives at the office days later, if it arrives at all. When the invoice goes out and the customer remembers things differently, there is no signed record from completion day to resolve it quickly.

A job ends the way most jobs end: the work is done, the site looks right, the customer says something like "looks great, cheers." The engineer packs up and leaves. The paperwork - if there is any - goes in the van, gets transferred to a bag, arrives at the office days later with one field missing and no customer signature. The invoice goes out the following week. Three weeks after that, the customer calls to say the scope was not what they expected, or a line item does not match their understanding of what was agreed. The work was finished. The proof of it was not captured at the right moment.

The Gap Between Done and Signed

The moment a job ends and the moment it is formally closed are rarely the same thing. Between them lies a process that most field service businesses have never properly designed: capturing what was done, what the customer accepted, and what the agreed basis for billing actually was.

In practice, it usually works like this. An engineer or installer finishes the job. The customer says they are happy. The engineer notes a few things on a job sheet or not at all, because the customer seems satisfied and everyone is in a hurry. The sheet goes back to the office - eventually - and someone tries to turn it into an invoice.

What is often missing from that sheet: the customer's signature confirming acceptance. A clear list of the specific tasks completed. Before-and-after photos of the finished state. The purchase order reference the customer's accounts team will need before they can approve payment. When those things are absent, the invoice either goes out late or goes out and comes back with questions attached.

Research by Fieldmotion into field service operations found that customer signature is the single most important field on a job sheet - and consistently the one most often skipped. A signed sheet is the customer confirming, at the time of completion, that the work was done. Without it, a business is in a significantly weaker position when a customer later disputes the invoice, the quality of the work, or whether specific items were completed at all.

The dispute-friendly window

Customers rarely raise concerns while the engineer is still on-site. Issues tend to surface later - when the invoice arrives and the customer has had time to reconsider, or has encountered a subsequent problem. At that point, the contemporaneous record of what was agreed on the day is the only reliable protection.

What a Disputed Invoice Actually Costs

The numbers on late payment give the sign-off problem some scale. According to Xero Small Business Insights data, 52% of UK SME invoices were paid late in 2024. The Federation of Small Businesses estimates that the average UK small business carries around £22,000 in overdue invoices at any one time.

Not all of that is disputed work - some reflects slow payment, some reflects genuine cash flow pressure on the customer side. But a significant portion of held or late invoices involves some form of query, challenge, or information gap that prevents payment from being processed promptly. When a customer questions what was done, or says the work did not match what they understood was agreed, payment stops until the issue is resolved.

Resolving it is not free. It takes someone's time to pull together evidence, re-attend site if necessary, correspond with the customer's procurement team, and manage the relationship while doing so. Analysis of manual invoice processing cited by Fieldmotion found that approval cycles routinely run to two weeks or more when paper-based processes are involved. Two weeks on a completed job is two weeks of working capital tied up on work that has already been delivered.

Multiply that across job volume. A business running fifty jobs a month, with even a modest proportion triggering queries, carries a recurring cash flow drag that has nothing to do with the quality of the work itself. The cost is not the invoice amount in dispute - it is the time and delay compounding across every other job running alongside it.

Why Paper Sign-Off Fails at the Handoff Points

Paper-based completion processes fail at every handoff. The form does not make it back to the office. The signature field is blank because the customer was not available when the engineer left. The photos were taken on a personal phone and never transferred. The description of work done says "electrical installation, second fix" rather than specifying circuits, cable routes, and test results.

When a dispute comes in, that paper record - even when it exists - is disconnected from everything. It is not in the job record. It is not attached to the invoice. It may not be findable at all. And if a customer wants to push back on an invoice, the absence of a traceable, timestamped record of what was accepted on the day makes that challenge considerably easier.

This is a pattern that runs earlier than the invoice. As the piece on invoice disputes describes, the conditions for a disputed invoice are set up long before the invoice is raised. A job record with no sign-off attached is a job record waiting for a query.

Connect, do not file separately

Every piece of completion documentation - sign-off form, photos, test results, purchase order reference - should attach directly to the job record the moment it is captured on-site. If it goes into a separate folder, it will not be retrieved quickly when it matters.

What Digital Completion Capture Changes

The right moment to capture proof of completion is while the customer is still on-site. Once the engineer leaves, that moment is gone.

Digital completion forms on a mobile device change the equation. An engineer finishes the work, opens the form on a phone or tablet, records what was done in structured fields, attaches photos, and requests a customer signature on screen. The customer signs. The form submits and attaches directly to the job record. The office can see it immediately.

The customer confirmed sign-off at 3pm on a Wednesday. If they call the following month to question the invoice, there is a timestamped record showing exactly what they confirmed as complete, signed, on that day. The dispute has nowhere to go because the evidence exists at the point it was created - not reconstructed afterwards.

This changes more than the dispute outcome. When completion data flows directly into the job record, invoicing can start immediately rather than waiting for paperwork to return and be interpreted. The invoice goes out the same day or the next morning, not a week later. That timing matters, because invoices sent promptly are more likely to land within the customer's normal payment cycle rather than sitting in a queue until the next run.

Zigaflow's eForms feature lets businesses build custom digital forms that field teams complete on-site. Sign-off forms, site condition records, pre-start checklists, and handover documentation all attach directly to the relevant job record in the platform. When the invoice is raised, the supporting evidence is already there.

Getting customer sign-off at the right moment costs nothing. Proving after the fact that work was done, done correctly, and accepted by the customer costs considerably more - in time, in payment delay, and in the commercial relationship. The completion moment is the cheapest point in the job lifecycle to capture proof. Most businesses treat it as an afterthought.

Sources

invoice disputesjob completiondigital formseformssign-offfield service

Related pages

Ready to run your business
on one platform?

Book a free demo and see how Zigaflow fits your team.

Book a free demoView pricing