The delivery sequence at a glance
This is the sample plan for the Harbor Street move. Weeks count from kickoff (Week 1). Each milestone lists its prerequisite, so you can see what a slip would hold up.
The table shows the agreed sequence, not today's task status. Daily progress lives in the project's work tracker, where each workstream owner updates their own tasks.
Sample milestone schedule
Illustrative target weeks. Read left to right: what, when, what it waits for, who answers for it.
| Milestone | Target | Waits for | Accountable role |
|---|---|---|---|
| Floor plan approved | Week 4 | Space needs from all six departments | Workplace Facilities Manager |
| Equipment and network ordered | Week 6 | Approved floor plan | IT Service Owner |
| Network equipment delivered | Week 7 | Week 6 equipment order | IT Service Owner |
| Phase 1 move: Finance, HR | Week 9 | Floor 2 network tested | Department Move Coordinators |
| Phase 2 move: Sales, Support | Week 12 | Phase 1 issues closed | Project Lead |
| Phase 3 move: Product, Operations | Week 15 | Phase 2 issues closed | Department Move Coordinators |
| Handover accepted | Week 17 | Phase 3 open items reviewed | Receiving Operations Lead |
If a prerequisite changes
Example: the supplier moves network equipment delivery from Week 7 to Week 8.
-
1
Name the change
Write one sentence: what moved, from when to when, and why. For example: 'The supplier moved switch delivery from Week 7 to Week 8.'
-
2
Find what waits for it
Check the Waits for column. Here Phase 1 depends on a tested Floor 2 network, so Week 9 is at risk.
-
3
Tell the Project Lead the same day
Send the sentence and the affected milestone before the next Thursday check-in, not at it.
-
4
Update the tracker, then the plan
The owner updates the task in the work tracker. The Project Lead updates this page if a target week changes.