> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/collaboration-and-automation/team-communication-tips.md).

# Team Communication Tips

### Overview

Communication patterns determine whether decisions remain retrievable.

These tips support scale across Organizations and Projects.

### Key Concepts

* **Decision pattern**: consistent formatting used for approvals and rationale
* **Thread hygiene**: keeping comments short, scoped, and linked
* **Signal vs noise**: minimizing non-action messages

### How It’s Used

Use these patterns during delivery and governance.

Use them during onboarding to establish consistent expectations.

### Benefits

* Faster reviews and approvals
* Cleaner audit trail for decisions
* Less repeated discussion during handoffs

### Setup Steps

{% stepper %}
{% step %}

### Adopt a decision format

Use a consistent pattern, such as:

* `Decision:`
* `Approved by:`
* `Date:`
* `Scope:`
  {% endstep %}

{% step %}

### Keep comments scoped

1. Ask one question per comment.
2. Reference the exact item field or acceptance criteria under discussion.
3. Link related items instead of copying long text.
   {% endstep %}

{% step %}

### Close the loop

After a decision, add a single summary comment that includes rationale.
{% endstep %}
{% endstepper %}

### Best Practices

* Prefer links to source items for traceability.
* Avoid mass @mentions. Use @mentions for action-required requests.
* Summarize meeting outcomes in one comment and link the meeting record.

### Summary

Communication patterns should optimize for searchability and auditability.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/collaboration-and-automation/team-communication-tips.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.