Project Tracker Templates
Single source of truth for initiatives, goals, and partnerships.
Why Use a Tracker?
A good tracker keeps everyone aligned without constant status meetings. It should:
- Be the single source of truth for the initiative
- Capture decisions (so you don't relitigate them)
- Track action items with owners and dates
- Store meeting notes in context (not scattered across docs)
Template Structure
1. Overview Section
Objective: One sentence describing what success looks like.
Goals/Milestones Table:
| Goal | Status | Due | Owner | Updates |
|---|
| Green/Yellow/Red | | | |
2. Document Directory
Links to all relevant docs: PRFAQs, specs, designs, meeting recordings, related projects.
Pro tip: Create a shared folder and link to it rather than individual docs.
3. Decision Log
| Decision | Date | Context | Who Decided |
|---|
| | | |
Capture decisions explicitly. Future you (and new team members) will thank you.
4. Open Questions
| Question | Raised By | Status | Owner | Due |
|---|
| | | | |
5. Action Items
| Item | Status | Due | Owner | Updates |
|---|
| | | | |
6. Meeting Log
## [Date] - [Meeting Title]
**Objective:**
**Attendees:**
### Agenda
1. ...
### Notes
1. ...
### Action Items
1. [Action] (Owner: X, Due: Y)
Best Practices
- Update regularly - stale trackers lose trust
- Decisions stay decided - reference the decision log when topics resurface
- Notes go in the tracker - not in separate docs or Slack threads
- One tracker per initiative - don't split across multiple docs
- Keep it scannable - executives should grok status in 30 seconds
Anti-Patterns
- The graveyard tracker - created once, never updated
- The meeting minutes dump - pages of notes, no structure
- The everything tracker - too many initiatives, loses focus
- The duplicate tracker - same info in multiple places
A tracker is a tool, not a deliverable. If maintaining it takes more time than it saves, simplify.