JOC Procurement

JOC Task Order vs Change Order: What's the Difference?

6 min read · PreCon JOC

In Job Order Contracting, the task order and the change order serve completely different legal purposes. Confusing them — or using them interchangeably — is one of the most common sources of audit findings and contractor disputes. This guide explains what each instrument is, when to use it, and the specific compliance risks that arise from misuse.

The core distinction

Task Order

A new, independent unit of work issued against the master JOC contract. Each task order is its own scope, its own line-item proposal, its own approval, and its own payment event. Task orders do not modify the JOC contract — they execute it.

Change Order

A modification to an already-issued task order — adding scope, removing scope, changing quantities, or adjusting timelines after the original task order was approved. Change orders modify an existing obligation; they do not create a new one.

The practical rule: if the work was not in the original task order, you generally have two options — issue a new task order or issue a change order to the existing one. Which is correct depends on whether the new work is a natural extension of the same scope or a genuinely separate project.

When to issue a task order

Issue a task order when you have a defined, self-contained scope of work to give to the awarded JOC contractor. Task orders are appropriate for:

Each task order requires a GC line-item proposal, an independent cost estimate (above your program's threshold), and formal written approval before work starts. The task order is the foundational document that creates the payment obligation — without it, there is no authorized expenditure.

When to issue a change order

Issue a change order when conditions on a task order that is already in progress require a modification. Legitimate change order triggers include:

A change order adds line items or modifies quantities using the same coefficient structure as the original task order. The GC cannot apply a different coefficient on change order work — the awarded coefficient is locked for the life of the JOC contract, including all modifications.

The compliance traps

HIGH

Using change orders to avoid the task order dollar limit

If your program caps individual task orders at $500K, issuing a $400K task order and then immediately modifying it to $750K with a "change order" is a circumvention of the limit. Auditors look at the original task order total plus all modifications and treat the aggregate as the true task order value. If the aggregate exceeds the limit, the entire task order may be considered unauthorized.

HIGH

Issuing change orders for unrelated work

Adding a completely new scope to an existing task order — a gym floor renovation added to an HVAC task order because the GC is already on site — is not a change order. It is a new task order using the change order mechanism to avoid the independent cost estimate, approval, and proposal requirements. This is a frequent audit finding.

HIGH

Backdating task orders or change orders

Issuing a task order or change order after work has already begun — and backdating the document to make it appear the authorization preceded the work — creates both an audit finding and potential legal exposure. Work that starts without a task order is unauthorized expenditure regardless of when the paperwork is completed.

MEDIUM

Skipping the independent cost estimate on change orders

Some programs require an ICE only on new task orders, not on change orders. If your change order adds significant scope — particularly NPP work or items above the ICE threshold — the same review obligation applies. A blanket policy of "no ICE required for change orders" is a compliance gap.

MEDIUM

No change order approval chain

Task order approvals have clear authority levels (the same people who approved the original task order must approve modifications above a threshold). If change orders are approved informally — by email, verbally, or by field staff who don't have authorization authority — there is no defensible record when the modification is questioned.

Decision framework: task order or change order?

When new work arises on an active JOC contract, run through these questions in order:

01. Is there a task order already open for related work at the same facility?

Yes →Consider a change order if the new work is directly related to that scope.
No →Issue a new task order.

02. Would adding this work to the existing task order exceed the program's task order dollar limit?

Yes →Issue a new task order — do not modify the existing one.
No →Either instrument may be appropriate; continue to the next question.

03. Is the new work a natural continuation of the existing scope, or a separate project?

Yes →Change order if continuation; new task order if separate project.
No →Issue a new task order for clearly distinct projects.

04. Has any work already started?

Yes →Stop. Do not issue either instrument retroactively. Escalate to procurement and legal.
No →Proceed with the appropriate instrument and ensure approval precedes work start.

Change order limits and your solicitation

Your JOC solicitation and contract should specify change order limits — both a per-change-order dollar ceiling and a cumulative ceiling as a percentage of the original task order. Common thresholds are:

If your solicitation doesn't define change order limits, now is the time to establish them in your program procedures — before an auditor asks why a $200K task order ended up at $600K through five sequential modifications.

Task order management

Track task orders and modifications in one place

PreCon JOC logs every task order and change order with timestamps and approvals. The audit trail shows original value, all modifications, and the running total — so you can see change order accumulation before it becomes a problem.

Set up your program →