Stages: the single answer to 'where is it?'
Stages exist so that a question with one correct answer has one correct answer. Typical production stages run from planning through material staging, execution, inspection, punch list and completion, but the right set is the one that matches how your trade actually works.
Keep the list short. Ten stages nobody updates is worse information than five that are always current.
Tasks: the unit of accountability
- Each task has an owner — a person, not a department.
- Each task has a point at which it is late, whether a date or a stage.
- Each task has a definition of done that someone else could verify.
- Tasks belong to the job; the same task should not exist in three tools.
Dependencies: what cannot start yet
Most schedule slippage is dependency slippage. Rough-in cannot be covered before inspection. Finish cannot start before delivery. Final cannot be billed before the punch list clears.
Writing dependencies down converts a vague sense that 'we can't do that yet' into a visible constraint the whole team can see and plan around. It also stops the well-meaning crew member who covers the work before inspection.
Templates for repeatable work
If you perform the same job type repeatedly, the stage and task set should be templated so it starts complete rather than being rebuilt from memory each time. The template captures what experience taught you; the judgement is in what you add or remove for this specific job.