Guide
Everything you need to know about the project schedule
A real project schedule is more than a timeline: it is a shared reference the whole team can work from.
When people think of a project schedule, they often picture a simple timeline. Building a genuine schedule requires something more: a reference that everyone on the team can use, and that survives the first week of reality.
What goes into a schedule
A schedule combines the task breakdown, the effort estimate for each task, the dependencies between them, the calendar (working days, holidays, leave) and the availability of the assigned resources. Remove any of those inputs and the dates become decorative.
Dependencies and the critical path
Linking tasks with finish-to-start or start-to-start relations reveals the chain that actually drives the end date — the critical path. Any delay on that chain shifts the whole project, which is where attention should go first.
Keeping the schedule alive
A schedule is only useful if it is updated. FoxPlan recalculates the plan when a task moves, shows the variance against the baseline, and lets you undo a change that turned out badly — so keeping the reference up to date does not become a project of its own.
