Data gapOwner missing for a privileged account
Assign ownerHow RapidValue works
Three loops.
One place it asks you.
The menu is organised by when you get value: Connect, See, Govern, Prove. Underneath, three different loops keep the system honest, with a gate before claims and one inbox for human judgement.
The model
Three loops. One governed inbox.
Data and access turn on machine time. The model runs at human pace. Each loop keeps moving independently—and brings human judgement to one shared place.
Turns continuouslyData loopIs what we know good enough to act on?
The data gateOnly defensible claims pass
Runs at human paceModel loopWhat exists to be governed?
Turns continuouslyAccess loopWho should have what—and does it still hold?
One governed inboxWhere human judgement happens
3 kinds of workRole proposalFinance role is ready for owner review
Review modelAccess decisionContractor access reaches its end date
Decide accessEvery decision returns to its loop with the reason attached.
Turns continuously
The data loop
Is what we know good enough to act on?
Read what is actually there. Resolve whose account it is, what kind of identity it represents and who answers for it. What remains unknown becomes a governed gap—not a guessed finding.
Runs at human pace
The model loop
What exists to be governed—and does it still deserve to?
Applications, entitlements and roles are proposed, shaped, owned, formalised and eventually retired. This loop lives at human pace because its decisions can last for years.
Turns continuously
The access loop
Who should have what—and does it still hold?
Expected access is compared with what target systems actually show. Approvals, lifecycle, reviews and reconciliation close the difference while preserving the reason.
The data gate
The data loop decides what the rest may claim.
Data quality is not an onboarding chore that ends. It holds a continuing veto: an unknown is reported as unknown, never converted into false confidence.
If activity cannot be read, an empty last-used date is untracked—not evidence of dormancy.
An event-only rule is reported as a review gap, not counted as a scheduled review.
A control with nothing to measure is excluded instead of rounded to 0% or 100%.
One inbox
Deciding happens in one place.
Approvals, certifications, reconciliation drift and findings arrive together. Each item says which loop asked, why it matters and where the decision returns.
- Answered questions supersede themselves with the reason on the trail.
- Oversight workbenches show what is happening; they do not create a second queue.
- The navigation badge and home tile read the same count from the same source.
The same model, in time
A first morning starts the loops. It does not create throwaway work.
Scope
Name the decision, boundary and safe starting mode.
Connect HR
Establish the identity truth before correlating accounts.
Connect one target
Read accounts, grants and the metadata the gate needs.
Inspect
Turn gaps into named, owned work—not an inert report.
Decide
Leave with a governed first view and a clear next move.
See the loops move