Features
One application, from logic to claim.
Most teams end up with three tools: something to build the schedule, something to grade it, and something to explain it when the dates slip. LumaPlan does all three on one dataset, so the analysis is always looking at the schedule you actually have.
The engine
The arithmetic is the product. Everything else is a view of it.
The scheduler is a standalone Rust crate with no database underneath it, so it can be tested directly against reference exports from P6 and MS Project rather than against itself.
Forward, backward, float
Early and late dates, total and free float, and the driving path recomputed on every change. Serial chains come back with zero total float — the symmetry is regression-tested, not assumed.
Minute-accurate calendars
Per-weekday multi-shift working time, holiday and exception days, and calendars resolved per activity and per resource. Durations in minutes, hours, days, weeks or months.
All four link types, lead and lag
FS, SS, FF and SF with positive and negative lag, plus cycle detection that names the loop instead of failing silently.
Constraints and deadlines
Start/finish no-earlier and no-later, must-start-on, as-late-as-possible, and deadlines that generate negative float rather than moving the bar.
Out-of-sequence handling
Work that started before its predecessor finished is reconciled with either retained logic or progress override — the choice P6 makes you make, made explicitly.
MS Project or P6 arithmetic
The two disagree on inclusive finishes, lag counting and milestone promotion. LumaPlan implements both and lets the project pick, so your dates match whoever you report to.
Resources & cost
Loaded schedules, levelled and costed.
Units, curves and rates
Assignments carry units, work and a distribution curve. Resource rates are time-phased, so a rate change part-way through a project costs what it actually cost.
Two levellers, real priorities
A greedy leveller and a resource-constrained critical-path (RCPM) leveller, both honouring a priority basis you choose: activity priority, total float, or early start.
Histograms and usage grids
Per-resource demand over time, over-allocation highlighted against max units, and a task-usage grid for the time-phased numbers behind the bars.
Accounts, expenses, schedule of values
Cost accounts, non-labour expenses, a schedule-of-values view, and financial periods so cost lands in the period it belongs to.
EVM from per-period actuals
Planned value, earned value, actual cost, SPI and CPI computed from period actuals rather than from a percent-complete field somebody typed.
Shared resource pools
A resource can link to an enterprise pool. Demand aggregates across a parent and every descendant sub-project, and contention is flagged with a per-project breakdown.
Risk & analysis
Answer “what happens if” before it happens.
Monte Carlo
Three-point durations simulated across the network for a distribution of finish dates and a criticality index per activity — which activities are on the critical path in what share of runs.
What-if branches
Branch the schedule, change it freely, and compare against the live plan. Scenarios are stored, not thrown away when the dialog closes.
Driving-path player
Replay how the driving path moved between updates. When the finish date slipped, this is the view that shows which chain took over and when.
Recovery planning
Work the schedule back toward a target date with the crashing and re-sequencing options priced, rather than guessing at a fragnet.
Schedule health
24 checks run automatically on every recalculation, each finding clickable through to the activities it names. See the list →
Time machine
Every change is recorded. Scrub the schedule back to any point and see what the plan said then — the version that matters in a dispute.
Views
Six ways to look at the same schedule.
Not six modes with different data behind them. One project, rendered the way the question needs.
Gantt
The main grid and timescale, with configurable bar styles, custom columns, filters, grouping and baselines. Holds 60 fps scrolling on a 19,000-activity programme.
Network diagram
The activity-on-node view, for when the question is about sequence rather than dates.
Flowline / time–location
Distance against time for linear work — tunnels, roads, rail, repeating floors. The view that shows crews colliding before they collide.
4D location timeline
Activities tied to locations and drawings, played over time. Where the work is, not just when it is.
Lookahead, kanban, my work
Rolling lookahead windows for coordination, a board view for teams that live in one, and a personal work list off the same activities.
Dashboard and presentation
A metrics dashboard, a report composer, and a fixed 16:9 presentation view that exports as PNG, SVG, PDF or PPTX without redrawing anything.
Working together
Multi-user, with a record of who changed what.
Presence and streaming updates
Several people on one schedule, changes streamed over a live connection, and avatars showing who else is in the file.
Change requests and a review board
Proposed changes can be raised, reviewed and accepted rather than applied straight to the baseline.
Activity codes and ID schemes
Multi-level activity code types and values, configurable activity-ID schemes, and code roll-down across a WBS.
Accounts and roles
Password-gated web access with per-project access control. The native desktop build signs in as the logged-in OS user instead.
Risk, deliverables, procurement
The registers that normally live in a spreadsheet beside the schedule, kept against the activities they belong to.
An MCP server for AI tools
LumaPlan exposes the schedule over the Model Context Protocol, so an assistant can query and change the plan through the same domain rules the UI uses.
Getting it out
The deliverable is usually a document.
Submittal packs
A schedule submittal with the columns you choose and a timescaled Gantt on any page size from A4 to 11×17, with critical work in red and progress overlaid.
Print current view
Prints exactly what is on screen — same filters, same sort, same columns — instead of re-deriving a different schedule on the server.
XLSX, PPTX, and back again
Spreadsheet export for the rows, PowerPoint for the presentation, and a live-XLSX link for the people who will only ever open Excel.
LumaPlan is in active development and not open for signups. Everything on this page is built and running against real construction programmes; the roadmap says plainly which parts are still being finished.