# Scheduling & the Critical Path
A schedule turns the work into a **sequence of tasks with durations** — and shows what has to happen when.
## Key ideas
- **Activities & durations** — break the job into tasks and estimate how long each takes.
- **Dependencies** — many tasks can't start until another finishes (you can't frame before the foundation cures).
- **Critical path** — the **longest chain** of dependent tasks; it determines the project's finish date. A delay on the critical path delays the whole job.
- **Float (slack)** — tasks not on the critical path have some wiggle room.
## Managing the schedule
- Use **look-ahead (short-interval) plans** — a rolling 2–3 week view of what's coming.
- **Update** the schedule regularly with actual progress.
- Protect the **critical path** above all — that's where delays hurt most.
**Takeaway:** Build a sequenced schedule, find the critical path (the chain that sets the finish date), and protect it with look-ahead planning.
> *Educational content — not legal or contractual advice. Follow your contract's specific procedures and deadlines.*
