Task List Template
Tasks with an owner, a due date and a status — nothing more.
Details
task list templateUploads
Your logo
A photo or picture
Goes on this page only. Drag it anywhere and pull its corner to resize it.
Your signature
Draw it with a finger, a mouse or a trackpad, and it goes on the page like a picture.
Pictures and signatures stay on this device. Nothing is uploaded to a server.
Red highlights mark what is still blank. Click anything on the page to change it. Your draft is kept on this device as you work.
| Project | [project] |
| Owner | [owner] |
| Period | [date] to [date] |
| # | Task | Owner | Due | Status |
|---|---|---|---|---|
| [add one task per line] |
What is a Project Task List?
A project task list is the flat record of everything that has to happen, each line carrying an owner, a due date and a status. It matters because work that lives only in someone's head or in a chat thread has no owner, and a task with no owner is not late — it is invisible. The list is what makes lateness visible early enough to do something about it.
Anyone running work that involves more than one person: a site foreman, an office manager arranging a move, a marketing lead running a launch, a teacher organising a school trip. It suits work of a few weeks to a few months — long enough that people forget things, short enough that a full project plan would be overkill. It is also the standard handover artefact: when someone goes on leave, the task list is what you send so the person covering knows what is outstanding and by when.
The format is universal; what varies is whether the list doubles as a legal record. Where tasks cover safety checks, statutory filings or regulated inspections, the record you must keep is set by the relevant authority — a workplace safety regulator, a tax authority, a professional body — and it usually specifies who signs, what is retained and for how long. Check that requirement before treating a spreadsheet row as evidence a check was carried out. Where the list names individuals and comments on their performance, data protection rules such as the UK and EU GDPR apply to it.
A task list does not show dependencies, and that is its main limitation. It will tell you the flooring is due on the fourteenth; it will not tell you the flooring cannot start until the electrician has finished. For work where one slip pushes everything behind it, you need a plan with sequence — a Gantt chart, or at minimum a dependency column. The list also carries no sense of effort, so a five-minute task and a three-week task occupy identical space on the page.
What to put in a Project Task List
These are the details this template asks for. Anything left blank is marked in red on the preview so you can see what is still missing.
| Field | What goes in it |
|---|---|
| Project | For example: Warehouse management system rollout |
| Project manager | For example: James Whitfield |
| Period from | Free text |
| Period to | Free text |
| Tasks | One per line: # | Task | Owner | Due | Status |
How to write a Project Task List
Write one task per line
A task is something one person can finish and mark done. 'Sort out the office move' is a project, not a task; 'confirm lift booking with building management for the fourteenth' is a task. If a line sits at half-done for more than one review, split it. Long compound lines are the usual reason a list stops being updated at all.
Give every task a single owner
Write a person's name, not a department. Facilities will not chase itself. Where the person doing the work sits outside your organisation — a contractor, a supplier — name your internal contact as owner as well, because you can only chase someone who reports into your project. A task with two owners behaves exactly like a task with none.
Put a real date in every row
Not 'ASAP', not 'ongoing'. Pick the date the task must be finished by for the next thing to start, and write it down. If you do not know, put your best guess and mark it provisional; a wrong date gets corrected at the next review, a blank one is ignored for a month. Write dates unambiguously — 14 March 2026 rather than 14/03, which reads as a different day on either side of the Atlantic.
Keep the status column to four values
Not started, in progress, blocked, done. Four states everyone reads the same way. 'Blocked' is the one that earns its place: it signals that the owner needs something from someone else, and it is the column you filter on before a status meeting. Add a short reason beside any blocked line, naming who or what it is waiting on.
Review the list on a fixed day
Fifteen minutes, the same time each week, working down the list rather than round the room. Change dates that have slipped instead of leaving them red — a list where a third of the dates sit in the past stops being read. Close out finished items by moving them to the bottom rather than deleting them, so you keep the record of what was delivered and when.
Common mistakes
- Assigning a task to a team rather than a person, so nobody starts it and nobody can be asked why it has not started.
- Using 'ongoing' as a due date, which removes the task from every filter you will ever run and guarantees it surfaces only once it is already late.
- Letting the list grow past a screen or two of lines, at which point people stop scrolling and the bottom third dies.
- Recording tasks without recording what blocks them, so a task sits untouched for weeks while its owner waits for information nobody knows they owe.
- Deleting completed rows, which leaves you with no record of what was actually delivered when a client or an auditor asks later.
Frequently asked questions
What is the difference between a task list and a project plan?
A task list is flat: every line is equal and the order is whatever you typed. A project plan adds sequence and dependency — it shows that task C cannot begin until A and B are finished, and it recalculates the end date when one of them slips. Use a task list when the work is mostly parallel and short. Move to a plan when one late item pushes a dozen others.
How detailed should each task be?
Small enough that its status is obvious to the owner without thinking, which usually means somewhere between an hour and a few days of work. Below that you spend more time maintaining the list than doing the work. Above it, the task sits at 'in progress' for weeks and tells you nothing. If you cannot say what done looks like in one line, break it up.
Should I put priorities on a task list?
Only if you will act on them. A priority column where four rows in five are marked high is decoration. If you need priority, mark a small number of items as this week's focus and leave the rest unmarked. For most short projects the due date already carries the priority, and a second ranking column just adds an argument to every review.
Can a task list be used as a compliance record?
Not by default. Where a check is required by a regulator — a fire safety inspection, a statutory filing, an equipment test — the form, the signature and the retention period are usually specified, and a spreadsheet row is not a substitute. Use the list to schedule and chase the check, and keep the official record separately. Confirm what your regulator requires before relying on it.
How do I stop the list going stale?
Give it one owner and one fixed review slot, and update it during that meeting rather than afterwards as homework. Lists die when maintaining them is somebody's private chore. It also helps to keep the list short enough to read in one pass: archive anything finished, and move anything that is not going to happen this quarter into a separate later section.
This page explains general practice and is not legal advice. Requirements differ between countries and, in some cases, between states — check what applies where the document will be used.