Approval decisions that account for value at risk
The planned policy checks a request's own risk score and the sum of requested amounts across all currently open items in its approval workflow. It adds each new request to that running total: requests that stay within the configured amount can be approved automatically, while requests that cross it are held for manual approval.
Route on the whole exposure
Adds this request to the open-item sum.
High individual scores also route to review.
Projected open exposure is $800 above the configured limit. The request score is below its limit.
Illustrative records, amounts, and scores only. This simulator uses no live tickets or policies.
One request is only part of the risk
The request score describes the item being reviewed. The cumulative rule sums requested amounts across all open items in the workflow, then adds the new request. The policy evaluates both rules before choosing automatic approval or manual review.
Keep the item's own score
Assess the risk of the action or case on its own, so each request keeps its individual context.
Account for risk already in play
Sum requested amounts across every open item in the workflow, then add the new request. A low individual score can still be held when that projected total crosses the configured limit.
Set the point for human review
Set the cumulative amount limit for a workflow. Exceeding that limit or meeting the separate request-score threshold routes the request for manual approval.
Let the configured exposure limit change the next step
For the configured workflow, sum the requested amounts on all open items and add the new request. If the projected total exceeds the amount limit, hold it for manual approval even when its individual score is low.
The reviewer should see the request score, the open-item sum, the projected total, and the limit that caused the hold. The approval decision and action result belong with the ticket they came from.
Within the configured limit
The request score stays below its threshold and the open-item sum plus the new request stays within the workflow's configured amount limit.
Above the configured limit
The request is held when either its score meets the individual threshold or adding it takes the cumulative open-item amount above the workflow limit.
Keep the gate, the reviewer, and the record together
This planned capability extends the existing approval model with exposure-aware routing. Latch already supports approval gates for plugin actions, independent reviewer checks, and ticket-level decision and execution records.
See how current approval workflows workValue-at-risk rules are planned
The current approval settings do not include an amount-based rule builder. Today, an amount threshold must be implemented in the connected action logic. This page describes the planned policy behaviour.
Follow the control path from intake to evidence
These pages work together: intake shapes the ticket, approvals gate sensitive actions, maker-checker enforces independence, security controls the deployment boundary, and auditability preserves the proof. The claims use case shows the controls assembled end to end.
Enforce separation between the person preparing an action and the person approving it.
Route sensitive actions through role checks and approval gates before they run.
Keep decisions, blocked attempts, approvals, and action results on the same record.
Deploy where ticket data, identity, and the AI models you choose stay inside your environment.
Bring email, forms, alerts, and system events into one ticket queue before actions begin.
See the controls assembled for claims work: checklist-driven file reviews, maker-checker, and upstream execution proof.
Questions about exposure-based approval
How the planned policy combines the individual request score with the sum of amounts on all open items.
What does value at risk mean in this approval model?
It is the configured amount limit for all currently open items in an approval workflow. The policy adds a new request to that open-item sum, then routes it for manual approval if the projected total crosses the limit. This page describes a planned capability; current approval settings do not include this rule builder.
Does the wider risk view replace a request score?
No. The policy checks the request score on its own and also calculates the sum of requested amounts across all open items in that workflow. Either rule can route the request to manual approval, so a low-scoring item can still be held if adding it would push the cumulative amount over the limit.
What happens when exposure passes the limit?
The planned policy holds the action for manual review. An authorised reviewer decides whether it can proceed.
Can teams set different limits for different workflows?
The planned configuration sets the scope and cumulative amount limit for each workflow. The current product does not yet provide this amount-based rule builder.
Set the review point around the risk you can accept
Discuss how a value-at-risk limit could fit alongside your current approval roles and action controls.