Back to the single queue
Q-0096 · Workforce transition
Customer Service: Tier-1 Resolution Processing Analyst cannot move to Control Tester, Tier-1 Resolution
Clear what is blocking the move, name a different destination role, or stop the transition and say what happens to the people inside it.
High materialityPeopleCustomer ServiceNo clockOpen
Consequence
27
of a possible 100, from four factors
Rank in this queue
12th
of 20 open items held by Oscar Duarte
Records covered
1
One record, one call.
Work held behind it
24
items that cannot move until this is decided
Waiting
45.3 wk
raised 2025-10-04 by Marta Alvarez · HR Business Partner · Customer Service · line owner Director, Tier-1 Service
Why it is ranked where it is
Four factors, scored out of 40, 30, 20 and 10, added to 27.
The commitment it breaches
Is there a window on this, and did it close?
0 / 40
No statutory consultation applies to this transition in AU, and no other date was ever set on it. Nothing about it is late because nothing about it is due.
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?
12 / 30
24.4 full-time equivalents are inside this transition with no destination role.
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 is carried on a transition record. The band is set by how many people are unplaced: twenty or more is high, ten or more is medium, below that low. That rule is this queue’s, not the estate’s, and it is stated here so it can be argued with.
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?
0 / 10
Nobody put a date on this. It waits until somebody looks, which is what a queue without clocks produces.
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 money at stake, which contributes 15 of the 27 points on this item. 2 factors score zero here: the commitment it breaches · whose clock it is. A zero is a measurement, not a gap in the data.
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.
The whole context, here
Everything the decision needs, so the queue is not a routing table.
What is being asked
Clear what is blocking the move, name a different destination role, or stop the transition and say what happens to the people inside it.
Why it is waiting
Blocked on independence. The destination is control testing and the only available reporting line is the process owner being tested. The destination on the record is: Redeployed into control design and independent testing. Headcount goes from 51.4 to 25.9.
Kind
Workforce transition
A person or a role is waiting on a decision.
Money on the record
No figure carried
The source record carries no dollar figure. The money factor is scored from the materiality band instead.
The clock on it
No clock
Deadline
None set
Nothing on this item names a date it has to be done by.
Whose clock
Nobody put a date on this. It waits until somebody looks, which is what a queue without clocks produces.
Not measurable: no date is recorded for this kind.
Not measurable. There is no window to be inside or outside of, so no attainment can be computed and none is shown.
No commitment reference is attached to this item, so the first factor scores on the clock alone.
Where it came from
The queue holds no work of its own.
Workforce Transition
/workforce · RT-134
That page counts 13 waiting and places 13 items here. One record, one item, so the two counts agree.
How items are formed from that page: One item per blocked transition. Each carries its own jurisdiction and consultation status.
The action that page names is: Unblock a role transition or place a released person. 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
Oscar Duarte · VP Workforce Strategy
Addressed to
Oscar Duarte
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
Naomi Muller
Chief of Staff, Corporate
Three days away with a named cover at the same ceiling. This is what the arrangement is supposed to look like.
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
0 decisions on the record
Nothing has been decided on this item yet. The first submission made here will appear in this list with its evidence 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.