Campaign Promise Tracker Kenya is a governance workflow for recording what a campaign has actually committed to, who reviewed it, which office or institution can influence it, what dependencies exist and which evidence supports each update. It should prevent a speech line, community request or draft manifesto idea from being treated as a guaranteed public outcome. A tracker improves internal discipline and transparency; it cannot guarantee election, funding, approvals, implementation or legal authority.
Who needs a campaign promise tracker?
The direct users are aspirants, campaign managers, manifesto and policy directors, researchers, communications reviewers, field coordinators and evidence officers. County or constituency leads may submit community issues, but the authorised policy team should decide whether an issue becomes a proposed commitment. Communications staff should publish only the approved wording and status.
Every political seat can use the workflow, but commitments must reflect the office being sought. An MCA operates in a county assembly context. An MP and County Woman Member sit in the National Assembly. A senator represents a county and has constitutional oversight roles. A governor leads a county executive. The President has national executive responsibilities. The Constitution of Kenya is the primary starting point for understanding those distinctions; policy and legal advisers should review the specific proposal.
Separate an issue, proposal and public commitment
Campaigns hear many legitimate concerns at doors, markets, town halls and online. An issue record captures what was reported and its context. A policy proposal is an option being researched. A public commitment is wording that authorised campaign leadership has reviewed and adopted.
Those are three different things. If the system converts every issue into a “promise,” it creates unrealistic expectations and inconsistent messages. If it stores only final slogans, it hides the research and dependencies that help a team communicate responsibly.
A practical tracker connects the records while keeping their status clear: issue received, research assigned, proposal drafted, jurisdiction checked, feasibility under review, wording approved and commitment published. Rejected or merged proposals should also have a reason so the same debate does not restart without context.
Test whether the office can influence the commitment
Before approval, ask what legal power, budget process, partner institution or legislative action is involved. Some objectives require cooperation between national and county government. Others depend on an independent institution, private actor, land process, procurement, public participation or future appropriation. Election to an office does not remove those dependencies.
The tracker should identify the level of government, responsible institution and relevant limitation in plain language. It should not display a legal “approved” badge generated by software. Qualified advisers must review questions of mandate and law.
This check also improves search and website content. A candidate can explain an intended contribution without claiming sole power over an outcome. Accurate boundaries are more credible than promising that every problem will be completed immediately after election.
Write commitments that can be reviewed later
A useful commitment record answers several questions:
- What exact action or direction has the campaign approved?
- Which geographic area and group does it concern?
- Which office, institution or partner would be involved?
- What assumptions and dependencies are known?
- What evidence informed the commitment?
- Who owns the next campaign-stage action?
- Which wording is approved for public use?
- When must the record be reviewed again?
Avoid vague superlatives, invented numbers and deadlines unsupported by research. If a target is an aspiration rather than a funded plan, label it honestly. If the team cannot verify a statistic, remove it or state the uncertainty. Do not copy another candidate's commitment without checking local needs and jurisdiction.
Use a controlled review and approval path
The workflow should make unauthorised changes difficult. A researcher drafts the evidence note. A policy lead reviews the proposal. Finance or technical advisers assess assumptions where relevant. A legal reviewer handles mandate or compliance questions. Campaign leadership approves the public wording. Communications then publishes the approved version.
Each change should record the editor, date and reason. If a material commitment is revised, preserve the previous version and provide a reviewed explanation. Quietly replacing a promise after public scrutiny damages trust and makes field teams repeat conflicting messages.
Approval is internal campaign authority, not official government approval. Vota is not the IEBC, Parliament, a county assembly, a treasury, a procurement authority or a government project-monitoring system.
Make evidence a requirement, not decoration
Evidence may include a public dataset, law, budget document, professional assessment, field observation, meeting record or appropriately consented community submission. The tracker should record source, date, reviewer and relevance. A photograph alone may show a condition at one location and time; it may not prove scale, cause or the correct solution.
Create an evidence-review status such as submitted, under review, accepted with limits, superseded or rejected. Note limitations. A link that no longer works, an undated screenshot or an anonymous claim should not carry the same weight as a current primary document.
Evidence reviewers should avoid exposing private residents. Remove unnecessary names, phone numbers, identity documents, precise home locations and sensitive personal information. A person who reports a road, health or service problem has not automatically consented to become a public campaign testimonial.
Choose statuses that do not overclaim progress
During the campaign, useful labels include proposed, researching, approved for manifesto, publicly announced, revised and withdrawn. After an election, a campaign may record handed over for transition or archived, but it should not relabel itself as the official government source.
Terms such as completed, delivered or fulfilled require a published definition and reviewed evidence. A meeting, letter or site visit is activity, not necessarily an outcome. A budget allocation is not the same as expenditure. Launching procurement is not the same as delivering a usable service. A partly completed action should be described with its remaining work and dependencies.
Avoid a single percentage unless the measurement method is clear. A careful narrative update with evidence can be more truthful than “80% complete” based on an unexplained formula.
Connect field reports without auto-publishing them
Field teams can submit observations and evidence through a controlled political campaign field reporting workflow. The promise owner reviews the report, requests clarification and decides whether it affects the commitment's evidence or status.
Raw reports should not automatically change a public page. They may contain errors, allegations or personal data. Communications staff need the approved statement, source context and review date. This separation allows a fast field workflow and a careful publication workflow to coexist.
Events can also feed the process. A listening meeting may reveal repeated priorities, but attendance or applause is not a scientific mandate. Use the campaign event management guide to organise issue capture and follow-up without treating every request as an approved commitment.
Publish commitments through one owner page
The aspirant's website should publish the current approved wording, evidence summary, dependencies and last-reviewed date. Do not maintain different versions across duplicated pages. Link speeches, social posts and media notes back to the owned public page where practical.
The political aspirant website guide explains how the public page differs from the internal workspace. The website is a campaign communication channel, not an official government record. It must not suggest that a proposed project has formal approval merely because it appears online.
When a commitment changes, publish the reason and effective date. If the campaign withdraws it, keep an appropriate archive instead of deleting the record and pretending it never existed.
Protect community data and peaceful participation
Issue collection needs a clear purpose, minimal fields and restricted access. Do not infer ethnicity, religion, health, political opinion or vote intention from a person's location or concern. Do not rank communities by assumed support or use access to public services as a campaign incentive.
Explain whether a submission may inform policy research, whether the person should expect a response and how information will be handled. The ODPC's guidance for electoral-purpose data processing provides an important reference. Obtain professional advice for the campaign's actual processing.
Moderation and review should support peaceful campaigning. Do not use a promise tracker to publish accusations against opponents, intimidate critics or mobilise confrontation. Evidence disputes should follow a calm correction and escalation process.
Campaign promise tracker configuration checklist
Before using a tracker, confirm:
- Issues, draft proposals and public commitments have distinct record types.
- Every commitment names the elective seat, area and authorised owner.
- Jurisdiction, institutions and dependencies are reviewed explicitly.
- Approved public wording is separate from internal research notes.
- Evidence has a source, date, reviewer, relevance and limitations.
- Material edits preserve the previous version and reason.
- Status labels have definitions that do not exaggerate outcomes.
- “Completed” requires reviewed evidence against a stated measure.
- Field reports cannot auto-publish or silently change status.
- Website, speeches and social content use one current owner record.
- Personal data is minimised, restricted and retained responsibly.
- Corrections, disputes, withdrawal and archival paths are documented.
- The workflow clearly states that commitments are not guaranteed outcomes.
Test the system with a promise that involves another institution, a disputed source and a changed deadline. The exceptions reveal more about the workflow than a simple demonstration.
How Vota supports commitment governance
The Vota Campaign Promise Tracker Kenya service is the transactional owner for this workflow. Vota can connect citizen issues, promise records, evidence, owners and field reports inside a controlled campaign workspace. That connection helps authorised teams move from listening to research and reviewed communication. Explore the broader Vota campaign management service for the platform overview.
Vota does not guarantee that a commitment is lawful, affordable, funded or delivered. It does not register voters, cast ballots, tally votes or publish official results. It cannot guarantee electoral success or a government outcome. Responsibility remains with campaign leadership, elected institutions and qualified advisers.
Frequently asked questions
Is every community request a campaign promise?
No. It begins as an issue or request. The authorised team must research mandate, feasibility, dependencies and wording before adopting a public commitment.
Can a tracker prove that a promise is fulfilled?
The tracker can organise evidence and review history. A responsible reviewer must assess that evidence against a published definition. Software alone cannot certify an outcome.
What happens to the tracker after an election?
The campaign should follow an approved retention and transition plan. Any transfer into public administration must respect law, institutional authority and data-protection requirements; a campaign database must not quietly become an official government system.
Can Vota predict whether a promise will win votes?
No. Vota does not predict votes or guarantee victory. Commitment governance is about accuracy, accountability and consistent follow-up.
What determines the cost?
Team size, geographic structure, modules, onboarding, data preparation and support may affect scope. Review Vota pricing and request an exact configuration discussion.
Request a promise-workflow demonstration
Bring one anonymised community issue, a draft commitment, its known dependencies and two sample evidence sources. The demonstration should show review, versioning, status and publication hand-off—not a guaranteed outcome. Contact Vota to assess a responsible workflow for your campaign team.