LensReading which lens this session carries.

RM-006 · Segregation of duties

Duty conflicts that have only been detected

291 of 385 conflicts — 76% of the population. Duty conflicts are counted by status. A conflict at detected has been found by the rule and nothing has been done with it. A named person has to act.

Back to the register
Outstanding
291
conflicts of 385
State
Part of the population is moving
60 of the wider population have moved to in-remediation, so work on this register entry has started; these 291 have not been touched.
Who closes it
A person
A named person has to act
First seen
2026-07-19
The earliest conflict still sitting at detected.
Platform date
2026-08-18
1 day away, and nobody has agreed to it

Where this entry came from

The query, run against the platform's own records

Duty conflicts are counted by status. A conflict at detected has been found by the rule and nothing has been done with it.

The earliest conflict still sitting at detected.

The records this counts

Who carries it

Taken from the records, never assigned

Group Financial Controller · Control owner

The owner named on the largest number of duty conflicts.

Thirty days from the first observation. The platform set this date; nobody has agreed to it.

What it would take to close this

2 steps, none of them blocked

1Group the conflicts by the person holding both dutiesHours
Two hundred and ninety-one conflicts resolve into a much smaller number of people. The platform can show that grouping.
The platform · A grouping over existing records.
2Take one duty away, or sign a compensating controlWeeks
Both are decisions about a named person’s job. Neither can be made by the platform and neither should be.
Group Financial Controller · Conversations with the people concerned.
1 step waits on somebody outside this platform. The same question across the whole register

Everything recorded against it

Each line is a record, not a note

The platform saw it2026-07-19
The platform · counted 291
Duty conflicts are counted by status. A conflict at detected has been found by the rule and nothing has been done with it.
An owner was taken from the records2026-08-17
The platform
Group Financial Controller was taken from the records, not assigned. The owner named on the largest number of duty conflicts.
A date was set by the platform2026-08-17
The platform
Thirty days from the first observation, applied to every entry in the register without exception. Nobody has agreed to this date.
Measured again2026-08-17
The platform · counted 291
60 of the wider population have moved to in-remediation, so work on this register entry has started; these 291 have not been touched.
Every line above was written by the platform. Nobody has touched this entry.

What it is tangled with

Dependencies taken from the steps, not asserted

Waits on

No other entry. Its first step can start today.

Holds up

No other entry is waiting on this one.

Alongside it in Segregation of duties

This is the only entry in its register.

Nobody agreed to this date

Every date on this page came from the same rule: thirty days from the first time the platform could see the gap. The platform set it. Nobody has agreed to any of them, no counterparty has been told, and none of them is a commitment. They are here so that an entry cannot sit without a clock against it, and they should be replaced by real dates the moment somebody accepts one.