General Conditions
The section of a construction contract, often a standard form like AIA A201, that sets the general rules, responsibilities, and procedures governing the whole project: how RFIs and change orders get handled, insurance requirements, dispute resolution, and dozens of other administrative provisions that apply regardless of what's actually being built.
Why it matters
General conditions are where most of the procedural "rules of the game" for a project actually live, separate from the specific scope of work. A dispute over how a change order should be priced, or how much notice a delay claim requires, usually gets resolved by checking exactly what the general conditions say, not by common sense alone.
On a real project
A contract's general conditions specify that any RFI must receive an architect's response within 10 business days. When a response takes three weeks, the contractor can point to that specific general conditions provision as grounds for a schedule impact.
Who this matters most to
A Contracts Administrator knows a project's general conditions in detail, since they govern nearly every procedural dispute that comes up. A Project Manager refers back to them constantly for things like notice requirements and payment timing.
Where this goes wrong
A project team assumes a specific procedural question, like how many days the owner has to respond to a submittal, works the same way it did on their last project. The general conditions on this particular contract set a different timeline entirely, and assuming the old rule applied costs the team a missed deadline they didn't realize existed.