Construction Administration: Roles and Project Records

Construction administration is the work of managing project communication and records while a building is being built. Depending on the contract, it can include submittal review, requests for information, site observations, change documentation, pay application review, meeting records, deficiency tracking, and closeout. The exact responsibilities vary by agreement and by the roles of the owner, architect, engineer, contractor, and construction manager.

The phrase should not be treated as a universal scope. A design professional’s construction-phase services may differ from a contractor’s administration work or an owner’s project controls. The agreement defines who performs each task, how the task is completed, and what authority the person has. For an overall project sequence, see the building construction process flow.

Construction administration and construction management

Construction administration generally refers to administering design and contract processes during construction. It may include answering design questions, reviewing submittals within a defined scope, observing progress, documenting changes, and supporting closeout. Construction management can be broader or differently defined. A construction manager may provide planning, cost, schedule, procurement, or site coordination services.

The labels do not determine authority. A project administrator may track a submittal but have no authority to approve a scope change. A design professional may review a product for consistency with design intent while the contractor remains responsible for installation, field dimensions, and coordination, as stated in the contract. The owner’s representative may review payment applications without changing the agreement.

The project should define each role, not simply list a title. A responsibility matrix can show who prepares, reviews, approves, distributes, and closes each item.

Set up the administration process before construction

Before mobilization, identify the official systems for documents, questions, submittals, meeting records, changes, payments, inspections, and closeout. Define how records are named, routed, revised, and retained. Confirm who can issue direction and what communication constitutes formal notice under the contract.

A useful setup includes a contact list, decision authority chart, document register, submittal schedule, RFI process, change log, payment calendar, meeting schedule, and closeout checklist. The team should know expected response times and how overdue items are escalated. These processes need to reflect the contract rather than impose an unrelated workflow.

The project phase plan can connect administration steps to work sequencing and handoffs. Review the construction phase plan headings guide for a phase-wide structure.

Submittals and product review

A submittal provides information about a product or installation for review. It may contain product data, shop drawings, samples, mockups, test information, or calculations. The contractor typically coordinates information from suppliers and trade partners, checks it for completeness, and submits it under the contract process.

A submittal log tracks required items, responsible preparer, due date, review duration, status, resubmission, procurement release, and installation need. Submittals should be scheduled early enough to avoid delaying fabrication or field work. The log should distinguish “submitted,” “under review,” “revise and resubmit,” and “review complete.” Status terms should match the project’s system.

A review should answer only what the reviewer is responsible for. The contract may preserve the contractor’s responsibility for dimensions, quantities, fabrication, coordination, and means and methods. If the review identifies a potential deviation, record the specific issue and obtain the required decision before procurement or installation.

Requests for information

An RFI asks for clarification when the contract documents or field conditions leave a question that affects the work. A useful RFI cites the drawing, specification section, revision, and location. It explains the conflict or missing information in neutral terms and asks one clear question. If appropriate, the contractor can provide options and identify a response date tied to the schedule.

The RFI log should include number, subject, date submitted, responsible reviewer, due date, response date, status, and potential cost or schedule effect. An RFI should not be used to quietly request a scope change. If the response changes scope, price, or time, use the contract’s change procedure.

The team should close the loop. Distribute the response to affected trades, update coordinated documents when needed, and record the decision in the project’s official system. An answer in a personal inbox may not reach the people installing the work.

Site observations and field records

Site observations document what a reviewer saw at a specific time and location. They are not necessarily continuous inspection or a guarantee that all work complies. Reports should state the date, area, observed condition, relevant document, and requested follow-up. Avoid broad claims that exceed the observer’s scope.

The contractor’s daily reports can include workforce, equipment, weather, deliveries, work performed, inspections, delays, and unusual conditions. Meeting minutes record decisions, open items, owners, and due dates. Photographs should include context and a location reference. Consistent documentation makes it easier to investigate a later question.

When actual conditions differ from the drawings, the team should use the designated clarification process. A field note is not automatically an instruction to change design. The record should identify who has authority to decide and whether work must pause in the affected area.

Changes and cost control

A change can arise from an owner request, site condition, design clarification, code or authority comment, substitution, or coordination issue. Administration should capture the reason, scope, supporting documents, price, time effect, and approval status. The change log should distinguish proposed, priced, authorized, installed, and closed items.

The parties should follow contract notice requirements. Do not represent a proposed change as approved. Do not rely on an informal direction when the contract requires written authorization. If an urgent condition needs immediate protection, follow the applicable safety and emergency procedures and document subsequent decisions through the required process.

Cost review should compare the proposed change with the agreed scope and verify assumptions, quantities, labor, materials, schedule effect, and markups as required by the contract. The administrator should route technical questions to the responsible designer and commercial questions to the authorized owner or contract representative.

Payment review and schedule records

A pay application requests payment for work or stored materials under contract terms. Review may include progress, schedule of values, required backup, lien documents, retainage, and prior payments. The administrator should document questions and corrections while respecting the agreement’s payment process and applicable requirements.

Progress reporting should use a consistent baseline schedule and current updates. A narrative can explain critical changes, procurement risks, recovery plans, and decisions needed. Record the source of percent-complete information and distinguish reported progress from independently verified progress when relevant.

Administration cannot fix an unrealistic schedule by changing status labels. If a milestone is at risk, identify the affected activities, dependencies, responsible parties, and options. If time or compensation may change, use the contract procedure.

Deficiency tracking, commissioning, and closeout

A deficiency or punch list entry should say what is incomplete, where it is, who owns correction, when it is due, and how completion will be verified. Grouping unrelated items into a vague “complete room” entry makes closure harder. Photos and current drawing references help the responsible party understand the issue.

Closeout requirements should be tracked before the end of construction. These may include inspections, commissioning, record drawings, manuals, warranties, training, spare parts, keys, access credentials, and final payment documentation. The project should name a recipient and format for each deliverable.

Commissioning and owner training should have milestones in the schedule. Operators need time to participate, ask questions, and practice. Closeout is not simply collecting files; the owner should be able to locate and use the information.

Common construction administration mistakes

• Assuming a title implies authority that the contract does not grant.
• Using email or meeting discussion as a substitute for a required formal change.
• Allowing submittals to arrive after procurement or installation deadlines.
• Failing to distribute an RFI response to affected trades.
• Writing observation reports that imply continuous inspection or final acceptance.
• Tracking closeout items only after the building appears complete.

Administration metrics and process review

A project can review administration performance without reducing quality to a single score. Track the age of open RFIs, overdue submittals, time from change proposal to decision, unresolved closeout items, and the number of records returned for missing information. Define start and end points for each measure. A shorter response time is useful only if the answer is complete and reaches the affected team.

Review recurring causes rather than blaming the person who enters a record. Incomplete submittals may indicate that the schedule is unrealistic or requirements are unclear. Aging changes may reflect missing pricing, unclear authority, or a funding gate. The process owner can address the source while keeping individual records visible.

At closeout, capture lessons that can improve templates and workflows. Retain the project’s records under the owner’s retention rules and preserve the link between decisions and final documents.

Frequently asked questions

Does construction administration mean the architect supervises the contractor?

Not automatically. The agreement defines services and authority. Design professionals may observe work or review submittals, while the contractor organizes the work and remains responsible for its contractual duties. Read the specific agreement.

Can a submittal review approve a change?

A submittal review does not automatically approve a contract change. If a proposed product or detail deviates from the documents, obtain the required technical and commercial approvals through the project process.

What records should be kept?

Keep the records required by the contract and owner system, including current documents, submittals, RFIs, changes, meeting decisions, payment records, inspections, testing, deficiencies, commissioning, and closeout deliverables.

Practical closeout check

Before closing an administration item, verify that the response reached the people who need it, the current document reflects the decision where necessary, and any related cost or schedule action followed the contract. Assign a new item if more work remains. Clear status language and reliable records help the finished building match the decisions made during delivery.