Has the Job Been Finished? Keep Office & Field Teams in Sync

“Has the Job Actually Been Finished?” How Trade Businesses Keep Office and Field Teams in Sync

You create the job.

Assign it to a worker.

They leave for site.

Then the questions begin.

Did they receive the job?

Have they arrived?

Has the work started?

Are they still there?

Did they take photos?

Has the job actually been completed?

Is there anything I need to know?

And finally:

Can I invoice it yet?

When you are a sole trader, most of those answers live in your own head.

When you start running two, three, five or ten people across different customer sites, that stops working.

Suddenly the owner or office spends part of the day:

calling workers

sending WhatsApps

asking for photos

chasing job updates

and:

trying to work out which completed jobs are ready to invoice.

That is the office-to-field communication gap.

And it is a very real problem for growing trade and field-service businesses.

Field-to-office communication is still an operational problem in 2026

This isn't just a software-company invention.

A February 2026 analysis of contractors managing multiple crews described managers repeatedly calling, texting and sometimes travelling to sites simply to find out what was happening, because information from field workers was not reaching the office in a structured way.

A UK-focused March 2026 field-service analysis identifies similar problems: jobs waiting to be invoiced because the office does not have the information it needs, staff chasing job updates, handwritten job sheets and uncertainty over whether work has actually been billed.

There is even a very practical UK example in a July 2026 Mitie job description. The contract coordinator role explicitly includes chasing engineers and subcontractors for maintenance reports, following up open jobs and ensuring completed work orders and documentation have been returned.

These sources do not establish a national percentage of UK tradespeople experiencing the problem.

But they describe the same operational failure repeatedly:

What happens on site is not automatically visible to the people running the business.

The problem isn't necessarily communication. It's visibility.

Your worker may be doing everything correctly.

They know:

I received the job.

I started at 1:06pm.

I found the leak.

I photographed the repair.

I've finished.

The owner doesn't automatically know those things.

So the owner asks.

Again.

And again.

That turns ordinary job management into constant interruption.

A better system should make the important job states visible:

Assigned

↓

Scheduled

↓

In Progress

↓

Evidence Added

↓

Completed

↓

Ready to Invoice

The worker updates the job.

The business record updates with it.

One underground leak: follow the job from office to field and back

Let's use one real Love Invoicing example throughout this article.

The owner creates:

Customer: ACME LTD

Job: Under ground leak

The job can then be scheduled and assigned to the worker.

That is where the handoff begins.

The worker should not need a phone call to know they've got a job

Once work is assigned, the field worker needs to know:

What is the job?

When is it?

Where am I going?

Traditional process:

“Josh, I've WhatsApped you that leak job for tomorrow.”

Then:

“Did you see it?”

Then:

“What time did I say again?”

A structured workflow is much cleaner.

In this example, the worker receives:

New job assigned

Under ground leak has been assigned to you for Tue 25 Aug, 12:30–13:30.

This separation matters

The owner and field worker do not need identical software experiences.

The owner needs to manage:

• customers;
• jobs;
• quotes;
• invoices;
• payments;
• teams;
• and the wider business.

The field worker primarily needs the information required to carry out the work they have been assigned.

That is why Love Invoicing uses a main business app together with a dedicated Love Invoicing Team experience for field workers.

The goal isn't to expose the entire business to everybody.

It is to give each person the information relevant to their role.

“Has Josh started yet?”

This is the question that begins wasting the owner's time.

Without job-status visibility:

Call Josh.

No answer.

He's working.

Send WhatsApp.

Wait.

Call again later.

But once the worker starts the job, the operational status can change to:

In Progress

The main business app can then show that status against the job.

Job status is more useful than “he's probably there”

This distinction matters.

There are different questions an owner might want answered.

Where is the worker?

That's a location question.

Has the worker started the job?

That's a workflow-status question.

What did the worker actually do?

That's an evidence question.

Has the job finished?

That's a completion question.

Can I bill the customer?

That's a commercial question.

Trying to answer all five through WhatsApp is where things become messy.

A proper field service job tracking system should keep those questions connected without pretending they are the same thing.

Optional live location answers a different question

Where authorised location sharing is enabled, Love Invoicing can also provide live worker location visibility.

Your Live Tracking example shows a selected team member displayed on a map together with a recent location update and directions.

That can help answer:

Where is the authorised worker right now?

But location should not be confused with job completion.

A dot on a map does not prove a job has been done.

That is what job status and evidence are for.

The field worker starts the job

Once the job is started, the worker can see the operational record.

Your example contains:

JOB-2026-0028

ACME LTD

Under ground leak

In progress

Josh Greenwood

13:06–14:30

and:

Complete Job

That gives the worker a defined job record rather than a collection of instructions in a chat thread.

The next question: “Did you take photos?”

This is one of the biggest office-to-field handoff failures.

Worker finishes.

Owner asks:

“Have you got photos?”

Worker:

“Yeah.”

Owner:

“Can you send them?”

Then five photographs arrive through WhatsApp.

Maybe with another customer's photographs between them.

Maybe two days later.

Now someone in the office has to work out:

Which job do these belong to?

Instead, evidence should be captured against the actual job.

Worker uploads the evidence

Your screenshots show the field worker adding evidence directly against JOB-2026-0028.

The worker can choose:

Photo

or:

Note

and add photographs from the camera or gallery.

In this example, five photographs documenting the underground leak are uploaded.

The worker can confirm that the evidence is attached

Your next screenshot still shows the worker-side job record.

It displays:

Evidence (1)

and:

Josh Greenwood

25 Aug at 13:12

5 photos

That means the evidence is no longer simply somewhere on Josh's phone.

It belongs to:

JOB-2026-0028

Then the field worker completes the job

When work is finished, the important action isn't:

“WhatsApp the boss and say I'm done.”

It is:

Complete Job

That creates a structured status change.

Your workflow then produces a completion notification:

Job completed

Under ground leak is complete. Create the invoice now.

That is exactly the office-to-field handoff we are trying to improve.

“Completed” and “invoiced” are not the same thing

This is another important operational distinction.

The job might be complete.

But the customer may not have been invoiced yet.

Your main-app job card makes that visible:

Completed

1 evidence entry

Not invoiced

with:

View Evidence

and:

Create Invoice

That is excellent operational information.

The office can now see:

The field work is finished.

Evidence exists.

The commercial next step is invoicing.

Now the crucial part: the owner can see the worker's evidence

This is where the two evidence screenshots must not be confused.

Earlier, we showed:

Worker view

Josh uploading the evidence.

Now we show:

Owner view

The main-app user reviewing the evidence Josh submitted.

The owner sees:

1 entry

5 photos

1 contributor

1 with location

and:

Josh Greenwood

together with the photographs and captured location coordinates.

That closes the information gap.

The owner doesn't need Josh to resend the photos.

They are already attached to the completed job.

Location-backed evidence gives context to the photograph

A photograph alone tells you:

Something was photographed.

A job-linked photograph gives you more context:

Which job?

Which worker submitted it?

When?

And where location information has been captured:

Where was the evidence recorded?

Your example displays coordinates against the evidence entry.

That creates a more useful job record than five photographs arriving in a WhatsApp chat with no structured context.

Location access should, of course, be used transparently and in accordance with the permissions, policies and legal requirements relevant to the business.

The owner can turn the completed job into a Job Report PDF

This is where the workflow becomes especially useful.

From the evidence screen, the owner can select:

View Job Report PDF

The actual report you uploaded contains:

• the job reference;
• completion status;
• customer;
• job title;
• job type;
• start and end date;
• job location;
• completed location;
• assigned worker;
• and the uploaded evidence photographs.

The example report is for JOB-2026-0028, prepared for ACME LTD, and identifies Josh Greenwood as the assigned worker. The report also includes the location information and GPS values alongside the evidence photographs.

That is a much stronger handover than:

“Josh said the leak was fixed.”

The Job Report PDF is more than a photo dump

Your actual two-page report demonstrates the difference.

Page 1 provides the structured job summary and identifies the assigned worker and completion details.

The evidence photographs continue through the report, with GPS information displayed below them.

That means the business has a portable record containing both:

job information

and:

evidence of the completed work.

This can be useful internally and can also provide a clearer record for customers where appropriate.

And the owner can send the report

Once the Job Report PDF has been generated, it does not have to stay inside the app.

Your screenshots show the device's sharing options being opened for:

JOB-2026-0028-epod.pdf

Available sharing destinations depend on the device and installed apps, but your example includes options such as:

Mail

Messages

and:

WhatsApp

The following screenshot then shows the PDF attached to a new email.

So the office can move from:

Worker completes job

to:

Owner reviews evidence

to:

Job Report PDF

to:

Send the report

without asking the field worker to manually reconstruct the job afterwards.

The complete office-to-field workflow

Now look at the entire journey.

OWNER

Create Job

↓

Schedule + Assign Worker

↓

WORKER

Receives Job Notification

↓

Starts Job

↓

OWNER

Sees In Progress

↓

WORKER

Adds Photos / Notes

↓

Completes Job

↓

OWNER

Sees Completed

↓

Sees Not Invoiced

↓

Reviews Worker Evidence

↓

Reviews Location Information

↓

Generates Job Report PDF

↓

Shares Report

↓

Creates Invoice

That is the real answer to the office-field communication problem.

This isn't about micromanaging workers

There is an important distinction here.

Good field-service software should not turn the owner into somebody staring at workers all day.

The objective is not:

“Watch Josh every second.”

The objective is:

Give the business enough operational visibility that normal questions don't require interruptions.

If the job says:

In Progress

there is probably no need to phone.

If it says:

Completed

there is probably no need to ask whether the work finished.

If five photographs are already attached:

there is no need to ask Josh to send them.

If the job is:

Completed — Not invoiced

the owner knows exactly what needs attention next.

That is the difference between visibility and micromanagement.

Five phone calls the system should help eliminate

1. “Did you get the job?”

Assignment notification answers that part of the workflow.

2. “Have you started?”

The job can move to In Progress.

3. “Did you take photos?”

Evidence stays attached to the job.

4. “Have you finished?”

The job moves to Completed.

5. “Can I invoice it?”

The owner can see Completed / Not invoiced and move directly to Create Invoice.

Each individual call is small.

Across several workers and several jobs every day, they become a management system made entirely of interruptions.

WhatsApp is communication — it shouldn't have to be your job database

WhatsApp is useful.

Your customers probably use it.

Your workers probably use it.

There is nothing inherently wrong with that.

The problem starts when you need to search through messages to establish:

Who had the job?

When did they start?

Which photographs belong to it?

Was it completed?

Who uploaded the photos?

Can we invoice it?

A messaging app can help people talk.

A structured job record should tell the business what happened.

What should field service job tracking software show?

If you are looking for job tracking software for tradespeople, don't judge it only by whether it has a calendar.

Ask whether the office can answer these questions:

Who is assigned?

The job should identify the worker.

Did they receive the work?

The worker should have a clear assignment workflow.

Has the job started?

Status should show whether work is scheduled or underway.

What happened on site?

Photos and notes should remain attached to the job.

Who submitted the evidence?

Contributor information matters.

Has the work finished?

Completion should be visible.

Is it ready for invoicing?

Operational completion and invoicing status should not be confused.

Can I produce a record?

A structured report is valuable where the work needs documenting.

That's a much more useful test than:

“Does it have lots of features?”

Why this becomes more important as the team grows

With one worker, the owner may know everything.

With two workers:

manageable.

With five:

information starts fragmenting.

With ten:

the owner cannot possibly be present on every job.

CompanyCam's 2026 discussion of contractor communication describes exactly that management problem: once several crews are operating, visibility across sites becomes more difficult and managers resort to calls, texts and site visits to stay informed.

A growing trade business therefore needs a transition:

Information in the owner's head

↓

Information in workers' messages

↓

Information attached to the job itself

That is the scalable version.

Faster completion visibility can also mean faster invoicing

There is a financial consequence to poor field communication.

Imagine Josh completes the leak on Tuesday.

The owner doesn't know until Thursday.

Photos arrive Friday.

Invoice gets created Monday.

The customer's payment terms haven't even started until nearly a week after the work finished.

A current UK field-service source specifically highlights unsent invoices as one consequence of operational processes that fail to move completion information efficiently back to the office.

This connects directly to another principle we've discussed:

Finish the administrative workflow closer to when the physical job finishes.

If the office can see:

Completed

and:

Create Invoice

the commercial process can continue sooner.

Love Invoicing's approach

Love Invoicing connects two sides of a field-service business.

Main Love Invoicing app

Used by the owner or appropriate business user to manage the wider operation.

Love Invoicing Team

Used by field workers for the work relevant to them.

That allows a workflow where the owner can:

• create and schedule the job;
• assign the worker;
• see job status;
• see who is assigned;
• review submitted evidence;
• see location-backed evidence where captured;
• generate the Job Report PDF;
• share that report;
• and continue to invoicing.

While the field worker can:

• receive the assigned job;
• open their work;
• start it;
• add photos or notes;
• and complete it.

The value is not merely having two apps.

The value is the handoff between them.

Frequently Asked Questions

What is field service job tracking?

Field service job tracking is the process of monitoring the operational state of work being carried out away from the office, including assignment, scheduling, job status, completion and supporting field information.

How can I know when a field worker has started a job?

A structured job-management workflow can change the job from Scheduled to In Progress when work begins. In Love Invoicing, the owner can see the resulting job status in the main business workflow.

How can I stop chasing engineers for job updates?

Move the updates into the job record. Assignment, In Progress status, evidence and completion should be recorded against the job so routine questions do not require repeated calls or messages.

Can Love Invoicing notify a worker when a job is assigned?

Yes. The worker-side example shown in this article receives a New job assigned notification containing the job and scheduled time.

Can the owner see whether the worker has started the job?

Yes. Once the job is updated to In Progress, the main app can show that status together with the assigned worker.

Can field workers upload job photos?

Yes. Workers can add evidence against a job using photos or notes.

Can the owner see photos uploaded by the worker?

Yes. This is an important distinction in the workflow: the worker uploads the evidence in their job workflow, while the owner can later review that evidence against the same job in the main app.

Can I see which worker uploaded the evidence?

The evidence example shown in this article identifies Josh Greenwood as the contributor to the uploaded photographs.

Can job evidence contain location information?

Where location information is available, permitted and captured, evidence can retain associated location data. The example Job Evidence record displays a captured location and the generated report includes GPS information.

Can Love Invoicing create a Job Report PDF?

Yes. A completed job with evidence can be used to generate a Job Report PDF containing structured job information and supporting evidence.

What information is included in a Love Invoicing Job Report PDF?

The example report includes the job number, customer, job title, job type, dates, job location, completed location, assigned worker and evidence photographs with GPS information.

Can a Job Report PDF be sent to a customer?

The generated PDF can be shared using compatible sharing options available on the device. Your example shows Mail, Messages and WhatsApp options, as well as the PDF attached to a new email.

Can the office see that a job is complete but hasn't been invoiced?

Yes. Your completed job example displays both Completed and Not invoiced, with a Create Invoice action.

What is the difference between live worker tracking and job evidence location?

Live tracking answers where an authorised worker is currently located while tracking is enabled. Evidence location provides location context associated with a recorded evidence entry. Neither should be confused with the job's completion status.

Is GPS tracking required for job management?

No. Job assignment, status, evidence and completion are separate concepts. Location features should only be used where appropriate and with the necessary permissions and transparency.

Is field service software useful for small trade teams?

It can become increasingly valuable when an owner manages several workers or simultaneous jobs and begins spending significant time chasing assignments, updates, photographs or completion information.

What software can plumbers use to manage field workers?

Plumbing businesses can use field-service or job-management software that connects scheduling, worker assignment, job status, evidence, completion and invoicing. Love Invoicing is designed around this connected workflow.

What software can electricians use to track jobs?

Electricians can use field-service job tracking software to manage assigned work, job status, evidence and completion across mobile workers. Love Invoicing supports these workflows through its main and Team apps.

Can job completion automatically mean the invoice has been sent?

No. Job completion and invoicing are separate business states. That distinction is useful because the owner can see that work is completed but still needs invoicing.