Challenge
Sud Ishlari is the Tashkent city administration's internal system for tracking court cases that involve the administration and city organizations. Its legal departments use it to register cases, follow hearings and rulings at each instance, and record awarded sums and their payment.
The Tashkent city administration's legal departments handle a steady stream of court cases: lawsuits from residents and companies, property and tax disputes. Information about them was spread across separate files, spreadsheets and paper summonses, so getting the full picture of a case was hard: where it stands, what was decided, how much was awarded and how much has been paid. Managers needed quick answers to simple questions — how many cases are unpaid, which cases a given organization is handling, what changed over a period. The city needed a court case management system with one card per case, a clear status and every document at hand.
A case rarely ends at the first instance. Cassation and review follow, and each stage brings new dates, rulings, approved sums and documents: summonses, court decisions, papers from the enforcement bureau. Money matters too: how much was claimed and how much was actually paid. Each instance also brings its own outcome: whether the claim was upheld, what sum was approved, whether an appraisal was made. A lost document here means a missed deadline and a risk to the city's interests. So the full history of a case had to be stored instance by instance, with dates and files, instead of being rebuilt from memory, folders and correspondence.
Hearings are set for a specific date and time, and they need the same close attention as the cases themselves. Staff needed a shared working list with a calendar showing what is coming up today, this month and this year, what is done and which tasks are still open. Entries had to be quick to create, mark as done and find by date. A comment on an entry had to stay short and to the point so the list could be read at a glance. The list had to be shared by the whole department so that anyone could pick up a colleague's case and immediately see what stage it is at.
Case cards hold personal data — personal ID numbers, passports, dates of birth — as well as sums, tax debts and the cadastral numbers of properties. So only users with the right role may change records, everyone else works in view-only mode, and access is protected by a login and password. The interface had to work in Russian and Uzbek and make sense to lawyers without a technical background: forms, filters and tables with no extra steps, and deletion only after confirmation. A mistake in a case card is costly, so forms had to check the fields and immediately show what was filled in wrong.
Solution
We split the system into two workspaces — a working list with a hearing calendar and a registry of court cases — and gathered everything known about a case in a single card.
The home page holds the working list with a calendar: each entry has an instance, court type, plaintiff, date, comment and a done or not done status. The Court Cases section is a registry with search by ID, case number and plaintiff name, filters by case type, organization, payment status and period, and an Excel export. From a registry row, a case can be opened, edited, deleted or updated with the paid sum right away. Each case opens as a card with three tabs: details, instances and documents. The summons, the enforcement bureau's document and the final court ruling are uploaded straight into the card.
The interface is built with React and TypeScript, whose strict type checks help keep the fields of long case forms from getting mixed up. Data lives on a Django REST Framework server, which checks every action against the signed-in employee's account. Forms show errors right under the fields, and files of up to 10 MB are dragged into the upload area. The disputed property is marked on an open Leaflet and OpenStreetMap map, and its coordinates are saved together with the cadastral number. Only administrators and moderators can add or change cases; everyone else works in view-only mode. The panel is available in Russian and Uzbek, with light and dark themes.
Court case registry
All cases live in one table: record ID, creation date, case number and type, plaintiff, organization, total and paid sums, and payment status. Search works by ID, case number and plaintiff name, and filters cover case type, organization, payment status and period. The filtered list exports to Excel with one button, and the number of rows per page is adjustable. Clicking a row opens the case card, and the row menu holds quick actions.
A case card with three tabs
The Case Details tab holds the registration number, parties, grounds, content, criteria and sums. Instances shows the case's path through the courts, and Documents stores files with a name, date and description. Papers no longer get lost between stages, and anyone on the team can see the full history of a case without asking colleagues. Tabs switch without reloading the page.
Instances and court rulings
For each instance, the system records the name, date, ruling, approved sum and whether the claim was upheld. If an appraisal was made, the appraiser and the appraisal date are recorded, and if a third party is involved, it is listed too. Instances appear as numbered cards in order and are added one by one, while deleting one requires confirmation so that nothing disappears by accident.
Sums, payments and tax debt
The card stores the total and paid sums, the tax debt and the payment status. Payments are entered through a separate window right from the registry, without opening the whole form. The enforcement bureau's document and the final ruling are attached to the case, and the payment status filter instantly shows which cases have not been paid yet. The payment window shows the claimed sum next to the payment field to prevent mistakes.
Hearing and task calendar
On the home page, case entries are collected in a table with a calendar that switches between days, months and years. Each entry has an instance, court type, plaintiff, date and time, a comment of up to 512 characters and a completion status. The status changes in one action from the entry's menu, where the entry can also be edited or deleted. The long list is split into pages with an adjustable number of rows.
Roles, sign-in and the map
Permissions depend on the role: administrators and moderators add and edit cases, while other users can only view the data. Users sign in with a login and password, and the role in the profile cannot be changed. The disputed property has a cadastral number and a point on the map: click the map or drag the marker, and the coordinates are saved with the case. Only an administrator or a moderator can change the phone number in a profile.
Results
The project's key outcomes in numbers.
- −65%Risk of losing documents
Summonses, rulings and documents for every instance are stored in the case card instead of scattered folders.
- ×2Faster work with cases
Search, filters, statuses and the hearing calendar made working with cases twice as fast: a case is found by number, ID or plaintiff instead of by digging through folders.
- 25 daysDevelopment time
We built the registry, the case cards, the calendar with tasks and the roles in twenty-five days, from the first screens to a working system.
- 3Tabs in the case card
Details, instances and documents: everything known about a case opens in a single card.
Project tech stack
The stack we used to build the solution for the client's task.
- Python
- Django
- Django REST Framework
- TypeScript
- React
- Vite
- Framer Motion
- Leaflet
- MobX
- React Router
Ready to become the next case?
Tell us about your task — a manager will assemble the team, calculate the estimate and send a proposal within the first hour after the request. No obligations, no drip campaigns.






