NetaTrack

02 · Problem

Political promises in Nepal are extremely visible at the moment they are made and almost invisible afterwards. Coverage moves on within days. By the time an election comes around, nobody has a consolidated record of what was committed to, so accountability depends on memory rather than evidence.

• Commitments are scattered across news articles, PDFs and social posts.
• Nothing links a promise to its later outcome in a durable place.
• Citizens have no low-effort way to check a representative's record.

03 · Concept

Treat a promise as a first-class database record with a life cycle, the way an issue tracker treats a ticket. Every entry carries who made it, when and where, what exactly was committed to, and a status that only moves when supporting evidence is attached.

The status vocabulary is deliberately small — Promised, In progress, Delivered, Broken, Unverifiable. Restricting the options forces a clear judgement and keeps the interface readable.

04 · Key features

1. Representative profiles

   A page per leader collecting their record, commitments and public rating in one place.

2. Commitment monitoring

   Promises recorded as structured entries, each status change requiring a source.

3. Constituency data

   Coverage across all seven provinces, so a voter can start from where they live.

4. Citizen grievances

   A route for the public to log issues against a representative or constituency.

5. Public ratings

   Citizen opinion on representatives, kept visibly separate from official figures.

6. Activity feed

   Political developments as they happen, alongside election news.

7. Fact-checking

   Claims checked and sourced rather than repeated.

05 · Technology

• Next.js — the application framework, server-rendered.
• React — profiles, filtering, search and the activity feed.
• TypeScript — types across representatives, commitments, sources and status history.
• Vercel — hosting and deployment.

06 · My contribution

NetaTrack is my own project, so the work is end to end: the product concept and scope, the data model, the moderation workflow, the interface design, the backend implementation and the deployment.

The part that took the most thought was not code. It was defining a standard for what counts as a promise and what counts as evidence — a platform like this loses all value the moment its judgements look arbitrary.

07 · Screenshots

08 · Challenges and decisions

Neutrality has to be structural

Anything that looks like editorialising discredits the whole platform. The answer was to make the data model enforce it: a status change requires a source, and the source is displayed alongside the claim. The platform reports the record; the reader draws the conclusion.

Deciding what qualifies as a promise

"We will build 200 kilometres of road by 2027" is checkable. "We will prioritise development" is not. Only measurable commitments enter the database; the rest are logged as context. This single rule removed most of the ambiguity from moderation.

Sources that disappear

News URLs rot. Records therefore store the publication, date and quoted text rather than relying on a link staying alive, so an entry remains meaningful even after the original page is gone.

09 · Status

NetaTrack is live at netatrack.com and in active development. The data model, admin tooling and public interface are built; ongoing work is deepening the sourced dataset and the verification workflow behind every status change.

10 · Links