Lesson 32 is where the design leaves the engineer's hands and becomes an instruction set. The one thing every student must leave with: the first move after a project is awarded isn't the vendor call, it's the handoff, a meeting plus a released drawing that puts every trade on the same page about the non-obvious decisions before mobilization. Don't teach it as paperwork. Teach it as the move that decides whether the project runs or the phone rings. Commissioning itself is Lesson 34; here you only plan the cutover.
| Segment | Min | What happens |
|---|---|---|
| Open on the debrief | 6 | Read the Monday-morning debrief question aloud, cold: Riverside said yes, the project's live, what's the first thing you do and who do you call? Don't answer it. Let every student commit to a first move in writing before you teach anything. |
| The drawing you hand off | 8 | The golden-plan standard, framed as the thing being released, not re-taught. The drawing's contents were built in Lesson 28. Here it gets released as the plan and defended. Land the line: every trade works from what's on that drawing. |
| The meeting and the skeletons | 16 | The center of the lesson. Run the incomplete-drawing exercise below. Surface we don't know what others don't know. The meeting walks the drawing with every trade in the room and calls out every non-obvious decision and its intent. |
| Interfaces and scope | 10 | Name every seam between trades: mechanical to electrical at the panels, electrical to controls at the Aux I/O and the WMS interface. Confirm every vendor's scope matches the released drawing. Agree the redline process, which Lesson 33 runs. |
| Brownfield cutover | 12 | Phased migration, rollback plans, uptime-protected windows, taught as concepts with no invented numbers. Run the STOP AND THINK. Hold the line: the operation can't stop shipping to let you install. |
| Checklist and close | 8 | Students build the six-item Riverside handoff package checklist. Close on the driving question: before the first bolt turns, does everyone know what you know? |
| Total | 60 | Baseline session. Expand with the 90-minute option below. |
Hand the room a drawing that's missing the speed callouts, the pull-cord E-stop path, and the accumulation zone release modes. Tell them they're the controls team on mobilization day. Now watch what they do. Some will invent workarounds. Some will call the engineer. Either answer opens the real conversation: why the drawing has to be complete and handed off before execution begins, and what it costs when it isn't.
Pair it with the vendor-call drill. Ask each student: if you were releasing this drawing tomorrow, which three vendors would you call first, and exactly what would you ask each one? The specificity of the answer is the tell. A student who names the controls team and asks for the setpoints they'll program has internalized the handoff. A student who says they'd send the drawing around and ask for comments has learned the word, not the habit.
Four failure patterns. Drive every one of them back to the same question: who's in the room, and what does each of them not know yet?
Run the Monday-morning debrief as a live discussion, not a written answer collected and moved past. Don't tell them the first move is the handoff. Ask. Steer the room until they discover for themselves that the vendor call comes after the handoff, not before it, and that Michael the maintenance lead belongs in the room from the start, because he works alone and has watched two systems fail on that floor. He lives with the result. He's in the meeting.
Then have them list Riverside's skeletons and interfaces before you show any of yours: the belted induction ahead of the merge, the mezzanine-decline landing, the offset transfer sensors, the forklift-aisle crossing, and the seams where each could get dropped. Hold the line on the cutover the whole way through: Riverside ships every day, so the plan has to protect daily shipping above the install schedule.
Question 1 (release with the controls team silent). Silence isn't sign-off. The controls team programs the setpoints, Aux I/O, and release modes off this drawing; releasing on the PM's four-day clock before they've confirmed it answers their scope pushes the gap onto mobilization day, where it becomes a field decision made without an engineer. Don't release on silence. Get the controls team on the phone first, even at the cost of a day; a day now is cheaper than a change order later. Strong answers name the failure mode (an unconfirmed drawing releasing straight to the field) and refuse to treat no-response as approval.
Question 2 (three flows, two-week window, can't go dark). Judgment answer, no single right sequence. Phase by flow: cut one flow at a time while the other two keep shipping on the existing path. Land the disruptive work in uptime-protected windows (off-shift, between waves, a light-volume day). The rollback for the first flow is the manual or legacy staging path kept open until that flow is proven and accepted, so if it isn't ready on the planned day the operation falls back and still ships. Watch for any plan that assumes the operation can stop, or cuts all three flows at once with no fallback.
The handoff package checklist the students build in this session is quietly the payoff of the project-folder easter egg that started in Lesson 1. The disciplined student who's kept organized project notes since the first Riverside voicemail already has most of these six items on hand: the drawing, the scope packages, the design decisions, the interface calls. They're not building the checklist from nothing. They're collecting what they already wrote down.
Don't say that out loud. Never explain the habit or where it leads. Just notice which students reach for existing notes and which start from a blank page, and let the difference teach itself. The ones who kept the folder feel the reward without being told to expect it. That's the whole point.