What CIAP Document 102 Actually Covers

CIAP Document 102 is the Construction Industry Authority of the Philippines' standard general conditions of contract — a template framework that most private construction agreements in the Philippines are built on, in the same way many international projects lean on FIDIC forms. Estimators don't usually draft contracts, but understanding the framework's shape helps you flag pricing implications that a purely technical read of the drawings and specs wouldn't surface.

General Conditions vs Special Provisions

The framework separates broad, standard terms — general conditions, covering things like payment terms, variations, delays, and dispute resolution in a form applicable to most projects — from special provisions, the project-specific terms layered on top for a particular contract. An estimator reading only the drawings and BOQ can miss cost drivers hiding in the special provisions: unusual retention percentages, tighter-than-standard variation approval processes, or liquidated damages clauses that affect how much schedule risk should be priced into the estimate.

Why This Affects Pricing, Not Just Legal Risk

Contract terms translate into real cost even when they never appear on a material take-off. A contract with a longer payment cycle affects a contractor's working capital cost. Tighter variation-order procedures can slow down how quickly a legitimate scope change gets paid for, which is a cash-flow risk worth pricing in on tight-margin work. None of this shows up in a BOQ line item, but experienced estimators build a contingency allowance that reflects it.

What This Means Day to Day

You don't need to be a contracts specialist to estimate well, but recognizing when a project's terms deviate from the standard CIAP framework — and flagging that to whoever is finalizing pricing — is part of producing an estimate that holds up once work actually starts. A technically perfect take-off built on the wrong contract assumptions is still a wrong estimate.

Worked Example: Retention Percentage in the Special Provisions

Say the general conditions in a CIAP-102-based contract set a standard retention of 10% withheld from each progress billing until substantial completion. If a project's special provisions override that to 20% — not unheard of on higher-risk or first-time-client engagements — that single clause change doubles the amount of cash a contractor has tied up in retention at any given point in the project. That's a working-capital cost that never appears as a BOQ line item, but it's exactly the kind of number an estimator who actually reads the special provisions (rather than skimming straight to the drawings) would catch before finalizing overhead and contingency percentages, not after the contract is signed.

Common Mistakes

The most common mistake is treating contract review as someone else's job entirely — leaving it to a project manager or legal reviewer while the estimator works exclusively from drawings and specs. That division of labor makes sense for the legal risk itself, but it misses the pricing implications baked into the contract terms, since by the time legal review happens, the estimate (and often the bid) may already be finalized. A second common mistake is assuming every project under a CIAP-102 framework uses standard terms by default, when the entire point of the special-provisions structure is that projects deviate from the standard general conditions routinely — retention percentage, payment cycle length, variation-order approval speed, and liquidated-damages exposure are all commonly adjusted per project, and none of them show up anywhere on a material take-off.

The practical fix is procedural rather than technical: before contingency and overhead percentages get finalized, someone on the estimating side reads the special provisions specifically looking for deviations from the standard general conditions — not the whole contract cover to cover, just the section most likely to hide a pricing-relevant term.