Standard Form Contracts (AIA & ConsensusDocs)
Pre-drafted, industry-standard contract templates, most commonly published by the American Institute of Architects (AIA) and ConsensusDocs, that project parties adapt and fill in for a specific project instead of drafting a custom contract from scratch for every job.
Why it matters
Because these forms are widely used and heavily litigated over decades, their terms are well understood across the industry: an owner, architect, and contractor working from an AIA A101 or a ConsensusDocs 200 already share a common baseline vocabulary for risk allocation, payment, and disputes, which speeds up negotiation compared to reviewing a one-off custom document line by line.
On a real project
A general contractor and owner use AIA Document A101 (Standard Form of Agreement Between Owner and Contractor) paired with A201 (General Conditions of the Contract for Construction) instead of drafting their own agreement, filling in project-specific terms, such as contract sum, schedule, and insurance requirements, into the standard template.
Who this matters most to
A Contracts Administrator needs to know these standard forms cold, since so much of the job is reviewing and negotiating modifications against a familiar baseline rather than reading an unfamiliar document from page one. A Project Manager relies on knowing which standard form governs a project to quickly answer questions about notice deadlines, payment timing, and dispute procedures without re-reading the whole contract.
Where this goes wrong
A project team assumes AIA and ConsensusDocs forms are interchangeable and treats contract review as a formality since "it's just the standard form." The two families allocate risk differently in places, for example around indemnification scope and dispute resolution defaults, and a party that skips careful review because the document looks familiar can agree to unfavorable terms buried in the specific edits made to that project's version of the template.