Change orders aren’t waiting for you to be ready for them. Things change in the field, a crew keeps working, and the office may not see the full picture until hours, or days, later. By then, the office is relying on someone’s memory of what happened, chasing down documentation, and trying to connect labor and materials to the right change.

A field-first change order workflow keeps the work moving and visible. When the change is captured where it happens, project managers can review it while the work is still active, and the project record stays connected to labor, materials, documentation, and billing.

Why traditional change order processes create delays

Many contractors still manage change orders through a series of handoffs between the field and the office:

• A technician sends a request to the office.
• Office staff evaluates and approves the change.
• The office creates a cost code tied to the change order number.
• Someone communicates the code back to the field.
• The crew uses the code to log hours and materials.
• The contractor compares the actual cost with the budget after the work has happened.

This process can provide all the right information eventually, but it’s also a great place for key details to get lost. The team has to wait to understand the cost and status of a change. Every handoff also creates an opportunity for information to be delayed, missed, or recorded inconsistently.

The result is often more administrative work after the fact, and a frustratingly longer path from completed work to an invoice.

What a field-first change order workflow looks like

A field-first process starts with the change itself, not with the paperwork that follows it.

1. Capture the change where it happens

When the scope changes in the field, the person who sees the change can start the request immediately. This creates a record while the details are still clear and the crew is still on the job.

2. Give the project manager visibility

The request moves to the project manager for review. The PM can determine what needs to happen next, negotiate the change when necessary, and approve the work without waiting for the project to move into a later administrative stage.

3. Keep the project record connected

Labor, materials, documentation, and billing information should remain tied to the project and its change order. That connection gives the project team a clearer view of what the change is costing as it progresses.

4. Act while the work is still active

The value of field-level capture is not just better documentation. It gives the team a chance to manage the change before it becomes an accounts-receivable problem.

5. Move the information into billing faster

When the change order record is complete and connected to the work, the office spends less time reconstructing events at the end of the job. That can shorten the time between completing work and sending an accurate invoice.

The field-to-office gap has a financial impact

Change order delays do more than create extra administrative work. They can slow billing, extend the accounts-receivable cycle, and make it harder to keep cash moving through the business.

The 2026 Torque Commercial Contractor Benchmark Report found an average project DSO of 68.1 days for contractors on BuildOps. But best-in-class contractors using BuildOps bring that figure down to 28.7 days, a 58% improvement.

The trade-level figures show why the process matters across different types of contractors:

• HVAC and mechanical: 65.6 days average DSO compared with 31.8 days for best-in-class contractors.
• Electrical: 72.9 days compared with 28.7 days.
• Fire and life safety: 87.6 days compared with 39.5 days.
• Plumbing: 69.9 days compared with 29.8 days.

A faster billing cycle can also release working capital. The report cites an example in which moving from 68 days DSO to 29 days on a $5 million project portfolio releases more than $530,000 in working capital.

What connected change order management changes

“We used to be two weeks behind on job costing. Now we're up to date daily,” said Jason Thompson, founder and president of Layer One.

When information moves more completely from the field to the office, the project team can spend less time finding missing details and more time managing the work. A connected process can help teams:

• Give the PM a complete starting point for reviewing the change.
• Keep labor and materials tied to the right work.
• Attach documentation while the project is active.
• Identify cost and billing issues before closeout.
• Reduce the time between field activity and invoicing.

And according to Brent Larson, member-owner and CFO of BP Mechanical,

"We can even initiate change order requests at the field level—allowing our project managers to remain aware of those changes, and negotiate accordingly.”

Find the leak in your change order process

If billing cycles are longer than they should be, look at what happens between the field and the invoice. Ask:

• Is a change order sitting in limbo while the crew continues working?
• Is labor difficult to tie cleanly to a change?
• Does documentation arrive after the billing window?
• Is the project complete except for the paperwork needed to get paid?

These questions help pinpoint whether the problem is the change order itself or the handoffs around it.

A field-first workflow gives contractors a practical way to address the gap: capture the change where it happens, give the PM visibility, keep project information connected, and move the completed record into billing without rebuilding it later.

BuildOps is designed to support that workflow. Field teams can capture changes where they happen, project managers can review and act on them, and labor, materials, documentation, and billing can stay connected to the project record.

The goal is simple: track change orders while the work is happening, not after the details, and the billing opportunity, have already moved on.