At 10 a.m. the exception queue has eight open items. It had seven yesterday. That rise might reflect one giant unresolved payment file, or just three provider replies still waiting for review. A useful queue tells the payroll lead which decision is needed, not just how many rows look red.

Count new, carried and closed items separately

Use the equation opening inventory + newly recognized cases − substantive closures = ending inventory. On Monday there were six carried cases and five additions. Three were closed on verified evidence, leaving eight. If two assigned owners moved their cases from the payroll desk to Treasury, those are handoffs, not closures. If one new case aggregates a related batch issue, document where the underlying item count is retained; use like units when comparing workload.

Split the aging view by action rather than by team name: wage outcome unknown, cash/funding evidence missing, provider definition needed, and ledger review pending. The cutoff or legal due date belongs on the individual internal case; a team-wide age threshold does not replace wage obligations. Let the wage owner choose and apply the relevant time rules. Averages should never bury a single urgent item.

Name what evidence would close each case

The Tuesday sample queue has three actions due before noon. Case A needs confirmation of the alternate payment outcome. Case B needs the bank trace already requested from Treasury. Case C is only waiting for a support reply that defines whether the report’s “accepted” status is at file or item level. Give each a next evidence time and an alternate owner if the primary reviewer is absent.

Keep enough separation that the person preparing an alternate disbursement is not also its only reviewer. Where a small team cannot arrange separation, its supervisor can design and document an appropriate independent check. Keep the work queue restricted and omit employee-identifying and financial information from training material. This site doesn’t receive queue exports.

At the end of the week, ask why cases carried over, not merely how many there were. Stalled cases might cluster around the same report, which is a reason to improve the status dictionary. Tie month-end carryovers to the close memo rather than starting another unsynchronized list.

Reference: GAO Green Book, used here as a public framework for monitoring and control design, not as a payroll regulation.