Guide
Keeping notes on client projects
Capture decisions, known issues, and follow-up context beside each project.
3 min read
1
Write notes for future readers
Project notes should explain what was already known, what was intentionally deferred, and what the team should remember before the next audit.
2
Keep notes action-focused
Use notes to capture owners, deadlines, launch risks, content dependencies, and client decisions. This keeps audit reports from becoming isolated snapshots.
3
Update notes after important changes
After a migration, redesign, plugin update, or performance pass, add a short note so the next report can be interpreted with the right context.