Event naming patterns for easier filtering

Bulk cleanup quality depends on naming quality. If titles are inconsistent, your filters will always be fragile.

Design principles for event names

1. Put stable identifiers first.
2. Keep variable details later in the title.
3. Encode intent, not just topic.

Recommended title schema

[Group] [Type] - [Outcome]

Examples:

• [Sales] Pipeline - Weekly forecast
• [Eng] Incident - Postmortem actions
• [Personal] Admin - Tax documents

Why prefixes matter

Prefix-first names let you run precise filters like:

• all [Eng] meetings
• all [Personal] Admin blocks
• all - Postmortem outcomes

Anti-patterns to remove

• Generic placeholders (meeting, sync, review)
• Emojis as the only classifier
• Inconsistent abbreviations across teams

Pattern library starter

Category	Prefix	Example
Team cadence	[Team]	[Product] Weekly - Priorities
Decision forums	[Decision]	[Decision] Pricing - Approve model
Deep work	[Focus]	[Focus] Writing - Draft v1
Personal admin	[Admin]	[Admin] Insurance - Renewal

Migration strategy

Do not rename everything at once.

• Start with new events this week.
• Rename only recurring series older than 30 days.
• Review filter quality after two weeks.

A small naming system gives you cleaner analytics, faster search, and safer bulk deletion.