Critical path scheduling

Every project is a web of tasks, and some can't start until others finish. The critical path is the specific run of linked tasks with zero slack — the tasks where a one-day delay becomes a one-day delay for the entire project. Tasks off the critical path have 'float': room to slip without moving the finish date.

How it's calculated

A scheduling engine walks the dependency graph forward to find the earliest each task can start and finish, then backward to find the latest each can run without delaying the project. Tasks whose earliest and latest dates are identical have no float — together they form the critical path. The technique, formalized as the Critical Path Method (CPM), is a core part of the standard project-management body of knowledge.

Why it matters for MSPs

MSP delivery work — client onboarding, email and file migrations, security rollouts — is dependency-heavy: you can't cut over mailboxes before the tenant is built, or deploy endpoints before the image is approved. Without a critical-path view, a technician's slip on a 'small' task quietly moves the go-live date and nobody notices until the client asks. With one, you know exactly which tasks to protect.

How Current does it

Current runs a dependency-aware scheduling engine with a real critical-path calculation, so the tasks that drive your go-live are flagged automatically. When a predecessor moves, downstream dates recast and the critical path updates — across the timeline, the dependency map, and what-if scenarios.