Legal Data Tech
DEPLAW

Automation & AI

Workflow Batch Processing

A workflow no longer starts case by case, but for thousands of filtered case files at once – with a preview before the start and live monitoring during processing.

DEPLAWapp.dep.law
Batch running · Dunning run stage 2487 case files
Overall progress73%
354
Completed
131
Running
2
Errors
Live logReal-time
INK-2024-1847 · Workflow started · filing generated09:14:32
INK-2024-1923 · beA dispatch initiated09:14:33
INK-2024-2001 · Running · waiting for filing09:14:34
INK-2024-1102 · Error: opposing party address missing09:14:35
Started 09:14:20 · ~2 min remainingCancel

Instead of triggering every case individually, DEPLAW starts a workflow for thousands of case files in a single batch run – precisely filtered by case status and additional conditions, manually reviewed before the start, and monitored live during processing. For orchestrated mass procedures such as dunning runs or deadline waves, this is the difference between manual work and a controlled, repeatable process.

Filtering Instead of Starting Blanket

The batch begins with selecting the case status, for example only running cases – closed or paused case files are excluded from the outset. Further conditions can then be stacked on top: the name of a stored follow-up reminder, specific placeholder values, or a combination of both. An optional limit caps the maximum number of cases, for example to first test a new batch on 50 or 200 cases before rolling it out to the full portfolio.

The Preview as a Checkpoint

Before actual execution, DEPLAW outputs the complete list of every matched case file with ID, description, and status. This preview is not an optional intermediate step but the decisive safety checkpoint: only after manually confirming that the filter conditions apply exactly as intended does the batch actually trigger – a case included by mistake can no longer be undone afterward.

Tracking Mass Processing in Real Time

Once started, DEPLAW processes all cases in parallel. A progress bar continuously shows how many case files are completed, in progress, or still pending, while a live log records every single action – including exceptions when a case’s status has changed in the meantime. The entire batch can be paused or stopped at any time; cases already processed remain in their completed state.

01

Filter cases by status

The batch specifically includes or excludes cases that are running, closed, waiting, or canceled — every non-matching case file is left untouched.

Running · Closed · Waiting · Canceled

02

Combine additional conditions

The name of a stored follow-up reminder or specific placeholder values can narrow the result set further, optionally capped by a fixed limit for an initial test run.

Follow-up reminder · Placeholders · Limit

03

Preview before the start

Before execution, DEPLAW lists every affected case file individually with ID, description, and status — the batch only actually triggers after this list has been manually confirmed.

No start without confirmation

04

Monitored and controllable live

A progress bar and a live log show completed, running, and failed cases in real time. The batch can be paused or stopped at any time; cases already processed remain completed.

Pausable · Live log

Example · Dunning run stage 2 · Collections

One workflow for 487 case files, started in four controlled steps.

From defining the filter to the running batch, the entire case volume goes through the same four steps — with one manual checkpoint just before the actual start.

Select case status
Only include running collection cases
Define conditions
Follow-up reminder "Dunning run stage 1" · offen_tage > 60
Check preview
487 case files listed individually, manually confirmed
Start batch
Workflow "Dunning run stage 2" · 15 steps per case
487
Case files in the batch
354 / 487
already completed
2
Errors in the live log

One click, hundreds of case files

487 case files. One batch run.

All matched cases from a dunning run go through the same workflow simultaneously — with live progress instead of individually triggered cases.

Case No.
Parties
Status
Due
INK-2024-1847
Kanzlei ./. Müller, Hans
Workflow started
INK-2024-1923
Kanzlei ./. Schmidt, Petra
beA dispatch initiated
INK-2024-2001
Kanzlei ./. Weber, Klaus
Running
INK-2024-1102
Kanzlei ./. Fischer, Anna
Error · opposing party address missing

See this feature live.

Book a free demo