Project Critical Path Planner

How to use Project Critical Path Planner

A forward topological pass finds earliest timing. A backward pass from the shared project finish finds latest timing. Zero total slack identifies critical tasks; connecting critical edges must also join matching finish/start times.

1. Enter task json (id, duration, predecessors array).
2. Choose the stated convention and check the units and supported model.
3. Calculate, inspect the result, then copy or download it.

Good to know

• Exact-grid inputs use plain decimals with at most six decimal places and magnitude at most1e9. JSON numeric inputs use their stored decimal spelling; quote decimals when their exact entered spelling matters. No input is evaluated as code. Up to100 tasks and500 edges. Nonnegative durations share your chosen time unit. All dependencies are finish-to-start with zero lag; no resource capacity, work calendar, probabilistic schedule or date prediction is modeled. Disconnected tasks share the same completion deadline.
• Runs locally without input persistence. Text/JSON fields have a30000-character cap unless a stricter page limit applies; output has a1000000-character cap. Exact-grid workflows preserve six-decimal arithmetic, while approximate workflows use finite floating-point values. JSON downloads retain complete stored numeric values and exact fractions where provided. Unsupported formats and detected numeric or work-budget excess return an error or a clearly unresolved classification.
• Educational user-assumption arithmetic only. No live prices, laws, tax rules, quotes or financial advice.