AI in local government6 min read

Digital mailroom: what must be in place before AI

Contents

A digital mailroom is the process that captures incoming post, assigns it to a department and files it as a task in exactly one target system. This page is about letters and documents, not parcel tracking for office deliveries. Only once this process exists can an AI employee take over the assignment. Four things must be in place first:

  1. An intake that makes every item available digitally (scan, email, upload, specialist system).
  2. A list of classes: the departments or case types an item can be assigned to.
  3. A target system where the task lands (DMS, specialist system, ticket system), with an interface that can create tasks.
  4. A rule for unclear cases: who decides when the assignment is unclear, and where that is recorded.

The Poststelle has to exist before AI can sit on top of it

The Poststelle, the team and process that opens and distributes incoming post, comes first. An AI employee classifies. It does not invent departments, it does not build a target system and it does not settle what happens in a doubtful case. Everything it does assumes a process that already runs without it, only slower and with more manual work. Where that process is missing, the project fails not on the AI but on the data and on unclear responsibility.

That is why every Pilotbetrieb, our fixed-price entry engagement, starts with a conversation about the process, not about technology. In the first week the Fachbereich, the department that owns the work, answers questions: What arrives? Where does it belong? Who says so today? What happens when it is unclear?

German federal law sets the same order. Section 9 of the federal E-Government Act (EGovG, German text) says federal authorities should document, analyse and optimise procedures that become largely electronic for the first time, before the IT systems are introduced.

The four building blocks in detail

Building blockWhat must be in placeHow you can tell it is missing
IntakeEvery item exists as a file: scanned, as an email attachment, by upload or from a specialist system.Paper is distributed before it is scanned; scans end up in personal mailboxes.
ClassesA written list of departments or case types, with examples for each class.The assignment lives in the head of one person in the Poststelle.
Target systemExactly one system where the task is created, and an interface for it: standard API, watch folder, sFTP or email.The same case is maintained in two systems; tasks are created by forwarding.
Unclear casesA named person in each department who resolves unclear cases, and a place where the resolution is recorded.Unclear post sits in a pile or goes round the office.

How the list of classes becomes an assignment at department level is covered in our page on document classification. How the task arrives in the target system is shown in the incoming mail workflow in the DMS.

Not all incoming post at once

The most common mistake is trying to digitise all of an organisation's incoming post in one step. One Vorgang (one intake, one task, one destination) is enough to start. That is everything that arrives daily, answers the same question and lands in the same system. A second intake channel or a second decision rule belongs in a second Vorgang, not in the first.

The boundary has a reason. Only a single-stage Vorgang can be measured against a hit rate agreed before the start. With an assignment into two systems, or with branching, there is no longer one number on which acceptance and operation can rest.

How a public administration starts with this one Vorgang is described in our page on mailroom automation. How a single item then moves through digital incoming mail in five steps is a separate page.

What the AI employee does, and what it does not do

In operation, the AI employee captures the incoming document, assigns it to the department, creates the task in the target system and hands cases below the confidence threshold to a person. Every assignment is recorded with timestamp and reasoning in the decision log.

What the AI employee doesWhat the AI employee does not do
Classify, extract metadata, route, create a taskPost, approve, pay, delete, trigger deadlines
Write into exactly one target systemWrite back into a second system
Hand unclear cases to a person and log itSettle unclear cases on its own

How a digital mailroom is set up in seven weeks

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

The Pilotbetrieb has its name because it runs productively on real documents from week three. If the agreed hit rate 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.

Frequently asked questions

Do we need a document management system or digital mailroom software first?

No, but you need a target system. That can be a DMS, a specialist system or a ticket system. What matters is that the task can be created there, through an existing interface, a watch folder, sFTP or email. Custom development against a legacy system does not belong in a Pilotbetrieb.

What happens to post the AI employee cannot assign?

It goes to a person. A confidence threshold is agreed before the start. When the AI employee's certainty falls below it, the AI employee stops, hands the case to the named person and logs why. Nothing sits in a pile, and nothing unclear is settled automatically.

Where are the documents processed?

Operation runs entirely within the EU, with responsibility from Düsseldorf. Processing is GDPR-compliant, with an AVV (data processing agreement) included. A complete decision log is available as evidence for EU AI Act audits, and a defined human intervention path is documented and triggerable at any time. Which internal instruction your organisation issues for it is your decision.

How much volume does a Vorgang need to be worth it?

Enough that the assignment keeps someone busy every day today. The hit rate is measured on real documents, so the four productive weeks need enough cases to give a reliable number. We agree the exact figure in the process conversation in the first week.

Can we extend the Vorgang later?

Yes, as a second Vorgang. A second intake channel, a second target system or a branch is not added to the first Vorgang. It is set up as its own Vorgang with its own hit rate. That way every Vorgang stays measurable, and acceptance and operation keep resting on one number each.

The next step

If your incoming post is distributed by hand every day, that is the Vorgang a Pilotbetrieb starts with: 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