FinitePath turns a static CPM file into a working model — plan it, cost-map it, compress it, and hand your client a report that shows exactly where the project stands and where it’s headed.
0 activities · CPM Pending
Everything below reads from the same live model — change one sheet and the rest recalculate.
Scheduling in one tool, resources in a spreadsheet, vendor progress in email, claims in a consultant’s report a year later. FinitePath runs all six off the same network.
A full forward and backward pass on every save — not a nightly batch, not an export.
Assign crews and see utilisation immediately, with over-allocation flagged rather than buried.
Three tiers of schedule that stay in step — the contractual one governs the rest.
Build the record as the project runs, not eighteen months later from memory.
Ask the schedule a question and get an answer with the evidence attached.
Durations calibrated to how the work actually goes in, where it is going in.
Any tool can shorten a bar. The question a planner has to answer is what was spent to do it — whose float, which handoffs, how much risk moved onto the trades behind. FinitePath compresses and shows the bill in the same view, so the decision is made with both numbers on screen instead of one.
Centre — the baseline as seeded. No overlap added or removed. Drag right to compress by spending float, or left to add buffer between crew handoffs.
Flags activities whose durations don’t hold up — AACE proportionality violations, activities needing decomposition. Every finding is a proposal you accept or reject.
Pessimistic, most-likely and optimistic in one click, plus forensic closes — as-planned, as-built to date, or closed at a review date.
Rewires crew handoffs across a WBS branch and shows the variant against the baseline ghost, with the float it consumed.
An order-of-magnitude estimate of recoverable days, ranked by priority — labelled as an estimate, because that is what it is.
Nothing here commits itself. Every optimization is a variant sitting beside your baseline. You compare it, promote it or discard it — and a recovery figure is always labelled an estimate, never a date the engine cannot defend after a re-run.
Generated from the model at the moment you print it — not assembled by hand the night before. Every figure traces back to an activity, and anything the data cannot support prints a diagnostic code instead of a number.
Three ways in, depending on where you are. Students and early-career schedulers learn CPM by building a network by hand. Superintendents and engineers start from a schedule they already have. Planners and executives start from nothing and let the guided builder structure it.
Three-point estimates — optimistic, most likely, pessimistic — resolved to an expected duration by (O + 4M + P) ÷ 6, with standard deviation from (P − O) ÷ 6. Build the network visually, watch the forward and backward pass run, and see total float, free float and the critical path fall out of it.
Import Primavera P6 (.xer / .xml), MS Project XML or an Excel BOQ. The importer carries calendars, relationships, constraints and cost assignments — then tells you what it could not resolve rather than quietly dropping it.
Answer a few questions — sector, structure system, scale — and FinitePath ranks your as-built library by fit, each with a confidence score. Launch the closest match and edit from there.
Product walkthroughs and short learning modules on CPM scheduling, baselines, project monitoring, reporting, and AI-assisted planning — new videos added regularly.
Import a schedule, run F9, and see the critical path in the time it takes to make coffee.
A schedule, a claim, or a baseline you need built. We answer with a person, not a sequence.