Approving value and initiatives
What needs approval, where approvals wait, who can approve, approval chains, delegation and the approval settings.
Answered from these docs only, by a model that cannot see your account. Check the pages it cites.
Checked against the product on November 9, 2026
Two things in Roiva need a person's sign-off: an initiative moving from review into implementation (an implementation approval), and every value entry before it counts toward cash value or freed capacity (a value claim). Costs don't need approving.
Where approvals wait
Inbox in the sidebar lists everything waiting on you, with a count beside it. Its Open tab is what you can decide now: each row carries Approve, and ticking several approves them together. If a row changes after the page loads (its figure is recalculated or retyped, say), it isn't approved with the rest, and the Inbox asks you to reload and review it again. Snoozed is what you have put off, and Done is what you have already dealt with.
Every approval decision already made is in the Approval Register under ROI → Reports: the figure, the approver and the outcome as it stood at the time.
Where the account requires sign-offs before approval, such as a privacy or workforce impact review, the final approval waits until each is signed off or waived. See Required sign-offs before approval.
Approving an implementation approval moves the initiative to Implementing, or, with an approval chain, on to the chain's next step until the last one approves. The final approval also sets the initiative's budget from the CapEx and OpEx in its business case. A Budget increase row is a revision that raised a budget above the senior approval threshold, or raised it at all when no threshold is set, which only an Owner can approve. See Budgets and budget vs. actual.
Approving a value claim adds its amount to cash value or freed capacity, whichever its type is, where it appears on the ROI dashboard, in board reports and in exports. Capacity realized as cash can be approved only up to the initiative's freed capacity approved for its month, less what's already been realized, and only with a document cited.
Dispute sends a value entry back and tells whoever recorded it, or the initiative's owner for an entry a formula or an integration worked out; it can then be changed and sent again with Submit for review. Only an entry waiting for approval can be disputed.
To challenge an approved one, either edit it, or choose Send Back for Review on it (in its row menu on the initiative's Value tab, or on its page or side panel) and say why. Either way it goes back to the approvers and isn't in cash value, freed capacity or ROI until it's approved again. A send-back appears in the Approval Register as Sent back, with the reason under it.
Which value entries wait for approval
- Entries an integration works out go straight to approvers. So do a value formula's, once the month they're for has ended. Until then a formula's figure is the month so far, so nobody can approve it, by hand or by auto-approve, and it isn't in the Inbox. Its page says Month still running and the day it can be approved.
- Value logged by hand, or by the Assistant, starts as a draft. A draft, or an entry an approver disputed, waits until someone chooses Submit for review on it. Its status then reads Submitted until an approver approves or disputes it. An entry a formula or an integration worked out, waiting on an approver, reads Calculated. An entry the Assistant drafted says so, on its page and on its row in the Inbox, and its page also says when someone has since edited it by hand. One it drafted before Roiva marked them, and approved in a month that has since been locked, still reads as entered by hand, since a locked month's figures don't change.
An entry a formula or a sync worked out says what it rests on that you should know before it counts. Its row in the Inbox names any figure Roiva supplied in place of yours (a default assumption such as the labor rate, a baseline Roiva estimated, a help desk's default deflection price or recontact window), and anything else worth a look:
- a figure carried forward from an earlier month
- a time study's figure past its re-study date (Re-study due)
- a unit that changed from the baseline's
- a figure dated after the month it priced
- a share you credited to the initiative
- a saving credited to another initiative's cost and left out here (it says how much and where, and an approval of one that adds nothing says it records the month at $0)
- the share of an IT incident's time its users were blocked (Blocked share)
- a figure converted to dollars at the European Central Bank's latest rate while its month's rates aren't all published (Provisional rate)
- a figure that left out a currency the ECB publishes no rate for (No ECB rate)
Its page marks each of those inputs, and the Approve confirmation names Roiva's figures again. Approving a selection together says how many of them rest on Roiva's figures.
ROI → Provisional lists those figures, the one the most waiting value rests on first, each with a link to confirm or replace it. The Inbox asks too, one row per figure with how many waiting entries rest on it, so whoever can set it confirms it once rather than approving each entry on Roiva's number; the entries waiting on it are then calculated again with your figure.
It also says how the figure was measured where that's worth a look: Outside its charter when it was calculated differently from the initiative's signed charter (see Measurement charters), Still settling for deflected tickets still inside their recontact window, and Estimate or Reconstructed when its baseline is one your own people estimated or a without-AI sample (see Baselines for an initiative that's already live).
Same month as another entry marks a formula's entry and one someone typed, imported or had the Assistant draft when both book the same kind of value on the initiative for some of the same days. If one repeats the other, approving both counts it twice; they can also be two different things, such as a one-off saving beside the monthly one. Each one's Approve confirmation names the other. Approving a selection leaves both out, so you approve each from its own page, and a row of a value entries CSV imported as approved is refused for those days: import it as reviewed instead. A formula's entry that can't be approved as it stands, such as one waiting to recalculate, isn't counted as the other side.
An entry someone typed, imported or had the Assistant draft, or a formula's or a synced entry someone changed the figure of (its source ends "then edited by hand"), lists its Supporting documents on its page: the initiative's documents and links it cites, or No source attached. It's what the figure rests on, so open them before you approve. The same words show under its source on the Value tab, and its row in the Inbox says how many documents it cites or that it has no source attached. Approving a selection together says how many of them have none. It's a prompt to check, not a block: you can still approve it.
Saving any change to an approved entry, including the documents it cites, sends it back for approval. So does Send Back for Review, which leaves the entry alone and asks for a reason; the approvers are told the reason, and it shows on the entry. Changing or deleting an approved entry takes someone who could approve it. Sending one back takes an approver too, but it can be the person who prepared it, since it takes the entry out of ROI and it has to be approved again: by someone else, unless the rule on approving your own entries steps aside (see Not your own entry below). Where you can't send it back, the button is grayed out and says why.
An approved entry calculated from a reading that changes afterwards keeps counting the figure that was approved. Its page names each reading that changed, from what to what, and the Inbox lists it under Changed since approval for whoever could send it back. Send Back for Review recalculates it from the readings as they are now, for an approver to approve again. Where its formula can't work it out (a figure it reads is missing for that month, say), the entry and the notice say so and it keeps the figure it had.
Whoever edits a reading an approved entry was calculated from is told above Save which approved entries were calculated from it and who will be asked (a reading that's one part of a weighted average is watched only for being deleted, so editing its value asks nobody), and whoever edits or deletes one is told again once it's done. Until the entry is sent back or the figure is put back, the reading shows Changed since approval and who it's waiting on, under Entries → Metric Entries and on the reading's own page.
An approved entry booked from won deals in HubSpot, Salesforce or Pipedrive also keeps counting the figure that was approved when the CRM changes afterwards: a deal's amount, close date or currency changes, it's no longer won or no longer in the CRM, its pipeline or Salesforce record type no longer counts as sales, the CRM's mappings for the initiative match it differently or not at all, the initiative is no longer linked to the CRM, or a deal joins a month already approved.
Its page names each deal that changed, and the Inbox lists it under Changed in the CRM since approval for whoever could send it back. Send Back for Review books it again from the CRM's deals as they are now, for an approver to approve again.
Where nothing would book it again, its page says so: a one-time entry whose deal was deleted goes with the deal at the next sync once it's back, and one whose deal no longer books, or whose initiative is no longer linked to the CRM, is archived by the next sync, so to keep a figure for it, record one by hand. Change a deal back and the entry drops off the list.
A one-time entry booked from a won deal that hasn't been approved yet follows the CRM, edited or not. If the deal is no longer won, its pipeline or Salesforce record type no longer counts as sales, or the initiative's link no longer books it, nobody can approve it: the next sync archives it, its page says why, and the initiative's activity records it. If a sync books the deal again, the entry comes back for approval. A month of recurring deals is booked again without the deal instead. To keep a figure for a deal that no longer books, record it by hand.
A formula's entry that hasn't been approved yet leaves Approvals if the formula can no longer calculate its month because a figure has gone, so nobody can approve the old figure. Its page names what's missing, and it comes back at a new figure once the formula has every figure it needs. Roiva tries each night.
Approved freed capacity that capacity realized as cash was approved against stays approved while the realization does. Editing, sending back or deleting it is refused if the month would be left with less freed capacity than was realized, and so is approving a negative freed capacity figure that would do the same; send the realization back first.
Payroll beyond freed capacity is always approved by someone who didn't record or edit it, whatever the account's self-approval setting, and only once the month's approved freed capacity is all realized. See Adding costs and value entries.
In a locked month, none of that is possible: an approved entry dated in the month (by its period start, or by when it was approved if it has no period) can't be changed, sent back or deleted, and no entry dated in it can be approved, until someone reopens the month with a reason. See Allocation rules and accounting periods.
An entry calculated from a figure at a provisional rate can't be approved yet. It's calculated again at the month's average once the ECB publishes the month's rates, and can be approved then; until it is, its Approve button says why.
Someone who edits an approved entry can't approve the change. Someone who only sends it back can approve it again, so a second pair of eyes needs a different approver to pick it up.
A spreadsheet import brings entries in as drafts, submitted for review, or approved. Only someone who could approve an entry can import it approved.
Initiatives from a spreadsheet
Initiatives created from documents, or brought in with Import, start at Identified or Reviewing, which need nobody's sign-off. Rows imported into Reviewing go to their approvers, who get one notification for the whole import. See Creating initiatives from documents.
Only someone who could approve an initiative can import it at a later stage, and doing so counts as their decision: the initiative shows them as its approver on the day of the import, and the decision appears in the Approval Register, marked as made by importing it. For anyone else, a row the sheet puts further along starts in Reviewing, where its approvers decide.
Who can approve
- The initiative's approval chain. On an initiative's edit form, Approval chain names who approves it: up to five steps, approved in order, each with its own approvers. Only the approvers at the current step can approve the initiative or its value entries, whatever their role. Only an Owner or Admin can set or change the chain, naming members who have joined the account; members see it read-only. Each change is recorded in the audit log with the chain before and after, including someone taken off it because they left the account or were removed. A step left with nobody in it falls back to any Owner or Admin.
- No chain: any Owner or Admin can approve.
- Senior approval threshold: above this amount (an initiative's planned CapEx plus a year of its planned OpEx, or a value entry's amount), only an Owner, or someone an Owner has delegated approvals to, can approve, whether or not the initiative has a chain. Its notification and Inbox row go to the Owners.
Not your own entry: by default nobody approves a value entry they recorded or edited (an entry edited before October 30, 2026 remembers only its last editor from then), or one a formula calculated from a reading or baseline they entered by hand or imported, or from a figure they set for that initiative alone (such as its attribution share, or its own cost per incident), or a deal, invoice or payment a connection booked at the margin they set for that initiative alone. The same goes for an entry calculated or priced from a time study they published, owned, left timings out of, timed tasks for or imported timings into (see Running a time study).
Nor does anyone approve an entry calculated with a formula they changed: not whoever last changed its expression or inputs, and not anyone who changed the formula after that, its type of value, unit or an input's label included. A synced reading, an account-wide figure like a labor rate, or a change Roiva made to a library formula doesn't count.
The rule steps aside in two cases: while nobody else could approve the entry, and when an Owner turns on Allow people to approve entries they recorded. Nobody else means nobody besides the people the rule keeps off it, among those who could approve this entry: above the senior approval threshold, the Owners; below it, the current step's approvers when the initiative has a chain, otherwise the Owners and Admins. Someone suspended, or who can't sign in, doesn't count. So in a one-person account, or when everyone who could approve the entry recorded it, edited it, entered a figure for it or changed its formula, any one of them can approve it. That case ends by itself as soon as someone else who could approve it joins. Either way the entry is marked as self-approved (see below). Payroll beyond freed capacity has no exception: neither the setting nor being the only approver lets its preparer approve it.
Delegation: someone going on leave can hand their approvals to a colleague for a date range under Profile → Delegations. The colleague approves as they would, held to the same rule: not an entry the person who delegated recorded, edited, entered a figure for or changed the formula of, unless that person could approve it themselves. A delegation from someone suspended passes on nothing. Saving or removing one is recorded in the audit log, and one still running or yet to start ends, also recorded, when either person leaves the account.
If the Approve button is grayed out for you, one of these rules is why: the entry's page says which, and names who can approve it. Whoever they name can approve it: only an Owner, or an Owner's delegate, above the threshold; below it, the current step's approvers when there's a chain, otherwise an Owner or Admin; and for a value entry, not whoever recorded or edited it, entered a figure it was calculated from, or changed the formula it was calculated with.
When someone approves their own entry
An entry approved by the person who recorded it, who edited it, who entered a figure it was calculated from or set the margin it was booked at, or who changed the formula it was calculated with, still counts. Without that, an account with one person in it could never approve anything. What changes is that it says so, wherever someone relying on the figure would look:
- The entry's page, under Approved By: "Recorded it too." (or "Edited its figures too.", "Entered figures it was calculated from." or "Changed the formula it was calculated with."), followed by why the rule allowed it. Either nobody else could approve it then, or the account's approval settings allow it.
- Exports and the Value Evidence Register: a Self-approved column says "Yes" and gives the reason. The register's summary sheet counts these entries and adds up their value.
- The Board Brief: when any of the quarter's approved value was approved this way, the brief's caveats give the amount.
- The audit log and the initiative's activity: the approval says the approver approved their own entry, and why.
Why the rule stepped aside is recorded when the entry is approved, because who else could have approved changes as people join and leave. Entries approved before Roiva recorded it are still marked, and their reason reads as not recorded. So are entries that someone who had changed their formula approved before Roiva began keeping those people off them, except in a locked month.
The mark doesn't stop anyone approving. If your auditors need a second person on every entry, make sure someone else can approve each one: a second Owner for entries above the senior approval threshold, a second approver at each step of an initiative's chain, and otherwise a second Owner or Admin. Leave Allow people to approve entries they recorded off. Then the rule has no exception to make.
Approval settings
These are under Organization Settings → Approvals. Only an Owner changes the first four; an Admin sees them and can change the SLA. The audit log records each change with the setting before and after, so a control loosened and tightened again shows on the record, and the account's other Owners are notified of each change to the first four.
Auto-approve formula-derived value entries — off unless you turn it on. When it's on, entries calculated by a formula Roiva supplied (one that comes from an initiative template, an auto-configure, a document extraction or an assistant suggestion) are approved automatically if they come from real readings, a person has already approved one of that formula's entries, and the amount is between half and double the last one a person approved.
An entry always waits for a person if it rests on any of these:
- a Roiva default
- a baseline Roiva estimated
- a share you credited to the initiative
- the share of an incident's time users were blocked
- a hand-entered volume from an earlier month
- a reading an AI assistant drafted outside Roiva and a person accepted
- a total a connection synced for an earlier month (spend, tickets or runs: most connections write a month only when it had some)
- a figure read from several connections combined that's missing one that had a total the month before
- a time study's figure past its re-study date
- a changed unit
- a formula that doesn't adjust a count for its volume
So does one calculated outside its initiative's signed measurement charter, one whose warehouse query has a new version since the last approval, one dated in a locked month, and one for a month in which the initiative already has a value entry of the same kind that someone entered by hand, imported from a file or drafted with the Assistant, even one still in draft. Formulas you wrote yourself, amounts above the senior approval threshold and amounts far outside the initiative's planned figures always wait for a person too.
When someone changes a formula's arithmetic, its entries wait for a person until someone who didn't change the formula has approved one calculated with the change. An approval by one of the people who changed it counts only when the rule stepped aside for them and the entry recorded why: nobody else could approve it, or the account allows people to approve their own entries.
Auto-approved entries show Auto-approved as their status, and each one is recorded in the audit log. Turning it on also checks the entries already waiting for review.
Allow people to approve entries they recorded — off unless you turn it on. It turns off the rule against approving your own entries.
A second person accepts assistant proposals — off unless you turn it on. A monthly reading, a vendor bill's costs or business-case figures an AI assistant drafted outside Roiva wait under Inbox → Proposals until a person accepts them (see Connecting Claude, ChatGPT, Cursor and other AI assistants (MCP)). Off, the person whose assistant drafted one may accept it themselves; on, another Owner or Admin accepts it, unless nobody else could. Either way, the person whose assistant drafted a reading and the person who accepted it both count as having prepared the value it calculates, as if either had typed the figure.
Senior approval threshold ($) — see above. Blank means no threshold for initiatives and value entries, while every budget increase then waits for an Owner (see Budgets and budget vs. actual).
Approval SLA (days) — anything that has waited longer shows as overdue in its approvers' Inbox, with how many days it has waited. Blank means three days. A value entry waits from when it was submitted, or from when a formula or a sync wrote it; a recalculation or an edit while it waits doesn't restart the count.
Roiva staff never approve anything in your account unless they are a member of it, and then only by these rules, like anyone else.
Next
- The initiative lifecycle — the stages an approval moves an initiative through
- Adding costs and value entries — where value entries come from
- How Roiva calculates value — which formula-derived entries auto-approve