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 scheduling engine is self-contained: no database beneath it, no interface on top. That is what lets it be tested against reference exports from P6 and MS Project, rather than against itself. The dates are the part that has to be right, so the dates are the part that gets proved.
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.
Multiple float paths, ranked
Not just the critical path. The second, third and tenth chains behind it, each ranked by the float that separates it from driving the finish. The chain about to become critical is the one worth watching.
Permitted work windows
Track possessions, outages, road closures: activities that may only run inside an agreed window. The engine schedules into the window, and flags work that has slipped outside every one it was given.
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, actual cost from your ledger
Planned value, earned value, SPI and CPI — actual cost can come from period actuals or straight from your imported accounting ledger, with a monthly screen that says in plain sentences whether the schedule and the ledger still agree.
A monthly close, not a spreadsheet
Drop in the accounting export and LumaPlan already knows its shape from last month. It then tells you where the two disagree — money charged to work nobody is doing, work underway that nothing has been charged to — and writes the actuals into the schedule once you agree.
One critical path across many projects
Link activities between projects and schedule the programme as one network. The driving chain crosses project boundaries, so the single-project answer and the portfolio answer stop disagreeing. Levelling can pool a resource two projects both booked.
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. You get a distribution of finish dates and a criticality index per activity: which activities are critical, 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.
26 checks, all 14 DCMA points
Every recalculation grades the schedule, and every finding clicks through to the activities it names. Eleven go past the published standard — among them a date another organisation owns that nobody has re-confirmed, and work that has drifted outside the window it was permitted. 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
Seven 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.
Pivot — rows you choose, time across the top
Group by WBS, activity code, resource or the period a date falls in, and put earned value in the cells. It is the shape a cost performance report already wants, built from the live schedule rather than retyped into a spreadsheet.
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.
Every variance stays reproducible
Proposed changes go through a review board with an approval chain and line items. If an accounting import moves a budget the schedule owns, LumaPlan auto-files the change request and re-baselines through it — never around it — so every variance you ever reported stays reproducible.
Global change and find-and-replace
Re-code a thousand activities, or shift a subcontractor's durations, in one pass. Every change is previewed before it is applied, and undone as a single step.
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. Critical work in red, 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.
All of it, on one schedule.
Everything on this page is built and running against real construction programmes. Early access is opening to teams running live work.
Bring a programme with you. Drop a .mpp or .xer straight into LumaPlan and it grades the schedule — no project to set up first.