Project Manual Organization: Bidding Requirements, Contract Forms, and General/Supplementary Conditions

How the project manual is structured beyond the drawings and specifications, covering bidding requirements, contract forms, general conditions (A201), and supplementary conditions (A503) that together define the contractual framework for a construction project.

ARE · Project Development & Documentation

Overview

Construction drawings get most of the attention, but the project manual is the document that holds the contractual and procedural backbone of a project together. Think of it as the rulebook that tells everyone how the project gets bid, who signs what, and what the ground rules are once construction starts.

The project manual contains three major zones. First, the bidding requirements section. This includes the invitation to bid, instructions to bidders (AIA A701), and the bid forms themselves. Second, the contracting requirements. These cover the agreement forms between owner and contractor (A101 through A105 depending on payment basis and project complexity), plus the bonds, certificates, and other legal forms. Third, the conditions of the contract. This is where the general conditions (A201) and supplementary conditions (A503 guide) live. A201 is the single most referenced document in conventional project delivery, spelling out the rights and responsibilities of the owner, contractor, and architect across 15 articles.

For the ARE, you need to understand not just what goes into the project manual, but where specific provisions belong and why supplementary conditions exist separately from the general conditions. The distinction between modifying A201 through supplementary conditions versus embedding terms in the owner-contractor agreement is a recurring exam scenario.

Essential

The project manual is a bound volume (physical or digital) that contains everything in the contract documents except the drawings. While drawings show the graphic information, the project manual provides the written rules. Getting the organization right matters because misplaced provisions create conflicts, ambiguity, and legal exposure. ## Project Manual Organization The standard project manual follows a CSI-established sequence: 1. Bidding Requirements (not part of the contract documents) 2. Contracting Requirements (contract forms, bonds, certificates) 3. Conditions of the Contract (general conditions and supplementary conditions) 4. Specifications (Divisions 00-49 per MasterFormat) That first distinction trips people up constantly. Bidding requirements are procedural documents used during procurement. Once the contract is signed, bidding requirements do not carry forward as contract documents. The instructions to bidders, invitation to bid, and bid forms serve their purpose and then step aside.

Professional

A mid-size firm takes on a public library renovation funded by a municipal bond. The project is Design-Bid-Build. The architect faces a series of decisions about what goes into the project manual and how to structure it. The municipality requires competitive bidding, so A701 (Instructions to Bidders) goes into the bidding requirements section. Because it is a public project, the invitation to bid must be formally advertised. The bid forms include a base bid, two add alternates (upgraded mechanical system and expanded reading room), and a requirement for bid bonds using AIA A310. For the owner-contractor agreement, the team selects A101 because the scope is well defined and the owner wants a stipulated sum contract. A201 serves as the general conditions. Now the supplementary conditions. The municipality requires specific insurance thresholds beyond A201 defaults. The project sits in a state that mandates liquidated damages clauses in public contracts.

TLDR

The project manual contains everything in the contract documents except the drawings: bidding requirements, contract forms, conditions, and specifications.
Bidding requirements (invitation to bid, A701 instructions, bid forms, bid bonds) are NOT contract documents. They expire when the contract is signed.
Owner-contractor agreements range from A101 (stipulated sum, complex projects) through A105 (small projects). Payment basis and project complexity drive the choice.
A104 has its own built-in general conditions. It does not use A201.
A201 (General Conditions) is the keystone document of conventional delivery, covering 15 articles across owner, contractor, and architect responsibilities.
Supplementary conditions modify A201 for project-specific needs. They do not replace A201.
A503 is a guide for drafting supplementary conditions. It is not itself a contract document.
A521 governs where information belongs in the project manual to prevent conflicts.
If the owner and contractor modify A201, the architect's obligations under B101 are unaffected unless B101 is also amended.

ELI5

Imagine you are organizing a big neighborhood kickball tournament. You need three things before anyone plays: The sign-up rules. How do teams register? What forms do they fill out? Do they need to prove they have enough players? This is like the bidding requirements section of a project manual. It tells contractors how to submit their bids, what forms to use, and what bonds they need. But here is the thing: once the teams are picked and the season starts, the sign-up rules do not matter anymore. Same with bidding requirements. They help pick the contractor but are not part of the actual contract. The team contract. Once a team is selected, they sign an agreement. In construction, this is the owner-contractor agreement. There are different versions depending on how you want to pay. One says "here is the flat price" (stipulated sum, A101).

AREProject Development & Documentation

Project Manual Organization: Bidding Requirements, Contract Forms, and General/Supplementary Conditions

2 min read205 words

The Project Manual: More Than Specs

Want to track your progress and access more study tools?

Create a free account