Today's Checklist
Daily rounds — 0/7
Stored on this device and reset automatically each day.
⚠ Log a delay
Delay log — last 7 days
The CSV covers every delay ever logged on this device — drop it straight into the weekly report.
Construction Scheduler Field Guide
Plain-English concepts, live calculators, and CPM practice — the working reference for schedulers who lead the plan instead of just typing it.
Start Here: What a Scheduler Actually Does
The job in one loop
Hover (or tap) each step to see what happens in that phase. The loop never stops — that's the job.
A schedule, building itself
Five tasks, four Finish-to-Start ties, one data date. Every bar starts where its predecessor ends — that cascade is the whole idea of CPM.
Your real product: translation
P6 speaks in float, logic, and data dates. The field speaks in crews, areas, and consequences. The scheduler's most valuable work is converting one into the other — in both directions. Numbers go out to the field as consequences and choices; field reality comes back into the model as logic and durations.
| The schedule says | What you say to the superintendent |
|---|---|
| "Level 2 MEP rough-in, TF = 3" | "The pipe crew has three days of cushion left. One more slow week and they set the building's finish date." |
| "Negative float −5 on the elevator chain" | "As of today, the elevator chain finishes five days late. Something has to give — sequence, crew size, or the date. Which lever do you want to pull?" |
| "Out-of-sequence progress in Area B" | "Your crews are building B in a different order than the plan assumed. Walk me through how you're actually sequencing it and I'll make the schedule match." |
| "Footings finished 8 days behind baseline" | "Footings cost us eight days against the promise. Here's what it pushed — and two places we could buy the time back." |
| "SPI = 0.85" | "For every day of progress we planned, we're getting 0.85 of a day. At this pace the finish moves — here's when we'd cross the line." |
The pattern: number → consequence → choice. Never hand the field a metric without the decision it points to. That's the difference between reporting the schedule and leading with it.
Who's who on a GC project
Terms & Acronyms (Spelled Out)
Every acronym is spelled out, every term explained in plain English — the same way you should explain it in the field. If you can't say it simply, you can't lead with it. Use the search box or filter by category.
Logic Ties: How Activities Connect
The 4 relationship types — watch the dependency flow
The moving gold arrow is the dependency: it leaves the predecessor at the event that triggers it (start or finish) and arrives at the successor at the event it controls.
| Type | Spelled out | Rule | Construction example | How common |
|---|---|---|---|---|
| FS | Finish-to-Start | B can't start until A finishes | Finish pouring the slab → start framing walls | ~90% — the default. Checkers want ≥90% FS. |
| SS | Start-to-Start | B can't start until A starts | Start excavating → 2 days later, start installing shoring behind the digger | Sometimes — for overlapping work |
| FF | Finish-to-Finish | B can't finish until A finishes | Duct inspection can't wrap up until duct installation wraps up | Sometimes |
| SF | Start-to-Finish | B can't finish until A starts | Temporary power keeps running until the permanent system starts. Almost never used — if you see one, ask why. | Rare — schedule checkers flag these |
Lags and leads
A lag is a built-in waiting period on a relationship. "FS + 3 days" means: A finishes, wait 3 days, then B can start. Classic example: concrete needs cure time before you strip forms.
A lead (negative lag, like "FS − 2") means the successor starts before the predecessor finishes. Schedule checkers hate leads because they hide overlap that should be modeled with an SS relationship instead. Rule of thumb: zero leads, and use lags sparingly with a reason you can say out loud (like cure time). Never use a lag just to push a date — that's called "hiding logic."
Open ends, constraints, and other logic vocabulary
- Open end: an activity missing a predecessor or a successor. Except for the first and last activities, everything should have both. Open-ended activities can "float" to weird dates and break the critical path calculation.
- Constraint: a pinned date forced onto an activity (like "Must Finish By Dec 15"). A hard constraint overrides logic and can create fake dates; a soft constraint (like "Start No Earlier Than") bends with logic. Use constraints only for real contract dates, and as few as possible — the schedule should be driven by logic, not pins.
- Redundant logic: a tie that's already implied by other ties (A→B→C plus a direct A→C). Harmless to the math, but clutters the schedule.
- Out-of-sequence progress: when the field does work in a different order than your logic said. The software has to decide how to handle it (see "Retained Logic" in the P6 tab). It's a sign your logic needs a conversation with the superintendent.
- Driving relationship: among all of an activity's predecessors, the one that actually controls when it can start. The chain of driving relationships from start to finish is the longest path.
🧮 Relationship date calculator
Pick a relationship type and see when the successor can start. Uses simple "project day" numbers (Day 1 = first workday).
Formulas & Live Calculators
Formula flashcards
CPM & float Duration & production Earned value Schedule health
Day-number convention: Day 1 is the first workday and durations are in workdays. P6 does the same math internally with calendars and dates.
🧮 1. Duration from quantity take-off
The core duration skill: count the work, divide by how fast a crew installs it — and be ready to defend the answer to a superintendent who knows the real rate.
🧮 2. Three-point (PERT) duration estimate
PERT = Program Evaluation and Review Technique. When nobody's sure how long something takes, get three guesses and weight the middle one.
🧮 3. Float (slack) calculator
Enter the four CPM dates for one activity (as day numbers) and get its float. Float = wiggle room.
🧮 4. Remaining duration from progress
The pro move at update time: don't ask "what percent are you?" — ask "how much is LEFT and how fast are you going?"
🧮 5. Workdays ↔ calendar days
Durations are in workdays, but people think in calendar time. A "20-day" activity on a 5-day week takes about 4 real weeks.
🧮 6. Earned Value quick check (EVM)
EVM = Earned Value Management. It compares the value of work planned, work done, and money spent. When schedule and cost meet in the forecast meeting, this is that conversation.
📝 EV briefing generator
Monday morning in one click: five numbers in, the weekly-report paragraph out. Updates live as you type.
CPM Practice Network (Fully Interactive)
Try it: a 10-activity building project
Today's network: the 10-activity building project
Change any duration below and hit Run CPM. The tool runs a real forward and backward pass — exactly what P6 does when you press F9 — then lights up the network node by node. Critical activities turn red and the critical path pulses. Try making "Underground Utilities" 15 days instead of 8 and watch the critical path move.
The red chain is today's critical path — the activities that set the finish date. Walk it before lunch.
Show the numbers as a table
Float cheat sheet
- TF = 0 → critical. A day lost here is a day off the finish. No cushion.
- TF negative → already late. The plan misses a required date. Start the recovery conversation today.
- TF 1–5 → near-critical. One bad delivery from red. Walk these too.
- TF > 5 → cushion. Real slack — if the logic is real. Huge float usually means a missing tie, not freedom.
Daily walk checklist — today's critical path
Check each red activity as you physically walk it. Resets each day.
How the passes work (the part interviewers ask about)
- Forward pass — start at the beginning. Each activity's Early Start (ES) = the day after its latest-finishing predecessor. Early Finish (EF) = ES + duration − 1. When an activity has several predecessors, it must wait for all of them — so it takes the latest EF.
- Backward pass — start at the end. Each activity's Late Finish (LF) = the day before its earliest-starting successor. Late Start (LS) = LF − duration + 1. With several successors, take the earliest LS.
- Total Float (TF) = LS − ES. Zero float = critical. Negative float = you're already late (the schedule can't hit a required date).
Primavera P6: The Last 10 Years
Version timeline, 2015 → today
P6 concepts you must be able to talk about
| Concept | What it is |
|---|---|
| EPS — Enterprise Project Structure | The company-wide folder tree that organizes all projects (by district, region, sector). Your project lives in one node of it. |
| WBS — Work Breakdown Structure | The outline INSIDE a project: Project → Phase → Area → Work package. Every activity hangs off a WBS node. |
| OBS — Organizational Breakdown Structure | Who's responsible for what — maps managers to EPS/WBS nodes and controls access. |
| Activity codes & IDs | Smart labels (Area, Floor, Trade, Responsibility) that let you group, sort, and filter thousands of activities. Companies have standards — learn yours before inventing your own. |
| Calendars | Define workdays/holidays/weather days. An activity's dates depend on its calendar. A classic rookie bug: mixed calendars making float look weird. |
| F9 / Scheduling | Pressing F9 runs the CPM calculation (the forward/backward pass you practiced in the CPM tab). |
| Data date | The "as of" line. Everything left of it is history (actuals); everything right is forecast. Updates move the data date forward — never edit history behind it. |
| Baseline | A frozen snapshot of the approved plan. Current schedule vs. baseline = your variance report. |
| Retained Logic vs. Progress Override | Scheduling options for out-of-sequence work. Retained Logic (the safe default) still respects remaining logic ties; Progress Override ignores them and can produce fantasy dates. Know which one your schedule uses. |
| Total Float / Longest Path | Two ways P6 defines "critical": float ≤ 0, or membership on the longest path. Multi-calendar schedules make longest path the more honest choice. |
| XER / XML files | How P6 schedules travel between companies. XER is the classic Primavera exchange format; XML is the newer one. You'll send and receive these constantly with subs and owners. |
| Global vs. Project data | Calendars, codes, and layouts can be global (shared company-wide) or project-only. Editing a GLOBAL calendar changes everyone's schedules — the classic new-hire landmine. Ask before touching global data. |
| Layouts & Filters | Saved views (columns, grouping, bars) and saved queries. Good schedulers build a library: "4-week look-ahead," "Critical path only," "Concrete activities by area." |
| Claim Digger / Schedule Comparison | P6's built-in tool that compares two schedule versions and lists every change — durations, logic, constraints. Run it on every schedule a sub sends you. |
Checking a Schedule (Yours or a Sub's)
The DCMA 14-point health check
| # | Check | Target | Why it matters (plain words) |
|---|---|---|---|
| 1 | Logic — activities missing a predecessor or successor | ≤ 5% | Unconnected tasks can't push or be pushed — the CPM math is blind to them |
| 2 | Leads (negative lags) | 0 | Hidden overlaps nobody can see or verify |
| 3 | Lags | ≤ 5% of relationships | Invisible wait time; should be real activities or have clear reasons |
| 4 | Relationship types — FS share | ≥ 90% FS | FS is transparent; heavy SS/FF often hides shaky sequencing |
| 5 | Hard constraints | ≤ 5% | Pinned dates override logic and fake the critical path |
| 6 | High float — activities with TF > 44 workdays | ≤ 5% | Huge float usually means missing logic, not real freedom |
| 7 | Negative float | 0 | The schedule already can't meet a required date — needs a recovery plan |
| 8 | High duration — activities > 44 workdays | ≤ 5% | Monster activities are impossible to status honestly; break them up |
| 9 | Invalid dates — forecast dates in the past, or actual dates in the future | 0 | Time travel. Always an update error. |
| 10 | Resources — activities with no cost/resource assigned | informational | Only applies on resource/cost-loaded schedules |
| 11 | Missed activities — finished later than baseline | ≤ 5% | Measures whether the plan is actually being executed |
| 12 | Critical path test | pass | Add a big delay to a critical task — the finish date should move with it. If not, logic is broken. |
| 13 | CPLI — Critical Path Length Index | ≥ 0.95 | How much cushion the critical path has to the required finish |
| 14 | BEI — Baseline Execution Index | ≥ 0.95 | Tasks completed vs. tasks that should be complete by now |
🧮 DCMA health check calculator — with scorecard
Type in the counts from your schedule (P6 filters or an export to Excel get you these numbers) and get an instant gauge dashboard: green = passing, yellow = passing but close to the limit, red = failing (misses the DCMA target).
Activity counts
Relationship counts
Execution & critical path
Outside software & processes for checking schedules
| Tool / process | What it does | When you'd use it |
|---|---|---|
| Deltek Acumen Fuse | The industry-standard schedule diagnostics tool. Imports your XER and scores it against DCMA 14-point and hundreds of other metrics; produces a "Fuse score." | Big GCs run every baseline and monthly update through it. If your company has it, learn it early. |
| Schedule Analyzer Pro (Ron Winter) | Deep P6 file forensics — finds things P6 itself won't show you. | Claims work and detailed reviews |
| ScheduleReader / ScheduleCleaner | Views and scrubs XER files without needing a P6 license. | Sharing schedules with people who don't have P6 |
| P6 Claim Digger / Schedule Comparison | Built into P6 — diffs two schedule versions and lists every change. | Every time a sub sends a "minor update." Trust, but verify. |
| Excel export checks | Export activities + relationships to Excel; use filters/pivots to count open ends, constraints, lags, high float. | The free, always-available option — and how you learn what the fancy tools automate |
| Manual "does it smell right" walk | Print the critical path and read it out loud with the superintendent: does the sequence match how they'd actually build it? | Always. No software catches "that's not how we build." |
| TIA — Time Impact Analysis | A formal process: insert a fragnet (a mini-schedule of a delay event) into a copy of the schedule and measure how much the finish date moves. | Delay claims and change orders — you'll assist on these before you lead them |
Planning & People: Leading the Process
Interactive Planning Session (IPS) — also called a pull plan
A working meeting where the people who will DO the work build the sequence together, usually with sticky notes on a wall (or a digital board). "Pull" planning means you start from a milestone (like "Building dried-in Nov 1") and work backward, each trade saying what they need finished before they can start.
- Prep (you): pick the milestone and window (usually 6–12 weeks), invite every trade involved, print the current schedule for that area, bring sticky notes color-coded by trade.
- Set the target: put the milestone on the right end of the wall.
- Pull backward: the last trade posts what they need done before they can start; the trade before them does the same; repeat until you reach today.
- Negotiate the collisions: two trades want the same room the same week — this is where the meeting earns its keep. The super referees; you capture.
- Test durations: ask each trade "what crew size does that duration assume?" Write it down — that's your production-rate backup.
- You translate: after the meeting, turn the wall into activities and logic in P6, then send it back to the room for a "did I capture it right?" check.
Moving ownership: from "the scheduler's spreadsheet" to the super's plan
A schedule only changes behavior when the superintendent treats it as their plan. If the field sees it as your paperwork, it gets ignored the first week it's wrong. Your leadership job is a deliberate handoff of ownership — while you keep ownership of the model's honesty.
| Move | How it builds ownership |
|---|---|
| Sequence comes from them | In planning sessions the super and trades set the order of work; you model it. People defend plans they authored. |
| Nothing publishes without their eyes | Every schedule the project sees carries the super's fingerprints. If they'd be surprised by anything in it, it isn't ready. |
| They present, you support | In the owner's meeting the super walks the schedule; you sit beside them with the backup. The room learns whose plan it is. |
| Offer levers, not verdicts | Bring recovery options with the trade-offs priced out ("re-sequence, add a crew, or move the date") and let the super choose. Choosing is owning. |
| Fix the model to match the field — visibly | When crews build differently than your logic assumed, say so and change the schedule. Nothing earns trust faster than the model bending to reality instead of arguing with it. |
| Hand them the critical path in their words | A one-page, plain-English critical path the super can recite without you in the room. When they quote it in the trailer, the transfer is working. |
🗓 3-Week Lookahead generator
The field's most-read schedule product. Enter up to 15 activities, generate the visual, print it (🖨 Print → this tab) or copy the text table into the coordination email. Saved on this device as you type.
The rhythm of a project (typical cadence)
| Cadence | What happens | Your part |
|---|---|---|
| Daily | Foremen's huddle; site walk | Walk the site; note actual starts/finishes; eyeball reality vs. plan |
| Weekly | Subcontractor coordination meeting; 3-week look-ahead review | Publish the look-ahead (a filtered slice of the master schedule); collect commitments and roadblocks |
| Monthly | Formal schedule update; owner's report; forecast meeting with cost | Move the data date, enter progress, run F9, analyze variances vs. baseline, write the schedule narrative, sanity-check against the cost forecast |
| Per phase | Interactive planning session for the next phase | Facilitate, capture, translate to P6 |
The 3-week look-ahead (some companies use 4 or 6) is your most-read product: a simple list of what's happening this week and the next two, by area and trade. Field people may never open P6 — but they read the look-ahead every week. Make it clean, accurate, and boring in the best way.
Getting good status from foremen and subs
| Weak question | Better question | Why |
|---|---|---|
| "What percent complete are you?" | "How much is left, and how many days to finish it with your current crew?" | Remaining duration is checkable math; percent is a feeling |
| "Are you on schedule?" | "When will you finish this area, and what could stop you?" | "On schedule" invites yes; a date invites truth |
| "Why are you behind?" | "What do you need to go faster — access, material, answers?" | Blame closes mouths; help opens them |
| (asking only the PM) | Walk to the work and count it yourself first | You can see whether the slab is poured. Verify, then discuss. |
People calibrate over time: some foremen are optimists ("two days" means five), some sandbag. Track promises vs. actuals in your notebook — after a month you'll know everyone's conversion rate. Never use it to embarrass anyone; use it to forecast better.
The paper trail that drives schedules
- RFI (Request For Information) — a formal question to the designer ("the drawings conflict — which is right?"). Open RFIs block work; track the ones sitting on critical activities.
- Submittal — documents/samples a sub sends for approval before building (shop drawings, product data). Long approval + fabrication lead times belong IN the schedule as procurement activities.
- Change Order (CO) — an approved change to scope, price, or time. If it adds work, it adds activities — and maybe a Time Impact Analysis.
- Long-lead items — equipment that takes months to arrive (switchgear, elevators, air handlers). Rookie schedulers model the install and forget the 6-month wait before it. Model: submit → approve → fabricate → deliver → install.
- NTP (Notice To Proceed), Substantial Completion, LDs (Liquidated Damages — daily money owed for finishing late): the contract dates your whole schedule serves. Read the contract's schedule section on day one.
Writing the monthly schedule narrative
Every formal update comes with a short written story. Standard skeleton: 1) current data date and forecast completion vs. baseline; 2) progress this period (what started/finished); 3) critical path description in plain sentences; 4) changes since last update and why; 5) risks and delays, with who owns each; 6) look-ahead of major work next period. Two pages, no drama, no surprises that weren't already communicated in person.
Theme Park Projects: Scheduling Where the Show Comes First
What-if scenario matrix — capture it on the spot
The owner just asked "what if…?" — write it down before it evaporates. Tap a cell to type; saved on this device.
| Scenario | Change | Milestone impact | Float impact | Decision by |
|---|---|---|---|---|
Back at the desk: run each row in a schedule COPY, never the live file — full workflow in Office Mode.
Operating-park constraints — quick reference
- Noise windows: loud work only in park-closed hours or scheduled around show times. Confirm tonight's window before promising it.
- Access: deliveries route backstage, often night-only, through shared gates. A late truck is a missed window, not a late truck.
- Screening: guests must not see the work. Scrims and themed walls go up before work starts — and removal is part of the reveal plan.
- Utility outages: tie-ins only during park-closure windows, permitted and rehearsed. Miss it and you wait for the next one.
- Reveal order: marquee elements install last, stay covered. Never uncover early for convenience.
Field questions
The 20-question quick-answer sheet, filtered to what gets asked on-site:
What's different from a normal building schedule
🎢 Ride & Show (R&S) systems drive everything
Ride systems are custom-engineered machines with 12–36 month procurement lead times — often ordered before the building is even designed. The chain: engineer → fabricate → FAT (Factory Acceptance Test, at the vendor's shop) → ship → install → SAT (Site Acceptance Test) → commissioning. Miss a FAT window and the whole back end compresses.
🤖 Show equipment has its own timeline
Animatronic figures, audio/visual gear, projection mapping, and special/practical effects (SFX/PFX) are procured and programmed separately from both the building and the ride. Show installation can't start until the building is dried-in and (usually) dust-controlled — and show programming needs the ride running. Sequence: facility → ride → show install → integration.
🏰 Facade & show set interfaces
Themed facades and scenic work sit on top of structural work but come from different trades with different tolerances — a rockwork carver and a steel erector do not think in the same eighth-inches. Every structure-to-theming handoff is an interface milestone worth modeling explicitly, or the scenic crew shows up to a wall that isn't ready for them.
🎟️ Opening is a sequence, not a date
Attractions open in stages: commissioning complete → technical rehearsals (running the attraction as if open) → cast member previews → soft opening (unannounced guest operation) → media day → hard/grand opening. Each stage is a real schedule phase with entry criteria — model the logic between them, not just the final ribbon-cutting.
📸 Media events pin hard dates
Press events and announced opening dates create hard-date constraints on specific areas — the parade route must be clear for the media day even if the land isn't finished. These are the rare cases where hard constraints in the schedule are legitimate: they're real contractual/marketing commitments.
🌳 Themed landscape is long-lead too
Mature trees, specimen plants, and sod have procurement lead times and seasonal planting windows just like switchgear. A 30-foot oak gets contract-grown years ahead and can only be transplanted in certain months. Model horticulture as procurement + seasonal constraint, not as "landscaping, 10 days" at the end.
Building next to an operating park
- Noise windows: loud work (pile driving, demolition, crane picks near show areas) is restricted to park-closed hours or scheduled around show times. Your calendars must model night-work and closure-window shifts — this is the theme park version of the weather calendar.
- Site access restrictions: deliveries route backstage, often only at night, through gates shared with park operations. Haul routes and crane locations need operations sign-off; a lane closure that would be routine downtown is a negotiated event here.
- Visual screening: construction must stay invisible to guests — scrims, themed construction walls, and height limits on equipment during park hours. Screening goes up before work starts and its removal is part of the reveal plan.
- Utility outages: tying into park power, water, or fire systems means shutting down systems that serve operating areas — allowed only during park-closure windows, sometimes only a few nights a year. Every tie-in is a scheduled, permitted, rehearsed event with a rollback plan. Miss the window and you wait for the next one.
- Reveal sequencing & secrecy: what guests can see gets built last or stays covered — marquee elements, character figures, and story moments are installed late to protect the surprise (and the marketing embargo). The reveal order is a real scheduling constraint that can force otherwise-illogical sequencing.
Working with a large GC schedule (the sole-source reality)
Major theme park work is often awarded to a sole-source / negotiated GC — a preferred contractor with a long park relationship, not the low bidder. That changes what the schedule IS: the GC is held to milestone compliance, not activity-level contract enforcement — so the schedule is enforced at the named milestones, and the activity-level detail works as a coordination tool for the owner. (The schedule itself is still a required contract submittal, and the evidence if a delay dispute ever comes.) And it's huge — a single attraction schedule can run 3,000–5,000+ activities that you didn't build and can't rebuild. Your job shifts from authoring a clean CPM to reading someone else's giant one.
| Skill | How it actually works |
|---|---|
| Know what each side tracks | The owner/CM cares about the 10–20 contract milestones and the interfaces between contractors (facility turnover to ride vendor, show install start, commissioning windows). The GC tracks thousands of internal activities to run their subs. Don't referee their means-and-methods detail — police the milestones and the handoffs. |
| Find the driving milestones in 5,000 activities | Start from the contract milestone list, not the schedule. For each milestone, trace the driving predecessor chain backward (P6: multiple float path analysis ending at that milestone, or walk driving predecessors in Trace Logic, or sort by total float and follow the lowest-float chain into it — the longest path filter only shows the chain to PROJECT finish). Build yourself a one-page "milestone map" — each milestone, its driving path in 3–5 plain-English steps, and its float. That page IS your working schedule; the 5,000 lines are backup. |
| Spot fragmentation | When a schedule gets that big, predecessor logic often goes thin: hundreds of open ends, date constraints pinning whole areas, float values in the hundreds, and dates that move between updates without logic changes (statused by typing, not by the network). Run the DCMA checks from the Checking tab on any 3,000-line schedule before trusting it — and run Schedule Comparison every update to see what silently changed. |
| Ask for the right level | Schedules come in levels: L1 (one-page executive summary) → L2 (major phases/milestones) → L3 (systems & areas) → L4/L5 (full working detail). When the L5 is 3,000 lines, ask for an L2/L3 summary rolled up from the same file, same data date — a WBS or activity-code rollup, not a hand-drawn PowerPoint that can quietly disagree with the real network. |
| Read between the status lines | A sole-source GC has less incentive to flag slippage early — the relationship survives a slip, so bad news travels slowly. Watch the trends, not the claims: float eroding on milestone paths update after update, the near-critical list growing, "resequenced" appearing in narratives, and milestone forecast dates holding suspiciously still while everything feeding them slides. Ask for a driving-path narrative per milestone, every update. |
| Variance that matters | With damages (if any) tied only to milestones, activity-level slips are conversation, not enforcement. Track milestone forecast trend — each milestone's forecast date across the last six updates — plus float consumption on each driving path. Escalate on trend ("Show Install Start has moved right three updates in a row"), don't wait for the milestone itself to go red. |
What-if scenario management (the owner's daily drill)
On an attraction project the owner runs what-ifs daily, not monthly: "What if structural completion slips 3 weeks — what's the new opening?" "What if we fast-track show install with a second crew?" "What if we cut this theming scope — how much float comes back?" Answering fast, without wrecking the schedule of record, is a core skill.
- Never in the live file. Every what-if runs in a copy — in P6, copy the project into a what-if node of the EPS (or use a reflection, P6's built-in copy that can merge changes back if the scenario is adopted). The schedule of record keeps its baseline untouched.
- Name scenarios like you mean it. A convention like PROJ-2027-0315-WI-showcrew2 (project, date, "WI", one-word tag) plus a scenario log — who asked, the question, the data date it was run against. Archive or delete copies once the question is answered; stale copies are how wrong versions escape.
- Keep a scenario matrix. One running table answers "what have we studied and what did it say":
Scenario Change modeled Opening impact Float impact Decision needed by WI-struct+15d Structural completion +15 workdays Opening +9 days Show install path float +6 → −9 Mar 21 owner's meeting WI-showcrew2 2nd show crew, install 120→85d Opening unchanged, buys 35d buffer Commissioning path float 0 → +35 Before award of show contract - Present the delta, not the schedule. Owners want one page: the changed milestones only, as was → now → Δ, with the decision and its deadline on top. Nobody in that room wants a 40-page schedule report for a what-if.
- When a what-if becomes the plan, rebaseline formally. Adopted scenario → formal approval → save the old baseline (never overwrite it), assign the new one in P6, and record in the narrative what changed and why. The history of baselines is your protection when anyone later asks "when did the plan change?"
- Guard against scenario creep. When six what-ifs are floating around, someone WILL status the wrong file. Antidotes: one scheduler owns all copies, one named schedule of record, scenarios retired the day their decision lands, and the scenario matrix as the single register of what exists.
One scheduler, three Orlando owners
The same GCs and schedulers rotate across Disney, Universal, and SeaWorld work — you might be on one owner's project this year and another's next. The craft on this page transfers; the owner context doesn't. Broad patterns worth knowing (every project differs — confirm locally, every time):
| Owner context | What tends to be different for the schedule |
|---|---|
| Design-build & fast-track heavy (Universal has this reputation) | Design overlaps construction, so the schedule carries design deliverables and procurement decisions as activities, churns more between updates, and commits to long-lead orders earlier off incomplete design. Expect more frequent resequencing and keep the what-if muscle warm. |
| Owner-controlled creative & gated reviews (the Disney-style model) | Creative/owner review cycles are real schedule logic — model approval gates, mock-up reviews, and show sign-offs as activities with owners and durations, because a slow review slides the build just like a slow crew. |
| Smaller footprint, animal & show constraints (SeaWorld-type projects) | Smaller sites but hard biological gates: life-support systems commission like ride systems, water chemistry needs stabilization time nobody can compress, and animal acclimation windows and welfare-driven noise limits gate sequencing the way guest-facing noise windows do elsewhere. |
| All three | Live-park adjacency is universal — but noise windows, backstage access routes, and closure-window policies differ by owner, by park, even by land. Never copy calendars and access assumptions from the last project; re-confirm them with operations at THIS park before baselining. |
🏗 GC schedule comparison — who's driving?
Theme park programs run several primes in parallel — civil/structural, ride systems, show/scenic, themed environments. Track each contractor's key milestone and see who currently drives the opening. Saved on this device as you type.
Theme park vocabulary (also searchable in the Terms tab)
| Term | What it means for the schedule |
|---|---|
| FAT / SAT — Factory / Site Acceptance Test | The two big proof gates for ride and show systems: FAT at the vendor's factory before shipping, SAT after installation on site. Both are milestone-worthy; a failed FAT is a schedule event. |
| Commissioning | Making the ride/show systems work as an integrated whole — cycles, fault testing, evacuation drills. Runs weeks to months and needs the facility essentially complete around it. |
| Technical rehearsals | Operating the attraction full-cycle as if open (no guests, then cast previews) to shake out reliability and operations. The entry gate: commissioning complete. |
| Soft opening | Unannounced, unadvertised guest operation — the attraction may open, close, or change without notice. Real-world load testing before the promised date. |
| Media day / press event | A hard date announced to the world. Everything the cameras will see must be finished; everything else must be invisible. |
| Hard (grand) opening | The announced, marketed opening. The one date that does not move — everything upstream flexes instead. |
| Maximum achievable opening ("MAPO" on some projects) | The earliest opening date the remaining work can actually support — reality's answer to the announced date. When it slips past the announced opening, leadership has a decision to make, and your schedule is the evidence. Heads-up: "MAPO" is not a settled industry acronym — its meaning varies by company (at Disney it historically names the ride-safety organization) — so confirm the local meaning before using it in a meeting. |
| Show readiness review | The creative team's formal review that the show (sets, figures, lighting, audio, effects) meets design intent — a sign-off gate before rehearsals/opening, parallel to the construction punch list but owned by creative. Package names vary by studio, so learn your project's term for it. |
| VTS — Vertical Transportation Systems | Elevators, escalators, and lifts. On attraction projects they're often show-critical (lift hills, vehicle elevators, evacuation lifts) and safety-certified — schedule them with ride-system rigor, not as ordinary building elevators. Ride vehicles and conveyors belong to the ride-system scope. |
| SFX / PFX — Special / Practical Effects | Fire, fog, water, scent, pyrotechnic, and mechanical effects. Separate vendors, separate permits (fire marshal), integration-tested during commissioning. |
| Dark ride / thrill ride / walk-through | Construction implications differ: a dark ride is a show building — huge clear-span box, climate control, show lighting, everything interfaces with theming. A thrill ride (coaster) is mostly structure and ride system — foundations and steel drive it. A walk-through is nearly all theming and finishes with heavy guest-flow/egress requirements. |
| Ride safety compliance | ASTM F24 standards (and state/OSHA requirements) drive mandatory testing, inspection, and certification milestones before guests board. These are regulatory gates — model them explicitly; they cannot be compressed by adding crews. |
| Cast member previews | Employee ride-throughs before soft opening — part thank-you, part load test with a forgiving audience. |
🧮 Theme Park Opening Sequence calculator
Enter your announced opening date and typical stage durations. The calculator works backward through the opening sequence and tells you when each upstream milestone must land — including when the building has to be structurally done. Durations are calendar days (theme park commissioning and rehearsals typically run 7 days a week).
Defaults are typical industry planning ranges for a major attraction — a small flat ride compresses everything; an E-ticket dark ride stretches it. Replace with your project's real numbers, and remember the stages overlap in practice (show install starts area-by-area, not building-wide).
Self-Check Quiz
Twelve questions covering the whole guide. Answer, then hit Grade Me. Aim for 10+ — and for each one, ask yourself whether you could explain the answer to a foreman in plain English. That's the real test.