The 30-day baseline
During baseline setup, Tend uses read-only telemetry permissions to read 30 days of history that already exists in BigQuery. BigQuery retains up to 180 days of job history inINFORMATION_SCHEMA. Tend reads the project-scoped JOBS orJOBS_BY_PROJECT views and, when configured at organization scope,JOBS_BY_ORGANIZATION. BigQuery requires each view query to include its region qualifier. See Google's BigQuery JOBS view documentation. If you export billing data to BigQuery, Tend also reads that export for billed reservation spend. Tend uses those sources to build a per-day reference curve. The curve is a baseline for comparison, not proof of what spend would have been without Tend. It does not isolate changes in workload mix, demand, pricing, commitments, or unrelated warehouse configuration.
What you can count as saved
Tend logs every reservation-ceiling change with a before value and an after value. The dashboard reports the reservation-spend delta observed after the change against the defined baseline. Today, reservation changes made by the agents are the only source in that total. Review the activity log with the preceding workload and pricing limitations before attributing the full delta to Tend.
BI Engine agent deltas appear as a separate line item after you enable that agent. For each agent's scope, see How each agent works.
Why you can audit the total
Every change appears as a row in your activity log. The row shows which agent made the change, what the agent changed, the value before the change, the value after the change, and a control to roll back the change. If you add those rows, you get the savings total. Tend does not hide any value in a rollup.
The 90-day guarantee
For customers with a signed agreement, Clevora refunds the first-quarter subscription fee when measured savings are less than 3 times the monthly Tend fee within 90 days after go-live. See Terms and Pricing.