Back to the single queue
Q-0005 · Population ruling
Operational routing and execution: 530 records are past the date the schedule set for them
Authorize destruction for the population, or place a hold on it and name the matter the hold rests on.
High materialityAssuranceAdministrationRetention dateOpen
Consequence
87
of a possible 100, from four factors
Rank in this queue
1st
of 15 open items held by Morgan Idris
Records covered
530
One ruling settles all of them, so it enters as one item.
Work held behind it
530
items that cannot move until this is decided
Waiting
0 min
raised 2026-08-17 by Records schedule, automated review
Why it is ranked where it is
Four factors, scored out of 40, 30, 20 and 10, added to 87.
The commitment it breaches
Is there a window on this, and did it close?
40 / 40
The destruction date sits on each record rather than on the class, so the queue cannot name one date for the population. What it can say is that 530 records are already past theirs, and a commitment already passed is a commitment breached however it is dated.
Measured from: Point scale out of 40: a window already closed scores 40, less than a quarter of the window left scores 28, inside the window scores 14, no window at all scores 0.
The work it holds
How much is stopped behind it?
24 / 30
530 records are held past their date. Nothing downstream stops until they are dealt with, but every day they sit there is a day the published schedule is not being followed.
Measured from: Point scale out of 30, on the count held behind the item: 1,000 or more scores 30, 100 or more scores 24, 25 or more scores 18, 5 or more scores 12, 1 or more scores 6, nothing held scores 0.
The money at stake
What band does the record itself carry?
15 / 20
No money figure exists on a retention population. It is banded high because keeping a record past the date the estate publishes for it is a breach of that schedule, and a breach is not priced here.
Measured from: Point scale out of 20, on the materiality band: critical 20, high 15, medium 9, low 4.
Whose clock it is
Is the deadline ours, a regulator’s or a court’s?
8 / 10
The retention class the record was filed under. Once the date passes, holding the record is itself the exposure.
Measured from: Point scale out of 10, on whose deadline it is: statutory 10, retention 8, board or committee 6, audit 5, expiry 4, service level 3, no clock 0.
The score is carried mainly by commitment breached, which contributes 40 of the 87 points on this item. All four factors score above zero on this item.
The ranking is a scheme, not a measurement. Four factors are scored out of 40, 30, 20 and 10, and the four scores are added. The ceilings were chosen by us and no one has yet agreed them. What is measured is each factor underneath: the window and whether it closed, the count held behind the item, the band on the record and whose deadline applies.
Nothing is above this item. It is the top of Morgan Idris’s queue.
Directly below · 76
Executive Support: AD4B-1054 held at approve
The whole context, here
Everything the decision needs, so the queue is not a routing table.
What is being asked
Authorize destruction for the population, or place a hold on it and name the matter the hold rests on.
Why it is waiting
Internal operating requirement. No statutory driver, so the shortest defensible period is used deliberately. Deleted at three years. This is the only class where the estate deletes rather than retains by default. The class covers 1093 records across US · UK · DE · FR · SG · AU · BR. Dated at assembly. The population behind this item has no single date on which it was raised, so the queue uses the moment it was assembled and says so rather than picking one record’s date and presenting it as the item’s.
Kind
Population ruling
One ruling settles a whole set of records.
Money on the record
No figure carried
The source record carries no dollar figure. The money factor is scored from the materiality band instead.
An item is one decision, not one record. Where a page holds a homogeneous population that one ruling settles, the population enters as a single item and states how many records it covers. That is why the number of items is far smaller than the number of things waiting.
The clock on it
Retention date
Deadline
None set
Nothing on this item names a date it has to be done by.
Whose clock
The retention class the record was filed under. Once the date passes, holding the record is itself the exposure.
Measurable against a recorded date.
Measured. The count of records past their date is stored on the retention class as the number due for review.
Commitment: Records schedule OPS-3Y, 3 years
Where it came from
The queue holds no work of its own.
Records and Retention
/retention · OPS-3Y
That page counts 2,833 waiting and places 6 items here. The counts differ because a homogeneous population enters as a single ruling.
How items are formed from that page: One item per retention class. Disposal is authorized class by class, not record by record.
The action that page names is: Dispose of records that are past their date. Clearing this item is that same decision.
What the queue will enforce
Checked at submission, not at display.
Authority to sign
Within the cap
The register carries a grant that covers this item at this value. No grant reference is recorded against the item.
Separation of duties
No rule engaged
No separation rule is engaged on this item.
One separation rule blocks and five report. Concentrating decisions on one surface makes that difference load bearing: the queue refuses a self-raised item at the point of submission under SOD-01, and records but does not stop the other five.
Who holds it, and who covers
Morgan Idris · VP Business Services
Addressed to
Morgan Idris
Routing is by remit alone. Nothing about the value of an item changes who receives it, only whether the person who receives it can sign it.
Cover
Anika Kaplan
Director, Security Engineering
Names security engineering as cover. Security engineering names this post back. Both are away on the same two days, so the delegation resolves to a loop and neither queue has anybody in it.
The cover board Decide it here
The outcome, the reason and the note go in one submission, and the evidence record is written on the way through.
Take the decision as asked. The item closes.
Note written onto the record
What has already been decided on this item
1 decision on the record
Refused to decide
QD-0009 · 2026-08-16
Morgan Idris · VP Business Services
Operational records held under the three-year schedule are not this desk’s to destroy. The schedule names a records owner and the queue has routed past them.
Reason RF-OWNERNo spine sequence
Decisions already on the record were reconstructed from the source rows at assembly and carry no spine sequence. A decision taken here writes one, and the sequence is shown against it.
What this item page is, and what it is not
This page carries the whole of one decision: what is being asked, the four scores that put it where it sits, the clock that applies, the page the row still lives on, and the two rules the queue will check when the submission is made. Deciding it here is the same act as deciding it there. There is no second copy of the work.
The consequence score is ours. The four things underneath it are measured, but the ceilings that turn them into a single number out of 100 were chosen by us and have not been agreed with anyone. Read the factors, not the total, if the two ever disagree.
The authority and separation checks shown above are statements of what will happen at submission. They are enforced by the server when the form is sent, not by hiding controls on this page, so a refusal always names the rule that produced it.