Clerk / Court operations
Clerk Operations Board
This is the clerk’s real operating surface: work objects, owners, statuses, packet readiness, timing clocks, service / proof posture, and next actions.
Received today
12
New intake and corrected packets.
Deficient
7
Returned items with cure windows.
Ready to assign
9
Reviewed packets ready for routing.
Needs slotting
5
Hearing or conference date needed.
Operations Board
Dispatch is the product.
The clerk board lands in live work lanes instead of a buried queue. Every item keeps packet readiness, service posture, closure discipline, and scheduling visibility on the same screen.
New intake
Initial review of newly received work
Filing review
Human-confirmed packet posture before routing
Ready to assign
Packets fit for routing or scheduling
Scheduling needed
Matters missing a hearing or conference slot
Exceptions
Blocked, sealed, duplicate, or transfer cases
Active queue discipline
Closure and work hygiene
| Outcome | Meaning | Required audit fields |
|---|---|---|
| Accepted and routed | Validated packet moved forward. | operator, timestamp, destination |
| Returned for correction | Deficiency notice sent with due-back date. | reason code, notice text, due-back |
| Closed – duplicate | Merged or suppressed duplicate work object. | linked duplicate ID, operator |
| Closed – transferred | Moved to another court or queue lane. | destination, reason, receiving queue |
Command shortcuts
Open the next operational lane