Build the schedule. Then break it.
Schedule Studio is a working CPM engine in your browser: logic, calendars, progress, baselines and a live Gantt. Every other instrument runs on the same network, so a slip in one place shows up everywhere. Load a sample or import your own P6 file.
- Instruments
- 7
- Shared CPM network
- 1
- Sample schedules
- 3
- Bytes uploaded
- 0
A CPM engine, not a picture of one.
Forward and backward pass, total and free float, FS, SS, FF and SF ties with lags, four calendars, constraints, actuals against a data date and baseline variance. Edit any cell and the network recalculates.
The file is read by this page only. It is never uploaded.
How to type logic, constraints and progress
- Predecessors use P6 style text:
A1020is finish-to-start,A1020FS+2adds a two-day lag,A1030SS,A1040FF-3for a lead,A1050SF. Separate them with commas. - Durations and lags are working days on the activity calendar. Lags count on the successor calendar.
- Progress: enter an actual start to start work, an actual finish to complete it, then set remaining duration. Move the data date and use Status to data date to apply the plan as progress.
- Retained logic holds out-of-sequence work behind its open predecessors. Progress override lets it run from the data date.
- Hard constraints (start or finish on or before, mandatory) can create negative float. Must finish by drives the late dates of open ends.
- Undo with Ctrl+Z. The schedule is saved in this browser only.
On live projects we run the same discipline in Primavera P6 every update: a fixed data date, retained logic, a frozen baseline and a written note on every change to the longest path.
Planning & SchedulingFourteen checks. No opinions.
The DCMA 14-point assessment runs on the Studio schedule by itself: logic, leads, lags, constraints, float, durations, dates, the critical path test, CPLI and BEI. Click a failed check to see the activities behind it.
Loading the shared schedule
- 01
Every activity has at least one predecessor and one successor. No open ends.
- 02
Hard constraints are rare, and each one is documented.
- 03
There is no negative float, or every case is explained with a recovery plan.
- 04
Lags are rare and documented, and there are no leads (negative lags).
- 05
Nine in ten relationships are finish-to-start.
- 06
Construction activities are short enough to measure, roughly 20 working days or less.
- 07
Few activities carry very high total float.
- 08
Updates use a fixed data date, with actuals before it and nothing actual after it.
- 09
Cost or resources are loaded, so progress and spend can be compared.
- 10
You can name the critical path from today to completion, and it is continuous.
An independent review runs these checks and the ones software cannot, then tells you in writing what to fix before the baseline is approved.
Independent Schedule ReviewSlip one task. Follow the damage.
Delay an activity or insert a fragnet, tag who caused it, and watch float absorb it until it reaches the finish. Each event is its own window, so time, liquidated damages and revenue at risk add up the way a claim does.
Loading the shared schedule
Impacted against unimpacted
For a real claim we run time impact and windows analysis on the native files, the contemporaneous updates and the as-built record.
Delay Analysis & ClaimsIs your date a plan or a hope?
Thousands of runs of the real network, each with fresh durations and risk events and a full CPM pass. You get P50, P80 and P90 dates, the activities that drive the spread, and the ones hiding behind float.
Loading the shared schedule
Risk register
Ranges per activity
Blank cells use the percentages above. Durations in working days.
What drives the spread
Correlation of each activity with the finish dateCriticality index
Share of runs where the activity sat on the critical pathOn real schedules we run quantitative risk analysis on the P6 file itself and give boards a P80 date and a contingency they can defend.
Schedule & Cost Risk AnalysisRead the pulse before the budget report.
Planned value from the baseline, earned value from progress, actual cost by month. SPI, CPI, earned schedule, three estimates at completion and the efficiency you would need to land on budget.
Loading the shared schedule
We build earned value into the schedule and cost system, so SPI, CPI and a forecast finish come out of every update without anyone retyping a spreadsheet.
Project Controls & Earned ValueWhat one late day really costs.
Revenue that has not started, interest on capital already spent, a site team still on the payroll and prices still rising. Set your numbers or pull the slip from the Studio, then see how little the liquidated damages cover.
On live projects we put this number at the top of every monthly report, so every acceleration decision is priced in real dollars.
Cost Control & ForecastingRecovery that moves the finish date.
Crash, add a shift, fast-track or resequence, each tested against the network. See which options buy days, what each day costs, and why money spent off the critical path buys nothing.
Loading the shared schedule
Recovered schedule against today
Our recovery plans test every option against the native schedule, price it, and show the owner the cheapest credible path back to the date.
Recovery PlanningEverything here runs in your browser. Files you import and numbers you type are never uploaded, and the working schedule is saved only on this device. The sample schedules are illustrative networks, not client projects.
Run this on your real schedule.
Lola Osoba, our founder, offers an independent review of your live schedule. Send the XER or MPP file and a senior project controls lead replies within one business day with what we see and what we would check first.