E-PARLIAMENT

E-PARLIAMENT

Client logo

Every decision a parliament makes starts as a document. It gets written, checked, debated, signed and filed passing through dozens of hands on the way, and it has to stay findable for decades afterwards. Awesomity is building the system that carries all of it digitally: seven parliamentary processes, one shared record, one signature that holds.

CLIENT

Parliament of Rwanda

Engagement

Phased delivery

SECTOR

Government · GovTech

REGION

Rwanda

7

Parliamentary processes now running digitally

2

Chambers and 106 members on a single platform

3

Languages supported — Kinyarwanda, English and French

1

Record carrying every document, decision and signature

01

CLIENT

Where a country's decisions get made.

The Parliament of Rwanda is where the country's laws are debated, agreed and passed. Two chambers, over a hundred members, and the staff who keep the institution running behind them. Everything it does produces documents — proposals, letters, reports, approvals. Those documents have to be accurate, traceable and kept for the long term. That is the work this system was built to carry

02

CHALLENGE

The work moved on. The record didn't.

Every decision travels before it is final — drafted by one person, reviewed by another, signed by a third, filed by a fourth. When each of those steps happens somewhere different, the trail breaks. Documents get chased. Approvals stall because nobody can see they are waiting. Printing was the fix. A signed copy in a physical file was the one version that could not be lost or overwritten, so that became the record everyone relied on. It worked — at the cost of handling every document twice, and of an institution whose decisions moved at the speed of paper.

03

APPROACH

Build the record once, then everything on top of it.

Rather than digitising each process separately, we built one foundation underneath all of them: a single record every document lives in, one trail of who did what and when, and one way of signing used right across the institution. That keeps the system consistent as it grows. A document raised anywhere follows the same rules and lands in the same place. And because the record is permanent, nothing is ever deleted — items are closed or retired, and their history stays intact.

04

PRODUCTS

Two products, one operation.

01

Committees Dashboard

Committees Dashboard

Where committee work is organised — membership, meetings, documents and the reports that come out of them.

02

Administration Dashboard

Administration Dashboard

Where the institution is set up and kept current — people, roles, access, and the rules the system runs on.

03

Bureau Dashboard

Bureau Dashboard

Where incoming items are received, assigned and tracked through to a decision, so nothing sits unanswered.

05

TECHNOLOGY

Under the hood.

The stack is built for reliability and speed. Next.js and TypeScript on the front, Symfony on the back, React Native for mobile. The AI models — YOLOv8, weight estimation, behavior classification — were all built specifically for livestock. Nothing off-the-shelf. Everything ships through CI/CD, and design is embedded from the start.

PostgreSQL
Keycloak
React
Next.js

06

IMPACT

Faster decisions, records that hold.

Nothing arrives unnoticed. Every incoming document is logged the moment it lands and is visible to the people responsible for it.

Approvals stop waiting on a desk. Signing happens inside the system, with full legal weight, wherever the signatory is.

Status becomes a screen, not a phone call. Anyone with the right role can see where something stands and what is holding it up.

The institution keeps its memory. Every document, decision and signature is held permanently and found again in seconds rather than days.

Impact

OWNERSHIP, NOT TICKETS

WHEN THE BRIEF DISAGREES WITH ITSELF.

Partway through, we found the requirements described who could see what in three different ways. The quick route was to build whichever version arrived last and move on. We took it back to the client instead, worked out what each version was protecting, and got one agreed answer before writing the code. It cost a week and saved a rebuild.

TESTIMONIALS

In their words

Client quote to be sourced

ICT director

Office of the Clerk or Parliament ICT Director

Have a project in mind? Let’s see if we’re a good fit.