Schedule Overview
Inspect one accepted schedule before making comparison claims.
Not assignedEvidence detailsChecking
Schedule Overview content
Inventory, hierarchy, dates, duration, and total float come from the selected immutable review. No trend or finish forecast is inferred.
Review, project, snapshot, Data Date, received time, and parser evidence stay together.
Choose a schedule.
The file carries no trade column. Pick a grouping it already contains — a code prefix, a WBS node, a calendar, or an assigned resource — and this reports what that caught, what it left out, and where your work hands off.
Your window, your float, the tightest run inside your package, and the project milestones downstream of you. Your tightest run is reported separately from the project critical path — they are usually different chains.
Your work and other trades’ work, traced back from your last finish through the declared logic, and where it meets the project’s Longest Path.
How much of its time-phased plan your package has earned, in weeks, read only when the plan, the cost weighting and the progress are in the file.
An XER carries no cure times, no lead times and no hoist counts, so nothing in the file can contradict it until you say them. Declare what you hold and this reports the durations, starts and site claims the schedule asks for that your evidence cannot support. Declaring nothing tests nothing — it is not a clean bill.
Every answer on this page about your package, on one page, bound to the name, hash and data date of the file it came from, with what each answer does not claim. Name an earlier release to read where your float went.
What is due in the window, which work front it sits on, and what the rate this project has actually been going at says about it. Readiness is separate from lateness: an activity can be on time and un-startable.
The job in eight coarse phases, from approvals and procurement to handover. Each activity is placed once, by the work its name or its WBS names; what names no work stays unassigned. Progress is by duration, not earned value.
How finished work of each trade ran against plan on other real P6 schedules, and where the open work here would finish if it ran the same way; then the months in which work done in the open ran long. Each activity is stretched alone; logic and float are not re-run, and nothing is written back to the schedule.
Counts and bounded date/float distributions describe structure, not quality or causation.
Schedule shape loads after a release is selected.
Selected metadata rows only; raw schedule bodies and server paths are never returned.
No schedule selected.
Each trade's open work against how fast it has finished work over the last four weeks (Little's Law), set beside the trade's own durations. More open than the pace supports reads as stacking.
| Trade | In progress | Finished, last 4 weeks | Implied days each | Its own median days | Reads |
|---|
Review status and evidence steps
Steps of the decision on this page.
