Anchor an update, confirm workable time, choose bounded recovery levers, and verify the result in P6.
View
Changes this browser only.
Export
No page-wide export is registered here. Use the scoped export controls within this page, where available.
Project: Select or create a project
Not assigned
Data DateNot read yetLoading the accepted schedule date.
Evidence detailsChecking
Checking effective role and scope
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.Try the material-and-crane mapping demo · synthetic practice
Does the material match—and can the work proceed?
Not the selected project's data. This fixed example uses local synthetic definitions inspired by bSDD. Review decisions, actors and times are illustrative, not your account's approvals. Nothing is saved to a customer project.
Friday installation and Saturday's remaining conditions
Six mapping evidence checks
Practice classification review—not field approval
Only A-010 has sufficient mapping and property evidence in version 1. The role selector below simulates a reviewer; it does not change your permissions.
Compare dictionary versions
Provenance and authority limits
Current report SHA-256:
All simulated actions remain in this tab. Closing or reloading the panel resets practice. No material, booking, inspection, appointment or recovery-plan publication is authorized here.
Recovery decision
No recovery read yet.
Enter the target milestone, the finish P6 reports for it and the working days it needs back, then run the zero-change gate and scenario. Each option appears here with what it recovers, the conditions it needs and whether anything approves it.
How does the target's remaining network time vary under declared duration assumptions?
Working hours only—not calendar finish dates, P6 verification or a completion guarantee. Every trial recalculates the whole eligible network, so the driving path can change.
Choose an authorized review.
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
Liquidated damages, from the contract
From the contract, not the schedule. The date alone says how far past it each option lands; the rate turns those days into money and the cap bounds it. With no working days entered above, the contracted date sets the gap. A contracted milestone saved in the project settings against this target fills the date when it is left blank. Only the exposure is read here: excusable delay, a time extension or a delay claim are not judged.
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.
Bringing in another crane or lift. Fill the last field with what it has to clear before it can lift, split by semicolons, each with its calendar days: permits and inspection stickers, delivery and erection, operator and rigger paperwork. Steps run side by side; start one with then when it has to wait for the step before it. The recovery board then reads the unit as an option, from the earliest to the latest day it can lift, on the work it is declared for.
Borrow a crew from another project
A crew from another project under the same company needs no hiring paperwork, but the project it leaves loses it for the loan. The scenario reads both: the days it gives back here, and what the other project’s latest schedule loses with the crew away. With no project named, that cost stays unknown, never zero.
The steps run side by side unless one starts with then, as for a crane. The other project’s schedule is read, never changed.
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.
Overtime productivity applies to overtime hours only; a second crew inside the hours already worked and a brought-in crane work straight time. The 2 h extension starts at 100% because, in the field, the 2 h is the incentive crews work for. The 85% for weekends, nights and long days is a product default for review. Neither models the productivity lost over many consecutive weeks of overtime.
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.
Recovery after a delayWhere the recovery left changes in kind as the delay grows, and the plans that survive one delay size.
bounded simulation
A tolerance is not yet a decision. Two days and three days can both be recoverable while the second leaves only plans that need Saturday access, an approval nobody has asked for, or a crew three weeks away. This ladders the delay named above and re-runs every recovery plan at each size.
Declared evidence that makes more recovery mechanisms evaluable
Shared crews, inspectors, access routes and their mobilization come from the site occupancy declared above; declared waiting inside durations comes from the kinetic limits. Anything not declared is unevaluated, never clear.
No recovery ladder run
Uses what is slipping and the delay sizes from the delay tolerance curve above, with the site envelope, occupancy and kinetic limits declared on this page. The zero-change replay gates it like every 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.