One workspace where you generate and diagnose in the same place, all governed by fixed rules. Talk to Nahla in plain English; the agents propose the changes, and you approve.
Access is arranged with us directly. We set up your workspace and walk through Nahla on your own programme, so you start on real data rather than a blank screen.
Describe what you need in plain English and the right agent or skill answers, drafts or simulates, then hands you a proposal. Nothing touches your schedule or your subcontractors on its own.
Two ways in. Describe the project and let Nahla draft the schedule, or upload the schedule you already manage.
Describe the project in plain English and Nahla drafts the whole programme: WBS, tasks, durations, dependencies and resources. You review and approve.
Drop a P6 or MS Project file. We parse and validate the structure before anything else runs.
Find any issue in the Diagnose view, compare against baseline or your last revision, then edit in Build with the AI proposing the changes. You approve, and it applies.
Ask in plain English and the AI proposes the edits; you approve and they apply. Nothing changes on its own.
Compare against baseline or your last revision to surface the riskiest deltas.
Ask “what's slipping?”, “show critical path”, or “which five tasks have zero float?” Every answer is grounded in the schedule and the governance rules underneath.
Sections accumulate from the conversation. Add Executive Summary, Monthly, Weekly, Monte Carlo, or any pinned Q&A. Brand it, save as draft, set a project manager, then ship.
The agents never work out a date themselves. They apply governance rules, such as the critical path method and DCMA-14, and that answer is the one you see.
When do we finish, and what is driving it?
What does this delay do to completion?
Is this schedule fit to report from?
Can the crews we have actually do this?
What changed since the last update?
Does the reported progress add up?
How far are we from the baseline?
What range of finish dates is realistic?