Why We Built Change Order Tracking to Start in the Field, Not the Office

The most expensive words in field service are "yeah, just do it." A customer says them on site. Your tech does the extra work. Nobody writes it down. And three weeks later, when the invoice goes out, there is nothing to back it up, no description, no photos, no written approval. The customer pushes back. The office has no record to stand on. The work gets absorbed.

This is not a billing problem. It is a capture problem. The change order was never raised where the work actually happened.

That is the design decision I want to walk through in this post: why PolarPath's change order tracking starts in the field, and why we chose that over the more obvious alternative.

The Obvious Alternative, and Why It Fails

The straightforward approach to change order management is to put the workflow in the office. The field calls in or texts the details. An admin creates the change order in the system. The PM or owner approves it. Then it gets billed.

That flow feels organized. It is not.

The problem is the handoff. Between "the tech mentions extra work" and "the admin creates the record," you have a phone call, a text thread, a sticky note, or a memory. All of those are lossy. Details get simplified. Photos stay on the tech's phone. The scope gets described in one sentence instead of three. And when the customer disputes it, there is nothing concrete to point to.

Worse: if the admin is busy, the handoff sits in a queue. Now you have work that is already done with no record of it, aging by the hour. Some of it gets billed eventually. Some of it does not. You find out which is which at month end when margin doesn't match the field.

This is the status quo for most mixed service and project operations in the GTA. The crew is competent. The billing process is leaky.

The Design Decision: Raise It at the Source

When we built change order tracking in PolarPath, we made a deliberate choice: the change order has to be raiseable from the field, on the job, at the moment the extra work is identified.

Here is what that looks like in practice:

1. The crew identifies extra work on site. Before they start, they open the job in PolarPath on their phone.
2. They create the change order directly on the job record. They describe the extra scope, enter the hours or materials, and attach site photos, right there, before the work begins or immediately after it is agreed to.
3. The change order sits on the job, in an approval queue, connected to every other detail about that visit.
4. The office sees it without being called. They can track its status, pending approval, approved, billed, without chasing anyone for the details.

That last point matters more than it sounds. The office is not re entering information. They are not trying to reconstruct scope from a text message. They are looking at a record the tech already built, with photos attached, waiting for action.

What "Attached to the Job" Actually Means

A change order that lives in a separate document, a separate email chain, or a separate spreadsheet tab is not really attached to the job. It is attached to the person managing it. When that person is busy, sick, or gone, the change order is effectively invisible.

In PolarPath, the change order is part of the job record itself. It does not float. It cannot get orphaned in someone's inbox. The connection between the extra work and the invoice that needs to go out is structural, not personal.

This matters especially for the mixed service and project reality that most of our customers operate in. A facilities management team handling reactive service calls AND multi week mechanical projects cannot afford two different informal processes for tracking scope changes. The reactive side generates verbal change orders constantly. The project side generates formal ones. Both need to end up billed. One platform, one place to track both.

The Tradeoff We Accepted

Raising the change order in the field puts more responsibility on the tech. They have to document the extra scope before or right after they do the work, not later.

That is a real operational ask. It requires training. It requires the mobile experience to be simple enough that doing it on site is not friction. And it requires that field staff understand why the record matters, not just that they were told to fill it out.

We accepted that tradeoff because the alternative is worse. An office initiated workflow sounds easier on the tech, but it creates a gap between work done and work recorded. That gap is where revenue disappears.

The practical answer for operations leads and owners: when you roll out field raised change orders, spend ten minutes with your techs explaining what happens when a change order does not get recorded. Show them a specific example from your own jobs. The behaviour change comes faster when people understand the cost, not just the process.

A Simple Checklist for Better Change Order Capture

Whether you use PolarPath or not, these habits close most of the gap:

• Describe the scope in writing before the work starts, not after. Memory degrades fast once the crew is on to the next job.
• Attach at least one photo. A photo of the existing condition and one of the completed work removes most disputes before they start.
• Get a written or digital acknowledgment from the customer on site. A text reply saying "yes go ahead" is a record. A verbal nod is not.
• Track every change order's status explicitly: raised, approved, invoiced. "We talked about it" is not a status.
• Review unbilled change orders weekly. Monthly is too slow. Work done in week one can hit your cash flow by week five if the billing lag compounds.

Closing Thought

The change order problem in field service is not that contractors are bad at billing. It is that the moment the extra work is agreed to, on a rooftop in Mississauga, in a mechanical room in North York, at a loading dock in Scarborough, there is no system waiting to catch it. The system is back in the office, and the office was not there.

PolarPath puts the capture exactly where the agreement happens. The office gets a record they can act on. The field does not have to call it in. And the work that got done actually makes it onto an invoice.

If unbilled change orders are a recurring problem in your shop, that is where to start looking: not at billing, but at capture.

See how change order tracking fits your operation at polarpath.ca.