Elections, digitalization & the state
Saying that the system for elections will not be ready in time can sound like a threat to voting itself. In fact, several layers need to be separated: who manages candidate lists, how results are transmitted, which law governs the elections and which legacy procedure remains available.
1. What the evidence shows
In 2026, the Ministry of the Interior proposed postponing the launch of selected public-administration information systems for elections. The new deadline is tied to the first nationwide elections held after 1 January 2028.[1]
The Ministry’s statement describes a postponement of the digital components, not the abolition of the legal framework for elections. Until the new systems are introduced, elections will be organized through existing procedures and institutions.[1][2]
The official election portal separately publishes timetables, candidate information, guidance and results for each type of election. The status of one IT component therefore cannot be equated with the status of the entire electoral process.[2]
2. How to read the claim in context
A postponement may reduce the risk of putting an untested system into live operation while also increasing costs or extending dependence on the old process. Without knowing the state of readiness, acceptance-test results and remedial measures, it is impossible to determine which effect will prevail.
The most important operational question is not merely the launch date. It is the contingency plan: what happens during an outage, who decides to revert to the old system, how data integrity is verified, and whether municipalities have practiced the procedure.
Political accountability requires the subject of the postponement to be specified precisely. Saying “the election system is not working” is too broad if only certain digital modules are affected; it would be equally inaccurate to claim that the postponement has no impact.
- The Ministry officially proposed a new deadline for selected systems.
- The lawful conduct of elections is not identical to deploying ISSV.
- Existing processes will be used until the change.
- The current technical readiness of each module without test results.
- The final additional cost of the postponement.
- Whether all conditions for the new deadline will be met.
3. Five questions to ask
- Which specific modules are being postponed?
- Which steps remain in the old process?
- What were the results of the security and acceptance tests?
- What are the budget, schedule and accountable owner?
- Is the backup procedure documented and rehearsed?
4. Conclusion
Postponing ISSV is not postponing democracy, but neither is it an insignificant IT detail. Trust can be maintained only through a precise list of affected functions, a verified backup process and a publicly scrutinized plan for meeting the new deadline.
— Jiný Kontext