Skip to main content
civitas.
For Einbürgerungsbehörden (naturalisation authorities)

Digitalisation for your Naturalisation authority.

civitas. reduces processing time, lowers Rückfrage (query) rates, and relieves your Sachbearbeitung (case-handling) team — without intervening in existing Fachverfahren.

−38%
Expected reduction in the follow-up enquiry rate through structured pre-capture
−11%
Projected shortening of throughput time through elimination of Medienbruch (media discontinuity)
admin.einbuergerungsservice.de/dashboard
Dashboard · Musterstadt
Demo client · sample data
Inbox
12
+3 today
In progress
47
6 SB
Ø Duration
14.2Mon
−11 %
Andriy Melnyk
EB-2025-00147 · Ukrainisch · § 10 StAG
New
Al-Hassan family
EB-2025-00138 · 4 Personen · § 10 + § 9
In progress
Maria Kovalenko
EB-2025-00135 · Ukrainisch · § 10 StAG
To the decision
The market context

Six challenges we have identified.

The StAG reform of 27 June 2024 lowered the legal hurdles to naturalisation — without modernising the administrative structures accordingly. The figures below are estimates based on public data from the Statistisches Bundesamt (Federal Statistical Office), media reports, and conversations with Einbürgerungsbehörden (naturalisation authorities).

01 · Volume
+38%

Increase in application numbers since the reform.

The 5-year period and the elimination of the obligation to give up one's previous citizenship have massively expanded eligibility. Municipal authorities report up to 38 percent more incoming applications — staffing capacity is not keeping pace.

02 · Quality
47%

Query rate for traditional applications.

Paper applications and monolingual online forms lead to a follow-up rate of around 47 percent. Each follow-up extends processing time by an average of three to six weeks — and ties up capacity twice.

03 · Language
>70%

Eligible persons whose native language is not German.

Monolingual forms create misunderstandings that come back as follow-up questions. Interpreters are expensive and not always available. The authority bears the cost of a structural language barrier.

04 · Media breaks
Paper

Manual data transfer into the Fachverfahren (specialised case-management system).

Application data is often manually transferred from paper or PDF forms into the specialist system (AKDB, Infoma, in-house solutions). Time-consuming, error-prone, not audit-proof.

05 · External communication
18–24Mon

Processing times publicly discussed.

Local media and municipal political bodies regularly request information about processing times. Without reliable statistics and evidence of optimisation, the administration lacks an argumentative basis for its statements.

06 · Scaling
0new positions

No headcount growth despite rising workload.

Municipal budgets rarely allow new hires in Einbürgerungsbehörden (naturalisation authorities). The only option is efficiency gains — more cases per Sachbearbeiter (caseworker) per month, without loss of quality.

Our answer

How civitas. addresses each of these challenges.

civitas. is not an island solution, but a layer between applicant and your Fachverfahren. The structured intake replaces the informal inbox — without your team having to switch from the tools they are used to.

01

Structured Antragserfassung (application capture).

Addresses: Volume · Quality

83 mandatory questions in 14 thematic sections. Applicants go through a digital wizard with automatic validation. The output is an authority-ready application — complete, formally correct, with all mandatory documents.

In comparable digitalization projects, follow-up query rates drop significantly. The total volume can be processed with the same staffing level.

02

Six languages with German output.

Addresses: Language

Applicants fill out the wizard in their native language — German, English, Turkish, Arabic, Russian or Ukrainian. The authority-ready application is automatically generated in German.

Your case officers continue to work exclusively with German documents. No interpreter appointments, no translation costs.

03

Direct API handover into the specialist case-management system.

Addresses: Media breaks

Structured data is handed over via standardised interfaces to AKDB OK.VORFAHRT, Infoma newsystem, d.velop documents, and FIT-Connect. No manual entry, no double input.

BZR Führungszeugnisse (police clearance certificates) are requested automatically. The file remains fully digital all the way through to archiving.

04

Automatic completeness check.

Addresses: Quality · Scaling

Before handover to your Behörde (authority), civitas. automatically checks: Are all 14 mandatory sections filled in? Are the required documents attached? Do dates and signatures match?

Incomplete applications are returned to applicants before they reach your inbox — with concrete notes on what is missing.

05

Reliable statistics for council, administration and press.

Addresses: External communication

The admin dashboard delivers daily-updated figures: processing times in quarterly comparison, follow-up query rates, team workload, country-of-origin distribution, approval rate.

Exportable as CSV or as a PDF report. A suitable basis for statements to the council, administrative leadership and the public.

06

Transparent team utilization.

Addresses: Scaling

Automatic assignment based on workload (optional), four-eyes principle for rejections, overview of open queries and overdue deadlines. Office heads see the overall picture, Sachbearbeiter:innen (case workers) see their own workload.

Goal: measurably more cases processed per Sachbearbeiter:in (case worker) per month — without extra work, through elimination of redundant steps. Concrete targets are defined in the pilot.

The admin dashboard · Demo scenario

What your team would see daily.

The following depiction shows an example scenario with a fictitious tenant and expected target values. Each municipality is technically its own tenant with isolated data. The interface is intuitive enough that no training is required — and detailed enough for office leadership, caseworkers and IT to find the information they need.

civitas.
Naturalisation authority Musterstadt
Admin portal · demo tenant
SRDr S. Reimer
Overview
Dashboard
Applications
Inbox12
In progress47
To the decision8
Queries5
Archive
Administration
Statistics
Team
Integrations3
Settings
Dashboard
Naturalisation authority Musterstadt · demo scenario · sample data
Inbox+3
12
New applications · awaiting assignment
In progress6 SB
47
Active cases
Ø Duration−11%
14.2Mon
Median Q1 2025
Queries−38%
18%
civitas. vs. 47% total
Priority · To be processed today8 entries
File reference numberApplicantInboxStatus
EB-2025-00147
Andriy Melnyk
Ukrainian · § 10 StAG
18 Feb 2025New
EB-2025-00142
Aylin Yıldız
Turkish · § 10 StAG
16 Feb 2025Query
EB-2025-00138
Al-Hassan family
Syrian · 4 people · § 10 + § 9
14 Feb 2025In progress
EB-2025-00135
Maria Kovalenko
Ukrainian · § 10 StAG
12 Feb 2025To the decision
Target values

The expected effect at your authority.

Target values based on a model calculation using publicly accessible procedural data from comparable digitisation projects in the municipal administration environment. We collect your concrete figures together with you in the pilot project.

Queries
−38%

Expected reduction in the follow-up enquiry rate through structured pre-capture. Measurable in the pilot from week 4.

Turnaround time
−11%

Projected shortening of the average processing time through elimination of Medienbruch (media discontinuity) and structured data handover.

SB (Sachbearbeiter — case worker) throughput
+32%

Expected increase in cases processed per case officer per month — with the same staffing level and the same working hours.

Onboarding
0Days

No structured training is planned. The interface is usable from day 1. Onboarding guide is 2 pages.

Cooperation models

Three ways to introduce civitas.

Depending on the maturity of your digital infrastructure and the available project scope, we jointly choose the right entry point. All three models can later be transitioned to white-label.

01 · Model

Pilot project

Individual municipalities or counties can introduce civitas. as a time-limited proof-of-concept — for one specialist area or a subset of applicants.

Includes onboarding, training of case officers, and accompanying measurement of throughput-time effects over 6 to 12 months. Cancellable after pilot.

Typical duration · 6–12 months
02 · Model

API integration

Integration with existing specialist systems via standardised interfaces. civitas. complements the existing system, it does not replace it — no parallel system, no duplicate data maintenance.

Interoperability with AKDB OK.VORFAHRT, Infoma newsystem, d.velop documents, MACH, FIT-Connect and proprietary specialist procedures is checked in advance.

Typical rollout · 3–6 months
03 · Model

White-Label

Dedicated branded instance for counties, cities or state authorities. The application process runs under the municipal brand, while the technical platform remains civitas.

Suitable for administrations that operate citizen contact points under their own brand but do not want to develop software themselves.

Typical rollout · 4–8 months
Integrations

Interfaces to existing administrative systems.

No island solution, no parallel world. civitas. complements your municipality's existing administrative infrastructure — via standardised interfaces or custom adapters for proprietary specialist systems.

AK
AKDB OK.VORFAHRT

Fachverfahren Einbürgerung (specialised naturalisation case-management system) — adapter for structured application data transfer and a return channel for decisions.

Available
IN
Infoma newsystem

ERP/specialised case systems — adapters for case-number assignment, fee billing and document archival.

Available
FI
FIT-Connect

Central federal gateway for digital administrative services — OZG-compliant application intake.

Available
D.v
d.velop documents

Audit-proof archiving (revisionssicher) — adapter for automatic filing, 10-year retention.

Available
BZR
Bundeszentralregister (Federal Central Register)

Interface for automated request of the extended Führungszeugnis (certificate of good conduct) — issued to the Behörde (authority).

Available
MA
MACH

Enterprise Content Management & Fachverfahren (specialised case-management system) — standard adapter for the MACH-Suite.

Available
eID
eIDAS portal

Qualified electronic signature in accordance with eIDAS — for digital Bescheid (administrative decisions) without paper process.

Q3 2026 planned
CS
Citrix ShareFile

Secure email communication with Antragsteller (applicants) — end-to-end encryption, DSGVO (GDPR)-compliant.

Available
?
Custom adapters

Proprietary Fachverfahren (specialized procedure systems) or in-house municipal developments — adapters are developed during the pilot.

On request
Compliance & security

Framework conditions that apply to you.

Public procurement law, the GDPR and the RDG (Legal Services Act) set clear guardrails for cooperation with a private software company. civitas. is structurally designed for this.

01 · Data protection

Server location Germany.

Exclusively Hetzner Online GmbH in Nuremberg. TLS 1.3 end-to-end, AES-256 at storage level. No data transfer outside the EU. AVV (data processing agreement) under DSGVO Art. 28 (GDPR Art. 28) as standard.

02 · Multi-tenant

Strict data separation.

Each municipality is its own tenant with full isolation. No data mixing, no cross-access, granular role and access rights — auditable via export.

03 · Interoperability

No vendor lock-in.

REST API documented, FIT-Connect integration standard. Export of all data possible at any time — in the XÖV standard format or as JSON. You remain technically sovereign.

04 · Legal framework

No Rechtsberatung (legal advice).

civitas. provides purely technical procedural support. No interpretation of individual cases within the meaning of the RDG (Rechtsdienstleistungsgesetz). Legal assessment and decision remain 100 percent with your authority.

Frequent questions from authorities

What heads of authorities (Amtsleitungen) typically ask.

Answers to the five questions that regularly come up in exploratory conversations. We clarify further topics in personal exchange.

What does civitas. cost for our Behörde (authority)?

The pricing model depends on the chosen cooperation model. In the pilot we charge a fixed project fee plus optional success share; in the long-term license, an annual client fee that scales with application volume. No hidden costs, no per-user billing. Offers are made based on a concrete requirements profile.

How long does the rollout realistically take?

Pilot project 6 to 12 months, API integration 3 to 6 months, White-Label 4 to 8 months. The decisive factor is clarifying the interfaces to your existing Fachverfahren (specialized procedure system) and archiving. We involve your IT department and Datenschutzbeauftragten (data protection officer) from the very beginning.

What happens to applicants who still want to submit on paper?

No one is forced. civitas. complements the existing inbox — the paper path is preserved. Experience shows the share of digital applications grows to 60–75 percent within 12 months without you having to actively steer it.

Do we need our own IT staff for operations and maintenance?

No. civitas. runs as a Managed Service — hosting, updates, security patches, and monitoring are on our side. Your IT department reviews the initial integration; ongoing operation is hands-off. For integration with your DMS, occasional coordination is sensible.

How do our Vergabevorschriften (procurement rules) fit with this?

civitas. is regularly eligible for public procurement (vergabefähig). Pilot projects typically run via municipal Beschaffung (procurement) or via Rahmenverträge (framework contracts). We provide all required documents (Angebotspflicht (offer obligation), Leistungsbeschreibung (specifications), DSGVO compliance, ISG certifications) on request. We cannot provide vergaberechtliche Beratung (procurement-law advice) — that is for your Rechtsamt (legal department).

Get in touch

Exploratory call about cooperation.

In an initial conversation of about sixty minutes, we discuss with you the concrete needs of your authority, the existing infrastructure, and the possible rollout paths. The conversation is non-binding and serves solely to clarify needs. You decide on next steps afterwards.