Advanced Guide to End-to-End Construction Project Controls

Project controls is a weekly operating system that forces decisions early, not a month-end report pack you read after the job has already drifted.

Think of a flight computer in a commercial aircraft. It doesn't just record the route after landing. It links speed, altitude, and fuel burn live so the pilot can correct course before the plane runs out of options. Your job needs the same live linkage between scope, schedule, cost, and field reality.

Controls spine

The minimum connected set of schedule, cost, change, and document controls that share the same job structure and run on a fixed cadence, with explicit decision triggers that force action before drift becomes damage.

Single job structure

One consistent breakdown that ties cost codes, CPM schedule activities, and the Schedule of Values (SOV) to the same work packages.

Cadence

The non-negotiable rhythm for updates and decisions: daily field capture, weekly operating review, monthly pay app and forecast sign-off.

Decision trigger

A clear threshold that forces a named person to act within a stated timeframe. Not a flag for discussion. An obligation to decide.

Disconnected controls turn small misses into unrecoverable misses. On a $14.2M tenant improvement, a two-week RFI backlog can create $86k of idle-crew time and re-sequencing cost. If the RFI log doesn't feed the CPM update, and the CPM update doesn't feed the cost-to-complete forecast, that $86k stays invisible until the AIA G702/G703 pay app reconciliation, when you've already burned the labor and lost the schedule float.

The seven controls, with decision workflows and triggers

You need seven controls, each with a named owner, a set cadence, a required artifact, and a decision trigger that removes ambiguity about when to act. The table below is your implementation template.

The weekly operating review: where the spine connects

Controls only work if they meet in one room, on one agenda, every week. Here is the meeting structure that ties the seven controls together.

• Meeting: Weekly Project Operating Review. 60 minutes maximum. Every Thursday at 3 PM (after the CPM update is posted at 2 PM).
• Attendees: PM (chairs), superintendent, project engineer, scheduler (if separate from PM), and project accountant or cost controller.
• Standing agenda, in order:
  1. Schedule status (10 min): scheduler presents critical path movement, float consumption, and any triggered thresholds. Super confirms lookahead alignment.
  2. RFI/submittal aging (10 min): PE presents aged items. Any item past its trigger threshold gets an owner and a resolution date assigned live in the meeting.
  3. Change Order exposure (10 min): PM reviews the PCOR. Running total of unapproved changes is stated as a dollar value and a percentage of contract. If the 3% trigger is hit, the escalation letter is drafted before the meeting ends.
  4. Cost and forecast (15 min): PM walks through cost codes with CPI below 0.95 or margin erosion above 2 points. Each gets a one-line recovery action or an explicit decision to accept the variance.
  5. Progress vs. billing (10 min): PM and super reconcile any SOV line with a 5%+ variance. Overbilling accruals and underbilling claims are resolved before the monthly pay app.
  6. Action log (5 min): every decision and escalation is recorded with an owner and a due date. Open items from last week are closed or escalated.

This meeting produces one artifact: a one-page action log with owner, due date, and trigger source. That log is the audit trail that proves your controls system runs, not just exists.

On a $22M multifamily project, a PM running this exact cadence caught a mechanical subcontractor's $310k re-sequencing exposure at week three, not week eleven. The CPI on the HVAC cost code dropped to 0.93 after two weekly updates. The trigger fired at the Thursday review. The recovery plan, negotiated labor rate adjustments and a revised rough-in sequence, saved $185k against what the final cost would have been without intervention. That's the difference between a controls spine and a filing system. In Archdesk, each of these triggers can be configured as automatic alerts on the live project dashboard, so the CPI drop or the aged RFI hits the PM's screen the day it crosses the threshold, not whenever someone remembers to pull a report.

Map quantities to activities

Setting: a 38,600 sq ft tenant improvement for a law firm across floors 12 to 14 of a live downtown tower. Contract is $8.74M under AIA A201, 26-week CPM schedule, and you are building the baseline and the first Schedule of Values (AIA G702/G703). The takeoff is detailed, but the draft schedule has lump activities like “Interiors”, “MEP Rough-in”, and “Paint”.

Worked example: split takeoff quantities into activities you can measure, buy, and bill

1. Start with three split rules. Split an activity if it crosses (1) locations with different predecessors, (2) trades that report progress separately, or (3) materials with different procurement paths.

   Failure mode: one “Paint” activity shows 14 days duration, but the work runs across about 10 weeks because you mobilize for primer, then finish coats, then touch-ups.

2. Pick three estimate lines that usually get lumped. Keep it real and pick trades that drive sequencing, submittals, and billing: drywall partitions, ACT ceilings, and paint.

   Takeoff and budgets: partitions 98,420 sq ft at $932,700, ACT ceilings 41,600 sq ft at $266,240, paint 31,400 sq ft at $78,500.

3. Split by floor first, because predecessor logic differs. Floor 12 can release while Floor 14 is still in design review and RFI cycles. If you don’t split, Floor 12 progress hides Floor 14 constraint.

   Estimate line	Total qty	How you split into activities	Qty per activity	Budget per activity
   Metal studs + 5/8 in gyp partitions	98,420 sq ft	“Partitions, Floor 12”, “Partitions, Floor 13”, “Partitions, Floor 14”	31,940 / 33,110 / 33,370 sq ft	$301,874 / $312,480 / $318,346
   ACT ceilings	41,600 sq ft	Split by floor and phase, “Grid install” then “Tile install”	13,540 / 13,860 / 14,200 sq ft (each phase)	Grid: $43,328 / $44,352 / $45,440 Tile: $45,702 / $46,782 / $47,930
   Interior paint	31,400 sq ft	Split by execution phase, “Primer”, “Finish coats”, “Touch-up and punch”	31,400 / 31,400 / 31,400 sq ft	$18,300 / $47,600 / $12,600

4. Add procurement gates where lead times can strand crews. One “Ceilings” activity hides constraints like specialty lights and linear diffusers that hold tile install. Put a $0 activity per floor, “ACT materials released and on site”, as a predecessor to “ACT tile install”.

   That turns a hidden risk into visible logic, so the schedule shows why tile install is not ready even if grid is 100%.

5. Calculate earned value from installed quantities, not opinions. Floor 13 partitions budget is $312,480 for 33,110 sq ft, so the budget rate is $312,480 / 33,110 = $9.44 per sq ft.

   Daily reports show 7,860 sq ft framed and boarded on Floor 13 by end of week 6. Earned value for that activity is 7,860 x $9.44 = $74,198. The percent complete is 7,860 / 33,110 = 23.7%, with numbers you can defend.

6. See what the split fixes in a schedule update and pay app. Week 12 “gut-feel” on lump activities often reads like “drywall 60%, paint 40%, ceilings 50%” because two floors are moving and one is stuck.

   Split activities force honesty: Floor 12 partitions can be 100% ($301,874), Floor 13 can be 76.3% ($238,508), and Floor 14 can be 0% ($318,346) if an RFI is blocking layout. Your SOV backup and your CPM update stop arguing with each other.

Takeaway

Activity splits are not “extra detail”. They stop one bar on the schedule from hiding three work fronts and two different constraints, which is where earned value and cash forecasts fall apart. The non-obvious win is early visibility: the moment Floor 14 shows 0% against a $318,346 activity, you can push the RFI and resequence labor in week 3, not explain a miss in month 3.

A billable Schedule of Values (SOV) is a measurement rulebook. Each line has a clear test for what "earned" means, so your pay app, retainage, stored materials, and earned value all agree.

Think of it like a restaurant menu with fixed prices. The kitchen can cook all night, but if the dish is not on the menu with a price next to it, you cannot charge for it. A weak SOV leaves real work off the menu, then you finance it until you fight about percent complete.

Schedule of Values (SOV)

The itemized breakdown of the contract sum used for progress billing under the AIA G702 (Application and Certificate for Payment) and G703 (Continuation Sheet). The lines must total exactly to the current contract value, including approved Change Orders.

Scheduled Value

The dollar value assigned to an SOV line. It is the cap for what you can bill when that line reaches 100% complete.

Percent Complete (by value)

The portion of a line's scheduled value earned through installed work, backed by an objective rule like inspected quantities or a defined milestone. Time passed is not evidence.

Stored Materials

Materials delivered to site, or to an approved off-site location, but not yet installed. Billed separately with invoices, delivery tickets, photos, and the storage location so the owner can verify what they are paying for.

Worked example: MEP package on a $9.65M commercial fit-out

Below is an excerpt from a real-shaped G703 continuation sheet for a $2.18M mechanical scope. Study the line-item structure, measurement rules, and how stored materials move to installed without creating disputes.

Those seven lines total $1,426,000. The full mechanical scope fills roughly 18 lines. The key point: no line exceeds $400k, every line has one measurement rule that doesn't change, and procurement is split from installation only where the item has a genuine lead time and clear serial-number tracking.

How stored materials move to installed on a pay app

Line 14.1 (AHU procurement, $312,400) shows the movement across three billing cycles on the G703:

Pay App #4: all four AHUs arrive and pass inspection. $312,400 enters "Materials Stored." Pay App #5: all four are set on pads. $312,400 moves from "Stored" to "Work Completed This Period," and "Stored" drops to $0. Total earned doesn't change. No double billing, no inflated progress. The stored-to-installed swap is a lateral move on the same line in the same cycle.

Retainage math that keeps the line honest

At 10% retainage on the $2.18M mechanical scope, $218,000 is held until Substantial Completion. That's real cash your business finances. A single blended line like "Mechanical – complete" at $2.18M invites the owner's rep to cut percent complete by 3-5% each month. On a blended line, a 5% cut means $109,000 of disputed value and roughly $98,100 in deferred cash after retainage. Split into 18 lines with objective rules, each dispute is capped at the line value. A 5% cut on the $386,200 ductwork line is $19,310, not $109,000. That's a fight worth having. The other 17 lines pay on time.

Aligning SOV lines to earned value

Earned value needs a planned budget per activity (BCWS) and an objective measure of progress (BCWP). The SOV already provides both if you build it right. Each SOV line's scheduled value is your BCWS. Each line's measurement rule gives you BCWP. Map every SOV line to a CPM schedule activity ID. When you bill 2,200 LF of the 3,600 LF copper piping, your earned value is 61.1% of $295,000, or $180,450. Your cost system shows $192,000 spent on that activity. CPI is 0.94, telling you the piping scope is running 6% over budget while it's still fixable. In Archdesk, this earned-value alignment happens automatically: as subcontractor valuations and committed PO costs post against schedule activities, cost-to-date and forecast final account update in the CVR view, so a $12,000 overrun on copper piping surfaces the same week it opens, not at the quarterly reconciliation.

Setting: a $9.65M GC contract for a 72,400 sq ft medical office tenant improvement in Phoenix, under AIA A102 (GMP) with a 38-week schedule. You're closing period 6, and the owner wants a lender-ready forecast. Job cost shows $3,410,800 spent, and the field team says "we're fine".

The trap is treating actual cost as total exposure. Your margin moves first in buyout gaps, committed-but-unbilled costs, and trend items that are real work but not yet an approved Change Order.

Step-by-step: build a CVR-style EAC (Estimate at Completion)

1. Lock your control totals. Contract value is $9,650,000. Your Budget at Completion (BAC, your full cost-loaded estimate across all packages, including general conditions) is $8,912,430. Starting planned margin: $9,650,000 minus $8,912,430 = $737,570 (7.6%).

2. Pull "committed" correctly. Committed cost means executed subcontracts plus issued purchase orders. Verbal quotes and "we're close" emails count as $0 in a forecast.

3. Calculate buyout gap per package. Buyout gap = committed minus budget. If electrical is bought out $58,690 over budget, that loss is already locked in even if no invoice has landed.

4. Add trend exposure as cost, not a note. Trend exposure is known scope or time pressure without an approved Change Order yet. Carry it in the forecast until it's formally denied in writing.

5. Forecast cost to complete (CTC) from the remaining work. Don't use "budget minus cost to date". Use remaining quantities, production rates, and committed-but-unbilled amounts. CTC must include both the remaining committed scope and any trend exposure that will become real cost.

6. Calculate EAC per line. EAC = cost to date + CTC. The CTC figure already bakes in trend exposure. Forecast variance = EAC minus budget.

Roll up to the job-level forecast

The table covers seven packages totaling $7,912,430 of the $8,912,430 BAC. The remaining $1,000,000 sits in other packages (sitework, fire protection, elevator, closeout) that are currently tracking to budget. Their EAC equals their budget, so the job-level roll-up is:

• Total BAC: $8,912,430
• Total committed (all packages): $9,007,370 ($8,007,370 from the table + $1,000,000 in remaining packages at budget)
• Total cost to date: $3,411,800
• Total CTC: $5,965,450 ($4,965,450 from the table + $1,000,000 remaining packages)
• Job EAC: $3,411,800 + $5,965,450 = $9,377,250
• Forecast variance to BAC: $9,377,250 − $8,912,430 = +$464,820 over budget
• Forecast margin: $9,650,000 − $9,377,250 = $272,750 (2.8%)
• Margin erosion: $737,570 − $272,750 = $464,820, cutting margin from 7.6% to 2.8%

Notice where the damage sits. Of that $464,820 overrun, $311,520 (67%) is trend exposure, not invoiced cost. The field team sees $3.41M billed against a $8.9M budget and feels comfortable. The CVR sees $311k in trends plus $94,940 in buyout losses and shows a margin that has halved.

One-paragraph EAC narrative (copy and edit for your report)

"Period 6 job-level EAC is $9,377,250 against a BAC of $8,912,430, forecast margin of $272,750 (2.8%) versus planned 7.6%. Three drivers account for 73% of the $464,820 variance: electrical is +$155,140 due to a $58,690 buyout loss plus $96,450 in trends tied to feeder re-routing and acceleration to protect the ceiling-close milestone; HVAC is +$142,950, with $84,300 in trends from controls and TAB scope growth pending Change Order approval; concrete is +$51,970 on a $33,550 buyout gap plus $18,420 in trend exposure for additional housekeeping pads. Of the total overrun, $311,520 (67%) remains as un-converted trend exposure. Next actions: price and submit $311,520 of trends as Change Orders tied to existing RFIs and field directives within the next billing cycle, lock the HVAC controls scope in the next OAC meeting, and reforecast general conditions weekly until the 19-day schedule drag is recovered or absorbed."

The lesson: "budget minus cost to date" tells you nothing about where you'll land. EAC = cost to date + CTC, and the CTC must include trend exposure and buyout gaps already locked in your subcontracts and POs. In Archdesk, this is the CVR view: committed PO values, subcontractor pay applications, and trend items feed straight into cost to date and CTC columns, so a $58,690 buyout gap on electrical shows up the week that subcontract is executed, and the job-level margin recalculates automatically, not at month-end when it's too late to trade it out.

Run change orders like a production line. Every potential change moves through the same statuses, with the same attachments and aging rules, until it is approved, time-adjusted, billed, and collected.

Think of it like an insurance claim. You can have a real loss, do the repair, and still get paid $0 because you missed the filing window or sent the wrong backup. Extra work on site is the same. The work can be real and still be unbillable if it never becomes an approved Change Order with the right attachments.

Potential Change Order (PCO)

A change event you have identified, but not yet fully agreed on cost and time. This is the placeholder that stops extra work from being buried in base cost codes.

Change Order Request (COR)

Your formal submission with pricing backup and time impact, tied to the contract basis (RFI response, owner/architect directive, differing site condition notice, ASI, CCD).

Construction Change Directive (CCD)

An AIA or ConsensusDocs instruction to proceed before price and time are agreed. Your cost and schedule links must start same-day.

Change order aging

How many calendar days the item has sat in its current status. Aging is your trigger to escalate before entitlement and cash go stale.

Worked example: PCO-047 on a $9.6M office build-out

Follow one change from discovery to collection so you can see every handoff, every document, and every aging trigger.

Day 0, Monday, PCO Open. The superintendent finds unforeseen rock 4 feet below grade during elevator pit excavation. He logs a daily report with photos and GPS coordinates, and calls the PM. The PM opens PCO-047 within 24 hours, links it to Daily Report #112 and the differing site condition clause (AIA A201 §3.7.4), and creates a dedicated cost code (CO-047-ROCK). From this moment every timecard, equipment ticket, and material invoice for this work hits CO-047-ROCK, not base scope.

Days 1–4, PCO Priced. The PM pulls labor actuals (3 operators × 2 days at $94/hr = $4,512), equipment (hydraulic breaker rental, $1,800/day × 2 days = $3,600), trucking and disposal ($2,100), and subcontractor re-mobilization ($1,650). Markups per contract: 15% OH&P on self-performed ($1,217), 10% on sub ($165). Total: $13,244. The PM writes assumptions in plain English: "Rock class assumed Type B per geotech report; if Type A encountered, unit rate increases 40%."

Day 5, Time impact documented. The PM builds a simple fragnet (a short chain of activities inserted into the current schedule). It shows the two extra excavation days pushed the elevator pit concrete pour from Day 38 to Day 40, which shifted the elevator rough-in start by two days on the critical path. The fragnet attaches to COR-047 with a before-and-after schedule comparison PDF and a written Time Impact Analysis (TIA) stating: "Net impact: 2 calendar days added to Substantial Completion, no concurrent delay identified." This is the step most teams skip. Without a fragnet tied to named schedule activities, the owner's consultant will reject the time extension and you lose the delay damages defense.

Day 5, COR Submitted. COR-047 goes to the owner's representative with this backup pack:

• Daily reports with photos (days 0–2)
• Labor timecards coded to CO-047-ROCK
• Equipment rental invoices
• Subcontractor re-mob quote
• Cost summary with markups per contract schedule of rates
• Fragnet and written TIA
• Reference to contract clause (AIA A201 §3.7.4)

Days 6–18, Under Review. The owner's consultant asks two questions on Day 9. Each question gets logged with a due date and a single owner on your team. At Day 14 with no decision, the PM sends a written escalation: "Per AIA A201 §7.3, COR-047 has been under review for 14 calendar days. Please confirm acceptance, rejection, or issue a CCD to proceed." This escalation letter is non-negotiable. Without it, the change sits in limbo and you lose use.

Day 20, CO Approved. The owner executes Change Order #12 for $13,244 and 2 calendar days. Now two things happen immediately: the contract sum updates from $9,600,000 to $9,613,244, and the Substantial Completion date moves from October 14 to October 16 in the baseline schedule.

Billing the approved change: pay app and SOV steps

An approved CO that never makes it onto the Schedule of Values is the same as an unapproved one. Here is exactly how CO #12 becomes cash.

Step 1, Add a new SOV line. In the next pay application (say, Pay App #5), add line item 14.12: "CO #12, Unforeseen Rock Removal, Elevator Pit" with a scheduled value of $13,244. Do not bury it inside an existing line. Owners and their consultants reject pay apps when change work is lumped into base scope lines because they can't verify what they're approving.

Step 2, Bill completed work. If the rock removal is 100% complete, bill $13,244 on line 14.12. The "% Complete" column shows 100%, and the "Work Completed This Period" column shows $13,244. Retainage applies per the contract rate (typically 5–10%), so at 10% retainage, you collect $11,920 on this line.

Step 3, Attach backup to the pay app. Staple the executed CO, the COR with full backup, and the coded cost reports behind the pay app. The owner's rep will cross-check. Missing backup is the number one reason COs get kicked from a pay app cycle, costing you 30 days of cash flow.

Step 4, Track retainage release. The $1,324 held as retainage on CO #12 releases at Substantial Completion per the same retainage schedule as base contract work. Log it separately so it doesn't get lost in the retainage reconciliation at closeout.

Status register with aging rules

The operating rule that protects entitlement

Every PCO must link to three things or it is not a real record: the cause document (RFI, ASI, CCD, directive, daily report), the exact schedule activities it touches, and the cost codes where labor and material are landing. That triple linkage turns a pay app backup pack into claim-ready proof instead of a story you assemble at closeout.

Setting: a $4.85M Class A office tenant improvement in Dallas, 38,600 sq ft, AIA A101, 22-week schedule. End of week 9, the GC wants earned value driven off the Schedule of Values (SOV), but only where percent complete is measured from installed quantities or signed-off milestones. A late RFI on ceiling plenum heights has slowed HVAC rough-in and is now blocking drywall close-up.

Step 1: Build PV, EV, and AC from the SOV and the week-9 schedule update

Planned Value (PV) comes from the baseline schedule percent for each SOV line at week 9. Earned Value (EV) comes from measured progress rules. Actual Cost (AC) comes from job cost to date, not billing, and you keep stored materials separate so EV doesn't get overstated.

Step 2: Calculate SPI, CPI, SV, and CV from those totals

1. SPI = EV ÷ PV. $1,417,480 ÷ $1,536,510 = 0.92. You're earning 92% of the progress you planned.
2. CPI = EV ÷ AC. $1,417,480 ÷ $1,504,250 = 0.94. You're getting $0.94 of budgeted value for every $1.00 spent.
3. SV = EV − PV. $1,417,480 − $1,536,510 = −$119,030. That's the dollarized schedule shortfall.
4. CV = EV − AC. $1,417,480 − $1,504,250 = −$86,770. That's the cost overrun already baked in.

Step 3: Forecast EAC and ETC using three formulas, then pick the right one

Full contract BAC is $4,850,000. The remaining work is BAC − EV = $4,850,000 − $1,417,480 = $3,432,520. Three EAC variants give you three different answers, and each one tells you something different about the job.

When to use each one:

• CPI-only assumes cost inefficiency continues at the current rate, but schedule recovers to plan. Use it when the schedule slip is caused by a one-off event you've already fixed, like an RFI that's now answered.
• CPI × SPI assumes both cost overruns and schedule delays keep compounding on the remaining work. Use it when the schedule problem is systemic, like labor shortages or a procurement chain that won't speed up. On this job, the HVAC RFI is still unresolved and blocking drywall, so CPI × SPI is the more honest forecast until the constraint clears.
• Bottom-up is the PM's independent re-estimate. It should always be run alongside the index forecasts as a cross-check.

Step 4: Credibility checks on the indices

Duration threshold. Week 9 of 22 is 41% through the planned duration. You've earned $1.42M of $4.85M (29% of value). Both indices have enough data behind them to act on. Waiting for "more data" just means you spend more money before you act.

Gap test between index EAC and bottom-up EAC. The CPI × SPI forecast ($5,473,851) is $584,251 above the bottom-up number ($4,889,600). That's a 12% gap. Anything over 5% means one of the two estimates is wrong. Here, the most likely cause is that the bottom-up hasn't priced the downstream drywall delay caused by HVAC. If the PM's re-estimate doesn't account for idle framing crews waiting on rough-in clearance, the bottom-up is understated. In Archdesk, this gap shows up in the CVR view as soon as subcontractor valuations and PO commitments hit the system, so the $584k discrepancy surfaces the same week instead of at the next monthly reconciliation.

Line-level sanity check. CPI on electrical rough-in is $382,980 ÷ $364,200 = 1.05. Electrical is ahead of plan and under budget. HVAC CPI is $427,120 ÷ $486,300 = 0.88. One trade is masking the other in the blended index. Always check CPI per SOV line before you trust the project-level number.

Takeaway

The non-obvious lesson: the CPI-only and CPI × SPI forecasts bracket your risk, not predict it. On this job, they produce a $317k spread ($5,156k vs $5,474k). That spread is your management question: do you believe the HVAC constraint is a one-off or a systemic drag? The action is commercial and operational in the same week. Price the $38,400 HVAC change order tied to the RFI delay and submit it before the next pay app. Re-sequence drywall to areas with completed rough-in so you stop the EV bleed. And run both EAC formulas every week until CPI × SPI and CPI-only converge, because convergence tells you the schedule problem is actually fixed, not just reported as fixed.

Project controls protect your margin when schedule, cost, and change all point to the same work packages. CPI, SPI, and EAC should drive decisions every week, not excuses at month-end. Below is a day-by-day calendar, with specific deliverables, templates, and meeting formats you can copy straight onto a live job.

Week 1 (Days 1–7): Lock the foundations

Week 2 (Days 8–14): Set the rules and baselines

Week 3 (Days 15–21): Launch the weekly cadence

Start the Weekly Production & Forecast Huddle. 60 minutes, same day and time every week, never canceled. Here is the five-item agenda, with time boxes:

1. CPI and SPI by cost code (10 min). Flag any code where CPI < 0.95 or SPI < 0.95. Name one owner and one corrective action per flag.
2. Buyout gap update (10 min). How much budget is uncommitted? Which packages bid above budget? Decision: rebid, value-engineer, or absorb and adjust EAC.
3. Top 5 aging RFIs by float impact (10 min). Sort RFIs by days open × float consumed. Any RFI open > 10 working days with critical-path impact gets an escalation call the same afternoon.
4. Top 3 trend items by dollars (10 min). Trends are potential changes not yet priced. For each: estimated cost, schedule impact, and owner responsible for pricing by next huddle.
5. Action tracker review (10 min). Every action from last week: done, in progress, or overdue. Overdue items get a new due date and an escalation path. If the meeting produces no actions, the meeting was wasted.

Capture minutes in a standing template: Date, Attendees, five-item summary, Action Items (Owner, Due Date, Status). Distribute within two hours of the meeting ending.

Week 4 (Days 22–30): Run the first monthly commercial close

The monthly close produces one output: a two-page Project Health Summary sent to leadership. Page one is a table of CPI, SPI, EAC, buyout gap, and retainage position. Page two lists the top five risks by dollar exposure, each with an owner, a mitigation plan, and a deadline. In Archdesk, this summary pulls directly from the CVR view, where cost-to-date, value earned, and forecast final account update automatically as subcontractor valuations and PO commitments are entered, so the buyout gap or a WIP variance shows up the same week it opens instead of surfacing at the quarterly reconciliation.

Ongoing cadence after Day 30

• Weekly: 60-minute Production & Forecast Huddle (the five-item agenda above). Update CPI, SPI, and log aging data every Friday before the meeting.
• Monthly: Commercial close on the last working day of the month. Reconcile pay apps, committed costs, EAC, and retainage. Publish the two-page Project Health Summary within 48 hours.
• Quarterly: Schedule a 90-minute baseline review. Re-run the five schedule quality checks from Day 3. If logic-tie density has dropped below 90% or hard constraints have crept in, fix before the next pay app cycle.

What to learn next

• Time Impact Analysis (TIA) basics. Change orders get decided on entitlement and CPM cause-and-effect, not on who argues best in the trailer.
• DCMA-style schedule checks. Missing logic and hard constraints create fake critical paths. Every delay discussion turns into opinion without them.
• Trade-level labor productivity tracking. CPI can look fine while one crew installs 15% fewer square feet per day than the bid. That's how a $180k overrun appears "out of nowhere" at closeout.