The routine work of a bailiff office, handled

LexIndex calculates deadlines and answers questions from your case files. You make the decisions. Your files stay on a server in your office.

Arrange a call See it in practice

Your office knows these problems well. And pays for them

Files pile up, deadlines run, and the responsibility always lands on the bailiff. Every one of these problems costs your office money, every month, whether anyone counts it or not. Here is how LexIndex takes each one off your desk.

20-year-old software your staff fight with every day

Endless windows, tabs and forms. Every piece of information buried several clicks deep. New staff take a long time to learn it, and experienced staff still lose time to it every day.

You pay full salaries for hours spent clicking.

How LexIndex solves it

Your system stays. The struggle goes.

LexIndex connects directly to the case system your office already uses and reads the cases itself. Staff stop clicking through windows and tabs. They pick a case and ask in Polish, the way they would ask a colleague.

See it in practice

  1. The same file, read over and over

    The creditor calls. The debtor calls. Each time someone stops working and digs through the file to answer one question.

    Paid hours, spent searching instead of moving cases forward.

    How LexIndex solves it

    Ask instead of digging through the file

    LexIndex reads the case file as specific facts: titles, debtors, seizures, deadlines. Asked what was seized and when, it answers directly, and shows the page of the file behind every fact.

    See a sample answer

  2. A missed deadline has real consequences

    Complaint periods, service dates, next steps. Counted by hand, across many cases at once. One slip is enough.

    One missed date can mean a complaint, a lost action and liability.

    How LexIndex solves it

    Deadlines calculated, basis in plain view

    The system calculates the deadline from the dates in the file and shows where it comes from: the service date, the length of the period and the provision. Nobody counts by hand, and the bailiff sees what the result rests on.

    See a deadline calculation

  3. Every mistake is the bailiff’s, personally

    A wrong letter, a badly grounded action, a complaint. That responsibility cannot be pushed onto the software or the staff.

    Damages for a faulty action can come out of the bailiff’s own pocket, with a disciplinary case on top.

    How LexIndex solves it

    Nothing that is not in the file

    Information without a source does not make it into the answer. If something is not in the file, LexIndex says so plainly instead of guessing. Every night, answer quality is checked against your own cases, on the server in your office.

    How sources work

  4. When an experienced clerk leaves, the knowledge leaves too

    New staff learn from the few colleagues who remember similar cases. Without them, the office slows down.

    Months of paid training, and your best people pulled off their work to give it.

    How LexIndex solves it

    The office’s experience, open to everyone

    Similar-case search and case summaries for all staff. A new colleague does not have to wait for someone to find time to explain how the office handled similar cases.

    See example questions

  5. An inspection means rebuilding history from memory

    Who did what in the case, and when? Instead of a ready answer: gathering documents and reconstructing events.

    Days of staff time on every inspection, and the risk of a finding.

    How LexIndex solves it

    An audit log that keeps itself

    Every query, permission change and generated output goes into a signed log on the server in your office. For an inspection or a DPO question, an export is enough.

    See the audit log

  6. Modern tools are off-limits to your office

    Cloud services and AI assistants send files to outside servers, often outside the EU. Professional secrecy does not allow it.

    Other businesses get faster every year. Your office keeps paying for manual work.

    How LexIndex solves it

    Modern tools, without giving up your files

    Your case files, the index and the audit log stay on the server in your office. Answers are produced there too, or on our own server in Germany, depending on what your office needs. That server keeps nothing and never trains on your data.

    How we protect data

Arrange a call

Made for the bailiff's office

A member of staff picks a case and asks a question in Polish, the way they would ask a colleague.

  • It works directly with the case management system your office already uses. Nothing has to be re-entered.
  • It knows enforcement terminology: enforceable titles, seizures, complaint deadlines.
  • It answers in Polish and refers to the documents in the file.

For a profession in which confidentiality is a duty.

Currently: preparing a pilot in the first office.

Example questions

Czy prowadziliśmy już podobną sprawę?

Have we handled a similar case before?

Streść tę sprawę na jutro.

Summarise this case for tomorrow.

Kiedy mija termin na skargę?

When does the complaint period end?

Co zajęto i na podstawie jakiego tytułu?

What was seized, and under which title?

Czego brakuje w aktach?

What is missing from the file?

Questions a member of staff might ask.

Keeping data private is not enough

Plenty of tools now promise to keep the data inside the office. That part is no longer hard.

What offices usually get, though, is a general-purpose document assistant. It answers fluently and confidently, and it can state things that are not in the file.

A bailiff signs every action. A wrong answer is as serious a risk for the office as a data leak.

A typical document assistant

Does the debtor own any real estate?

Yes. Besides the flat already in the file, the debtor owns a plot near Gdańsk, land register GD1G/00041207/3.

No source. This cannot be checked.

Every answer has a source

LexIndex knows how a bailiff's office works. It reads a case as specific facts (titles, debtors, seizures, deadlines) and links each one to the page of the file it comes from. Language models do the reading; LexIndex decides what counts as an answer.

Not just the document. The exact entry in the file.

Sample answer. Synthetic case KM 412/26.

Who is the debtor, what has been seized, and when does the complaint period end?

Every fact opens its page in the file.

Nakaz zapłaty z klauzulą wykonalnościp. 2

Sąd Rejonowy Poznań-Grunwald i Jeżyce nakazuje, aby pozwany Marek Zieliński zapłacił powodowi kwotę wskazaną w pozwie wraz z odsetkami.

Every fact opens its page in the file.

Zawiadomienie o zajęciu wynagrodzenia za pracęp. 1

Na podstawie art. 881 k.p.c. dnia 21 października 2026 r. dokonuję zajęcia wynagrodzenia za pracę dłużnika do wysokości egzekwowanego świadczenia.

A calculation shows its basis.

Basis of the calculation§

  • Notice of the seizure served: 23 October 2026
  • Complaint period: 7 days from service
  • Art. 767⁴ § 1 k.p.c.

Ends 30 October 2026

Not recorded does not mean it does not exist.

The whole file was read. It contains no information about other accounts, and LexIndex reports exactly that.

No source, no answer.

Left out. No page in the file confirms this, so it does not appear in the answer.

Quality checked on site

Every night the system checks the quality of its answers against your own cases, on the server in your office. Only the resulting figures leave the office.

Your files stay in your office

A bailiff's office handles some of the most protected data in Poland: debtors' finances, addresses, enforceable titles, seizures. Most modern software wants that data in someone else's cloud. LexIndex keeps it where it is.

Tajemnica komornicza
The bailiff is personally responsible for any information that leaves the office.
GDPR
Case data is personal data, mostly about people who never agreed to share it.
US CLOUD Act
A US provider can be required to hand data over, even when it is stored in the EU.
Sample case file. Synthetic data.

Where answers are produced

Your office decides, depending on its needs. We agree it before installation.

  • On the server in your office

    Everything happens inside the office. Nothing about a case leaves the building, and LexIndex keeps working without an internet connection.

  • On our own server in Germany

    Only the question and the passages needed for one answer travel there, encrypted. The server keeps nothing once the answer is returned and never trains on your data.

What stays, what travels, what is never sent

Stays in your office, always

  • Case files and scans
  • Data from your case system: debtors, creditors, amounts
  • The search index
  • Encryption keys
  • Staff accounts and the audit log

Travels for one question, then deleted

Only if your office uses our server in Germany. Encrypted on the way; kept only while the answer is prepared.

  • The question
  • The passages from the file needed for the answer
  • The answer, on its way back

Never sent

  • Whole case files
  • Lists of debtors or creditors
  • Anything a model could learn from

Four guarantees, each enforced by how the system works, not only by a clause in a contract

  1. 01

    Files are stored only in the office

    Case files, the index and the audit log are kept only on the server in your office. The system will not connect to any provider outside an approved EU list, and no US-controlled provider can be on that list.

  2. 02

    No access from outside

    The server opens an encrypted connection to us itself; nobody can connect to it from outside. Updates are versioned and rolled out in stages. The server holds no credentials that could change its software.

  3. 03

    We do not see case content

    Nobody at LexIndex sees the content of files or questions. Our monitoring receives only technical information about how the system is running. Three independent mechanisms enforce this.

  4. 04

    The office stays in control

    Each office has its own signed licence and its own server. If you leave, your office exports what it needs to keep (audit log, reports, summaries); we collect the server and erase it, confirmed by a certificate.

Who builds LexIndex

The team combines years of work in bailiff offices with experience building systems where an error or a data leak is not an option.

The server in your office is built on the same principles: minimal permissions, signed updates, nothing trusted by default.

Bailiff offices
Years of work in Polish bailiff offices, on the cases, files and deadlines LexIndex works with.
Payment systems
Settlement systems in which every transaction has to reconcile.
Key protection
Systems in which losing a key means losing the funds.
Critical infrastructure
Platforms that have to stay available without interruption.

How getting started works

  1. 1

    A 30-minute call

    We show the system on a synthetic sample file and answer your security questions. A mutual non-disclosure agreement is signed before anything specific to your office is discussed.

  2. 2

    Server installation

    A single sealed, rack-mounted device, included in the subscription. Your IT technician installs it, connects power and network and allows its outgoing connection: about two hours of work. We do the rest remotely.

  3. 3

    Files indexed on site

    Documents are indexed where they are. Before the whole office uses the system, we check its answers against questions your office prepares.

  4. 4

    In use after about a week

    Answers with sources, case summaries and similar-case search for all staff in the office.

LexIndex

One subscription per office

Included: the server in your office, processing on our server in Germany if your office uses it, software and updates, technical support and audit documentation for your supervisory authority.

  • No setup fee
  • No separate hardware costs
  • No integration project
  • No per-question charges
  • First three months at a reduced price
Arrange a call

Frequently asked questions

How much does it cost?

One monthly subscription per office, with no setup fee, no separate hardware costs and no per-question charges. The first three months are at a reduced price. We give the exact price for your office on the call.

What about our current system?

It stays. LexIndex connects to the case system your office already uses and reads the cases from it. Nothing is replaced and nothing has to be re-entered.

Who at LexIndex can access our data?

By default, nobody. Our monitoring receives only technical information, never the content of files or questions. A support session requires your consent, is time-limited and is logged on your server under the name of the support engineer.

Where are answers produced?

On the server in your office, or on our own server in Germany, depending on what your office needs. Either way, case files, the index and the audit log stay in your office, and our server keeps nothing after an answer.

Is each office kept separate?

Yes. Each office has its own server, its own index and its own audit log. Case data is never combined.

Does it work without an internet connection?

Yes. Search, reading files and the audit log work fully offline. If your office uses our server in Germany, new answers wait until the connection is back.

What happens when the answer isn't in the file?

LexIndex says so plainly. Missing information is shown as missing, and information without a source is left out rather than guessed.

Can our data protection officer review the setup?

Yes. Before go-live we make the configuration, retention rules, list of sub-processors, audit log and DPIA worksheet available for review.

What if a sub-processor changes?

We give 30 days’ notice. If your office objects, the contract lets you leave without penalty.

What happens if we cancel?

Your office exports what it needs to keep: audit log, reports, summaries. We collect the server and erase it permanently, confirmed by a certificate. We hold none of your case data, so there is nothing to delete on our side.

Security information