Lesson 2.1

The end of the job IS the job

Startup phase: sequence the checkout (407), schedule FPTs with the CxA (308), and drive the punch list to zero — tracked items, owners, dates; never a seasonal mood.
Closeout is money: as-builts, O&M, training, verified backups are contract obligations tied to retainage — the cash is literally in the documents (206/407's packages, priced).
Warranty writes reputation: tracked response, root-cause fixes (302), honest communication (309's laws at project scale — bad news early).
The service handoff: baseline docs, known issues, contacts, open items — the building's file goes live with the service team (307's asset, born here).
Margin management runs the whole arc: protect estimate margin via change discipline, labor tracking, and buyout wins — margin is defended weekly, not discovered at closeout.
Close the loop: post-job review feeds estimating actuals, standards updates, institutional memory (ES/409). The PM's product: profitable job, working building, documented turnover, customer who calls again.

LAB — run the simulated job

Inherit a mid-project controls job (schedule, budget burn, sub status supplied) with four injects arriving over the session: a GC slip compressing startup, an out-of-scope directive from the owner's rep, a labor overrun signal, and a failed FPT week before turnover.
For each inject: decide, document (log entry, CO paper, recovery plan), and communicate (the email you would actually send).
Assemble the closeout checklist mapping every deliverable to its retainage release requirement.

Pass: injects handled with paper and honest comms; closeout mapped to money.

LAB DEMO VIDEO

Instructor walkthrough — handling the GC-slip and out-of-scope injects

[ ~12 min ]

The controls PM dashboard — one-page job view: schedule ribbon (controls last, float flags), labor burn vs estimate curve, change-order pipeline, punch trend to zero, closeout/retainage checklist — inject icons showing where the four classics strike