Public proof path

Backlog should be measured as operational work, not hidden pressure.

Aggregate metrics can show queue age, deficiency turnaround, first-touch time, slotting needs, service/proof exceptions, packet readiness, and rework without exposing private records.

FocusAggregate operational metrics
UsePublic accountability and pilot evaluation
Privacy postureNo protected case details in public metrics

What metrics should explain

Backlog is not only a count. It is the lived result of queues, incomplete packets, correction loops, missing service/proof, slotting pressure, staff burden, and unclear readiness.

Useful public measures

First touch

How long received work waits before initial review.

Deficiency turnaround

How long correction loops take from return to resolution.

Queue age

How old unresolved work is across operational lanes.

Packet readiness

How much work is ready for review versus blocked by missing steps.

Public reporting boundary

Public reporting should use aggregate measurements and public-safe explanations. It should not expose private case details, protected records, or personally sensitive material.