Assign a manager
if needed.
- 9.Add a follow-up date or notes.
- 10.Save the project.
Key fields to complete
While many fields may be optional, these are the most useful to fill in first:
- project name
- ecosystem
- status
- priority
- assigned manager
- next follow-up
- contact name or handle
Recommended naming style
Use the public or commonly known name of the project. Good examples:
- Azura
- Moongrid
- Nova Labs
- Vertex DAO
Avoid vague names like:
- new partner
- outreach target
- WL project
What to add if you have it
If available, add:
- website
- X / Twitter
- Discord
- Telegram
- contact handle
- short internal notes
This makes the project more useful for the whole team.
Why completeness matters
A strong project record makes it easier for:
- managers to take over if needed
- leads to understand context quickly
- founders or owners to see current progress
- the team to follow up consistently
💡Best practices
- create the project as soon as it becomes a real target
- don’t wait until a deal is active
- fill in enough detail so another team member could understand it
- use notes for useful context, not long essays
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
Assign a manager
Assigning a manager gives one team member clear ownership over a project. This is one of the most important steps for accountability inside CollabOS.
Why assign a manager
Without clear ownership, projects often become passive or inconsistent. Assigning a manager helps:
- define responsibility
- reduce confusion
- improve follow-up consistency
- make reporting more meaningful
- create stronger accountability across the team
What assignment means
When a manager is assigned to a project, that usually means they are responsible for:
- moving outreach forward
- maintaining relationship context
- updating the project
- managing related deals
- keeping follow-ups current
When to assign a manager
Assign a manager when:
- a project becomes active enough to need ownership
- one operator is clearly leading the relationship
- a handoff needs to happen
- leadership wants accountability on the project
Reassigning a manager
Sometimes a project needs to be moved to another team member. This may happen because:
- workload changes
- team structure changes
- a manager leaves the workspace
- the relationship fits another operator better
When reassigning, make sure the project notes are updated so the new manager has context.
💡Best practices
- assign one clear primary owner
- don’t leave important projects unassigned
- update assignment quickly if responsibility changes
- combine assignment with notes and next follow-up timing