Docs/Projects/Edit a project
Projects

Edit a project

Projects should be updated as relationships develop. Editing a project keeps the workspace accurate and makes sure the rest of the team can rely on what they see.

When to edit a project

You should update a project when:

  • contact details change
  • a manager is reassigned
  • outreach status changes
  • the ecosystem or category needs correction
  • follow-up timing changes
  • new notes need to be added
  • public links need updating

What can be updated

Common project updates include:

  • name
  • category
  • ecosystem
  • website
  • X / Twitter
  • Discord
  • Telegram
  • contact name
  • contact handles
  • status
  • priority
  • assigned manager
  • notes summary
  • next follow-up date

Why regular editing matters

A project that is never updated quickly becomes misleading. That creates problems for:

  • reporting
  • handoffs
  • team visibility
  • manager accountability
  • follow-up quality

Good editing habits

Update a project after:

  • important conversations
  • new contact information
  • status movement
  • internal reassignment
  • a decision to revisit later

💡Best practices

  • keep project records fresh
  • remove outdated assumptions
  • update notes after meaningful progress
  • treat the project as a living record, not a one-time entry