The difference between “saved” and “submitted” can look like a small interface detail. In an election system, it can decide whether candidates appear on a ballot.
That was the centre of the dispute between the African National Congress and the Electoral Commission of South Africa. Before the 28 August 2026 deadline, the ANC had completed forms, uploaded supporting documents and paid deposits for affected nominations. It had not activated the Online Candidate Nomination System’s Submit as Final function for 181 candidates across six municipalities.
The Electoral Court initially held that the nominations remained provisional without that final action. On 15 October, the Constitutional Court ordered the IEC to include the candidates. The IEC then extended equivalent relief to other parties in the same position.
The timing raises the stakes. South Africa’s local government elections take place on 4 November 2026, the day after this story is published. The court decision therefore landed close to voting day and prompted strong, often emotional public reactions about fairness, deadlines and democratic participation.
This article does not take a position on the ANC, the IEC or the legal outcome. It focuses on the design question exposed by the case: how should a high-stakes system communicate the difference between information that has been uploaded and a submission that has legally taken effect?
This was a legal dispute about what counts as submission under election law. It is also a useful case study in critical UX: the design of a system can give an action operational meaning far beyond the visual weight of a button.
A file can exist without being final
Most digital products have several states: draft, saved, uploaded, validated, submitted and confirmed. Teams understand these distinctions because they built the system. Users often see a completed form and assume the job is complete.
The IEC argued that final submission communicated a party’s definitive choice while lists could still be amended or withdrawn beforehand. The ANC argued that the required information was already in the Commission’s possession and that the legislation did not make the extra click a condition of validity.
Reasonable people can disagree about the judgment. The interface lesson remains useful: when two states have radically different consequences, the difference must be impossible to overlook.
High stakes need stronger feedback
A critical workflow should answer four questions at every stage:
- What is the current status? “Draft saved” and “Submission received” should never look interchangeable.
- What remains to be done? The final action should be visible in the main flow, with the deadline and consequence stated in plain language.
- Did the action succeed? A final submission needs a durable receipt, timestamp, reference number and confirmation sent through another channel.
- How can failure be recovered? Timeouts, expired sessions and incomplete records need safe recovery paths that preserve work and explain the next step.
Warnings alone are not enough if they sit outside the user’s immediate task. Training also cannot carry the whole burden. A system used under deadline pressure must communicate its own state clearly.
Design for the final hour
The closer a workflow gets to a deadline, the less attention people have available. They may be switching between documents, resolving errors, coordinating with colleagues and working across many records at once.
Good design anticipates that pressure. It can group incomplete submissions, show a persistent count, prevent users from leaving a near-complete record without a clear warning and offer a final review screen that distinguishes uploaded information from officially submitted information.
For administrators, the system should provide an audit trail that is understandable before a dispute reaches court. For users, it should provide the same certainty in simpler language.
The interface is part of the institution
Public-service software is not a neutral layer placed on top of policy. It is where people encounter the policy. A hidden state, ambiguous label or weak confirmation can become a barrier with real legal, financial or democratic consequences.
That does not remove responsibility from the organisation making the submission. It does raise the standard for the organisation designing the process. The more serious the consequence, the clearer the state, feedback and recovery must be.
The ANC–IEC dispute is a reminder for every bank, university, insurer and government department: if one final action changes everything, design the entire journey so nobody can reasonably mistake “almost done” for “done.”
Designing a high-stakes service or submission flow? Talk to Clekzo Studio about making status, confirmation and recovery clear.
