Lesson 33: Execution Support, Instructor Session Plan

The build is live, and the student's job just changed from producing the design to protecting it. Two ideas have to land: a field change is never evaluated locally, and the as-built is a legal document. If they leave here still saying yes or no on the phone, or still treating redlines as end-of-project paperwork, the lesson didn't take. Teach it as the resource half of the job, not the paperwork half.

Run of Show (60-minute baseline)

Segment	Min	What happens
The 7 a.m. field call	6	Open on the field call. Two minutes versus voicemail. Make the point that availability during execution is active, not passive, and that the role has shifted from producer to resource.
Architect and the lane	8	Architect and resource, not project manager. Draw the lane: the PM owns schedule, budget, and subs; the engineer owns the design. Ask the room which questions belong to whom.
Field scenarios and the folder	10	Walk the three recurring scenarios: missing part, question about intent, setpoint question. Land the folder as the speed advantage. The folder is the difference between a two-minute answer and reconstructing under pressure.
Change-impact matrix + ripple	16	Core segment. Walk the change-request table. Then run the ripple exercise below: hand them a minor-looking change and make them map every element it touches. The miss is the lesson.
Redlines and the as-built	10	Redline governance on a cadence, not at the end. Then the as-built as a legal document. Use the five-years-later expansion to make legal concrete, not abstract.
Close and the Riverside change	10	Project-close controls: what makes a folder closed. Then run the Riverside decline-landing change as a live change-impact build. Collect their downstream lists.
Total	60	Baseline session. Expand with the stretch options below if you have 90 minutes.

Stretch options (for a 90-minute block):

Three change requests of increasing subtlety (add 20 min): run three changes, each with a less obvious downstream effect than the last, and time how long it takes the room to find every one. The clock makes the discipline visible.
Argue the local view (add 5 min): have one student defend approving the column shift on the spot, then have the room trace what it missed downstream.
Build a redline log (add 10 min): give the room the Riverside redline stack and have them sort it into within-intent and needs-design-work before it becomes an as-built.

KEY TEACHING MOMENT

Give the room a change request that looks minor. The column shift works, or invent one of your own. Ask them to map every element of the system it touches. Do not accept the first three answers as complete. Plenty of students will miss one, curve geometry or pull-cord spacing usually.

Use the miss as the lesson. The change-impact discipline is exactly for the consequence they didn't see. Then reinforce the two anchors: as-builts are legal documents, and the folder protects both the customer and the engineer on every future conversation about this system. That is why the evaluation gets documented, not just done.

WATCH-FORS

Four failure patterns show up in this lesson. Drive every one of them back to the same two questions: what else does this affect, and whose job is this?

Students who answer a change yes or no on the spot. The installer standing there waiting is not a reason to skip the downstream check. Tell them: call back, don't guess back.
Students who evaluate a change locally and never trace it downstream. Push them past the obvious effect. Ask what the accumulation zone does when the position moves.
Students who treat redlines as end-of-project paperwork. Correct the cadence: collect at every visit, process right away. A redline on the clipboard is a gap in the record.
Students who blur the lane and try to own the schedule. Name it. The PM owns schedule and budget. The engineer owns the design. Both matter; they are not the same job.

RIVERSIDE FACILITATION

Run the decline-landing change as a live change-impact exercise. The crew finds the horizontal run off the mezzanine edge is obstructed and wants to shift where the powered decline lands. Do not hand them the downstream effects. Make the room build the list.

Steer them to the Tall Case tumble limit on their own. Do not tell them; ask. The 10 by 8 by 14 carton has a high center of gravity, and shifting the landing changes the decline angle, which reaches the tumble limit. If they don't get there, ask what a decline change does to the tall, narrow box in the mix. If a student wants to run the tumble or gap arithmetic, redirect: that math is L14 and L25. Here the skill is knowing the change reaches those calculations before you approve it, not running them in the room.

CHECKPOINT ANSWER KEY

Question 1 (column shift, local versus system). Don't answer yes or no on the phone. The process is the change-impact matrix: the first question is never "can you do it," it's "what else does this affect." Trace the eighteen-inch shift through everything the drawing connects, curve geometry, accumulation zone length, sensor placement and the PLC delay the timing leans on, pull-cord spacing, and the rate the original speed was set to hit. Document the evaluation; if it needs design work, that work happens before the field proceeds, and if it touches scope, cost, or schedule it becomes a formal change order with written confirmation behind any verbal yes. Evaluating locally means checking only whether the move clears the column and fits the run right there. Evaluating at the system level means following the ripple outward, because a change to one section never happens in isolation. Watch for a student who approves on the spot or stops at the column; the answer you want traces the effects the installer can't see and calls back with the downstream check instead of guessing back.

Question 2 (redline stack, memory habit). Review every redline, decide whether each change was within design intent, update the drawing to what got built, and produce the as-built set. Govern them on a cadence: collect at every visit, not at the end, and process them right away, because a redline that stays on the clipboard never becomes an as-built. The as-built is a legal document; a customer expanding five years out designs from it, and if it doesn't match reality they start from a false premise. The memory habit sets up the failure mode this lesson is built to prevent: with the design only in one person's head, retrieval is slow under pressure, the wrong setpoint gets programmed and misses rate at commissioning, and when that engineer is unreachable or gone nobody can reconstruct why the system is built the way it is. The folder protects both the customer and the engineer. Strong answers name the as-built as a legal document and name the specific failure the memory habit invites, not just "keep better notes."

INSTRUCTOR ONLY | DO NOT SHARE WITH STUDENTS

The change-impact evaluations and the redline log are project-folder artifacts. A student who has kept the folder current across the whole program is walking into this close with much of it already done. Their evaluations are filed, their redlines are logged, and the as-built practically assembles itself from what they've been keeping all along.

Never explain that out loud. Just keep reinforcing the habit, the way you have since Lesson 1. The payoff belongs to the students who kept the folder without being told why. Let them find it here, at the close, on their own.