AI in local government6 min read

Mailroom automation in public administration: how it works

Contents

Mailroom automation in a public administration means that every incoming item exists as a file, is assigned to the responsible department and waits there as a task in exactly one target system. Five steps get you there:

  1. Choose one Vorgang: one intake, one task, one destination, such as the letters the Poststelle (the mailroom) distributes to departments by hand today.
  2. Make the intake digital: paper post is scanned; email, uploads and specialist systems already deliver files.
  3. Write down who is responsible: the departments or case types an item can be assigned to, with examples for each.
  4. Fix the target system: the DMS where the task is created, through an interface that already exists.
  5. Hand over the assignment: an AI employee assigns each item and creates the task. When it is unsure, it hands the case to a person.

Scanning alone does not digitise the mailroom

Many projects stop where the letter sits as a PDF in a folder or an electronic file. The real work remains: someone reads every item, decides which department is responsible and forwards it. That assignment stays manual work, every day.

The mailroom is digital only when the item arrives as a task in the responsible department. Scanning is the first step, not the result.

One Vorgang is the right place to start

A Vorgang is everything that arrives daily, answers the same question and lands in the same system. For incoming post, the question is usually: which department is responsible?

Starting with one Vorgang means the result can be measured with one number. A second intake channel or a second decision rule becomes its own Vorgang with its own measurement, not an extension of the first.

Who does what in a digital mailroom

The Poststelle stays, the DMS stays, responsibilities stay. The only change is who makes the assignment.

WhoTask in the digital mailroom
Poststelle (mailroom)opens, scans and checks completeness, as today
AI employeereads the item, recognises sender, date and file reference, assigns it to the department and creates the task in the DMS
Fachbereich (department)works the case, decides on the matter and resolves the cases the AI employee hands over
IT or data centreprovides access to the target system: standard API, watch folder, sFTP or email
Agentivobuilds the AI employee in the first two weeks and then operates it: monitors, corrects, takes responsibility

What the AI employee does with an item

For every item, the AI employee follows the same sequence:

  1. It reads the document and recognises sender, date, subject and, where present, the file reference.
  2. It assigns the item to a department.
  3. It creates the task in the target system, with the recognised details as metadata.
  4. It records the assignment with timestamp and reasoning in the decision log.

When its certainty falls below the agreed confidence threshold, it stops and hands the case to a named person. It does not decide on the matter, set deadlines or delete anything.

From scan to departmental task in seven weeks

The Pilotbetrieb, our entry engagement, takes seven weeks. Four of them are productive operation on your real documents.

WeekWhat happens
1Process conversation with the department, define classes, review examples, clarify access
2We build and train the AI employee, set up quality checks and test on real documents
3Acceptance against the agreed hit rate, go-live, handover
4 to 7Productive operation on real volume; we monitor and correct
End of week 7Written evaluation: hit rate achieved, cases processed, time saved

The hit rate is agreed before the start. If it is met, operation begins under a monthly operating agreement that can be cancelled monthly. If it is missed, the Pilotbetrieb ends with no further obligation.

Traceability is part of operation

For a public administration it matters not only whether the assignment is right, but whether it can be explained later: to the leadership, the finance office or an auditor. That is why every operation includes:

  • Operation entirely within the EU, responsibility from Düsseldorf.
  • GDPR-compliant processing with an AVV (data processing agreement) included.
  • A complete decision log available as evidence for EU AI Act audits.
  • A defined human intervention path, documented and triggerable at any time.

The legal bases are Article 28 of the GDPR for the AVV and the EU AI Act, Regulation (EU) 2024/1689.

Which internal instruction your organisation issues for a digital mailroom, and what your data protection officer reviews, is your decision. We provide the AVV and the log for it.

Frequently asked questions

Does the AI employee replace the Poststelle?

No. Opening, scanning and checking completeness stay in the Poststelle. The AI employee takes the next step: it reads the scanned item, assigns it to the responsible department and creates the task in the DMS. The people in the mailroom stop distributing post by hand and only resolve the cases the AI employee hands to them.

Which post is a good place to start?

Post that arrives every day, raises the same question and lands in the same system. A typical start is the letter post of a central mailroom that is distributed to departments by hand today. What matters is a manageable list of classes with examples. Special cases such as invoices or citizen enquiries become separate Vorgänge later, each with its own hit rate.

How does the AI employee reach our DMS?

Through access that already exists: a standard API, a watch folder, sFTP or email. It writes into exactly one target system, for example d.velop documents, and nowhere else. Custom development against a legacy system does not belong in a Pilotbetrieb. We agree the right interface with your IT or data centre in the first week.

How do you measure whether the assignment is right?

With the hit rate: the share of items the AI employee assigns correctly. It is agreed before the start and tested at acceptance in week three, on real documents. In weeks four to seven we keep measuring on real volume. The Pilotbetrieb ends with a written evaluation of the hit rate achieved, cases processed and time saved.

What happens after the seven weeks?

If the agreed hit rate is met, operation begins under a monthly operating agreement that can be cancelled monthly. We keep monitoring the AI employee, correct it when responsibilities change and take responsibility for the result. If the rate is missed, the Pilotbetrieb ends with no further obligation. The price is settled beforehand either way: fixed price, agreed before we start.

The next step

If your Poststelle distributes incoming post to departments by hand today, that is the Vorgang for a Pilotbetrieb: one intake, one task, one destination. Fixed price, agreed before we start. Seven weeks, four of them productive operation on your real documents.

Request a Pilotbetrieb

← Back to insights