Keep a conversation connected to the work
Return to the same portfolio or project context when a conversation continues.
Keep decisions in the project thread
Use the linked conversation to discuss scope, dates, deliverables, locations, usage, access and changes. Start from the relevant portfolio or brief so the other person can see the context you mean. Avoid putting passwords, card numbers, bank details or unnecessary identity documents in chat.
When a message changes binding terms, move that change into a new Agreement version or amendment. Keep the explanation in chat and the decision in the structured record so delivery has one source to consult.
- Name the project and the decision in each change.
- Check names, dates, numbers and promises before sending.
- Keep confidential material to the smallest audience.
Use drafts and AI carefully
A failed send should retain a clear draft or retry path when the interface provides one. Re-read before resending so a duplicate does not create confusion. If an optional AI suggestion is available, treat it as a draft that requires explicit consent and human review.
Check tone, names, dates, numbers, scope and promises. AI does not know your permission or the full project context, and no suggestion should be sent automatically or treated as a decision.
Use safety controls when needed
Report suspicious or unsafe behavior with enough context to understand the concern and block new contact when you need distance. A block changes contact behavior; it does not erase an accepted Agreement or the project history participants need to inspect.
If a project cannot continue safely, pause the work and use its issue control. Describe what happened, what is affected and the resolution you are requesting. Keep messages and evidence in the project context so the participants can understand the concern without exposing it to an unrelated audience.