← Back to work

Auditability and voting integrity

VOX Electoral System

Design a voting flow where traceability, transactional safety, and product clarity reinforce each other from end to end.

Open live project
RoleProduct architecture, backend design, audit-oriented modeling
TimelineIndependent public case
StackAngular / NestJS / PostgreSQL

Auditability and voting integrity

VOX was conceived as an institutional voting platform where every critical interaction needed explicit state handling, auditable decisions, and confidence under concurrent access.

The work focused on translating trust requirements into domain rules, persistence strategy, and user feedback that kept the flow legible without making it feel bureaucratic.

500+Concurrent users
100%Vote trail coverage
0Ambiguous flow states

Editorial reconstruction of the platform logic, emphasizing election state, trust checkpoints, and operator visibility.

System view

Audit-first election flow

Structured states, transaction checkpoints, and traceable actions.

Operator view

Clear feedback under load

System signals designed to reduce ambiguity during critical windows.

Reliability view

Trust expressed as data lineage

Every relevant transition leaves an explainable footprint.

Challenge

Voting systems fail when correctness is implicit. The challenge was to make integrity visible in both architecture and experience.

Each state transition needed to be deliberate, recoverable, and explainable to operators and users.

Constraints

  • Institutional trust requirements.
  • Concurrent access during critical voting windows.
  • Need for transparent audit history without overwhelming the interface.

Architecture decisions

How the system was shaped.

01

Model irreversible steps explicitly

The flow was organized around state transitions that reflected finality and removed hidden behavior from the voting journey.

02

Treat audit trails as product surface

Logging and trace history were not afterthoughts. They shaped how entities, validations, and admin feedback were designed.

03

Balance confidence with usability

UI states avoided ambiguity while keeping the experience fast and readable for high-attention moments.

Results

  • A coherent voting system narrative where trust is reinforced by both backend guarantees and interface behavior.
  • A case that demonstrates thinking around state, auditability, and critical product flows under concurrency.
  • 01

    Domain model designed around elections, ballots, sessions, and validation states.

  • 02

    Transaction rules and audit trails treated as first-class system behavior.

  • 03

    Frontend flow kept explicit so users always understood progress and finality.

Next case

Etecfy

A music platform shaped around catalog growth, fast discovery, and a launch experience built to absorb attention.

Open case study