Somewhere in your inbox right now is an email like this: "Thanks for yesterday! Quick thing before I forget, could you get the revised figures to Sara before Friday's board meeting? Also loop in Tom if the timeline shifts." That's a friendly note on the surface. Underneath, it's two tasks, a deadline, and a conditional, and none of it is tracked anywhere except your working memory.
Task organising for email people starts with one skill: extraction. Getting the ask out of the thread and into a list, in a form your future self can act on without reopening the email to reconstruct what it meant.
Why the inbox can't be the task list
It's tempting to skip extraction and just "keep it in the inbox until it's done." Three reasons that fails:
- Wrong sort order. Inboxes sort by arrival. Your Friday deadline sinks under Thursday's newsletter.
- No structure. An email can't hold sub-steps, a status, or a due date. Multi-step work has no home.
- Attention leak. Every scroll past an undone thing costs a little focus. Psychologists call the effect of open loops on attention the Zeigarnik effect: unfinished tasks keep intruding on the mind until they're captured somewhere trusted.
Flagging is the same trap with a star on it. Flags carry no deadline and no priority, so the flagged pile becomes a second inbox you also avoid. If your flagged list currently has more than ten items and you can't say what the third one is, you already know.
The anatomy of a good extracted task
A task that will actually get done captures four things at the moment of extraction:
| Part | Bad | Good |
|---|---|---|
| Verb-first action | "Sara figures" | "Send revised Q3 figures to Sara" |
| Deadline | none | "by Thursday EOD (board meets Friday)" |
| Source link | none | link back to the original thread |
| Owner | ambiguous | you, or delegated + logged as a waiting-for |
The verb matters more than it looks. "Lease" on a list produces a small dread every time you read it, because you have to re-derive what it means. "Review lease draft, reply to Anna with comments" can be started cold. The source link matters because context ages fast: three days later you will not remember which of four lease threads this came from.
When to extract: at processing time, in batches
Extraction belongs inside your email processing sessions, two to four a day, never during focused work. The moment you read an actionable email, it takes one of two exits: under two minutes, do it now; over two minutes, extract it and archive the thread. The one forbidden move is closing an actionable email with no exit, because that schedules a re-read, and re-reading the same message five times is where email hours quietly go. The full processing routine is in our email management system.
Don't forget the other direction: waiting-fors
Half your open loops don't come from what you receive but from what you send. Every question, delegation, and proposal in your outbox is a task on someone else's plate that you need to track. Keep a waiting-for list beside your task list, and sweep it weekly for anyone gone quiet. GTD practitioners consider this list the method's most underrated component; our GTD and email guide goes deeper.
Manual methods, and where they crack
Copy-pasting into a task app works and costs 30 to 60 seconds per email. Forward-to-app addresses work too, though the task arrives verb-less and needs editing anyway. Both share a failure mode: they depend on you noticing the ask in the first place, and at 120 emails a day, buried third-paragraph requests get missed precisely on the days you're busiest.
That noticing-and-extracting step is what Pidgy automates. It reads your Gmail or Outlook inbox and turns requests into verb-first next actions with the deadline and source thread attached, splits what you're waiting on from others into its own list, and files informational mail as reference. You approve a prepared list instead of building one by hand. The Sara email at the top of this post becomes two tracked tasks and a follow-up watcher in the time it took you to read it.
