Best Practices

What separates teams that get value from Intelligence from teams that stall.

Treat coverage as the foundation

Analysis cannot recover an observation that was never captured. When a result looks wrong, check coverage before questioning the analysis. Work the coverage cards on the Intelligence hub until each one is resolved rather than leaving them at needs confirmation indefinitely.

Keep profiles honest and current

Answer the interview as the operation actually runs today.
Republish when your role, sites or commercial terms change. A detention rate with a stale effective date quietly misleads.
Give the assistant any terminology or response-style instructions it needs in the conversation or its own settings. The SiteTrax.io public profile tool returns selected published facts and priorities, not your saved working brief, custom instructions or response-style preferences.

Ask precisely

Name SiteTrax.io, the site, the period and the asset type. Most disappointing answers are underspecified questions rather than product limitations.

Verify anything that will be acted on

Before a charge is disputed, an invoice paid or a number published, open the underlying record and look at the image. The evidence trail is the reason to use SiteTrax.io rather than an estimate, so use it.

Use the language precisely

Say	Not
No observation of the unit in that period	The unit was not there
The reading could not be resolved	The container is damaged
The observed interval was 52 hours	The unit was delayed 52 hours
Stored readings	Units, when counting records

Give feedback on bad reads

Mark records correct or incorrect from the detail page. It takes a moment and it is the mechanism by which capture quality problems become visible.

Keep access tight

Review project users quarterly, including service accounts.
Grant the notifications write scope only to create or cancel supported alerts and digests. Listing them and reading delivery history needs only read access.
Never put passwords or tokens in a prompt or a support email. Query results are shared with the assistant provider you choose; review your organization’s data-handling requirements. See Account Access and OAuth.
Before connecting an assistant, confirm the intended account in the SiteTrax.io application and finish email verification. Use the account that holds the relevant project access and, if wanted, the published profile. After OAuth approval, ask the assistant to list your projects.