Roadmap
Built against a gap analysis, not a wish list.
The plan below comes from a full audit of the codebase against P6 and MS Project — what those tools do that LumaPlan did not, ranked by whether it blocks real work. Each phase ships or it does not; the status here is the same status the repository carries.
Status
Where each phase actually is.
The statusing loop
Actual start and finish, remaining duration, percent-complete types, and a data date that means something — the loop that turns a plan into a progressed schedule.
Import fidelity
Calendars with exceptions, task types, constraint handling and provenance carried through the importer instead of parked in fields nothing reads.
Import accuracy
Every file LumaPlan reads is checked field by field against what the tool that wrote it actually produced, on real project files rather than samples. Ongoing by design.
Cost engine and time-phased data
Cost accounts, expenses, resource rates over time, per-period actuals, and earned value computed from them.
Working-time engine and rich calendars
Minute-level scheduling with per-weekday multi-shift calendars. Resource-calendar union is the piece still open.
MS Project round-trip
Baselines, priorities, and a file that reopens in MS Project with everything intact — most of it shipped; the remainder is resource and assignment fields.
Matching dates, at scale
Closing the last measured differences against P6 and MS Project on real programmes, and holding the performance budget while doing it.
Schedule log and diagnostics
A readable account of why the engine put each activity where it did — which constraint bound it, which predecessor drove it. The answer to “why is this date what it is”.
Wire the disconnected
An explicit sweep for capabilities that exist in the engine but were never connected to the interface. It is the recurring failure mode the audit found, so it gets its own phase.
How it is run
A feature that is not wired end to end is not shipped.
The audit that produced this roadmap found the same failure repeatedly: capability built into the engine and never connected to anything. Monte Carlo with no endpoint. Resource curves stored and never read. Leveling priority hardcoded. Columns marked editable that rendered read-only.
So the rule is: engine, API, interface and documentation, or it does not count. Where a link is genuinely missing, it gets written down as missing rather than described as done.
That is also why this page exists. A roadmap that only lists wins is a brochure.
Not open for signups yet.
LumaPlan is being built against real construction programmes, and it will be available when it is good enough to hand someone a contract schedule in.