Templates and practice · Reviewed 5 November 2026

A work to-do list template you can use today

Use this free template to keep your own actions, real deadlines and promised inputs in one readable record. Copy or download the blank list, then use the filled example to adapt it to your work.

Handling a blocked task with a deadline · See a master-to-daily worked example, or start with the blank below.

Start with the blank template

Download the plain-text file, or edit the version below and copy or download your changes. No account needed. You can paste the text into your notes app or a document.

Download the blank template (.txt)

This editor does not save your changes when you leave or reload. Copy or download your list before closing the page. Its copy and download actions do not send your list contents to Qubit.

What belongs on a work to-do list?

Record the next action you own, a real deadline when there is one, and enough context to find the request again. Keep promised inputs from other people in a separate section. That lets you see the work you can move forward without losing the things you need to check.

You do not need to fill every field for every small task. “Send the signed form to Maya” may be enough when the context is obvious. Add the source and a check-back point when the task will be hard to reconstruct later.

Next action
Write something you can do. “Budget” is a topic; “Check the revised budget and send the questions” is an action.
Due date
Use the agreed completion date. Leave it blank if no deadline exists. A day you hope to work on it belongs in the planned-work field.
Source or context
Keep the message, meeting note or document that explains the promise. A short reference is enough if you can reliably find it.
Next check / planned work
Write when you will revisit the item or work on it. This is your plan, which can change without changing the agreed deadline.
Waiting on someone else
Record who owes the input, what they promised and when you will check back. Their delivery date and your follow-up date can be different.

If a request is still too vague to put on the list, see next-action examples for email, Slack and meetings.

A filled example: a briefing and the figures it needs

Fictional example. These entries illustrate how to use the template, not a result extracted by Qubit.

My next action

Action: Draft the launch-risk briefing for the client.

Due: Friday, as agreed in the client email.

Source: Tuesday's scope email.

Planned work: Outline on Wednesday; check the figures before sending.

Waiting on someone else

Person and input: Maya's approved launch figures.

Agreed delivery: Wednesday.

Check back: Wednesday afternoon if the figures have not arrived.

Related action: Finish the figures section of the briefing.

The briefing remains your task. Maya's figures are an input you need from her. If the figures are late, you can still prepare the outline, ask for an update, and discuss the delivery impact. A waiting-on record helps you notice that decision; it does not resolve the dependency for you.

Turn a master to-do list into a realistic daily list

Your full list keeps work from disappearing. Today's list is a choice about what you intend to do with the time available. You can use two views in one app, or mark selected items in the same document; you do not need to maintain two competing records.

Fictional Wednesday example. Time estimates and the selection below illustrate the process, not an optimized schedule or a recommended daily task count.

The full work list

  • Client memo: send tomorrow; draft needs about 50 minutes.
  • Budget review: due Friday; reviewing the changes may take 30 minutes.
  • Approved figures: waiting on a colleague; the agreed check-back point is today.
  • Research a possible new tool: optional, with no agreed deadline.
  • Client call at 2 pm: a fixed appointment already in the calendar.

The choice for today

After accounting for the call and other commitments, suppose you have about two hours available for this work. Draft the memo, review the budget changes and send a short check-in about the figures, allowing about five minutes for that message. The rough estimates total 85 minutes, leaving about 35 minutes for transitions, overruns or new information.

The optional research stays on the full list for later consideration. The call stays in the calendar. The waiting-on entry remains open until you confirm the figures have arrived and are usable. Choosing three actions here is a consequence of this fictional day's work, not a rule to pick three tasks every day.

Make the selection without losing the remainder

  1. Check time and consequences first. Look at fixed appointments, real deadlines and any work that unblocks someone else. A short task is not automatically more important.
  2. Select available actions. Break off a useful first step if a task is too large. If it cannot move without an input, record your follow-up rather than treating the blocked work as ready.
  3. Keep unselected commitments visible. Leave them in the full record with their actual deadlines and sources. Not choosing them for today does not cancel them.
  4. Reassess after a change. If an urgent agreed request arrives or work takes longer, decide what moves and whether another person needs an updated expectation.

At the end of the day, confirm completed work and reconsider unfinished actions. Do not automatically change an agreed deadline because you did not get to the task. If the plan repeatedly fails to fit, discuss scope or timing instead of endlessly copying the same list to tomorrow.

Use the list/calendar guide to distinguish the delivery deadline from your work session. If an item is still vague, start with the next-action examples before choosing it for today.

A blocked task can still have a real deadline

Keep three dates separate: when you owe the delivery, when someone promised the input, and when you will check back. A task being blocked explains why it cannot move; it does not cancel the agreement you made.

Fictional example, separate from the examples above.

Your delivery: send a client summary on Friday at noon.

Input you need: approved figures promised for Thursday morning.

Your check-back: Thursday afternoon if the figures have not arrived.

Available work: prepare the parts of the summary that do not depend on those figures.

If Thursday's check finds the input missing, keep Friday's real delivery deadline in the record. Contact the person responsible, establish what is available, and assess whether Friday remains feasible. If it does not, discuss a revised scope or delivery time with the person expecting the summary. Do not silently replace the deadline with a follow-up date.

  1. Record the blocker precisely. Name the input or decision, who can supply it, and the source of the agreement.
  2. Keep your next check visible. A separate reminder can bring the waiting item back to your attention without presenting the blocked delivery as ready to execute.
  3. Make the consequence explicit. If the missing input threatens delivery, record the decision needed about scope, timing or another workable input.
  4. Check before resuming. An attachment arriving does not prove it is approved or answers the request. Confirm it is usable, then identify the next action on your delivery.

If there was no agreed delivery date, leave that fact clear rather than inventing one. If you cannot influence the input or deadline, make the unresolved constraint visible to the responsible person; a better list cannot supply missing authority or capacity.

The waiting-on example separates your action from another person's promise. For returning after the wait, see the restart note and source-check example.

Keep the template current when work changes

  1. Check the original request. Confirm what changed before editing the task. A suggested date is not always a new agreement.
  2. Update the action as well as the date. If the client now wants only launch risks by Monday, replace the old scope and Friday deadline. Keep the new message as context.
  3. Keep your work plan separate. Moving a writing block from Wednesday to Thursday does not move a deadline you agreed with someone else.
  4. Close completed work. Confirm that you sent the intended briefing before marking it done. Remove or archive it so the active list stays readable.
  5. Review the waiting-on section. Check whether an input arrived, whether it answers the request, and whether your own next action can now proceed.

For a fuller before-and-after example, see keeping a task current after a changed commitment. For follow-up messages and a thread ledger, use the client follow-up tracker.

Adapt it for daily or weekly use

For weekly use, revisit the full record as commitments change, then choose each day's actions from that current inventory. Keep one reliable record of the obligation so daily copies do not accumulate conflicting versions.

If you need to reserve a working session, put that time in your calendar. The list keeps the action and its context. The to-do list versus calendar guide explains how to keep a deadline distinct from a work block.

When this template is enough, and when to use an app

Keep the template if you can record and update your work reliably with little effort. A downloadable worksheet does not need to become another app subscription. If you already manage work successfully in a task app, use its equivalent fields instead of maintaining an extra copy here.

If the repeated problem is missing requests or manually changing the list after conversations, compare AI to-do list capture methods. Qubit can create and update tasks from supported captured context, with sources you can review and corrections you can make. It can still miss or misread work. Mac and web inputs and data handling differ; this standalone template has no connection to your Qubit account.

Other template formats

This page provides an editable plain-text list, not an Excel, Google Sheets or PDF download. If you need a shared team log with several owners, Smartsheet's action-item templates offer spreadsheet and document formats. If you already use Todoist, its template library may let you stay in the system you have.

Published by Qubit. The blank structure and fictional example are original editorial resources. They are not a tested productivity method or a promise that no commitment will be missed.

For freelancers, agency owners and teams, fractional CXOs, consultants, and client-facing roles like account managers. Use the template when a clear working record is enough. If keeping it current becomes another job, examine that upkeep separately.