Construction Contract Administration: The Architect's Role and How GCs Navigate It
Contract administration is where the architect transitions from design professional to project referee — and where GCs either leverage the process effectively or get buried in it. Understanding exactly what the architect can and cannot do during construction, how the RFI and submittal workflows operate under AIA A201, and how payment certification works gives GCs the framework to protect schedule, cash flow, and their contractual rights.
What Is Construction Contract Administration?
Contract administration (CA) is the set of services the architect provides during the construction phase to help the owner confirm that the GC is building in conformance with the contract documents. The architect does not supervise or direct the GC's work — that's the GC's exclusive domain — but acts as the owner's representative to observe, interpret, certify, and in limited cases, decide.
Under AIA A201 General Conditions, the architect holds a dual role: agent of the owner in most matters, and quasi-independent decision-maker in others (such as interpreting contract documents and making initial decisions on claims). This duality creates a relationship that is neither purely adversarial nor purely collaborative — and GCs who understand the distinctions navigate it far more effectively.
Core Contract Administration Duties
The architect makes periodic site visits to observe the progress and quality of work — not continuous inspection. AIA A201 §4.2.2 explicitly distinguishes between "site visits" (what architects do) and "inspection" (what testing agencies and building officials do). The architect is not responsible for the GC's construction means, methods, sequences, or safety programs.
GCs should document when the architect visits, what they observed, and any comments made — in the daily report. An architect who visits infrequently and then raises deficiency concerns at substantial completion has less credibility when the daily reports show they had ample opportunity to observe the work as it progressed.
The architect is the first point of contact for RFIs (Requests for Information) — questions about drawing intent, specification conflicts, and missing information. The architect reviews and responds, sometimes with clarifications that do not constitute a scope change, and sometimes with supplemental instructions (ASIs) or architect's supplemental instructions that direct additional work.
Shop drawings, product data, and samples flow through the architect for review and approval. The architect's role is to confirm conformance with design intent — not to verify dimensions, quantities, or field conditions, which remain the GC's responsibility. AIA A201 §4.2.7 is explicit: architect approval of a submittal does not relieve the GC of responsibility for errors.
GCs who submit with inadequate lead time and then claim an architect delay caused a schedule impact face an uphill battle. Build submittal lead times into the project schedule and track the submittal log actively.
The architect reviews the GC's payment applications and issues (or withholds) a Certificate for Payment (AIA G702). The certificate is not the architect's endorsement that all work is complete — it represents the architect's judgment that the work has progressed to the point indicated and the GC is entitled to payment.
Under AIA A201 §9.4, the architect has 7 days after receiving the GC's application to issue a certificate. The owner then has 7 additional days to pay (subject to contract payment terms). Architects who consistently delay certification without documented justification are creating a payment default situation.
The architect prepares and issues change orders but has limited authority to approve them unilaterally. Under AIA A201, a formal Change Order requires signatures from Owner, Contractor, and Architect. The architect's authority to issue a Construction Change Directive (and direct the GC to proceed before price is agreed) is bounded by the contract.
GCs should know the numerical limit of the architect's independent change authority (if any) stated in the owner-architect agreement — this is sometimes shared during preconstruction. Changes above that threshold require owner approval regardless of what the architect says.
Under AIA A201 §15.2, the architect acts as Initial Decision Maker (IDM) for claims between owner and contractor. The architect reviews and renders a decision within 30 days of receiving a fully documented claim. The decision can be accepted, or either party can demand mediation and then arbitration/litigation. GCs who skip the IDM process lose procedural rights — always file formal claims per the contract's notice requirements even if you expect rejection.
The A/E Relationship: What GCs Need to Know
The architect-engineer (A/E) team during construction is not the GC's adversary — but their primary obligation is to the owner, and GCs who forget this get surprised. Key dynamics:
| Situation | Architect's Position | GC Best Practice |
|---|---|---|
| Drawing error or omission | May resist acknowledging error; may issue clarification without CO | Submit RFI formally; assert cost impact in writing before proceeding |
| Slow RFI response | May not track response time as urgently as GC needs | Log RFI impact on schedule; document cost of delay contemporaneously |
| Rejected submittal | May reject without clear explanation | Request specific deficiency in writing; resubmit promptly; document delay impact |
| Certification withheld | May withhold based on owner direction, not documented deficiency | Demand written statement of withholding grounds per §9.5.1; escalate to owner if not provided |
| ASI with cost impact | May issue as "no cost" clarification | Respond in writing with cost/time estimate within notice period; don't proceed at risk |
| Verbal direction on-site | May give direction informally during site visits | Document in daily report; follow up with written confirmation request |
Notice Requirements: The GC's Most Critical Obligation
AIA A201 imposes strict notice requirements on the GC for claims of additional cost or time. The core provision (§15.1.3): the GC must provide notice of a claim within 21 days of first recognizing the condition giving rise to the claim — or the claim is waived.
This notice requirement is one of the most consequential provisions GCs routinely fail to comply with. Common scenarios where notice gets missed:
- ▸GC proceeds on verbal direction from the architect, plans to "sort out the CO later," and misses the 21-day window
- ▸Unforeseen subsurface condition encountered; field team focuses on solving the problem rather than sending the formal notice letter
- ▸Owner delays furnishing equipment or access; GC absorbs the impact informally before realizing the schedule impact
- ▸Cumulative impacts of multiple small changes: each individually seems minor; together they constitute a compensable impact, but the notice window closed on each one
Build a notice checklist into your project management process: any event that could give rise to a cost or time claim gets a formal notice within 21 days. Over-noticing is far less costly than under-noticing.
5 Best Practices for GCs in Contract Administration
-
1.
Treat every architect communication as a formal document. Email from the architect saying "go ahead and use the alternate detail" is a verbal directive — respond in writing acknowledging what you understood the direction to be and any cost/time impact. The paper trail you create protects you when memories diverge six months later.
-
2.
Know the A201 response timelines cold. Architect has 7 days to certify payment. Architect has 10 days to respond to a CCD request for cost breakdown. Owner has 7 days after certification to pay. GC has 21 days to give notice of a claim. GC has 60 days to submit a claim after initial notice. These deadlines are enforced.
-
3.
Distinguish between "clarification" and "change" and push back in writing. When the architect issues an ASI labeled "no cost/no time," evaluate it independently. If it directs work not in the contract documents, respond: "GC acknowledges receipt of ASI-007. GC's preliminary review indicates potential additional cost of $X and schedule impact of Y days. GC will provide detailed pricing within [X] days per §7.3."
-
4.
Track RFI response times and link them to schedule impact. An RFI open for 14 days that's on the critical path is a potential delay claim — but only if you've documented the schedule tie-in contemporaneously. Your project controls system should flag open RFIs with schedule dates at risk.
-
5.
File the IDM claim even if you expect rejection. When the architect serves as IDM, many GCs skip the formal claim process because they assume the architect will side with the owner. That assumption may be correct — but failing to file the claim per §15.2 means you can't proceed to mediation or arbitration. File it. Get the rejection in writing. Then escalate.
Track RFIs, Submittals, and Change Events in One Place
SheetIntel connects your RFI log, submittal register, and cost tracking — so contract administration events are tied to schedule and cost impact from the moment they open.
Get Early Access →