The schedule, read by an engine that agrees with P6.
Drop a Primavera P6 export, a P6 XML or a Microsoft Project file. In seconds you have the critical path, float, milestones, resources, risk, quality grade, forecast and a question box, all computed with the rules P6 uses, and checked against the dates in your file.
Built by planners who update P6 schedules every month. Data stays in Australia.
Ask the schedule a question. The answer comes from the engine, not a guess.
Fourteen kinds of question, answered with a sentence, a table and a link to the page that shows more. These three were answered on the sample while this page was built.
what drives the finish
The forecast finish 10-Mar-27 is set by COM-040 Performance testing; the driving chain runs back 7 activities to MEC-020 Structure installation Area 2 (In Progress, finish 11-Sep-26).
what if MEC-020 slips 10 days
If MEC-020 Structure installation Area 2 slips 10 working days, the project finish moves +14 days to 24-Mar-27; 8 activities move and 2 milestones are affected.
what starts in the next 4 weeks
1 activity starts in the next 4 weeks from the data date 03-Aug-26, the first MEC-030 on 18-Aug-26.
One engine under every page
The critical-path engine reproduces Primavera P6 activity by activity: early and late dates, total and free float, longest path, calendars with exceptions, lags on the lag calendar, the three progress modes, every constraint type, level-of-effort hammocks, expected finish, durations driven by units.
Validated on 37 real schedules with 15,685 open activities: 99.5 % same-day agreement on all five dates, 32 schedules at 100 %. Every import repeats the check against the dates in your file and shows the result.
Quality grade
B (87.8 / 100) on the sample: the DCMA 14-point checks plus the engine's own, weighted by what a reviewer cares about, with the fixes ranked.
Monte Carlo and forecast
Ranges learned from the project's own finished activities, P50 / P80 / P90, the chance of the baseline date, likely-late milestones and the drivers.
Optimisation
Crew resequencing by earliest release, a search over site order, three options to compare, and targeted mode: which activities bring the finish to a date.
Update review
What changed, what moved the finish, float erosion, BEI, CPLI, SPI, and the signs of compression: cut durations, removed logic, shortened lags, new constraints.
Three apps, one login, one set of files
Reporting
Sixteen pages read straight from your updates, from the portfolio down to a single lag. Excel export on every table, PDF from the report, a feed for Power BI.
Scheduling
A P6-style editor on the server: WBS, activities, logic, calendars, resources, codes, F9 with the P6 rules, Check Schedule, optimisation, export as XER that opens in P6 with the same dates.
Delay analysis
Forensic analysis on the chain of updates: windows, suggested delay events with their mechanism, a register with cause and party, time impact analysis, collapsed as-built, concurrency, and a method statement in every report, built on AACE 29R-03 and the SCL Protocol.
The Reporting pages
The same frame on every page: project and snapshot, data date, baseline note, labelled filters, a KPI strip, then the content.
Formulas first. AI where it reads better.
Every page works from the schedule's own numbers, with no model involved. When your space turns AI assistance on, the pages that can do better with a model show an extra option beside the formula one: the question box understands free questions, the executive report gets a written summary, and schedule building drafts from your own sample schedules and documents.
The model never changes a number. It writes words, chooses between options and maps your text to the schedule; the engine computes and checks everything it proposes. You choose the provider, Anthropic or OpenAI, and the daily budget; the keys stay on the server.
What the AI option does on each page
How it works
- 1
Drop the files
XER, P6 XML or Microsoft Project XML; one file or a whole portfolio folder. A file named baseline is the baseline; the others are ranked by data date into current and previous updates.
- 2
The engine schedules them
On our servers in Sydney: parse, calendars, spreads on the activity calendar, CPM, self-check against the file's own dates. A typical 3,000-activity schedule takes under two seconds.
- 3
Read, ask, compare, decide
Pages open from cached results. Ask a question, change a remaining duration in a what-if, run the optimiser, print the report, or point Power BI at the feed.
Your data
Files are stored encrypted in Australia, inside your own space. Only the people you invite can open it, with the role you give them: owner, planner or viewer. Every import, export and share is logged, and you can export or delete the whole space yourself at any time.
The calculation code never leaves our servers; your browser receives dates, floats and hours, nothing else. We use aggregated, de-identified statistics to keep improving the engine and the benchmarks; the agreement you sign says exactly that and nothing more.
Pricing
Prices in Australian dollars, GST invoices, cancel any month. Launch pricing will be confirmed with the first customers.
| Plan | For | Projects | People | Per month |
|---|---|---|---|---|
| Free | Trying it on one schedule | 1 project, 3 updates | 1 | $0 |
| Pro | A planner running their projects | Unlimited | 1 | from $79 |
| Team | A project controls team or a contractor | Unlimited, portfolio views, Power BI feed | 5 included | from $290 |
| Delay analysis | Claims, EOT assessments and disputes, on top of Pro or Team | Unlimited cases | as the plan | priced separately |
| AI assistance | Model calls on your own provider account | as the plan | as the plan | at cost |