Governor Campaign Manifesto Checklist Kenya gives an aspirant and county campaign team a disciplined route from ward concerns to reviewed public commitments. A manifesto should not be assembled from unverified requests, copied promises or whichever speech draft is newest. It needs clear county-function checks, evidence owners, dependencies, approvals and one current version. Vota's Governor Campaign Tool can organise that internal workflow while people retain responsibility for policy judgment and public communication.
Important: Vota is campaign-operations software. It is not the Independent Electoral and Boundaries Commission (IEBC), a voter register, nomination, eligibility or filing service, a voting platform, tallying or results system, county-government planning portal, or legal or policy adviser. It does not approve a manifesto, determine whether a promise is lawful or affordable, predict votes, or guarantee nomination, support, funding, implementation or victory.
Who should use this governor manifesto workflow?
The main buyer is a governor aspirant or campaign manager who needs one accountable process across a county. Daily users may include the policy director, research and evidence lead, running-mate team, communications reviewer, finance adviser, constituency coordinators, ward coordinators, citizen-issues desk and data-protection lead. Each role needs access to the records required for its work, not unrestricted access to every resident's information.
The Governor Campaign Management Platform is the broader commercial owner for countywide governor operations. This article addresses the narrower manifesto workflow. The Campaign Manager Software can help a named manager assign research, review overdue decisions and maintain one approved publication queue.
Why a manifesto becomes an operations problem
A campaign may receive hundreds of proposals through meetings, forms, coordinators, professionals, businesses and community organisations. Without a controlled process:
- one complaint is mistaken for a countywide priority;
- a national-government responsibility is presented as a governor's direct mandate;
- different speakers announce conflicting figures, locations or deadlines;
- a draft promise is published before evidence, costing or dependency review;
- personal stories and contact details reach teams that do not need them;
- a correction changes one poster but not the speech, website or briefing note; and
- no person owns the next decision after a ward issue is recorded.
The answer is not to promise less or more automatically. It is to make the route from a structured listening tour to approval visible.
Check county functions before drafting promises
The Fourth Schedule of the Constitution of Kenya separates national and county functions. County responsibilities include areas such as county agriculture; county health services; county transport; trade development and regulation; county planning and development; pre-primary education, village polytechnics, homecraft centres and childcare facilities; county public works and services; firefighting and disaster management; control of air and noise pollution and outdoor advertising; cultural activities and public amenities; and facilitating community participation.
Use three internal classifications for every proposed commitment:
- Direct county function: the subject falls substantially within a county responsibility, although implementation will still require lawful planning and resources.
- Shared or dependent commitment: delivery requires cooperation, legislation, approvals, land, infrastructure, funding or action by another institution.
- Outside direct county control: the campaign may advocate, convene or seek partnership, but should not state that a governor can deliver the outcome alone.
This check prevents mandate confusion; it does not settle a legal interpretation. Where scope is uncertain, the campaign should obtain current qualified advice before publication.
The County Governments Act also matters. It connects county leadership to accountable governance, citizen participation and county planning. It identifies planning instruments including the county integrated development plan, sectoral plans, spatial plan, and city or urban plans. A campaign manifesto can propose priorities, but it is not an official CIDP, annual development plan, appropriation, procurement decision or approved county programme.
Ward issue to county priority: an eight-step workflow
1. Capture the issue for a defined purpose
Record what the person or group voluntarily raised, the ward or relevant location, the service area, date, source channel and permitted follow-up method. Separate the issue from supporter, volunteer and event-attendance records. Raising a concern does not show political support and must not be treated as a vote signal.
2. Clarify without converting an allegation into fact
An authorised reviewer should identify the practical problem, affected people, frequency and existing response. Keep opinion, reported experience and verified fact visibly distinct. Sensitive attachments or allegations need restricted access and an appropriate escalation route; a campaign database is not an emergency or official complaint channel.
3. Run the county-functions check
Assign the issue to a direct, shared or outside-control category. Record the constitutional or statutory basis reviewed and any question that needs specialist advice. This creates a visible reason for the classification instead of relying on an undocumented assumption.
4. Test whether the issue is a wider priority
Compare reviewed submissions across wards with credible public evidence, existing plans, service data and stakeholder research. Do not equate the number of records in Vota with a representative opinion poll. Coverage can show what the campaign has heard and where follow-up is incomplete; it cannot establish how all residents think or how they will vote.
5. Build a short evidence brief
For a viable priority, record the problem statement, affected area, available baseline, source links, evidence limitations, relevant county function and unanswered questions. Give every source an owner and review date. Photographs, documents and testimonies should retain provenance and publication restrictions.
6. Draft a bounded commitment
Write the proposed outcome, intended beneficiaries, geographic scope, time horizon and accountable campaign owner. Add dependencies such as county-assembly approval, planning, budget and appropriation, procurement, staffing, national-government cooperation, regulatory permission or external funding. Avoid absolute language when delivery depends on decisions not yet made.
7. Pass the review gates
Policy, evidence, finance, privacy and communications reviewers should approve their own fields rather than one person approving everything. Record comments, required changes and the final decision. A rejected or deferred proposal remains useful when the reason is preserved.
8. Publish one approved version and control changes
Link the approved wording to speeches, website copy, briefing notes and campaign materials. When evidence or circumstances change, create a new version, record why and withdraw superseded wording. The public should not receive several incompatible promises from the same campaign.
Vota's Campaign Operations Software can connect assignments, evidence and approvals across that path. The broader Campaign Management Software helps teams relate manifesto work to authorised events, field reports and communications without converting operational activity into a vote forecast.
Give every promise and evidence item an owner
A useful promise record should identify:
- the original issue or research question;
- ward, constituency and county relevance;
- county-function classification;
- policy owner and due date;
- evidence sources, provenance and limitations;
- finance or feasibility reviewer;
- dependencies and assumptions;
- approved wording, status and version;
- communications owner and publication channels; and
- correction, withdrawal or follow-up history.
Use the Citizen Issue Management System to route voluntarily submitted concerns into private review. Use the campaign Evidence Centre for controlled supporting records, and the Campaign Promise Tracker for approved commitment versions, owners and dependencies. These workflows improve internal accountability; they do not prove that an allegation is true, a policy is sound or a promise will be delivered.
Apply six review gates before publication
- Mandate gate: Is the proposed action a county function, a shared responsibility or advocacy outside direct control?
- Evidence gate: Are sources identified, current enough for the claim and honest about limitations?
- Feasibility gate: Are major funding, staffing, planning, approval and procurement dependencies visible?
- Language gate: Does the wording distinguish a proposal from an already approved government programme?
- Privacy gate: Have personal details, sensitive material and publication permissions been handled appropriately?
- Conduct gate: Is the commitment communicated peacefully without threats, bribery, discriminatory incitement, deliberate falsehoods or interference with opponents?
The Electoral Code of Conduct in the Elections Act provides an official reference for peaceful, non-intimidating campaign conduct. Vota may record internal reviews, but a completed checklist is not legal clearance or an IEBC approval.
Protect residents while listening across wards
Collect only information needed for the stated issue-review purpose, explain how it will be used, document an appropriate lawful basis, restrict access, secure records, correct inaccuracies and set retention or deletion rules. Do not publish a resident's identity, contact details or sensitive story merely because it was submitted to a campaign.
Do not profile residents by ethnicity, religion, health, disability, family circumstances or inferred political preference. Do not use ward issues, event attendance or service complaints to label loyalty or target pressure. The Data Protection Act, 2019 and ODPC Guidance Notes for Electoral Purposes are primary references; campaign teams should obtain current professional guidance for their circumstances.
Coordinate with other seats without merging mandates
A governor team may receive local context from an MCA campaign workspace or constituency context from an MP campaign workspace. A sponsored candidate may also coordinate approved work through the Party Campaign System. That cooperation must preserve separate candidate authority, purposes, permissions and data ownership. An MCA, MP, party official or governor aspirant should not silently inherit another team's private citizen records.
Governor Campaign Manifesto Checklist Kenya: practical review
Before approving a manifesto section, confirm that the campaign has:
- named the issue and location without exposing unnecessary personal data;
- separated reported experience, opinion and verified fact;
- checked the Fourth Schedule and recorded the mandate classification;
- compared ward submissions with credible wider evidence;
- assigned a policy owner and evidence owner;
- stated the proposed outcome and intended beneficiaries;
- recorded cost, funding and staffing assumptions where available;
- identified assembly, plan, budget, procurement and partnership dependencies;
- completed evidence, feasibility, privacy and communications reviews;
- used bounded wording without presenting a proposal as an approved programme;
- approved one canonical version for all campaign channels;
- retained a correction and withdrawal route;
- restricted sensitive evidence to authorised roles;
- avoided sensitive-trait profiling and vote prediction; and
- confirmed peaceful, truthful and non-intimidating communication.
Frequently asked questions
Should every ward issue become a manifesto promise?
No. An issue may need clarification, referral, further evidence or private follow-up. Some matters fall outside county control, while others may reveal a broader priority only after responsible research. Recording an issue is not a promise.
Does Vota write or approve the governor's manifesto?
No. Vota can organise issues, tasks, evidence, review status, versions and publication hand-offs. The aspirant and authorised advisers remain responsible for policy, legal, financial and political judgment.
Is a campaign manifesto an official county plan?
No. A manifesto communicates campaign proposals. Official county plans, budgets, appropriations and procurement decisions require their own lawful processes after an election. Software cannot bypass those processes.
Can issue totals be used to predict support by ward?
No. Submissions are not a representative poll, voter register or election result. Vota should not be used to infer political preference or guarantee performance at the ballot.
Can Vota guarantee that a promise will be implemented?
No. Implementation may depend on election, lawful authority, evidence, assembly decisions, plans, funding, procurement, staffing and other institutions. A tracker supports accountability; it cannot guarantee an outcome.
See the manifesto workflow in a Vota demo
Bring one anonymised ward issue, a draft commitment, two sample evidence sources and the campaign's proposed approval roles. Ask the demonstration to show intake, county-function classification, ownership, review gates, version control and responsible publication from beginning to end. Review Vota pricing, then contact Vota for a scoped governor campaign demonstration.