Anchor an update, confirm workable time, choose bounded recovery levers, and verify the result in P6.
Project: Select or create a project
Data DateNot read yet
Evidence detailsChecking
Project IDNot assignedData Date sourceLoading the accepted schedule date.Checking effective role and scopeBounded evidence only · original schedule source remains protected
Critical Path What-If Lab content
Overview
No scenario run yet: prove the zero-change replay, then read what recovery buys.
No picture yet
Bounded scenario arithmetic against the uploaded schedule; not an approved recovery.Evidence boundary: observed inputs support bounded derived views; unsupported conclusions remain withheld.
Every narrowing step keeps its workability receipt and authority label. A browser result is never an approved recovery.
Commitment P6 only
Compare releasesProve identity and evidence boundaries before reviewing recovery scenarios.
metadata only
Loading authorized releases…
The bounded evidence report appears after two authorized releases are selected.
A calendar says when work may occur—not that work can occur. This bounded lab clones scenario calendars, freezes actual work, and withholds results unless the zero-change replay matches the uploaded P6 schedule.
1. Target and replaySelect the target milestone and prove the local engine reproduces P6 before changing anything.
required gate
2. Work calendarHow much the crews work now, and what this worksite and its neighbors allow.
observed + declared
Two different questions. The work pattern is read from the uploaded schedule. Sound, traffic, and timing limits are not in a schedule file—they come from an ordinance, a permit, or an agreement, and you declare them here. The difference between the two is the only headroom a recovery scenario may reach for.
Choose a saved review to read the calendars this schedule actually uses.
Site and neighborhood envelope
Nothing typed here is written to the schedule or saved onto the review. An undeclared limit stays undeclared: it never becomes zero and it never becomes unlimited.
Declare the envelope to measure how many hours a week are still legally available.
Shared resources — what cannot happen at the same time as what
Schedule logic says what follows what. It does not say that two crews cannot stand in the same room, that one crane cannot make two lifts at once, or that the inspector who has to witness both tests is one person. Declare them and the scenario can name which two activities collide instead of only that leveling is needed.
Kinds: EQUIPMENT, SPACE, CREW, SUPPORT, ACCESS, STAGING. The selector matches activity codes, a WBS prefix, a calendar name, or any word in an activity name. A resource nobody declares is one nobody has told us about, never a cleared one.
3. Kinetic limitsThe hours on this corridor that no crew, weekend, or shift can buy — and the ones only pretending to be.
declared evidence
A cure does not care how many people are watching it. Concrete strength gain, coating dry-through, a mass-pour cooldown, a contractual hold: each is governed by a rate or a clause, so every lever on this page buys exactly zero hours against it. Declare those activities here and the recovery arithmetic stops spending time that does not exist. The check runs the other way too: queue, lab, inspection, or handoff hours sitting inside a duration called “cure” are a false floor, and those hours are recoverable.
No kinetic floor declared
Run a scenario. With nothing declared, the recovery arithmetic assumes every hour on the corridor is for sale.
4. Approved materialsHold the schedule to the day each approved product can actually be on site.
declared evidence
A start date is a plan; a lead time is a consequence. An XER has no manufacturer, no model, and no lead time, so it cannot tell you that the work starting Monday needs a product that was released three weeks ago against an 84-day fabrication. Paste the submittal register and the schedule is held to the dates procurement can support. An item with no released submittal has no computable date at all — it carries no floor here, so the movement you get back is the least the target moves, never the most.
No approved-materials evidence
Without a register, every start date on this schedule rests on nothing but the plan.
5. Workability receiptSeparate display conversion from actual availability. Each factor is explicit; zero means unavailable.
Adjust a factor to see which operational gate narrows available calendar hours. This is a receipt, not a probability.
6. InterventionScenario calendars are cloned and assigned only to selected remaining work.
Choose a review and target. Calendar-only dates are never presented as committed recovery.
Scenario results
No scenario has been run.
Recovery optionsWhich added hours actually reach the milestone, and whether this worksite is allowed to work them.
scenario arithmetic
Run a scenario to score each option against the target and the declared site envelope.
Delay tolerance curveHow far a precursor can slip before the target moves, and what each further day costs after that.
bounded simulation
“Steel is critical” is not a decision. A lead time is. This pushes the same delay through the network at growing sizes, so the reading is a tolerance in days rather than a label on an activity.
No delay curve run
A saved review, a target activity, and a delayed scope are required. The zero-change replay gates the curve the same way it gates a scenario.
Buildable frontierHow connected the remaining work still is, and which section is holding it together.
observed logic
An activity count cannot see this. Twenty sections that all drain through one inspection and twenty sections that reach the finish independently have the same open-activity count. This groups the remaining work into sections, weights the logic that crosses between them, and reads the graph that comes out.
Choose a saved review, then read the frontier.
Interpret this resultUse a bounded follow-up that keeps the scenario authority and P6 verification boundary visible.
talking points
7. P6 round-trip verificationAfter the approved change packet is scheduled in P6, upload that XER as a new review and compare the target date.
Observed → derived → withheld remains explicit. These talking points stay tied to the selected evidence; they are not an unrestricted database question box.
bounded scenario preview not causation commitment resource leveling or p6 verification
Observed selected source valuesDerived visible inputs and formulaWithheld unsupported or unavailable
Current context
Unavailable context remains explicitly not supplied.
This talking point preserves the page’s evidence and authority boundary.
