19 items

Email Management System Setup

Configure Gmail or Outlook once, correctly, and stop managing email forever. This checklist covers exact filter rules, a minimal folder structure, and the processing habits that keep your inbox at zero — permanently. For more background and examples, see the guidance below; for built-in tools and options, use the quick tools guide.

Author

Checklistify Editorial Team

Last Updated

Checklist Items

0 done•19 left•4 of 5 sections collapsed

Dedicate 20–30 minutes to a pure unsubscribe session — sort inbox by sender, unsubscribe directly from every email you don't actively read.

Volume reduction is the highest-leverage action in this entire setup: filters and folders organize email that arrives; unsubscribing prevents it from arriving at all. Dedicate a separate session purely to this before building any folder structure or filter — mixing unsubscribing with regular processing slows both tasks. Sort your inbox by sender (Gmail: switch to a search view sorted by From; Outlook: View → Sort By → From), which groups all emails from each sender together and makes the volume from each source visible at a glance. The decision rule: if you can't remember the last time you read it and can't name a reason you'd miss it, unsubscribe — not filter. Tools that help: Gmail's Promotions tab groups subscription emails automatically; Unroll.Me aggregates all subscriptions and allows bulk unsubscribing with one click, but note it has had documented privacy issues involving sale of user data to third parties — direct unsubscribing via the footer link in each email is slower but preserves your data privacy. Most legitimate newsletters include an unsubscribe link in the footer per CAN-SPAM requirements; if an email lacks one, mark it as spam rather than attempting to reply directly.

Create a dedicated secondary email address for future low-value signups, free trials, and gated content downloads.

The most permanent way to prevent subscription volume from growing back is to never give your primary address to services that don't genuinely need it. Set up a free secondary Gmail or Outlook account as a 'junk collector' and use it exclusively for: free trial registrations, contest entries, content gated behind an email form, and any service you're evaluating once and may cancel. You check this account rarely — weekly or never. Your primary address is now reserved for genuine professional and personal communication. For situations where even a secondary address feels like too much overhead, browser-based alias services like Apple's Hide My Email, Fastmail's masked addresses, or SimpleLogin generate throwaway addresses that forward to your real inbox until you delete the alias — nothing from that sender ever touches your primary address again. The two-address discipline prevents the system from needing to be rebuilt every six months as new subscriptions accumulate.

Disable all email notifications on every device — badges, lock-screen previews, banners, and sounds — completely, with no exceptions.

Email notifications are the primary mechanism that converts email from an asynchronous communication tool into a real-time interruption channel. The interruption cost extends far beyond the seconds it takes to glance at a notification — per Gloria Mark's UC Irvine research, recovering full focus after any interruption averages approximately 23 minutes, even when the interruption itself takes only seconds. For someone who checks email 15–20 times per day (a figure consistent with multiple workplace studies), the compounded attention overhead is several hours of fragmented work daily. Disable completely: on iOS, Settings → Notifications → [Mail app] → turn off all notification types including the badge count. On Android, long-press the app icon → App Info → Notifications → off. On macOS, System Settings → Notifications → [Mail app] → off. On Windows, Settings → System → Notifications → toggle off for your email client. The common objection — 'what if something urgent arrives by email?' — is worth examining honestly: in most roles, genuinely urgent matters arrive by phone call, text, or instant message. If a specific address or sender does require near-real-time monitoring, configure a forwarding rule for only that sender to go to SMS — turn on notifications for one person, not for all email.

Create exactly four top-level categories: Action Required, Waiting For, Reference, and Receipts — nothing more.

Email systems with more than five or six folders fail not because of poor intentions but because the decision overhead of choosing the correct folder becomes a recurring friction point that makes filing feel like work. The four-category system maps to the only four meaningful states an email can be in: it requires an action from you (Action Required), you've acted and are waiting for a reply or an outcome (Waiting For), it contains information you may need to retrieve but no action is pending (Reference), or it's a financial record with potential future utility (Receipts). In Gmail, these are Labels — navigate to the left sidebar, scroll to the bottom, and click 'Create new label.' Gmail labels tag emails rather than moving them, so a single email can carry multiple labels simultaneously. In Outlook, these are Folders — right-click Inbox in the folder pane and select 'New Folder.' One critical Outlook distinction: moving an email to an Outlook folder removes it from the Inbox view entirely, while a Gmail label tags it and leaves it accessible everywhere including All Mail. Both approaches work; consistent application matters more than the specific implementation. Resist any urge to add subcategories such as 'Action Required / Client' or 'Reference / 2025' — additional granularity rarely aids retrieval and significantly increases filing overhead on every single email.

Create a VIP label or contact rule for senders whose email must always reach your inbox, bypassing all other filters.

Every automated filtering system carries a risk of over-filtering — a newsletter filter catches an email from a real contact whose address happens to match a pattern; a subject-based filter catches a legitimate invoice alongside promotional noise. A VIP allowlist is the explicit safeguard. Create a label called 'VIP' or a contact group called 'Priority Senders.' In Gmail, create a filter with criteria 'From: [sender@domain.com]' and the actions 'Never send to spam,' 'Apply label: VIP,' and optionally 'Mark as important.' Add the people whose email genuinely requires same-session attention: your manager, key clients, your accountant, close collaborators. In Outlook, right-click an email from a VIP sender → Rules → Always move messages from [sender] to a designated priority folder, or use the Focused Inbox setting and manually mark VIP senders as 'Always move to Focused.' The VIP list should be narrow — if everyone you work with is VIP, the concept loses meaning and the filter system becomes ineffective. Revisit it quarterly: add newly critical contacts, remove those whose work relationship has changed.

Keep the label and folder hierarchy entirely flat — no nested subfolders beyond the four main categories.

Nested folder structures (Reference → Clients → Client A → 2025 → Projects → Project X) look organized but create two concrete problems: filing any email requires navigating multiple levels of hierarchy, and retrieval almost never uses the folder structure anyway — people search. Modern email search in both Gmail and Outlook indexes full message content, sender, subject, and attachments, making deep folder hierarchies obsolete as retrieval mechanisms. A flat structure with four labels is faster to file into and exactly as easy to search. When you find yourself wanting to create a subfolder, test the search alternative first: in Gmail, 'from:clientA.com label:reference' retrieves every reference email from that client without requiring a dedicated subfolder. The cognitive and time cost of maintaining a deep folder tree is real; the retrieval benefit over good search habits is near zero.

Create a 'Newsletters' filter using the list-unsubscribe header — this single filter catches virtually all bulk and marketing email automatically.

Gmail filter setup: Settings gear icon → See All Settings → Filters and Blocked Addresses → Create New Filter. In the 'Has the words' field, enter: list-unsubscribe. Set actions: 'Skip the Inbox (Archive It)' and 'Apply the label: Newsletters.' Check 'Also apply filter to matching conversations' to apply it retroactively to existing email. The list-unsubscribe header is required by law (CAN-SPAM in the US, GDPR in the EU) on all legitimate bulk and newsletter email, which means this single filter catches virtually every newsletter, marketing campaign, and subscription sender without requiring individual sender-by-sender rules. It also catches new subscriptions automatically — you don't need to add a new filter every time you sign up for something. One exception to monitor: some order confirmation emails from retail sites also include this header. If you find receipts being caught, create the Receipts filter (next item) with the action 'Never send to spam' applied first to those sender domains, which takes precedence over the newsletter filter. In Outlook, the equivalent requires creating a rule using condition 'with specific words in the message header' — enter list-unsubscribe — and the action 'move to Newsletters folder.'

Create a 'Receipts' filter to auto-sort order confirmations, invoices, and billing statements — and auto-mark them as read.

Gmail filter criteria: in the Subject field, enter: receipt OR invoice OR "order confirmation" OR "your order" OR "payment confirmation" OR "billing statement" OR "has shipped" OR "shipment notification." Set actions: skip inbox, apply label 'Receipts,' and mark as read. The mark-as-read action is deliberate — receipt emails rarely require action beyond occasional lookup, and an unread count on a receipts label creates false urgency during processing sessions. For Outlook, create a rule with 'subject contains' — each keyword added as a separate condition with 'or' logic in the rule conditions panel. Review the Receipts label monthly rather than during daily processing sessions: it functions as a searchable archive for returns, warranty claims, and expense reporting, but only if the filter is capturing correctly. Add sender-specific entries for services you purchase from regularly — for example, a filter explicitly routing from:amazon.com to Receipts as a supplemental rule — to catch any transactional emails with non-standard subject lines.

Create a 'CC — FYI' filter for emails where you appear in the CC field rather than the primary To field.

Emails where you're in CC typically require awareness rather than action — you're being kept in the loop, not asked to do something, and treating them the same as direct emails creates a volume problem. In Gmail, the filter criteria to catch emails where you're CC'd but not a primary recipient uses this in the 'Has the words' field: to:(-me) cc:(youremail@domain.com) — replace with your actual address. Apply label 'CC — FYI' and skip inbox. Also add 'mark as read' to prevent the unread count from signaling false urgency. In Outlook, create a rule with condition 'where my name is in the Cc box' plus exception 'except where my name is in the To box,' and action 'move to folder: CC — FYI.' Review this label in dedicated batches — skim subject lines for anything unexpectedly relevant — but do not feel obligated to read every threaded discussion in full. A refinement for heavy CC users: create a separate filter for your direct manager's CC'd emails that routes to inbox rather than the FYI label, since manager visibility often warrants closer attention than peer-group CC'd threads.

Create filters for automated system notifications — GitHub pull requests, Jira tickets, CI/CD build results, deployment alerts.

Automated notification emails from development and project management tools are typically high-volume and low-urgency individually: a busy GitHub organization can generate dozens of emails per day from PR comments, review requests, and CI results. Filter by sender domain or subject pattern. GitHub notification emails originate from notifications@github.com; Jira notifications from jira@[yourorganization].atlassian.net; CI/CD systems vary but typically use consistent sender domains. Apply a label per tool (label 'GitHub,' label 'Jira,' label 'Builds') and skip inbox. Review these labels in dedicated batches once per morning rather than reacting to each one individually. Critical exception: genuine on-call infrastructure alerts (PagerDuty, OpsGenie, Pingdom, Datadog) must not be routed through this filter. Those services should escalate via phone call, SMS, or app push notification — channels that can interrupt sleep and break through do-not-disturb modes. Email is a structurally unreliable channel for time-critical infrastructure alerts. If your monitoring setup currently sends alerts only by email, configure a phone escalation path before applying any email filter to those alerts — the filter will suppress their inbox visibility and the escalation ensures you're still reached.

#10

Create a calendar invitation filter to route calendar responses and event invites out of the inbox automatically.

Calendar invitation emails update your calendar when you respond (Accept/Decline/Maybe) and become clutter in the inbox thereafter — the calendar itself is the correct place to track scheduled events, not the inbox. In Gmail, use the search operator has:invite in the 'Has the words' filter field. Apply label 'Calendar' and skip inbox. In Outlook, the Rules Wizard includes a built-in condition 'which is a meeting invitation or update' — no keyword matching needed; use this native condition and move matching emails to a Calendar folder. For invitations to events more than four to six weeks away that you haven't responded to yet: consider snoosing them to one week before the event rather than archiving, so they resurface at an actionable moment. One scenario to watch: invitations from external parties whose addresses aren't in your contacts may occasionally get caught by overly broad spam filters before the calendar filter processes them — ensure your calendar filter is prioritized above spam rules in filter order.

#11

Enable keyboard shortcuts and learn the five that cover 90% of email processing: archive, delete, reply, label, and next message.

The speed difference between processing email with keyboard shortcuts versus mouse clicks is significant when compounded over thousands of emails. In Gmail: enable shortcuts via Settings → General → Keyboard shortcuts → Keyboard shortcuts on → Save Changes. Core shortcuts: e (archive), # (delete/move to trash), r (reply), l (label), j/k (move to next/previous email). With these five shortcuts, an entire processing session can be completed without touching the mouse. Gmail also supports g then i (go to inbox), g then l (go to label) for navigation. In Outlook: Delete key (delete), Backspace or period (archive/mark as done depending on configuration), r (reply), Ctrl+Shift+V (move to folder dialog). Outlook's Quick Steps feature (Home ribbon → Quick Steps → New Quick Step) allows creating single-keystroke multi-action rules — for example, a Quick Step that simultaneously labels an email 'Action Required,' moves it to the Action Required folder, and marks it as flagged with one keyboard shortcut. The learning curve for keyboard shortcuts is two to three days of conscious practice before they become automatic.

#12

Create reply templates for the 5–8 email types you send most frequently — acknowledgments, status updates, FAQ responses.

In Gmail, enable Templates via Settings gear → See All Settings → Advanced tab → Templates → Enable → Save Changes (requires a page reload). To create a template: compose a new message, write the reply text, click the three-dot menu in the compose window → Templates → Save draft as template → give it a name. To insert during a reply: three-dot menu → Templates → select template name. Templates worth creating: a 'received your message, will respond by [date]' acknowledgment for when you can't reply fully during a processing session; a standard meeting request response with your scheduling link; a 'here's the status' format with placeholder fields for your most common project update type; a polite 'please use this channel instead' response for colleagues who send email that belongs in your project management tool; and a FAQ answer for your most common inbound question. In Outlook: Insert → Quick Parts → AutoText → New Entry (or save to the Quick Part Gallery for cursor-positioned insertion). Templates don't need to be complete emails — even saving a paragraph you rewrite from memory on every similar reply saves meaningful time across a month.

#13

Use Snooze to defer emails that are correct to defer — remove them from the inbox until the moment they're actionable.

Snooze solves a specific problem that neither archiving nor labeling handles: an email that doesn't need action now but will need it at a defined future point. Without snooze, the options are leaving it in the inbox (creating visual noise and making the inbox an unreliable signal of what needs attention) or moving it to Action Required (where it may not surface at the right time without a corresponding task entry). Examples of ideal snooze use: an event invitation you can't respond to until you check a travel schedule — snooze until you'll have that information available; an email about a decision that depends on a pending outcome — snooze until that outcome is expected; a message you want to follow up on if no reply arrives by a specific day — snooze to that morning. In Gmail: hover over an email in the inbox to reveal action icons, click the clock icon, and select a preset or custom date and time. In Outlook: right-click an email → Snooze → select a time or choose 'Custom' for a specific date. Snoozed emails disappear from inbox view and reappear at the top of the inbox at the chosen time. The key mental model: snooze is for emails that are correctly deferred, not for emails you're avoiding — if you snooze the same email three times, it belongs in Action Required with a real task entry.

#14

Configure 'Send Later' for outgoing emails you draft outside business hours or want to queue for a specific delivery time.

Sending emails at 10pm or 6am implicitly signals your availability at those hours and may create expectations of similar response times from recipients. Send Later lets you write emails when you have the thought and deliver them at an appropriate time. In Gmail: compose a message, click the dropdown arrow next to the Send button → Schedule send → select a date and time or choose a suggested slot. Common patterns: write responses during an evening session but schedule delivery for 8:30am the next business morning in the recipient's time zone; batch-draft multiple emails in one sitting and spread delivery to avoid overwhelming a collaborator; queue a project follow-up for the day before a deadline. In Outlook: compose message → Options tab → Delay Delivery → check 'Do not deliver before' → set date and time → Send (the message sits in your Outbox and sends at the scheduled time; note that for traditional Exchange setups Outlook must be running, while Microsoft 365 cloud-based accounts handle scheduling server-side). In Apple Mail on macOS Ventura and later: write message → Send Later button. Scheduled send is distinct from Snooze: Snooze manages an incoming email's visibility; Send Later manages an outgoing email's delivery. Both contribute to a communication rhythm that doesn't create false urgency on either side.

#15

Schedule 2–3 fixed email processing windows per day and treat the intervals between them as email-closed — no ad-hoc checking.

The most common email system failure mode is implementing filters and folders while retaining reactive checking habits — the result is a well-organized inbox that still interrupts you throughout the day. The fix is scheduling: define specific windows when email receives focused attention (for example, 9:00am, 1:00pm, and 4:30pm) and treat those windows the same way you'd treat a meeting. Between sessions, the email client is minimized and notifications are off. A processing session is a distinct activity from a working session: during processing, you triage the inbox by deleting, archiving, labeling, or routing email to Action Required, but you do not complete the work that email has generated — that happens in separate work sessions. Processing sessions should feel fast and mechanical, not like work. Duration: 15–20 minutes per session handles moderate email volume once filters are correctly configured. If a session consistently exceeds 30 minutes, the correct response is to refine the filter system to reduce what reaches the inbox, not to extend the processing time further.

#16

Apply the two-minute rule during processing: handle any email immediately if the full response or action takes under 2 minutes; move it to Action Required if it takes longer.

David Allen's two-minute rule from Getting Things Done: if an email can be fully handled — replied to, archived, or acted on — in under 2 minutes, handle it immediately during the processing session rather than deferring it to a task list. The reasoning is efficiency: the overhead of deferring an email (adding it to a task entry, re-opening it at a later session, re-reading context, re-deciding what to do) costs more total time than just acting on it when the 2-minute threshold is genuine. The rule breaks down when applied too liberally — 'under 2 minutes' must be honestly assessed. Firing off a hasty reply to a complex question in 90 seconds because you wanted to hit the threshold is a different failure mode from the one the rule prevents. Apply it to: simple acknowledgments, quick yes/no decisions, forwarding to the correct person, or archiving purely informational emails. For anything requiring substantive thought, meaningful research, or more than two sentences: move it to Action Required and immediately create a specific next-action task in your task management system (Todoist, Things, Notion, a paper list — wherever your real work lives). The inbox is not a reliable task manager; leaving email in it as a reminder is a system design error, not a reasonable workaround.

#17

Archive the existing inbox backlog in one batch — select all emails older than 30 days and archive them together.

An inbox with thousands of accumulated emails is not just a productivity problem — it's a psychological one. The visual backlog creates a persistent background anxiety that competes with the new system's utility. The most effective reset is a mass archive: in Gmail, search for older_than:30d in:inbox, click the checkbox to select all conversations on the page, then click 'Select all conversations that match this search,' and archive. In Outlook, sort by date, select all emails older than your chosen cutoff date using shift-click, right-click → Archive. These emails are not deleted — they remain fully searchable in All Mail (Gmail) or the Archive folder (Outlook). Nothing is permanently removed; it's only removed from the inbox view. If this feels too drastic: create a folder called 'Old Inbox — [today's date]' and move everything into it as a batch — the functional outcome is identical (a clean inbox) with a slightly more cautious framing. The clean inbox is not a permanent achievement; it is a starting condition. The habits and filters in this checklist are what keep it clean going forward. Without the habit changes, a clean inbox returns to its previous state within two to four weeks.

#18

Schedule a 15-minute monthly filter audit to prevent system drift — review each label for misclassified email and update your VIP list.

Email systems that aren't periodically reviewed degrade over time as new subscription sources emerge, professional relationships change, and notification patterns from tools shift. A monthly audit prevents silent drift. Review agenda: check the Newsletters label for any legitimate contacts whose email was incorrectly caught — add exceptions to the filter if needed; check the Receipts label to confirm all relevant receipt formats from your regular vendors are being captured; scan the CC — FYI label for email that should have reached the inbox directly; review the VIP list to add newly critical contacts and remove those whose priority has changed. Separate from this audit: if you're consistently missing emails that matter, that's a filter specificity problem — increase the specificity of the offending filter rather than removing it. Duration: 15 minutes, once per month. Schedule this as a recurring calendar event to prevent it from being indefinitely deferred — it's easy to postpone 'system maintenance' work until the system has fully degraded.

#19

🧮 What reactive email is actually costing you

McKinsey Global Institute research found that knowledge workers spend roughly 28% of their workweek on email — approximately 11 hours in a standard 40-hour week. At that rate, a single employee processes the equivalent of 14 full workweeks of email per year. The majority of that time isn't spent on high-value communication; it's spent triaging, re-reading previously seen emails to remember context, deciding what to do with items that have been deferred multiple times, and hunting through unstructured inboxes for things that were never filed.

40 hrs/week × 28% = 11.2 hrs on email per week

11.2 hrs × 50 working weeks = 560 hrs/year

At $40/hr fully-loaded cost = ~$22,400/person/year in email overhead

The two-hour setup investment described in this checklist is recovered within a single working day of using the system.

⚠️ The full inbox as identity

Organizational behavior researchers have documented a pattern called "busyness performance" — using visible signs of overwhelm as a proxy signal for importance and demand. A visibly full, churning inbox can read as evidence that you are needed. People who resist inbox management systems are often not resisting the logic; they're resisting what an empty inbox might signal about them. Identifying this as a cognitive pattern rather than a practical concern is often the actual prerequisite for changing it.

💡 What an empty inbox actually communicates

An inbox maintained at zero does not suggest low demand — it signals controlled demand. Senior executives, who typically receive significantly more email than their direct reports, are disproportionately likely to maintain strict inbox discipline. An empty inbox is not a signal of irrelevance. It is the operational signature of someone who has separated the communication channel from the task system and operates both intentionally.

🔧 Reducing volume at the source — channel selection

The most sustainable email volume reduction isn't a filter — it's a personal or team commitment to not sending email that shouldn't be email. Most inboxes are significantly inflated by communication that arrived in the wrong channel.

Situation	Right channel	Why email fails here
Quick yes/no question to a colleague	Slack, Teams, or IM	Creates inbox noise for both parties; async overhead is unnecessary for a one-word answer
Infrastructure incident or on-call page	PagerDuty, SMS, or phone call	Email is structurally too slow and too easily filtered for time-critical signals
Ongoing project discussion involving multiple stakeholders	Linear, Notion, Basecamp, or Confluence	Email threads lose full context for new joiners and can't be searchably linked to tasks
Sharing a document for review or collaborative editing	Google Drive, Notion, or a shared link	Attachments create version conflicts and generate inbox entries for every revision
✅ Formal external communication, legal or financial records, decisions requiring a written trail	Email	Email is correct here — universal, auditable, expected by external parties, and legally defensible

🚨 Three ways maintained email systems break down

Most email systems work well in the first two weeks and quietly degrade over the following months. The failure modes are consistent across different types of users:

1. VIP list inflation

Every new contact gets added to the VIP allowlist "just to be safe," until the list contains fifty people and the inbox is functionally unfiltered again. The VIP list should contain only people whose email requires same-session attention — not everyone who emails you. The test is simple: if their email can comfortably wait until a scheduled processing window, they do not qualify as VIP. Review the list quarterly and remove contacts who no longer meet that standard.

2. Session creep

Three daily processing windows become four. "Just a quick check" between sessions becomes habitual. Within two weeks, reactive checking is fully restored. This pattern typically starts during a high-demand period — a launch, a difficult client situation, a deadline sprint. The correct response to temporarily higher email volume is longer processing sessions, not more frequent ones. Frequency increases compound the very interruption cost the system was built to reduce; length increases don't.

3. Inbox-as-task-list relapse

Emails start staying in the inbox as visual reminders: "I'll leave it here so I see it." This feels reasonable for about three days, after which the inbox is a task list again and the whole system has collapsed. The Action Required folder only functions as intended when paired with a real external task manager. The inbox is a communication processing queue — not a place for work to live. Emails left as proxies for tasks get re-read, re-deferred, and eventually missed.

📖 The $8,000 subject line that looked like everything else

A freelance designer with approximately 4,200 unread emails received a new client inquiry — a logo and brand identity project worth around $8,000. The email arrived on a Tuesday with the subject line "Quick question about a logo project." By the following Friday, the client had hired someone else and cited the non-response as the reason. The designer found the email weeks later while searching for something unrelated — still unread, sitting between a promotional offer from a software vendor and an automated shipping notification. The subject line was indistinguishable from the noise around it. The initial setup described in this checklist takes roughly two hours. The cost of not having it, in this case, was concrete and permanent: the client became a long-term repeat buyer for the designer who responded promptly.

✅ Managing the transition with contacts who expect fast replies

Switching from reactive to scheduled email monitoring will change your visible response patterns, and some contacts will notice the shift. A brief, transparent communication prevents misunderstanding: an email signature note or auto-responder stating your check times and providing a phone number for urgent matters — "I process email at 9am, 1pm, and 4pm on weekdays. For anything urgent, text [number]" — sets accurate expectations and provides a genuine escalation path.

Most contacts adapt within a day or two. A small number will actually use the phone number — and when they do, you'll quickly discover whether their urgencies are genuine or whether they were simply accustomed to treating email as a real-time channel. The ones with real urgency will appreciate having a reliable path that reaches you. The ones who don't have real urgency will adjust their expectations.

Master This Checklist Quickly

Every important button and option for this pre-made checklist, shown in a glance-friendly format.

Start Here

1
Click any item row to mark it complete.
2
Use the note row under each item for quick notes.
3
Use the tool row for undo, redo, reset, and check all.
4
Use Save Progress when you want to continue later.

Checklist Row Tools

UndoRedoResetCheck allCollapse/Expand sectionsShow/Hide detailsInline notes

Top Action Buttons

Open all sharing and export options in one menu.

Email DraftContinue on another devicePrint or Save as PDFPlain Text (.txt)Word (.docx)Excel (.xlsx)

Add & Ask

Open one menu for apps and AI guidance.

NotionTodoist CSVChatGPTClaude

Copy and customize

Create a new editable checklist pre-filled with your chosen content.

Save Progress

Adds this checklist to My Checklists and keeps your progress in this browser.

Most Natural Usage

Track over time

Check items -> Add notes where needed -> Save Progress

Send or export

Open Share -> Choose format -> Continue

Make your own version

Copy and customize -> Open create page -> Edit freely

Email Management System Setup

Checklist Items

Phase 1 — Reduce Incoming Volume First

Phase 2 — Build Your Folder and Label Structure

Phase 3 — Configure Automatic Filters

Phase 4 — Enable Power Features

Phase 5 — The Processing System and Clearing the Backlog