Skip to content

afeezadebayo/email-inbox-skills / email-system-audit

email-system-audit

Verified

Audit how a person or small team uses email: volume by source, time and checking habits, triage, structure, response targets, writing, follow-ups, templates, team norms and security scored 0 to 3, then a simple email system, team norms and a four-week rollout with measures to check. Use whenever email takes over the day, the inbox feels out of control, someone starts a new role, a team wants better email habits or before setting up an AI email assistant.

Email System Audit

Email problems rarely come from one bad habit. They come from a system nobody designed: notifications on for everything, dozens of newsletters, folders nobody uses, colleagues copying everyone, no rule for response times and an inbox checked fifty times a day. Each part costs a few minutes; together they cost hours a week and much of the person's focus.

This skill audits how a person or small team uses email, measures where time goes, finds the few changes with the biggest effect and builds a simple email system: rules, filters, a triage rhythm, response targets, templates and team norms. It is the entry point for the Email and Inbox set.

Operating principles

  1. Measure before changing. Volume, sources and time spent show where the real problem sits.
  2. Fix the source, not the symptom. Unsubscribing and team norms beat faster reading.
  3. Few moving parts. A handful of categories, filters and routines the person will keep.
  4. Protect focus. Email should fit into set sessions, not interrupt every hour.
  5. Keep people informed. Clear response targets make batching safe.

Audit areas

AreaWhat to checkTypical finding
Volume and sourcesEmails a day by type: people, notifications, newsletters, internal listsOver half is automated or bulk mail
Checking habitsHow often the inbox is opened; notifications on or offChecked constantly; alerts for every message
TriageHow messages get decisionsMessages read several times before action
StructureFolders, labels, filtersMany folders, few used; no filters
Response timesExpectations by sender typeNo targets; anxiety about slow replies
WritingLength and clarity of sent emailsLong emails, unclear asks
Follow-upsHow promises and waiting items are trackedRelies on memory; things slip
TemplatesRepeated repliesSame answers rewritten weekly
Team normsCc habits, reply-all, chat versus emailEveryone copied; urgent issues by email
SecurityPhishing awareness, two-step loginPayment change requests not verified

When to use, and when not to

Use it when email takes too much of the day, the inbox feels out of control, a person starts a new role, a team wants better email habits, or before setting up an AI email assistant.

Don't use it to sort today's inbox (inbox-triage) or to write a specific reply (email-reply-drafting).

Inputs to ask for, in one message

  1. Role and the people the person most needs to hear from.
  2. Rough daily volume, or access to count a typical week.
  3. Current folders, labels and filters.
  4. Notification settings on desktop and phone.
  5. What feels most broken.
  6. For teams: how email, chat and meetings are used.

Workflow

Step 1. Count a typical week

Group messages by source: named people, internal lists, notifications from tools, newsletters and promotions, external requests. Note which sources lead to action.

Step 2. Estimate time

Time in the inbox per day, how many sessions, and time on replies versus reading.

Step 3. Score each area

Score 0 to 3 with one line of evidence each.

Step 4. Find the top leaks

Usually: too much bulk mail, constant checking, no follow-up tracking, or team habits that create mail.

Step 5. Design the system

  • Triage two to four times a day with the six triage categories.
  • Filters that move bulk mail and notifications out of the main inbox.
  • Response targets by sender type.
  • A waiting-for list for follow-ups.
  • Templates for the five most repeated replies.
  • Notifications off except for priority senders.

Step 6. Agree team norms (if relevant)

When to use email versus chat versus a call, Cc and reply-all rules, subject line conventions, and the route for urgent issues.

Step 7. Roll out gradually

Week one: filters and unsubscribing. Week two: triage rhythm and notifications. Week three: templates and follow-up tracking. Week four: team norms.

Step 8. Measure again

After a month, compare volume, time in the inbox and missed follow-ups.

Scorecard template

| Area | Score (0-3) | Evidence | Fix | Skill |
| Volume | 1 | 62% bulk mail | Unsubscribe and filter | newsletter-cleanup, inbox-rules-filters |
| Follow-ups | 0 | Two missed client replies | Waiting-for list | follow-up-tracking |

Response targets example

SenderTarget
Key clients and managerSame working day
TeamWithin 24 hours
External requestsWithin 3 working days
Newsletters and notificationsNo reply needed

Team email norms example

  • Email for decisions and external contact; chat for quick questions; calls for anything urgent or sensitive.
  • Cc only people who need to act or must know; say why in the first line.
  • Reply-all only when everyone needs the answer.
  • Subject lines start with the action and date when one is needed.
  • No expectation of replies outside working hours.

Measures to track

MeasureWhy
Emails a day reaching the main inboxVolume after filters
Inbox sessions a day and minutes per sessionChecking habits
Median reply time to priority sendersResponsiveness
Missed follow-ups a monthReliability
Bulk senders unsubscribedSource reduction
Record a baseline before changes and compare after four weeks.

Quick wins in the first hour

Turn off new-mail notifications, unsubscribe from the ten noisiest senders, create one filter for tool notifications, and book three daily triage slots in the calendar.

Edge cases and judgement calls

SituationWhat to do
Role is mostly email (support, sales)Shorter triage cycles; strong templates; shared inbox rules
Executive with assistantDelegation rules and a daily brief
Heavy regulatory record-keepingKeep archiving and retention rules; never auto-delete
Several accountsOne triage session covering all, or forwarding to one inbox
Team resists normsTrial for four weeks and review the results together

Handoffs to specialist skills

  • Daily sorting: inbox-triage
  • Replies: email-reply-drafting
  • Follow-ups: follow-up-tracking
  • Filters: inbox-rules-filters
  • Subscriptions: newsletter-cleanup
  • Repeated replies: email-templates
  • Hard messages: difficult-emails
  • Clearer emails: email-writing-clarity
  • Phishing and fraud: email-security

Worked example

A sales manager received about 180 emails a day and spent close to three hours in the inbox. The audit found 58% bulk and tool notifications, the inbox open almost all day, no filters and two missed client follow-ups in a month. The plan unsubscribed from 40 senders, filtered tool notifications into a weekly digest folder, set three triage sessions, turned off notifications except for key clients, added a waiting-for list and five reply templates, and agreed Cc rules with the team. A month later, daily volume in the main inbox had fallen by more than half, inbox time was about an hour, and no client follow-ups were missed.

Output format

# Email audit: <person or team>, <date>
## Summary (top leaks and first moves)
## Volume and sources
## Time and checking habits
## Scorecard
## Email system (triage rhythm, filters, targets, templates, follow-ups)
## Team norms (if relevant)
## Four-week rollout
## Measures to check after a month

Common mistakes

  • Reading faster instead of reducing volume.
  • Folders for everything.
  • Notifications on for all mail.
  • No response targets, so batching feels risky.
  • Ignoring team habits that create mail.

Self-check before you answer

  • Is volume measured by source?
  • Are the top two or three leaks fixed first?
  • Is the system simple enough to keep?
  • Is there a measure to check after a month?

Created by Afeez Adebayo, Marketing, SEO & Growth Expert Website: https://afeezadebayo.com LinkedIn: https://www.linkedin.com/in/afeez-adebayo/ X: https://x.com/za_icon Source: https://afeezadebayo.com/skills-md/productivity/email-inbox/email-system-audit/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall