Construction Administration: A Phase Guide for Architects

Key takeaways

• Construction administration is the post-design phase where architects review submittals, answer RFIs, and certify substantial performance and final completion.

• Core CA deliverables form a dependency chain: field reports feed change orders, which feed certificates for payment, so disconnected records create real exposure.

• Construction administration is not project management: the architect administers the owner-contractor contract while the contractor owns means, methods, and schedule.

• Small firms typically staff CA with a licensed CA architect plus an administrative assistant, often drawn from existing project staff.

• Architects can decline or cap CA services when the contract excludes them, but every unobserved site condition is a potential inherited liability.

Construction administration is the phase where your firm reviews submittals, answers RFIs, and certifies substantial performance and final completion while the contractor builds. This walkthrough covers each decision point, the documents and sign-offs due at every step, and where spreadsheet-and-email CA workflows break small firms.

What is construction administration in architecture?

Construction administration is the set of services an architect provides during construction, after the design documents are done. Under the AIA's standard owner-architect agreement, these duties include reviewing submittals and shop drawings, answering contractor RFIs, issuing clarifications and Change Documents, and certifying payments due, with the architect acting as the owner's initial decision-maker on contract matters (per AIA contract documents). It applies to any firm delivering a project under a full-service contract, from a 5-person interior studio doing FF&E through a 30-person practice running CA on a multi-year build. It is distinct from design phases: the drawings are largely fixed, and the work shifts to responding to what the contractor finds. Where those responses live (email threads, spreadsheets, shared drives) is where small firms feel the strain, which later sections address, including how a single relational system like Househouse's Revit-connected setup keeps drawings and CA records linked.

What happens during the construction administration phase of a project?

Construction administration runs chronologically from pre-construction coordination through to final review. Each step generates documents, decisions and correspondence that need to stay connected to the contract and the drawings.

Before construction starts

The architect confirms the contract documents are complete, coordinates with the contractor on schedules and procedures, and sets up the channels RFIs and submittals will flow through. Getting this structure right determines how much friction the rest of the phase carries.

During construction

This is the bulk of the workload. The architect answers RFIs, reviews submittals and shop drawings against the contract documents, conducts site visits at agreed intervals, and issues change documents when field conditions or owner decisions alter the scope. On a regular cycle, the architect reviews the contractor's applications for payment and issues certificates for payment based on the work observed in place.

Every one of those items is a record. An RFI response can trigger a change document, which affects a certificate for payment, which the owner queries eight months later. When those records live in email threads and spreadsheets, the principal reconstructing the story for a fee proposal or a project forecast is doing archaeology, not administration. Enter it once, connected to the project, and the answer is a lookup instead of an afternoon.

Substantial performance to final review

The architect reviews the work for substantial performance, issues the certificate, then manages the closeout: deficiencies, final site review, and the final certificate for payment. Closeout is where incomplete records hurt most, because everyone has moved on and the file is the only witness.

What does a construction administration architect actually do on site and off site?

The construction administration architect splits their time between field work and office work, and the two demand different habits. Field work is about observing and recording. Office work is about answering, certifying, and keeping the contract moving.

On site

Site visits mean walking the work at defined stages, photographing conditions, and writing observation reports that note deviations from the drawings. As substantial performance approaches, the architect prepares punch lists and inspects against the contract's definition of that milestone. The AIA's general conditions distinguish substantial performance from final completion, and the architect's certifications differ at each point (per AIA contract terms).

Off site

Office duties carry most of the volume: logging RFIs, reviewing submittals, issuing payment certificates, and processing change orders. Each item touches the drawings, the spec, and the fee forecast, which is why firms that track CA in disconnected spreadsheets lose the thread. Specs and their revisions belong in one system, not in folders (see how we handle specs).

What documents and site reviews does the architect produce during CA?

Construction administration produces a short list of documents, but each one carries contractual weight and most of them reference each other. The core deliverables:

The dependency chain is the problem. A certificate for payment that misses a change order, or a deficiency list that never made it into the final review, creates real exposure. If your RFI log lives in a spreadsheet and your field reports live in folders, nothing updates anything else, which is why firms that have outgrown spreadsheets look for one source of truth. We compare that approach against Notion in our Notion comparison.

What's the difference between construction administration and project management?

Construction administration is not project management. During CA, the architect administers the contract between owner and contractor: reviewing submittals, answering RFIs, certifying payments and judging conformance with the drawings and specifications. The contractor owns means, methods, sequencing and schedule. The owner's project manager, if there is one, sits on the other side of the contract and may push scope or cost questions back through the architect.

The confusion is expensive because small firms often staff one person for both roles. In the US, construction managers earn a median of $104,900 per year, while architects earn a median of $93,310, per BLS occupational data, so blending the roles blurs who bills for what. Keeping the boundary explicit in your fee proposals and project forecasts makes scope creep visible. A single system of record helps track which duties sit on which side of the line (see our systems and automations services).

What jobs exist in construction administration and what do they require?

Small firms usually staff CA with two roles rather than a dedicated department.

Construction administration architect

The CA architect is a licensed architect who reviews submittals, answers RFIs, issues supplemental instructions, and certifies payment applications during construction. Firms typically expect 5-10 years of experience, full licensure, and enough field literacy to catch a coordination problem in a Revit or AutoCAD drawing set before it becomes a change order. On a 5-30 person firm, this is usually a project architect who carries CA for several jobs at once, alongside fee proposals and project forecasts.

Construction administration assistant

The assistant handles the paper: logging submittals, tracking RFI response deadlines, filing site review reports, and keeping the CA register current. The role suits someone 1-3 years out of school, often working toward licensure, and it is frequently remote or part-time. The work is administrative but unforgiving; a missed submittal turnaround date sits in the contract, and the contractor will notice.

Most firms fill these roles from existing project staff, which is exactly why CA record-keeping breaks when it lives in spreadsheets and email.

When can an architect decline or limit construction administration services?

You can decline CA when the contract of record doesn't include it: if the owner engaged you for design and permit drawings only, you have no obligation to visit site, review submittals, or answer RFIs. You can also scope CA down, capping site visits or submittal reviews, but the trade-off is real: every observation you don't make is a defect you may inherit liability for, and your field reports are your defence if a dispute reaches litigation.

The AIA's guidance on architect's site visits and field reports is explicit that observations should be documented each visit, and that reports state what the architect saw, not certify the contractor's work (per AIA best practices resources). Write the fee proposal to match: list visit frequency, submittal review turnaround, RFI response time, and what happens when the contractor exceeds them. A scope that names its limits is defensible; a vague "as required" line is how CA becomes unpaid work.

How should a small firm keep CA records without drowning in spreadsheets?

CA is a data problem before it's a staffing problem. An RFI references a spec section, which references a drawing, which triggers a submittal, which becomes a site review item. When those records live in email threads and spreadsheets, the connections break, and you reconstruct them by memory during a dispute or a fee proposal.

Generic tools like SmartSuite give you a relational structure but none of the vocabulary: you build RFI logs, submittal registers and FF&E tracking from scratch. Architecture-native tools like Monograph and Programa understand the vocabulary but treat each project as a self-contained workspace, so cross-project forecasting and a firm-wide spec library stay weak.

Househouse Systems takes the opposite bet: one relational database underneath projects, specs, people and deliverables, so you enter data once and everything updates. The honest trade-off: it's custom, so onboarding takes longer than signing up for Monograph, and you won't get a polished mobile site-review app on day one.

FAQ

Is construction administration included in the architect's basic fee or billed separately?

It depends on the contract. Under AIA's B101, CA services are listed separately from basic design services, so many firms bill them as an additional service or carry them in the basic fee with a defined visit allowance. The safe move is naming visit frequency and RFI turnaround explicitly in the fee proposal so scope creep stays visible.

How many site visits per month is typical during construction administration?

There is no fixed standard; frequency depends on construction pace, project complexity, and what the contract specifies. Active structural and envelope work usually justifies weekly visits, while fit-out phases may need biweekly ones. The key is that the contracted interval matches the construction schedule, because observations you don't make become defects you may inherit liability for.

Who signs the certificate of substantial performance, the architect or the contractor?

The architect signs it. The contractor applies for the milestone, but the architect reviews the work against the contract documents, prepares the deficiency list, and certifies substantial performance once items are complete enough to trigger warranty and holdback timelines. The contractor cannot issue it, and the certification is based on observed conditions, not a guarantee of the contractor's work.

Can a construction administration assistant attend site reviews instead of a licensed architect?

No, not as the responsible party. An assistant can log submittals, track RFI deadlines, and file reports, but observation and certification of the work require a licensed architect, since field reports and certificates carry contractual weight. An assistant may accompany the architect to photograph conditions or take notes, but the review and the report remain the architect's duty.

What happens if the owner skips construction administration services entirely?

The architect has no obligation to visit site, review submittals, or answer RFIs if the contract excludes CA, but the owner loses the initial decision-maker on contract matters. Submittals go unreviewed, payment certifications rest on the contractor's say-so, and disputes have no neutral party interpreting the drawings. Many owners instead cap CA to a minimum visit and review allowance.