Straight into the service manual page
WrenchQuarry
More

Unit-price quantity changes: 3 limits to check

WrenchQuarry Editorial Team · Published · 12 min read · How these guides are written

When a unit-priced job runs above or below its estimated quantity, check three limits: the 15 percent band, the cost basis and the ten-day deadline. If you bid a unit-priced job, you agreed to a simple deal: the agency pays a fixed amount for each unit of work, and the bill is the unit price times the number of units you actually do. The estimate on the bid sheet is only a guess at those units. When the real count lands far from the guess, the money changes too, and the contract has to say how much room there is before someone can ask for a change.

Key takeaways

  • Check each unit-priced line against the 85 and 115 percent marks.
  • Measure any adjustment by the cost change caused solely by the variation.
  • Count the ten days from the beginning of the delay, and make the request in writing.

For a federal contract, the clause that handles this is FAR 52.211-18, Variation in Estimated Quantity. It is short, and it sets out three limits that matter on the dispatch floor as much as in the front office: the band that triggers an adjustment, what the adjustment is measured against, and a deadline for asking for more time when the extra work stretches the schedule. Work through each one before you accept a unit-priced award, and again when quantities start moving in the field.

This post walks through those three limits in plain words. It does not replace reading your own contract. Clauses get changed, added, and dropped, and state and local agencies write their own versions of this idea. Use the quotes here as a starting point for one question: what does my contract actually say?

Limit 1: the 15 percent band

The first limit is the trigger. The clause comes into play when the actual quantity of a unit-priced item varies more than 15 percent above or below the estimate. FAR 52.211-18 puts it this way: if the quantity of a unit-priced item is an estimated quantity and the actual quantity varies more than 15 percent above or below it, an equitable adjustment in the contract price shall be made upon demand of either party.

Read that twice. A small overrun that stays inside the band does not qualify. Neither does a modest shortfall that stays inside it. The clause is not saying the price changes whenever the count moves. It is saying that a quantity swing beyond a set band is the event that opens the door to an adjustment.

For a dispatcher, the practical point is that the band is measured against the estimate in the contract, not against what the team thought the job would be after a walk-through. The band is a fixed reference, and the crew's sense of the job does not move it.

Keep a running count by line item, against the contract estimate, not against the job plan. Many field crews track units in a shop log or a dispatch note, and those numbers drift from the contract line over time. A unit might be split across two tickets, or a subcontractor's work might be counted under a different item. Reconcile the log to the contract quantity every week or so, and you will see the band coming before you are inside it.

Watch for items that are counted in more than one way, too. If the contract line and the work order use different units, convert them once, write the conversion down, and use the same conversion every time. A band check only works when both sides of the comparison mean the same thing. A mismatch in units looks like a quantity problem, and it is much harder to explain later than it is to prevent now.

Limit 2: what the adjustment covers

The second limit is what the adjustment is based on. Once a variation passes the band, the clause does not say the price simply moves up or down by the percentage of overrun. FAR 52.211-18 says the equitable adjustment "shall be based upon any increase or decrease in costs due solely to the variation above 115 percent or below 85 percent of the estimated quantity."

Two words in that quote do most of the work. The first is "costs." The adjustment tracks cost change, not revenue change. The second is "solely." Only the cost change caused by the variation itself counts. Costs that would have happened anyway, or costs that came from some other cause on the job, are not part of the measure.

That has a few consequences for how you prepare. First, a band breach is not an automatic payday. You are not entitled to the overrun multiplied by your unit price just because the quantity went up. You are entitled to an adjustment that reflects the cost difference the variation caused. Second, the clause measures both directions. If the quantity falls below 85 percent, your costs may have dropped in some ways, such as fewer materials or less equipment time, and the clause accounts for that as well. Third, the adjustment is about the extra cost of the variation, so your records have to show what the variation cost you.

Good records look like ordinary field records, kept consistently. Keep material tickets tied to the line item they serve. Keep crew hours by job and by line. Keep equipment logs under the same job code. When a variation arrives, you then have a clean trail that separates the cost caused by the extra or missing units from the costs of everything else on the site.

Be careful about how you describe the claim. Write it in terms of cost, not in terms of lost margin or a feeling that the bid was low. The quoted clause does not talk about margin at all. A claim framed as "we are underpaid" is harder to support than one framed as "these specific costs changed because the quantity changed."

So the adjustment is driven by a demand, not by the count moving on its own. If the band has been crossed and nobody raises it, the clause as quoted does not say the contract adjusts by itself. That makes it your job to notice the band and decide whether to demand the adjustment. Put the band check on the billing checklist, and bring the issue to the contracting officer or the agency's project lead as soon as the count crosses the line.

Limit 3: the ten-day clock for more time

The third limit is about schedule. Large quantity swings do more than change the price. They can push out the finish date. FAR 52.211-18 addresses that directly: if the quantity variation causes an increase in the time necessary for completion, the contractor may request, in writing, an extension of time, "to be received by the Contracting Officer within 10 days from the beginning of the delay, or within such further period as may be granted by the Contracting Officer before the date of final settlement of the contract."

Three things stand out. The request is for an extension of time, and it has to be in writing. The clock runs from the beginning of the delay, not from the day someone on your team notices the job is late. And the window has an exception: the Contracting Officer may grant a further period before final settlement. That exception is a matter of the officer's discretion, not something you can plan around.

The practical reading is blunt. If a variation starts pushing the schedule, the start of that delay is where your ten-day count begins. A dispatcher who sees the crew falling behind on a high-quantity line should flag it that day, not at the next weekly meeting. A foreman who says "we are behind, we will catch up" has not made a written request. A supervisor who logs the delay in the daily report and sends a note to the project lead does not satisfy the clause, because that note is internal and never reaches the Contracting Officer. The written request must reach the Contracting Officer within 10 days from the beginning of the delay, or within any further period the officer grants before final settlement.

Set up a simple rule. When any line item passes a planned completion point, or when a crew falls behind on a line that is running high, the dispatcher starts a written note with the date the delay appears to have begun, the quantity to date against the estimate, and the revised completion estimate. The owner reviews it within a day. If the variation is real, the written request goes to the contracting officer in time.

Do not wait on the exception. Treat the ten days as the working deadline, and treat anything beyond it as a favor you may or may not receive.

Illustrative example: a trench line

Say the contract estimates a conduit run priced by the foot, at 100 feet. The band is measured against that estimated quantity, so the 85 percent and 115 percent marks both come from that one number. Suppose the crew finishes at 90 feet, which is 90 percent of the estimate, inside the band.

Keep the arithmetic simple and written down. Divide the actual count by the estimate, multiply by 100, and record the result beside the date.

A line whose actual quantity lands above the 115 percent mark may have a claim, subject to the cost basis and the timing rule in the clause; a projection alone does not create one. Once the actual quantity is below the 85 percent mark, the line is outside the band on the low side, and the same clause applies to it.

Timing the delay

Now the schedule side. If the extra quantity means the crew needs more time than planned, the question is when the delay began. Whether that was the day the crew first fell behind the planned pace, or the day the count crossed a mark, is a question for your contract and for the contracting officer. The safe working assumption is the earliest date you can show the crew falling behind on that line. A dispatcher who waits for the count to cross the band before writing the delay note may have given up days from the window. That is why the cost check and the schedule check belong together.

Working the three limits on an actual job

Now put the three limits together. Start with the contract's estimated quantities for each unit-priced line. Write down the 85 and 115 percent marks for each line. The list is short, and you can keep it in a spreadsheet or on a whiteboard in the office. The point is that every line has a trigger you can see from a distance.

Next, pick a check cadence. Once a week is a reasonable default for most field-service work, and more often for a line that is running fast or slow. At each check, compare the actual count to the estimate. If a line is within the band, note it and move on. If a line is approaching the band, flag it. If a line has crossed the band, open the cost file and the schedule note at the same time.

Be honest about what the clause does not cover. The three limits here are about quantity variation and the time it causes. A scope change, a site condition, a change in the specification, or a delay caused by the agency's own work may raise a different issue under different terms. Read your contract for those. Do not stretch a quantity clause to cover a problem that belongs somewhere else, because that is how a good claim gets weakened.

Keep the owner in the loop, even if the owner is the person who signed the bid. The owner needs to see three things: the quantity to date against the estimate, the cost change tied to the variation, and the date the delay appears to have begun. Those answers decide whether to send the written demand or the time-extension request. They also answer a separate question that many owners care about most, which is whether the job still pays at the unit price. That is a different question from whether the clause gives you money, and keeping the two apart makes the conversation clearer.

Dispatch notes matter more than most owners think. A dispatcher writes the daily note that says a crew was held up waiting on a material delivery, or re-doing a section after an inspection. Those notes become evidence. If the variation caused the delay, the note should say so in plain terms. If another cause did, the note should say that too. Mixing causes in the same note is a common way to lose the argument, because the reader cannot tell which cost belongs to which event. For a handoff checklist, see Field Service Work Order Checklist for Dispatch Handoffs.

Before you sign the next unit-priced bid

Read the quantity clause in the solicitation before you price the bid. Find out whether it includes the variation clause and how the band is set. If the contract you are bidding has no such clause, your protection on quantity changes may be thinner than you expect, so price that risk into the unit rates before you submit.

Look hard at the estimate itself. The estimate is what the band is measured against, so an estimate that looks low or high compared with your field experience deserves a question before the award, not after. Ask how the estimate was built, and whether the agency expects the work to come in near the number on the sheet. A question asked during the solicitation period costs nothing. The same question asked after a large overrun costs a great deal.

Set up your records before the first unit is installed. Pick the job code, the line item mapping, and the logging method on day one. Tell the crews how tickets and dispatch notes map to contract lines. A tidy system at the start is much cheaper than a rebuild at the end, when the quantities have already moved and the crew has already moved on to the next job. For the cost side, see job costing setup for field service.

Finally, keep the three limits on one card in the office: the band, the cost basis, and the ten-day clock. The band and the ten-day clock carry numbers, and the cost basis comes from the clause's wording, so each is easy to forget when a job is busy. A dispatcher who can say, in one breath, "we are above the 115 percent mark on the trench line, the delay note started on Tuesday, and the request goes out by Thursday," is the dispatcher an owner can trust with a unit-priced job.

Today, pick one open unit-priced job, pull its estimated quantities from the contract, and write the 85 and 115 percent marks beside each line.

Related guides: Check 5 guardrail and toeboard limits before dispatch · Field service integration checks: 6 limits to verify · Flat-rate pricebook price: 3 parts to build in.

Frequently asked questions

Does a quantity change adjust the price automatically?

No. The adjustment is made on demand, so someone has to raise it.

What does the adjustment measure?

It measures the increase or decrease in costs due solely to the variation, not the overrun times the unit price.

How long do you have to ask for more time?

You have 10 days from the beginning of the delay to get a written request to the Contracting Officer, unless a further period is granted before final settlement.

Sources

More field guides