A Weekly Project Controls Review for Small Construction Teams

Turn the weekly meeting into a decision record

A useful construction review should end with decisions: what changed, who needs to respond, and when that response is needed. A small team can organize that conversation without building a separate reporting department.

My background is in California construction project management and project controls. The construction portfolio includes healthcare work and public sources for selected projects. This article sets out a practical review format; it is not a description of any former employer's internal procedures.

Start with the decisions due this week

Put the unresolved decisions at the front of the meeting. For each one, record the question, the person responsible for answering it, the required date, and the work affected by a late answer. A general statement such as “design coordination is ongoing” does not identify an action.

First check whether the current drawings and specifications already answer the question. The design team and owner have developed and vetted those requirements; the owner’s representative relies on that retained expertise and carries them into construction. For specified equipment, ask the general contractor for the current coordinated submittal and its required design and owner review disposition. Do not send an established selection back to the owner as if it were undecided.

If the record leaves a real gap, identify the responsible professional and use the project’s clarification or request-for-information process. A proposed substitution or change follows the required separate review and authorization process. If specifications are unavailable, state the documented basis you have and the missing requirement; do not invent it to complete the report.

Put milestone commitments with the party that controls the activity. The general contractor coordinates confirmations from trade partners, manufacturers, carriers, and any vendor further up their supply chain; it does not promise their dates for them. Each confirmation should identify its scope, conditions, date, evidence, and current document revision. Keep the contractor’s planning estimate visible until that confirmation arrives. Design and owner review authority remains with the assigned reviewers.

Compare the schedule with field progress

A critical path method schedule represents activities and their dependencies. Its value depends on whether actual progress and remaining work are reflected in each update.

Before discussing the completion date, check which activities actually started or finished, what quantities remain, and which assumptions changed. Ask the field team about access, inspections, material deliveries, and trade interfaces. Record the reason for a changed forecast so the next review can distinguish a new problem from an old one.

An activity marked nearly complete can still hold up its successor. Report the remaining constraint in plain language rather than relying on a percentage alone.

Separate incurred cost from the cost to finish

Invoices describe a portion of the cost picture. A forecast also needs commitments, work performed but not yet billed, expected changes, and the estimated cost of remaining work.

Eligible stored materials may enter monthly progress billing before site delivery or installation. Keep installed work, onsite storage, approved offsite storage, and in-transit or not-yet-delivered items distinct. After required submittal approval and release conditions, order to protect the supplier-confirmed lead time; support payment with the contract’s required approvals, identified material and owner-interest protection, applicable waivers, insurance, and delivery evidence. AIA’s offsite-payment discussion illustrates one contract approach. The project’s own terms control.

Use categories that the accounting and field teams can reconcile. Where productivity is relevant, compare installed quantities with the labor used and explain what is driving the difference. Avoid treating an unexplained favorable balance as savings when the associated work has simply moved later.

Give changes a next action

A change log should show more than a running total. Include the reason for the change, its current status, any supporting information still needed, its possible schedule effect, and the next decision date.

Distinguish a potential change from a priced proposal and an approved change. That separation keeps the cost forecast understandable and gives the team a way to see what remains unresolved. Keep the supporting records linked to the log so the next reviewer can follow the same evidence.

A returned submittal does not by itself change the contract scope. Record any deviation from the current requirements and follow the applicable substitution or formal change process, retaining the responsible reviewer’s disposition and any separate authorization.

Finish with a short decision record

The weekly record can use five fields:

• Issue: What changed or remains unresolved?
• Evidence: Which current specification section, drawing revision, submittal disposition, schedule update, field record, or cost entry supports it?
• Effect: Which work or forecast could change?
• Owner: Who is responsible for the next response?
• Required date: When is that response needed?

Carry unresolved items into the next review with their history intact. When an item closes, record the decision and its source. The purpose is to make the team's next actions clear and traceable.

After each meeting, distribute the meeting notes, decisions and action record to the team so the history is available without reading it aloud at the next meeting. Do not reread or rehash settled items simply because they appeared on an earlier agenda. Revisit a settled item only when confusion arising after the decision needs clarification; address that specific confusion, document the clarification and distribute the updated record. Otherwise, let the record stand and use meeting time for unresolved decisions and current actions.

Reviewing the schedule in detail

Use the construction schedule update checklist to check the status date, field evidence, remaining work, and milestone changes before issuing the next update.

A worked weekly cost and schedule report

Illustrative figures only. This fictional example is not an actual client report or a claim about a completed project. All amounts are in United States dollars and use the same reporting scope and status date, October 16, 2026.

Reconcile the forecast before writing the summary

The categories must not overlap. An approved change already included in a purchase order belongs in that commitment, not in unresolved exposure again. If the $60,000 issue is approved later, transfer its cost to the appropriate category and reconcile any budget adjustment separately. Approval alone does not create a new $60,000 cost.

Explain what changed and what requires a decision

The prior forecast was $1,230,000. This week it rose by $50,000: $35,000 for revised remaining labor and $15,000 for a newly identified interface issue. Those amounts are already included in the current cost categories above. They explain the movement; they are not added a second time.

The required completion date is November 12. The current schedule forecasts November 20, an eight-calendar-day variance. The equipment is already specified, but the contractor's current coordinated submittal still needs its required design and owner review disposition. The project manager needs that disposition by October 20 and the supplier's delivery confirmation before the team can evaluate a recovery sequence. The report does not promise recovery before that evidence exists.

The owner summary

“The forecast increased $50,000 this week to $1,280,000, leaving $20,000 below the approved budget. Completion is forecast eight calendar days after the required date. Please complete the assigned review of the contractor's current equipment submittal by October 20, referencing the applicable specification and drawing revisions. The project manager will then coordinate confirmation from the manufacturer and any upstream supplier for their own milestones, reconcile delivery with the carrier, and issue a revised sequence and cost effect. The $20,000 balance remains subject to the unresolved exposure in this report.”

The supporting record links each number to its cost entry, the schedule update, and the current equipment specification, drawing revision, and submittal disposition. The next review records whether the required reviews were completed, whether any conditions remain open, whether delivery was confirmed, and what changed in the forecast. For the corresponding field approval sequence, see the occupied-hospital planning example.

Use the monthly reporting tool without losing the weekly decisions

The Pacific Project Controls owner-reporting resource turns this review method into a reusable workbook and decision register. The company library contains original teaching tools with fictional examples; it does not reproduce a former employer's reports. Use the weekly meeting to maintain evidence and decisions, then reconcile those records at the monthly reporting cutoff.

Assign a meaning and a cutoff to every number

Before someone fills a dashboard cell, agree on its scope, unit, source and reporting date. “Cost to date” could mean cash paid, invoices received or cost incurred including accruals. Those are different measures. A report can show more than one, but each needs its own definition and reconciliation. The same rule applies to progress: a billing ratio measures billing against a stated value. Physical progress needs field evidence such as installed quantities or completed and accepted milestones.

Keep the weekly decision register open between reporting cycles. For each decision, retain the question, accountable role, required date, supporting record and consequence of delay. At month-end, freeze the report as issued. If a decision arrives the next morning, record it as a subsequent event rather than silently changing yesterday's evidence.

Test the message before presenting the dashboard

In a fictional review, the latest invoice may cover stored equipment while the installation area remains unavailable. The billing ratio rises, but that does not establish installed progress or release the next activity. Report the commercial event, the field constraint and the decision needed separately. Ask the receiving owner to identify the next action from the summary alone; if the action is unclear, improve the explanation before adding another chart.

For a changing allowance or pending proposal, use the companion allowance and change-control worksheet. Reconcile the issue when it changes status so approval, commitment and billing do not become three separate additions to the same forecast. The tools support a management conversation; they do not replace project accounting, contract interpretation or an approved schedule update.

Related work and background

The healthcare construction case study links to public project reporting. What Project Controls Really Do explains the broader role of scheduling, cost reporting, and documented decisions.

Ryan Lippmann works in construction project management and project controls and is the founder of TuneView.

Use the construction handoff checklist when responsibilities change. If the reporting process needs a new tool, the project controls software evaluation checklist provides a practical demonstration sequence.