Metrics, baselines, and readings
Metrics, baselines, readings, assumptions and value formulas: how Roiva calculates value, and what to record next.
Answered from these docs only, by a model that cannot see your account. Check the pages it cites.
Checked against the product on September 19, 2026
Roiva calculates value by comparing what things were like before an initiative with what they're like now. Four pieces make that work, and each has a tab under Measurement in the sidebar.
Metrics
A metric is something you measure: tickets resolved, average handle time, won deals, tokens used. Each has a type (count, sum, average, ratio, percentage, currency, duration or score) and a unit. The Metrics tab opens on In Use, the metrics your initiatives hold figures for and your formulas read or produce, once there are any. Library lists every metric you can use, Roiva's and your own, and New Metric adds your own.
Metric entries: baselines and readings
A metric entry is one value of a metric for a period. Two kinds matter:
- A baseline is the before-value: what the metric was before the initiative started.
- A reading is a value after it: this month's handle time, say.
Metric entries come from connected integrations, from value formulas, from CSV import (Entries → Metric Entries → Import, which takes baselines too) or by hand.
A metric entry is called an observation in the API, in the MCP tools and in the columns of the CSV export and import. It is the same record under the engine's own name.
Baselines mostly fill themselves in. When your connected systems have figures for the three complete months before an initiative started, or for any of them, Roiva calculates the baseline from them. Otherwise Roiva may hold an estimate, and replaces it with a baseline from your history if those months sync in or are imported later. A baseline you enter or import yourself is never overwritten.
Assumptions
An assumption is a figure a formula takes as given: a loaded labor rate, minutes saved per automation run, a price per million tokens. Roiva ships a default for most, usually with its source, and the Assumptions tab is where you confirm or change them. While a formula runs on a Roiva default, the value it calculates is held for review.
Value formulas
A value formula is the arithmetic that turns readings, baselines and assumptions into value entries: for example, (tickets handled) × (hours to first response before − hours now) × (labor rate). The Value Formulas tab lists them, and each shows its inputs and what it calculated. A calculated value entry's Formula Inputs section shows the arithmetic behind that one entry. See How Roiva calculates value.
What to record next
- The Missing Inputs page lists the figures formulas are waiting on, and you can enter them there. Some say where to find the figure.
- The Inbox lists every figure your active initiatives need from a person — a missing baseline, an after-value to compare with one, or a figure due to be measured again — each with the form that records it.
- Each initiative's Setup tab lists what that one initiative still needs.
When a measurement falls due, your Inbox carries a row for it with the form that records it. See What an initiative needs before it has a number.