Project task list template (delivery-ready)
Copy this skeleton for a single project—from internal tool rollout to client delivery. Each phase ends with a “phase exit” check so you do not confuse motion with progress.
When you are ready to assign tasks, attach files, and track status with your team, start with TeamTasks instead of duplicating this list across chat threads.
Project header
Phase 0 — Alignment (before “real” tasks)
- Confirm problem statement and success metrics with stakeholders.
- Identify legal/security constraints (PII, access, retention).
- Agree communication channel for decisions vs. noise.
Phase exit:
Written approval from stakeholder(s) on scope and success definition.
Phase 1 — Plan and breakdown
- Work breakdown: deliverables → work packages → tasks (small enough to finish in < 3 days where possible).
- Risk register: top 5 risks, trigger signals, mitigation owners.
- Dependency map: who waits on whom; external vendor touchpoints.
Phase exit:
Published task list with owners and due dates for the next milestone.
Phase 2 — Execution cadence
- Daily: unblock list (15 min) — only actions, not status theater.
- Mid-week: scope triage — cut or defer before the deadline crunch.
- Weekly: demo or review of integrated work (even internal).
Phase exit:
Milestone demo accepted or change request logged with new dates.
Phase 3 — Hardening and handoff
- Checklist: monitoring, backups, runbooks, on-call, rollback.
- Training: who needs what level of access and documentation.
- Support transition: who owns incidents for the first 30 days.
Phase exit:
Signed handoff (even informal email) from project owner to operational owner.
Master task table (duplicate per work package)
| Task | Owner | Due | Priority | Blocked? | Notes / link |
|---|---|---|---|---|---|
| [Concrete verb + object] | P1/P2/P3 | Y/N | |||
Track the project in TeamTasks
Replace static tables with tasks your team can update, comment on, and filter by owner, due date, and status.
Create your team workspace