On 8 October 2026 the Diia press service announced that drivers can file a Europrotocol, the joint statement for a minor road accident, entirely in the Diia app, according to Interfax-Ukraine. There is no call to the patrol police and no paper form. It is a small feature, and it shows a lot about how digital public services should be designed.
What actually changed
A driver opens the app and goes to Services, then Driver, then Europrotocol. Driver, vehicle and insurance details are pulled automatically from state registers. The driver enters the circumstances and uploads photos of the damage. The second driver joins through a QR code or an in-app notification, and both sign with Diia's electronic signature. The completed form goes to the Motor Transport Insurance Bureau of Ukraine (MTIBU), which is expected to forward it to the insurers, and the drivers then contact their insurer for next steps.
The legal groundwork came earlier. On 11 December 2025 the government adopted a resolution allowing the full Europrotocol cycle to run inside Diia. Prime Minister Yulia Svyrydenko said drivers would be able to record an accident immediately at the scene. The government's notice said the service would be operational in the first quarter of 2026. Per the Interfax report, it reached users on 8 October 2026, roughly two quarters later than announced.
The case for caution
The strongest argument against a feature like this is about fraud and fairness. A paper Europrotocol already depends on both drivers agreeing, and a phone-based version makes it faster to submit a staged or exaggerated claim. An officer at the scene is also an independent witness, and some drivers, particularly in a country at war with stressed insurers and strained police, may feel pressured to sign something they do not fully understand. Moving a government-adjacent workflow into one app also concentrates risk: an outage or a compromised account affects everyone who relies on it.
Those concerns are serious, and the design addresses most of them reasonably well.
Why the design is proportionate
The service is deliberately narrow. According to the Interfax report, it applies only when no one is injured, only two vehicles are involved, neither driver is under the influence of alcohol or drugs, both have valid compulsory motor insurance, and both agree on how the accident happened. Anything outside that box falls back to a paper form or the police. That is the right way to regulate a new channel: the state does not try to adjudicate disputes in software, it only removes friction where the parties already agree.
The fraud-resistance comes from identity and data rather than from surveillance. Both drivers must have verified identity documents, a driving licence and a vehicle registration in Diia, and each vehicle needs a valid policy. Vehicle and insurance data are filled from registers, so neither driver can mistype a plate or a policy number. The government itself said the change would remove data-entry errors that could lead to insurance payouts being refused and reduce the load on the police. Neither claim is yet backed by published figures, and the government gave none, so those benefits remain plausible rather than demonstrated.
Why it works here
This feature is cheap to add because Diia already exists as an identity and documents layer. The app had passed 21 million users by October 2024, according to then-minister Mykhailo Fedorov, so the registers, signature and verified documents were already in place. The Europrotocol adds a workflow on top. That is the pattern worth copying elsewhere: build a trusted credential and a set of interoperable registers once, then let each new service be a thin layer instead of a new system.
The design also keeps the market in the loop. MTIBU and the insurers remain the ones who process and pay claims. The state supplies identity, registry data and a signature, and private insurers still do the underwriting. This is closer to a public utility than to a state takeover of insurance, and it leaves room for competition on claims handling, which is where customers actually feel quality.
What to watch
Three things will decide whether this is a model or a footnote. First, uptake: nothing published shows how many drivers will use it, and the registration prerequisites (tax number, ID, licence, vehicle certificate all verified in Diia) may exclude drivers who have not set up the app fully. Second, insurer behaviour: if insurers treat app-filed reports with more suspicion than paper ones, drivers will go back to paper. Third, dispute handling: the form only works when the parties agree, so the quality of the fallback path matters as much as the headline feature.
The reasonable test is simple. If accident reports filed in Diia are paid as fast as paper ones, with no rise in contested claims, the feature has earned its place. If not, the narrow eligibility rules mean the downside is limited, because drivers can always go back to the old process.
For other governments, the lesson is that digital services need less ambition than they usually get and more plumbing. A well-scoped feature, built on registers that are already trusted and an opt-in process that fails safely to paper, does more for citizens than a sweeping new mandate.