Straight into the service manual page
WrenchQuarry
More

Contract changes and the 25 percent surety line

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

Why changes matter on a bonded contract

Under a Florida contract statute, the surety's approval is required to bind it once cumulative changes pass 25 percent of the original contract amount. When the scope, schedule, or price of the work changes, the surety's exposure changes with it. On a bonded job, a change is never just paperwork. Each approved modification can shift the amount the bond is expected to cover, and some combinations of changes can cross that line.

Key takeaways

  • Measure every change against the original contract amount, which does not change.
  • Put each change in writing, with its own number, amount, and issue date.
  • Recalculate the cumulative percentage before a change is issued, not after.
  • Obtain the surety's written approval before the total passes 25 percent, for the portion above the line.
  • Treat any change that extends the physical limits of a project as a separate test.

Owners and team leads usually sign off on changes, which makes them the people best placed to notice when small changes add up. This post walks through the rules in the sources cited here, shows how to read them, and offers a working approach for tracking changes on a live job.

A caution first. The detailed threshold below comes from a Florida statute that governs contracts entered into by the state department it names. It is not a universal rule. Other owners, states, and federal agencies set their own terms, so the number in this post is no substitute for your own contract and bond.

Written change documents are the safe default

The Florida statute starts from a simple point about form. It says the department "shall permit the use of written supplemental agreements, written work orders pursuant to a contingency pay item or contingency supplemental agreement, and written change orders to any contract entered into by the department." (Fla. Stat. 337.11)

The lesson for any bonded contract is that a change should exist on paper before the extra work is treated as part of the contract. A verbal instruction on site, a text message, or an unsigned email is hard to trace and harder to defend later. Give every modification its own written change document, numbered in sequence, with its amount and issue date on the face of it.

This FAR clause follows a similar approach. The Construction Wage Rate Requirements clause in the Federal Acquisition Regulation covers one specific kind of price adjustment, a change tied to wage rates. It states: "Upon agreement of the parties, the Contracting Officer will modify the contract price or contract unit price in writing." (FAR 52.222-32)

That clause is narrower than a general change order, but it shows the same principle. Agreement comes first, and the price change follows in writing.

Rules at a glance

The table compares the rules from both sources. Each row uses only the wording of the source named in its last column.

TopicWhat the source saysSource
Form of changes (Florida)Written supplemental agreements, written work orders, and written change orders are permittedFla. Stat. 337.11
Surety liability up to 25 percent (Florida)Surety is fully liable up to and including 25 percent over the original contract amount, whether or not it knew of or approved the modificationsFla. Stat. 337.11
Cumulative changes past the line (Florida)Surety approval is required to bind the surety on the portion that exceeds 25 percent, measured against the original amountFla. Stat. 337.11
Extensions of physical limits (Florida)Cost shall not exceed $100,000 or 10 percent of the original contract price, whichever is greaterFla. Stat. 337.11
Wage-rate price adjustment (federal)Contracting Officer modifies the price in writing upon agreement of the partiesFAR 52.222-32
Pending adjustment (federal)Contractor continues performance pending agreement on or determination of the adjustment and its effective dateFAR 52.222-32

Disclosure rules differ by state

Other states write their own rules for contracts, and some are far more specific about how terms must appear. Arizona's contractor statute shows three patterns worth noticing.

The first is that an exemption can change which rule applies: "This paragraph does not apply to a person who is subject to and complies with section 12-1365." (Arizona State Legislature) A rule that looks like it covers you may not, if you already comply with another section. Find out whether an exemption applies before you assume the general rule governs.

The second is that format can be part of the rule: "The information in this paragraph must be prominently displayed in the contract in at least ten-point bold type." (Arizona State Legislature) A required notice buried in fine print may not satisfy the law, even if the words are technically there.

The third is that the contract itself has to carry the practical details: "The contract shall contain the registrar's telephone number and website address and shall state that complaints must be made within the applicable time period as set forth in section 32-1162, subsection A." (Arizona State Legislature) The deadline is set by statute, but the owner should be able to find it in the signed document.

For a bonded change process, the same discipline applies. Approval terms and deadlines you rely on belong in the written instrument, not only in a side conversation on site.

Keep working while a change is pending

The federal clause also covers what happens while a price adjustment is still open: "The Contractor shall continue performance pending agreement on or determination of any such adjustment and its effective date." (FAR 52.222-32)

For an owner or team lead, the federal clause applies only to wage-rate adjustments. Under that clause, work continues while the price and effective date are being settled. Other bonded contracts need their own terms checked before work continues while a change is pending. Gaps left until the price is agreed are hard to close, so the team should treat open work as part of the job's financial picture from the start.

The clause describes continued performance only. It says nothing about how a surety treats a pending change under a bond. That question has to be answered from the bond itself and the surety's written position, not assumed from the federal rule.

The 25 percent line

The most important bonded-change rule in the Florida statute concerns the surety's own liability. The statute reads, in part: "...337.18 shall be fully liable under such surety bond to the full extent of any modified contract amount up to and including 25 percent over the original contract amount and without regard to the fact that the surety was not aware of or did not approve such modifications." (Fla. Stat. 337.11)

Read plainly, the first half sets the limit: the surety is fully liable up to and including 25 percent over the original contract amount. The second half protects the party relying on the bond, because liability holds even if the surety was not aware of or did not approve the modifications.

The statute then addresses the point where the limit is reached: "However, if modifications of the original contract amount cumulatively result in modifications of the contract amount in excess of 25 percent of the original contract amount, the surety’s approval shall be required to bind the surety under the bond on that portion in excess of 25 percent of the original contract amount." (Fla. Stat. 337.11)

The word that matters most is "cumulatively." The test is not applied to each change on its own. Several modifications add together, and the running total is measured against the original contract amount, not against the amount as it stood before the latest change. A series of changes that each look minor can cross the line without anyone deciding to cross it.

The statute says approval is "required to bind the surety" for the portion above the line. That makes approval a precondition for that portion, not a formality. Treat it as something to obtain before the change is issued, not something to chase afterward.

The phrase "on that portion in excess" matters too. The statute does not say that every change past the line voids the bond or that the whole contract needs fresh approval. It limits the approval requirement to the part of the modifications above the line. At the line, then, the question is narrow: which dollars sit above it, and has the surety approved those dollars in writing?

In practice, a team can work from a simple rule. Keep a running total of modifications, express it as a percentage of the original amount, and recalculate the figure for each proposed change, not only after approval. If a proposed change would take the total past the line, stop and request the surety's written approval first.

A useful approval request states the original amount, the total of approved modifications to date, the amount of the proposed change, the resulting cumulative percentage, and the portion that would fall above the line. Attach the written instrument that would be issued. A request laid out this way lets the surety assess the exposure without reconstructing the job's history, and it leaves a clean trail if the approval is questioned later. For a step-by-step approach to getting approval first, see Extra repair work: 6 steps to get approval first.

Illustrative example: running total on a 10 million contract

Assume an original contract amount of 10 million. Change 1 adds 1 million, or 10 percent of the original amount. Change 2 adds another 1 million, and the total is still below the line, so the approval requirement does not yet apply. Change 3 would add 2 million more, which pushes the total past 25 percent. This example is illustrative only and is not drawn from any contract.

Physical limits on extensions

Florida also caps the cost of one more kind of agreement: "The cost of any such agreement extending the physical limits of a project shall not exceed $100,000 or 10 percent of the original contract price, whichever is greater." (Fla. Stat. 337.11)

The cap is the larger of the two figures, so it is not one fixed dollar amount. The 25 percent test and this cap are separate rules, so each needs its own calculation. Staying within one does not show that you have stayed within the other.

Common mistakes to avoid

Several errors come up when teams track changes informally.

Tracking only signed changes can hide how close a proposed change would take the job to the line. The check belongs on the proposed total, because that is the number the approval decision depends on.

Measuring against the wrong base is another common error. The rule measures against the original contract amount. A running total measured against the most recently modified amount gives a different and misleading percentage, and it can make a job look further from the line than it is.

Assuming one approval covers everything is a third mistake. The statute ties the approval requirement to the portion above the line. An approval for one change does not, from the statute's wording alone, settle the question for later changes that move the total further along.

Ignoring the separate extension cap is the fourth. When a change extends the physical limits of a project, the cap is its own test and needs its own calculation.

Letting the written file fall behind the work is the last. The federal clause expects performance to continue while adjustments are pending. If the paper trail trails the job, the eventual modification is built on memory rather than on what was actually done.

Questions to ask before issuing a change

Before any change is issued, a team lead can run through a short checklist. Each question maps to a point made above.

  • Is the change in a written form that the governing rules allow for this kind of modification?
  • What is the cumulative total against the original contract amount, with this change included?
  • Does any part of this change fall above the line?
  • If it does, is the surety's written approval in hand for that portion?
  • Does this change extend the physical limits of the project, and if so, does it fall within the cap?
  • Is there open work whose price is not yet agreed, and will the eventual modification match what was actually done?

A "no" or an unknown answer to any of these is a reason to pause the change, not a reason to proceed and sort it out later.

Applying this on a live job

A workable process for a live bonded contract looks like this:

  1. Fix the baseline. Take the original contract amount from the signed contract. That figure does not change, and every percentage on the job is measured against it.
  2. Keep one modification log. For each change, list its number, the type of written instrument, its amount, its issue date, and whether the surety has approved it. This log is the single source for every running total on the job. For a related record format, see Job cost sheet: 3 cost lines to total on every job.
  3. Recalculate before issuing. Work out the cumulative percentage against the original amount before a change is issued, not after.
  4. Set an internal checkpoint short of the line. A checkpoint well before the line gives you time to obtain the surety's written approval without rushing the decision.
  5. Attach each approval to its change. Keep the written approval with the change order, supplemental agreement, or work order it covers.
  6. Track open adjustments. If a price is still under agreement, carry the work performed in the job's financial picture, and make sure the eventual modification matches it. Check the governing contract and bond before work continues on an open adjustment.

When to get help

When a change is close to the line, or when the contract or bond language is unclear, involve the right people early. That means the surety, the contract administrator, and counsel familiar with the governing law. Bring the modification log, the original contract, the bond, and the written instruments already issued, so the discussion starts from facts rather than memory.

The Florida text cited here is the 2025 version of the statute. Later amendments may change the thresholds or the approval language, so confirm the current text before relying on it.

Next step today: Open your job's modification log, add the original contract amount and each change's amount, and calculate the cumulative percentage for the next proposed change before it is issued.

Frequently asked questions

When does surety approval become required?

Under the Florida statute quoted here, approval is required to bind the surety on the portion of cumulative modifications above 25 percent of the original contract amount.

Does the 25 percent line apply to every contract?

No. The threshold comes from the Florida statute quoted here, which governs contracts entered into by the state department it names. Other owners, states, and federal agencies set their own terms.

Does a change below the line need the surety's approval?

The statute's approval requirement applies only to the portion above 25 percent of the original contract amount, so the running total still needs to be tracked for every change.

Summary

Changes on a bonded contract are a financial and legal event, not just a form to sign. Put every change in writing, keep a running total against the original amount, and treat any move toward the line as a reason to bring the surety in before the change is issued. Florida's 25 percent rule is one clear example of why the running total matters, and the same discipline serves a job under any bond.

Sources

More field guides