Most of what you owe this week arrived by email. So a to-do list made only of email covers most of your work, and it has one real strength. Every line on it came from somebody’s own words, with a date and a sender attached. You can always go back and check. The catch is that your inbox, left as it is, makes a weak list. The list that works is drawn out of the inbox, one ask per line. It also has a short tail of things that never came by mail.
- The inbox already holds the asks. It just doesn’t hold them as a list.
- A good line names the ask, who asked, the date if they gave one, and a link back to the thread.
- Calls, hallway asks and your own ideas never reach your mail. One list needs room for those too.
- A line goes stale when the thread moves on. The link back is how you catch it.
Can your inbox be your to-do list?
People have argued both sides of this for years, and both sides are right about something.
The case for is about habit. A post on Zapier’s blog puts it simply: “My Gmail inbox, on the other hand, is open all day, every day.” A list you never open is no list at all. Your inbox is the one place you’re sure to look.
The case against is about shape. Leo Babauta, writing on Zen Habits, lays it out:
You’ll need to open each email to find the actions, which is very inefficient.
He adds that one email can hold several actions, that an inbox can’t be put in order of importance, and that new mail keeps pulling you away. His fix is to “choose a simple to-do list and as you process your email inbox, pull out the actions.”
Put the inbox next to a working list and the gap is easy to see.
| What a list needs | What the inbox gives you |
|---|---|
| Each line says what to do | A subject line, which usually names the topic |
| One line per job | One message, which may hold two or three asks |
| A date you can sort by | The date the message arrived |
| A way to mark one job done | Archive, which clears every ask in the message at once |
| Only work | Work mixed in with news, receipts and newsletters |
The common workarounds sit in the middle. Many people mark a message unread to come back to it, or star it, or flag it. Each of those says “something here,” and none of them says what. The rest of this guide is about the list Babauta describes, built only from your mail.
What one line on the list carries
Here’s an email of the kind Sarah, who runs a seven-person firm, gets most mornings. It’s from a client on a Tuesday.
Hi Sarah, thanks for the call yesterday. The board liked the direction. Before Friday’s meeting, could you send the revised fee table? Also, our new controller starts Monday. I’d like her to have access to the shared folder by then. Have a good week.
That message is two lines on the list. Here’s what each one carries.
| Field | Line one | Line two |
|---|---|---|
| The ask, as a verb | Send the revised fee table | Give the new controller access to the shared folder |
| Who asked | The client, Tuesday | The client, Tuesday |
| The date | Before Friday’s meeting | By Monday |
| Whose move | Yours | Yours, or whoever runs the folder |
| Link back | The thread | The same thread |
Each field earns its place.
- The ask, as a verb. “Fee table” is a topic. “Send the revised fee table” is a job. You can tell at a glance whether it’s done.
- Who asked, and when. That’s what tells you whom to answer, and how long they’ve been waiting.
- The date they gave. Use the sender’s date, in their words. If they gave none, leave it blank rather than guess one. A made-up date on a list soon teaches you to ignore all the dates.
- Whose move it is. Some asks land on you but belong to a colleague. The line says so, so it doesn’t sit on your list as yours.
- The link back. This is what makes a list made of email trustworthy. Three weeks on, “send the revised table” won’t tell you which table. The thread still will.
Gmail’s own Add to Tasks keeps a link to the email for exactly this reason. Moving an email into a list without retyping it is its own job, and from email to task, without retyping a word walks through the routes.
Where the asks on it come from
Most lines start in a message someone sent you. A few start elsewhere in your mail, and they belong on the same list.
- Asks in your incoming mail. These are most of the list. Some hide below the news or second in a message, and where action items hide in a thread shows where to look.
- Promises in your sent mail. “I’ll get that to you Monday” is an item, even though nobody asked it as a question.
- Notes you email to yourself. Plenty of people send themselves a one-line email as a reminder. It works, because it puts the note where you already look. Give it a subject that’s the job itself, like “Call the landlord about the lease,” so it reads as a line.
- Forwards with one line on top. “Can you handle?” above someone else’s email means the real ask is in the forwarded part.
What stays off matters as much. A newsletter, a receipt and a “thanks, got it” are mail, but they’re not work. An ask that a colleague already answered on the thread is history. Keeping those off is what lets you trust the list when it says something is yours.
What never arrives by email
A list made only of email has blind spots, and they’re predictable.
- Asks made out loud. A client mentions on a call that they need the signed copy. Nothing about that ever reaches your mailbox.
- Your own ideas. The project you mean to start, the supplier you should switch, the hire you need to make.
- Recurring work. Payroll, the quarterly filing, the month-end close. These come from the calendar, not from a sender.
- Asks inside attachments. A contract with a signature line on page nine says nothing in the email body.
- Anything settled off the thread. A client cancels by phone at 8:30. The email asking for the meeting is still sitting there at 9:40.
The fix is simple. Keep one list, mostly fed by email, and let yourself add a line by hand when work arrives some other way. Two lists, one for mail and one for everything else, is how things fall into the gap between them. A one-line email to yourself after a call is a fine way to bring a spoken ask onto a list made of email.
Keeping each line true as the thread moves on
An email list has one quirk a handwritten list doesn’t. The source keeps talking. A Thursday reply can move the date, shrink the job or cancel it. Someone else on the thread can do it for you.
So each line is a pointer into a live conversation. A few habits keep it accurate.
- Open the thread before you act on an old line. Read the newest message first. A line that’s been sitting for a week is the likeliest to have changed.
- Update the line, then do the work. If the client moved Friday to next Wednesday, change the date on the list. Otherwise next week you’ll be chasing a deadline that no longer exists.
- Cross off what someone else did. If a colleague already sent the fee table, the line is done. It isn’t yours to do twice.
- Watch the replies that change scope. “Actually, just the summary page” makes a big job small. The line should say the smaller thing.
What happens after a line is on the list, the chasing and the closing, is its own subject. What turns an ask into a loop you can close picks it up from here.
A list made of email that Point keeps for you
Point is an email client, and it reads each thread as it lands. When a message asks something of you, Point drafts a task from it. The task carries the ask, the date the sender named, and a link to the exact words. Sarah’s client email above would come through as two tasks, one due before Friday and one by Monday.
How far Point goes depends on the setting you choose for tasks.
- Suggest only. Point shows you the ask it spotted. You decide whether it goes on the list.
- Review. The task is ready and waiting for your yes. Every kind of action starts on this setting out of the box.
- Handled outright. The task goes straight onto your list.
Tasks you type in yourself sit on the same list, so a spoken ask has a home next to the emailed ones. When you answer a thread in the ordinary way, Point can mark the matching task as looking finished. It shows you why, and the call is yours.
Point misses things, in the same places a person does. It only reads what came through your mail, so a phone call is invisible to it. A conditional ask, like “if you want the Tuesday slot, confirm by Friday,” is a judgment call. An ask buried in an attachment is worth checking yourself. That’s why every task keeps its link back. When a line looks wrong, the sender’s words are one tap away.
Adding a task in seconds, giving it a date and getting a nudge to chase are covered in email task management, without writing it down. Briefings, drafted replies and the other jobs Point takes off a busy morning are listed on the benefits page.
Common questions
Should my inbox double as my to-do list?
It works as a place to look, and it’s weak as a list. The inbox shows topics, not jobs, and one message can hold several asks. Archiving clears them all at once. Most people do better pulling each ask onto one list, each line linked to its thread.
What should a to-do item made from an email include?
The ask written as a verb, who asked and when, the date they gave, and whose move it is. Add a link back to the thread. Leave the date blank if the sender didn’t name one.
Should I email myself reminders?
It’s a reasonable habit if your list is built from your mail. Write the job itself in the subject line, like “Send Dana the signed lease.” Then it reads as a line on the list instead of a vague note.
How do I get asks from phone calls onto an email-based list?
Add them by hand, or send yourself a one-line email straight after the call. Either way, keep them on the same list as your emailed asks. A second list for spoken asks is where they get lost.
What happens to a task when the email thread changes?
Nothing, unless you change it. A later reply can move the date or cancel the job, and a list line won’t know. Open the thread before you act on any line that’s more than a few days old.
Can software build my to-do list from my email?
Partly. Several tools read a thread and suggest tasks, and some will add them for you. All of them miss asks made off the thread, and some misread conditional ones. What an app can read in your mail covers what comes out cleanly and what doesn’t.