Set up the board by stage.
The board shows authorized cases in status columns. A successful move updates the record; other users and metrics see it on their own refresh. The board and flow below are illustrative; they create or move no real record.
01/04Preparation
2026/18 E.
Labour Court
2026/21 E.
Commercial CFI
02/04In progress
2025/310 E.
Consumer Court
03/04Hearing
2026/42 E.
Civil Court
2025/214 E.
Civil Court
04/04Decision
2024/87 E.
Civil Court of Peace
A card moves column by column.
An illustrative manual-move flow; it creates no real record, team broadcast or webhook delivery. A hearing date does not change the stage automatically; closure depends only on the target status closed flag.
- 01/04
The sample case is in Preparation; this is not a fixed first-stage rule or actual creation record. A real card shows number and court.
- 02/04
An authorized user manually moves the card to In progress. A successful operation writes status and an activity summary; other screens refresh separately. This illustration performs no actual move.
- 03/04
Entering a hearing date does not move the card automatically. In the example, an authorized user manually selects Hearing; a real deadline badge is not shown on the card.
- 04/04
Decision is flagged closed in this example; its name alone causes no closure. Moving preserves an existing closure time or sets operation time if absent. The sample date proves no actual decision/move; returning to open clears it.
Preparation
The card carries the summary of the file.
Web and mobile cards show case number and court. A detail link also requires full or assigned-case read permission. These examples do not mean the real card contains a deadline badge, lawyer name or client field.
- File number (esas no)
- Court
- Case details when permitted
- Stage-change control with write permission
2026/42 E.
Civil Court of First Instance
The rules of the board
The board shows existing case statuses; moving changes the stored status. Managing the status catalog, reading the board and moving a card require separate permissions.
- 01/06
Stages are your firm’s workflow
A user with catalog-management permission adds and names statuses and sets the closed flag. Columns follow status creation order; dragging columns to maintain a custom order is not provided here. Refresh the board to see catalog changes. See case management.
Web columns use pages of 50 cards and mobile columns 25. Web offers Load more; mobile offers Previous/Next. Paging promises neither unlimited data nor measured latency; records in old/deleted statuses may remain visible even when those columns are not move targets.
Stage names can describe office workflow; a name such as Decision or Closed alone does not define closure behavior. The status closed flag controls it.
- 02/06
Drag and drop plus an accessible Move menu
With permission, drag a web card or select a target from Move; named keyboard controls are provided. Mobile uses the relevant target-stage button. A read-only/blocked company cannot move cards; accessibility and real-device acceptance require separate verification.
- 01/03Drag a web card or use the Move menu
- 02/03Choose an eligible target-stage button on mobile
- 03/03Use keyboard controls; refresh the board after an error or uncertain result
Kanban board - 03/06
What happens in the background when a stage changes
A successful operation writes case status, the closure rule and a safe activity summary in the same transaction. Later reads and external delivery are separate concerns.
- Status is updated · The case takes the target status ID; other lists and users see it through their own queries/refreshes.
- Closing date is written · A closed target preserves an existing closure timestamp or sets the operation time if absent. An open target clears it; this is not a legal finality date.
- Activity log entry · A safe “case stage changed” summary records actor, record and time; a detailed dump of every old/new stage name is not promised.
- Search indexing event is queued · The search update is processed through a durable event; this guarantees neither simultaneous visibility, a new status field nor fixed completion time.
- Webhook delivery is configured separately · A stage move produces a case-update event; it is passed on only to an automatic webhook subscription that the firm enabled in its integration settings for the relevant branch. Delivery is at-least-once and receiver-side acceptance is not guaranteed.
- 04/06
Team view and permissions
Board read/move permissions combine with company, branch and applicable case scope. An assigned-case reader sees scoped cards; full reading from another grant broadens access. Opening details requires the separate case-read permission. See roles and permissions.
- Kanban read
- Sees the board and reviews cards
- Kanban update
- Moves a card to another stage
Review visible cases during a meeting; other users’ screens are not presented as live collaborative editing. Refresh the board for current records. A card does not create tasks automatically; task assignment is separate.
- 05/06
Mobile reading and authorized moves
Board on mobile Mobile board columns are paged. With Kanban read/update permission, current company access and an eligible target, use stage buttons to move; read-only mode disables writes. Detail links support full or assigned-case reading. See mobile app scope.
- 06/06
Kanban or list?
Both read authorized case records through separate queries, paging and filters; they need not show the same card count at every instant.
Kanban board
- See workload and stages at a glance
- Review files one by one in the weekly firm meeting
- Spot where cases pile up
Case list
- Find a specific file with type and status filters
- Scan many records page by page
- Search in detail by file number or court
For the list and the file details see case management software, and for management indicators see reporting.
The board and metrics perform separate reads.
Metrics and reports query case records within current authorization; a move does not atomically refresh every dashboard card. Average closure duration is system creation to closure timestamp, not assumed legal filing/decision duration. See reporting; the distribution below is illustrative.
Dashboard
Stage distribution
- Preparation2
- In progress1
- Hearing2
- Decision1
What do lawyers ask about the board?
Who defines the stages?
Catalog-management permission is required; board reading or moving alone grants no status-definition authority. Statuses become columns in creation order; the closed flag, not the name, controls closure. Refresh the board.
Can I move a card without dragging it?
Yes. Web has a Move menu and keyboard controls; mobile has eligible target-stage buttons. Moving requires update permission and a writable company; read permission alone cannot move.
What happens when a case closes?
A closed target preserves the closure time or sets operation time if absent. Returning to open clears it. The case is not deleted; an activity summary is written and search processes the queued event. This is neither legal finality nor instant refresh of every screen; the case list queries separately.
Can cards be moved on mobile?
Yes. Mobile stage buttons use Kanban read/update permission, current writable company access and an eligible target. Mobile is not limited to read-only use; real-device acceptance requires separate verification.
Who can see the board and who can move cards?
Kanban read opens the board; Kanban update enables moving with a writable company and eligible target. Company/branch/assigned-case scope remains. Case details require full or assigned reading; defining statuses requires catalog management. See roles and permissions.
Is there a limit to the number of stages, and does a crowded column slow the board down?
Columns follow creation order; no custom column ordering or unlimited-stage/performance guarantee is made. Web uses Load more pages of 50 cards and mobile Previous/Next pages of 25; measured performance acceptance is separate.
- Case management · the file behind the card: parties, hearings, notes, deadlines and activity.
- Reporting and dashboard · case indicators and the average case duration come from the same data as the board.
- Mobile app · read the board on your phone and use stage buttons with permission, company access and an eligible target.