Give the team a common source to work from
Give recurring knowledge an owner, a source and a clear rule for when it should be used.
Make the authoritative source easy to identify
Teams need to know which product facts, policies and voice guidance apply. Name an owner for each durable source and record when it should be reviewed. Keep customer-specific material separate from reusable organizational context.
| Context | Maintenance decision |
|---|---|
| Product facts | Who approves changes and availability claims? |
| Policy | Which version applies to this audience and date? |
| Brand voice | Which examples show style without supplying new facts? |
| Customer material | Who may access it and when should it be removed? |
Write a context-use agreement
The agreement belongs with the source collection and should be understandable without knowing the original conversation.
Use the approved product sheet for factual claims and the writing guide for tone. If a customer-specific document contradicts the product sheet, surface the conflict to its owner instead of overwriting the shared facts. Keep customer details within the current task. Before sending external copy, confirm that availability, pricing and commitments have an authoritative source.
A shared workflow does not replace access controls
Instructions about confidentiality are not technical permission boundaries. Use the actual account and workspace controls, verify supported sharing behavior and review any external destination before moving information.
Common questions
Should every teammate use the same prompt?
Use a reviewed starting workflow and authoritative context, then adapt the task-specific details. Different audiences or decisions may require different instructions.
Sources and review
Reviewed