xGRC · anatomy of a control execution

Five screens, and "executable" stops needing explanation.

Most people hear "executable" and picture a notification announcing work to be done. The real mechanism is simpler and more radical: the control loads itself, reads your data, reaches a verdict and starts what comes next.

The screens below are illustrative, non-contractual representations, pared back to isolate the mechanism. Real screens carry a density of structured data we do not publish — you will see them in a demonstration.

Scheduling

You configure the control once: which process, which task, which data, what cadence, which checklist and which remediation plan. The scheduler then creates every occurrence to come.

There is no campaign to launch, no reminder to send, no tracking sheet to maintain. The administrative weight of control disappears here, not further down the line.

Control setup · CTL-114

PROCESS · TASK

Claims settlement → Approval

LINKED RISK

RSK-0391

CADENCE

Daily

MODE

Robot — direct

COVERAGE

Full population

OCCURRENCES CREATED BY THE SCHEDULER

30 Sep · done 1 Oct · today 2 Oct 3 Oct 6 Oct + 249

1 One setup, 254 occurrences already created. Nobody is going to schedule those by hand.

Semantic layer · data feed script

PRODUCTION DATA SOURCE

SYSTEMCore insurance — production

TABLESCLM_CASE · CLM_APPROVAL · REF_LIMIT

RELIABILITY● Trusted source

PII▲ 3 personal data fields — masked

GENERATED SCRIPT

SELECT c.reference, a.approver, a.amount, l.delegation_limit
FROM CLM_CASE c
  JOIN CLM_APPROVAL a ON a.case_id = c.id
  JOIN REF_LIMIT l ON l.profile = a.approver_profile
WHERE c.approval_date = :occurrence_date

1 The semantic layer knows your systems, tables and joins. The extraction script is described in plain language; personal data is flagged natively.

Loading

At the due date, the day's occurrence goes and fetches the production data itself — full population or sample, as configured.

Nothing is replicated, nothing is re-keyed. The time spent reaching the data under control — a real share of control time in a declarative setup — falls to zero.

Where a document has to be prepared by an operator, the request goes out with its deadline and the occurrence waits.

Execution — two paths

The robot path short-circuits more than 90 % of volume: no human analysis, running as permanent control over short periods. The controller path handles the rest, with an overall status or a status weighted by a checklist of minor and major points.

Working a manual control — and even simply viewing its contents — is restricted to members of the execution group it belongs to. A control is not a document you open in passing.

ROBOT · DIRECT > 90 % of volume

The robot reaches a verdict on every row and triggers remediation on failure. No involvement at all.

CLM-40812● Compliant

CLM-40817▲ Major failureREM-2291

CLM-40823● Compliant

CLM-40826● Compliant

2,418 rows processed · 11 failures · 4 s

CONTROLLER weighted status

The controller re-keys nothing: they set the status, or the checklist that weights it. Self-control is not permitted.

Supporting document on fileminor Amount matches the schedulemajor Signing authority within limitmajor Four-eyes check evidencedmajor

Weighted status: 68 % — major failure recorded

Cadence describes the control, not the remediation. Human control is monthly at best, often quarterly; the robot runs continuously. Remediation handling is independent of both and happens continuously.

Remediation

A failure starts the remediation plan and ties it, compulsorily, to a risk. That link is what reveals, over time, which risks were misidentified or misrated.

The plan is not an alert: it carries the actions that fit the failure found. The operator accepts, qualifies the case, adds a voluntary action, or rejects it as a false positive — and can hold the case pending supporting evidence when the document is not yet available.

Pre-emptive remediation names the step that was skipped: the operator learns by doing, and the system improves with no dedicated programme.

Worklist · RemediationREM-2291

OPEN RISK RSK-0391 CASE CLM-40817

Approval beyond delegated signing limit

This case was approved by a profile whose delegated limit is below the amount committed. Expected step: hierarchical counter-approval before settlement.

OPERATOR RESPONSE

1 Linking to a risk is not optional. That is what turns an isolated incident into management information.

Worklists — each at their own station

There is no single landing screen where everyone hunts for their task. Each role enters through its own worklist and lands directly on the step that concerns them. Nothing is serialised, nothing routes through a central point.

Evidence preparation

OPERATOR

Documents to supply, with their deadlines. Five, eight or fifteen days for period-end data.

Controls

CONTROLLER

Occurrences awaiting a verdict, data already loaded. Only manual controls appear here.

Remediation

OPERATOR

Cases to handle, colour-coded: robot in the background, manual, awaiting a document.

Describe one of your controls.

We configure it and run it in front of you. It is the shortest way to check whether any of the above holds up.

Request the demonstration Self-assessment