Project Task Tracker
A tracker for project tasks: list, overdue tasks, completions, and review.
Download this template
Choose the file you need, then download it. No sign-up, no payment.
Choose a design
The same document in 9 designs, same content and editable fields, different styling. Pick the design you like and download that version. Click any design to preview it larger before downloading. The Sample card shows a completed example, filled in with sample details.
Classic Navy
Executive Charcoal
Modern Minimal
Compact
Burgundy
Forest
Teal Professional
Warm Copper
Mono
Sample
What’s Included in This Resource
Every resource on The Office File provides a complete toolkit rather than an empty, unhelpful document shell:
- Editable Microsoft Word (.docx) template (42 KB)
- Printable PDF version (99 KB)
Sample included: Example: Project Task Tracker in use. Tracking project tasks week by week: task list, overdue tasks, completion record, and weekly review.
How to Use This Template
Follow these practical steps to customize and roll out this procedure with your team:
1. List tasks with owners and dates
Every task carries an owner, due date, and status.
2. Move overdue tasks explicitly
Give overdue tasks a new due date and a reason, never leave them stale.
3. Record completions
Log who completed each task, when, and who checked it.
4. Review weekly
Record completions, carry-forwards, and blockers at the weekly review.
About This Template
Tracking does not need expensive software. This template is a practical, printable tracker with the essential columns for monitoring progress, flagging issues, and recording outcomes. Use it in weekly reviews to keep everyone aligned on what is open, what is stuck, and what is done.
Tracking project tasks week by week: task list, overdue tasks, completion record, and weekly review.
When to Use This Template
- Reporting progress to clients or management with real status data
- Escalating blocked items with a clear history of what has been tried
- Visualising workload distribution across team members
- Closing the loop by recording outcomes, not just activities
- Following up on outstanding actions so nothing goes stale
Key Sections Explained
Understanding what goes in each part of the document helps you fill it in correctly the first time:
Outcome and close-out
How it ended and any lessons recorded, so the tracker becomes organisational memory, not just a to-do list.
Item identification
What is being tracked, a task, issue, asset, or case, with a unique reference for each row.
Owner and dates
Who is responsible, when it was raised, and the target date. Ownership plus deadline is what drives action.
Notes and history
Running commentary on progress, blockers, and decisions, the narrative behind the status.
Status column
Where things stand: open, in progress, blocked, or closed. This is the column your review meetings revolve around.
Frequently Asked Questions
How often should the tracker be reviewed?
Weekly at minimum for active trackers. A tracker reviewed monthly will accumulate stale items; one reviewed weekly stays honest and actionable.
What do we do with blocked items?
Name the blocker, name the person who can unblock it, and set a date to revisit. 'Blocked' without an owner and a next step is just a polite way of giving up.
When should an item be closed?
When the outcome is recorded, not just when the activity stops. 'Done' with no outcome noted teaches nothing; a one-line outcome turns the tracker into organisational memory.
How many items is too many?
If the tracker has more open items than the team can meaningfully discuss in a review, split it by area or priority. A tracker nobody can hold in their head stops being a management tool.