The fastest way to understand what makes a to do list work is to look at finished ones. Below are three to do list examples in full: a week inside a company, a week running your own business, and one bigger project. All three follow the same three rules: tasks start with a verb, lists are split by place, and a date appears only where a real deadline exists.
None of them are aspirational. They are meant to look like a real week, including the parts nobody puts on a productivity blog.
A week running projects inside a company
Product managers, team leads, consultants: work arriving from your own projects and from everyone else's at the same time.
Computer
- Email Priya the final draft of the Q3 roadmap
- Write three talking points for the one-on-one with Daniel
- Rework the pricing slide after Monday's objections
- Renew the analytics license deadline: August 21
Calls
- Call the vendor's account manager about the contract terms
- Call back the candidate who left a message on Tuesday
In the office
- Pick up the signed contract from legal
- Catch Daniel after standup about the sprint scope
Waiting on
- Priya's feedback on the Q3 draft
- Legal's sign-off on the vendor contract
Why it works: at your desk, the two calls are out of sight, and the things that need someone physically present wait until you are in the building. One real deadline exists in the whole set, so when it appears, it means something. Each entry can be started without thinking first. And the waiting list keeps handed-off work in view without letting it clutter the lists you work from, which is the difference between remembering to chase legal and discovering on Friday that nobody did.
A week running your own business
Freelancers and solo founders: client work, the admin nobody assigns you, and the business development that only happens if you make it happen.
Computer
- Send the revised proposal to Meyer & Co
- Write the March invoices
- Add the Kessler project to the portfolio page
- File the quarterly VAT return deadline: April 30
Calls
- Call the new lead back about scope and budget
- Call the accountant about the invoicing rule change
Waiting on
- Meyer & Co's answer on the proposal
- The signed contract from Kessler
- The February invoice, unpaid since the 14th
Why it works: "write the March invoices" has a visible finish line, unlike "sort out the billing." The VAT return carries a date because the tax office set it, not you. The proposal does not, because chasing it on Thursday instead of Tuesday costs nothing. And the waiting list is where a freelancer's money lives: an unpaid invoice that exists only in your memory is the one that goes unchased for six weeks.
A bigger project: launching the new pricing page
A launch is too big to be one entry. "Launch new pricing" would sit on a list for three months, radiating dread. Instead, the project gets broken into next steps, sorted by place like everything else:
Pricing launch: computer
- Draft the three tiers and what each one includes
- Send the refund wording to legal for review
- Write the migration email for existing customers deadline: October 1
Pricing launch: calls
- Call the payment provider about changing plan tiers mid-cycle
- Call two long-term customers about the new tier names
Pricing launch: waiting on
- Legal's review of the refund wording
- The final page design from Kessler
Why it works: only the current next steps are visible. The analytics events, the help-center rewrite, and thirty other future tasks stay in the project's notes until their turn comes. The one real deadline, the migration email, carries a date because it has to reach customers before the change. The rest happens in order, not on schedule.
What these examples have in common
Three patterns repeat across all of them, and they matter more than any layout:
- Tasks start with a verb and can be started without interpretation.
- Lists are split by place or tool, so each list only shows what is possible right now.
- Dates are rare and real. When one appears, it is believable.
The verb-first rule is more than taste. A concrete entry pre-decides the what and the where, which psychologists call an implementation intention. A 2025 meta-analysis of 642 tests found that these plans measurably raise the odds a task happens, and that the concrete "when and where" form outperforms a plan written as a vague schedule. Which is the case for writing "call the new lead back about scope and budget" instead of "new lead."
People often search for an effective to do list template, and the honest answer is that the template is the least important part. These three rules survive any medium: a notebook, a notes app, a spreadsheet, a whiteboard. A beautiful template full of topic entries and invented dates fails; a scrap of paper following the rules works.
One more thing the examples hide: behind each set of short lists sits one complete collection that holds everything, including what is not visible today. That collection is the master to do list, and it is what keeps the short lists trustworthy.
Make your own
The full method behind these examples, from the first complete capture to the weekly reset that keeps a list alive, is in the main guide: how to make a to do list that actually works. And if you want a tool where this pattern is the default rather than a discipline, tingdo works exactly like these pages read: lists by place, verb-first capture in two seconds, and no invented dates anywhere.