Casework analytics, in jurisdiction.
Raw records that must stay in their jurisdiction stay there; the agent runs in-jurisdiction and computes beside them. A residency review reads locality, lineage and access logs off the run itself.
The casework cycle, district by district.
The case file and its analytics remain in the approved jurisdiction throughout processing.
Intake
A case enters through a district office or a portal and lands in the system of record.
records stay in-jurisdiction
Assignment
Cases route to officers. Backlogs start forming here.
Processing
Documents, checks and decisions accumulate on the case file.
Decision
The outcome is recorded. The file closes or escalates.
Reporting
Throughput by district, backlog age, and where the queue actually stalls.
Analytics computes beside the case store
execution location, lineage and access are recorded for review
Throughput, backlogs, and who read the file.
Live views over the case store as it stands, read in-jurisdiction.
Analytics · live views
Ranked backlog attention with reasons, so intervention starts in the right district.
Analytics · attention queue
One row per read on the in-boundary ledger: question, rule, reader, timestamp.
Orchestration · audit
Where the agent sits.
KEZEL · DEPLOYMENT · PUBLIC SECTOR
- agent
- deployed in-jurisdiction
- components
- Orchestration + Analytics
- residency
- raw records stay in-jurisdiction
- audit
- in-boundary ledger
Local execution, lineage and access logs are designed to support the team's residency review.
Show us the data you are not allowed to move.
Tell us which systems you use and what you need to do. We’ll walk through a demo, then plan a pilot with your security team.