Task Naming Conventions

To keep our task timeline scannable, we use a [Category] - [Brief Description] format. This allows anyone to glance at the Org record and understand the history without clicking into every task.

1. Past Interactions (The Paper Trail)

For tasks that record what has already happened, lead with the medium or action.

• Format: "[Medium] - [Subject/Purpose]"

• Examples:
  

• Email - Sent initial discovery deck
  

• Text - Confirmed arrival for site visit
  

• Research - Reviewed LinkedIn/Company website for Q3 goals
  

• Internal - Drafted project scope for approval
  

2. Present/Future Actions (The To-Do List)

For tasks that need to be completed, lead with a "Verb" to indicate action is required.

• Format: "[Action] - [Specific Deliverable] - [Deadline/Priority]"

• Examples:
  

• Follow up - Email regarding draft contract 
  

• Send - Revised pricing suggestions
  

• Schedule - Client sync regarding Job Report
  

Best Practices for Scannability

✅ Do: Be Specific

• Bad: "Follow up"
  

• Good: "Follow up - Call Sarah re: Business Insurance renewal"
  

• Why? It saves the next person from having to dig through notes to see what the follow-up was about.
  

❌ Don't: Use Vague Verbs

• Avoid: "Check in", "Touch base", "Update"

• Use: "Confirm", "Request", "Deliver", "Verify"
  

💡 The "One-Second Rule"

If a techtown team member or fellow coach looks at the Task Timeline, they should be able to understand the last three things that happened in under one second just by reading the task titles.

Comparison of Clean vs. Messy Task Titles