> For the complete documentation index, see [llms.txt](https://help.runonrufus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.runonrufus.com/rufus-cloud/race-app/team-chat.md).

# Team Chat

The **Team Chat** view provides a shared event communication room between judges and Race Control.

It is designed for operational coordination during race day.

<figure><img src="https://3240794926-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1sZIrkMlXm95ujcqAqfj%2Fuploads%2FL7fo73lYeqMtOYNqlDKo%2FWhatsApp%20Image%202026-03-03%20at%2022.08.50.jpeg?alt=media&amp;token=4eb26670-0add-4e9f-a6ef-6e8d885008ef" alt="" width="360"><figcaption><p>Team Chat Screen</p></figcaption></figure>

## What Team Chat Does

Team Chat allows real-time messaging between:

* Judges using the Race App
* Race Control inside Race Manager

It is separate from Live Activity and maintains its own message feed.

## Chat Behavior

Team Chat:

* Polls periodically for updates
* Refreshes immediately when focused
* Updates instantly after sending a message
* Persists across judge logins using the same token

If a judge logs out and another logs in with the same token:

* Chat history remains available.

## Sending Messages

Messages should be:

* Short
* Clear
* Operational

Example:

* “First woman approaching finish.”
* “Bib 245 collapsed near km 3.”
* “Checkpoint water running low.”

Avoid long explanations. Use Race Alerts for formal reporting.

## Operational Best Practices

* Mention checkpoint context when multiple checkpoints are assigned.
* Use precise language (what / where / when).
* Keep communication concise.
* Do not rely on Chat for classification decisions — use Penalty & Bonus instead.

## Summary

Team Chat enables fast, informal coordination between judges and Race Control, complementing structured tools like Race Alerts and Penalty & Bonus.