01 ViVE Comply
Compliance and controls
A rule is only a control if something checks it
ViVE Comply lets compliance teams define what must happen, then check actual execution against those rules. Every case in scope can be evaluated against the rules that apply to it, with the supporting evidence available for review.
out of the boxconfigured, not coded
evaluatedno sampling
before breachwhile the case can still move
to the eventready for audit
02 What Comply is for
Sampling tells you about the sample. Comply checks the population in scope.
Periodic sampling can miss what happened outside the sample. ViVE Comply evaluates applicable rules across the full population in scope using the same process data as the rest of RE-ViVE.
- Which open cases are at risk of missing the SLA?
- Where is a mandatory step being skipped, and by whom?
- Are approvals happening before the thing they approve?
- Has anyone raised and approved the same transaction?
- Which control has degraded since last quarter?
- Can we show the auditor the evidence, not the policy?
See risk before the breach
Open cases can be evaluated against their thresholds while work is still in progress, so teams can see which cases are approaching a breach and act sooner.
A control you can demonstrate
Each rule has a definition, a population, a result and supporting execution evidence.
Audit evidence without a fire drill
When a review request arrives, the supporting evidence is already available: the case, rule, activity, timestamp and actor behind the result.
03 The five compliance types
Configure controls without custom development
Five core rule types are configured by selecting activities and setting the relevant thresholds or conditions — without custom scripting.
End to end, against the promise
A threshold on total elapsed time for the case. Open cases are projected forward; closed cases are settled.
breach — 7.1 d against a 5 d promise
A threshold on a single step
Each activity carries its own limit, so a slow step is attributable even when the case as a whole still clears.
breach — screening 6.2 d against a 2 d limit
A step that must always happen
Nominate the activities that cannot be absent. Comply finds the cases that completed without them.
violation — 4,102 cases closed without screening
Order that has to hold
Declare that one activity must precede another. Cases where the order inverted are listed, not averaged away.
violation — 812 releases preceded their approval
Two steps, two people
Pair the activities that must not share an actor. Comply checks the resource on each event, including automated ones.
violation — 37 transactions raised and approved by one user
Two additional control templates
X-R and X-S are available as additional control templates alongside the five core rule types. Set the scope and conditions, and the applicable cases are evaluated using the same Execution Data Model.
COPY NEEDED: confirm what X-R and X-S expand to and the exact rule each enforces, so this card can describe them as specifically as the five above.out of the box — no development required
ViVE Comply reads the same Execution Data Model as ViVE Optim and ViVE Insights, so control results, process measures and dashboards use the same underlying process data.
04 Risk before it happens
Finding a breach early gives you time to act
When source data is refreshed during the life of a case, open work can be checked against its thresholds before the case closes — giving teams time to reassign, escalate or expedite.
One rule for historical and current monitoring
Use the same rule definition for historical reporting and current monitoring when the underlying data is available.
Exposure, not just counts
Breaches carry the value, customer and product behind them, so a hundred small cases and one large one are told apart.
Trend on the control itself
Whether attainment is improving or drifting, period on period, on the population rather than a sample of it.
05 Evidence for audit
Every result drills to the evidence behind it
A control result includes the rule, population, outcome and the underlying execution evidence. Reviewers can trace a result back to the activities, timestamps and actors that produced it.
| control | rule | case | result | evidence |
|---|---|---|---|---|
| SLA-01 | Overall SLA 5 d | ONB-4471902 | breach | 41.2 d elapsed |
| ACT-04 | Credit check ≤ 2 d | ORD-991027 | pass | 1.4 d |
| SEQ-03 | Approve before Release | ORD-882140 | violation | release 14:02, approve 16:41 |
| SOD-02 | Raise / approve separation | INV-77219 | violation | u.patel on both events |
| MAN-01 | KYC screening present | ONB-4102338 | violation | activity absent, case closed |
| ACT-04 | Credit check ≤ 2 d | ORD-991184 | pass | 0.6 d |
For controls configured across the full population, every case in scope is evaluated against the applicable rule, and each result can open the execution sequence behind it.
The value is population-level visibility: attainment reflects the cases in scope rather than only a selected sample.
06 The rest of the platform
Comply is one of four ways to use the same process data
The same process data used for controls also powers ViVE Optim, ViVE Insights and ViVE Genie. Move from a control result to the process behind it without rebuilding the analysis.
ViVE Optim
Variants, times, rework, bottlenecks and root cause, with drilldown to the individual case and what-if simulation.
ViVE Insights
Drag-and-drop reports and dashboards over the Execution Data Model, built the way your team wants to monitor the process.
ViVE Genie
Ask questions in natural language using the same RE-ViVE process data, with your SOPs and designs available as additional context.