The contract clauses that quietly cost contractors money

You priced the bid right. Materials, labor, overhead, a fair margin sitting on top of all of it. Then the project runs eight weeks over, retention sits with the client for a year, and a SAR 400,000 change order gets disputed until it's written off. The margin is gone, and it was never about the pricing.

This is where most contractors actually lose money: not in the estimate, but in four clause types that sit quietly in every tender document. Liquidated damages, retention, variations, and scope wording loose enough to argue about. Here is what to check in each before you sign, not after you've already won the job.

Liquidated damages and the daily rate that eats your margin

Liquidated damages (LDs) are a fixed penalty per day or week of late completion, usually written as a percentage of contract value. A rate of 0.1% to 0.5% per day sounds small until you multiply it by ten or twelve weeks of delay, and many contracts cap total LDs at 5% to 10% of contract value, which on a mid-size project can be the entire margin.

Before you sign, check three things: the daily rate against the actual value of the work, whether it's proportionate or set to punish rather than compensate, and the total cap, and whether LDs are the client's only remedy or whether they can also claim general damages on top. Then check the extension-of-time clause. If client-caused delays, late approvals, or force majeure don't give you a formal right to extend the completion date, every day lost to someone else's decision still counts against you.

• Daily or weekly LD rate benchmarked against likely loss, not an arbitrary round number
• A hard cap on total LD exposure, stated as a percentage of contract value
• LDs named as the client's sole remedy for delay, not "without prejudice to other rights"
• A workable extension-of-time clause covering late approvals, client-instructed changes, and force majeure
• A realistic notice period for claiming an extension, 7 to 14 days rather than 48 hours

Retention terms and how long your cash stays locked up

Retention is usually 5% to 10% withheld from every payment certificate, released in two halves: the first at practical completion, the second at the end of the defects liability period, commonly 12 months later. On a project that takes eight months to build, your cash can stay tied up for close to two years from first invoice to final release.

Two things matter most here. First, whether the contract lets you replace cash retention with a bank guarantee, which frees the money immediately instead of leaving it sitting with the client. Second, how the defects liability period's end date is defined. If release depends on the client certifying satisfaction rather than a fixed date, that certificate can sit on someone's desk indefinitely, and your retention with it.

Variation clauses: where contract clause risk hides in change orders

Variations, extra or changed work outside the original scope, are where a well-run project quietly starts losing money. The contract should spell out exactly how a variation gets raised, priced, and approved: a written instruction, agreed rates pulled from the original bill of quantities, and a set window for the client to respond.

The problem is what happens on-site. A supervisor gives a verbal instruction to change a detail, the crew does the work that day because the schedule doesn't wait for paperwork, and three months later the client's project manager says there's no signed variation order, so it isn't payable. That gap between how sites actually operate and how the contract says they should is the real contract clause risk in this clause.

Contract clause risk in practice: how variations actually get paid

Negotiate a process that matches reality. Instructions can be verbal on-site but must be confirmed in writing within a set number of days, say three to five. If the client doesn't respond to a submitted variation within 10 to 14 days, it's deemed approved rather than stuck in limbo. And push for a payment timeline on approved variations that isn't "settled in the final account", because final accounts on delayed projects can take months to close.

Ambiguous scope language that quietly shifts risk to you

Phrases like "all works necessary for completion" or "as required by the engineer" look harmless in a scope document. In practice, they let the client fold almost anything into your original price, because the wording never draws a line around what's included.

Before signing, get the scope tied to specific drawings and specifications by revision number and date, not a general description. List exclusions explicitly rather than assuming they're understood. And name anything that's "by others" so it's clear on paper, not just in the meeting where everyone nodded.

None of these clauses look dangerous on the day you sign. They read like standard boilerplate, the same paragraphs sitting in every tender document you've seen before. The damage shows up months later, when the bank guarantee was never offered as an option, the defects liability period never got a fixed end date, and a SAR 200,000 variation is still under review. Read these four sections before you price the job, not after you've already won it.