Government Services Portal with Five-Agency Integration
Citizens visit 3–5 agencies for a single permit, collecting dozens of certificates. We explain why a 'one-stop shop' doesn't solve the problem and how to build real inter-agency integration — from 3 weeks to 2 days.
A typical situation: to obtain a single permit, a citizen visits 3–5 agencies with a folder of paper certificates, spending 2–3 weeks. Each agency works in its own system and won’t accept colleagues’ data without paper confirmation. The data exists in the systems — but without a stamp, nobody trusts it.
Why a ‘one-stop shop’ doesn’t solve the problem: the standard first attempt is a physical service center. Applications are accepted in one place, but sent to agencies by courier. Each agency does its own check, results are assembled manually. Time drops from three weeks to two — progress, but not a breakthrough. The substance doesn’t change: agencies don’t share data electronically. A tax authority certificate is printed and carried to the cadastre.
Our approach to this challenge: the technical part — integration bus, standard APIs, portal with personal accounts — takes roughly 30% of the effort. The other 70% is organization. We create the ‘room’ — a weekly meeting of agency representatives, where decisions are made: who provides which data, in what format, with what legal standing. This is hard work — every agency protects its territory. The turning point comes when the first 2–3 services launch on pilot and citizens start leaving positive reviews. After that, the remaining agencies connect significantly faster.
The practical outcome: average service delivery time drops from three weeks to two days. Citizen satisfaction grows from 23% to 78%. But the main result — the infrastructure created: the integration bus and API standards that allow connecting new services in weeks, not months. This is a platform that scales.
Typical Problem
A typical picture: to obtain a single permit, a citizen visits 3–5 agencies, collects 8–12 certificates, and spends 2–3 weeks. Each agency works in its own system, requires paper confirmations from others, and doesn't trust third-party data. The data exists in the systems — but without a paper copy, nobody accepts it.
Why This Happens
The standard first attempt — a physical 'one-stop shop': the service center accepts applications, but sends them to agencies by courier. Time is cut by a day or two, but the substance doesn't change. Each agency insists on its own forms, checks, and stamps. The root cause — agencies don't share data electronically. No common identifiers, no exchange standards, no regulation for inter-agency interaction in electronic form.
How We Diagnose It
The inter-agency integration problem is 80% organizational and 20% technical. Agencies have information systems with data. But each considers its own data the only valid source and won't accept colleagues' data without paper. The technical barrier — absence of common identifiers and exchange standards. The organizational one — lack of trust. Our approach: we begin by creating a 'room' — a regular meeting of representatives from all agencies, where decisions are made: who provides which data, in what format, with what legal standing.
The Right Model
An integration platform (data bus) between agencies with legally significant exchange: (1) unified citizen authentication via OneID, (2) standardized APIs for inter-agency requests, (3) electronic signatures for legal validity, (4) portal with citizen personal account. Launch — with 2–3 simple services, then scale.
How We Implement It
We design and implement the inter-agency integration bus, standardize services for the first phase, develop the portal with personal accounts, integrate OneID for authentication and digital signatures for signing. We launch a pilot with 2–3 services, demonstrate results, then scale. In parallel, we organize the 'room' — a weekly meeting of representatives from all agencies to resolve disputed questions. Without this 'room,' the project gets stuck in inter-agency approvals. A typical project takes 8–10 months.
How the Team Works
Projects like this run with a team of 9: 4 developers, 2 integration engineers, 1 architect, 1 business analyst, 1 project manager. I lead the integration platform architecture, API standards, and inter-agency coordination. The team implements integrations, the portal, tests, and documents.
Results
If agencies don't trust each other's data without a paper certificate — technical integration won't help. Start by organizing a 'negotiation room' between agencies. This will take more time than development — and that's the right priority.
Key Lessons
- • If you're planning inter-agency integration — allocate 70–80% of effort to organizational work, not code.
- • The 'room' for weekly resolution of disputed questions between agencies is a mandatory project element — without it, approvals will stretch on for years.
- • Start with 2–3 simple services and demonstrate results — this is the only approach that works in the public sector. After the first positive citizen feedback, other agencies connect faster.
- • Electronic signatures solve the trust problem between agencies — this isn't bureaucracy, it's a necessity for legally significant exchange.
Similar challenge?
Tell me what's going on. I'll review the situation and suggest a concrete path forward.
Обычно отвечаю в течение нескольких часов