V Vota

Governor and Running Mate Campaign Coordination Kenya

A practical operating model for governor aspirants, running mates and countywide campaign teams that need shared calendars, clear responsibilities, reviewed messages and accountable field follow-up.

Governor and Running Mate Campaign Coordination Kenya helps a countywide campaign replace two parallel teams with one accountable operating plan. A governor aspirant and running mate may attend different events and supervise different workstreams, but their calendars, messages, assignments, field reports and decisions must return to a shared record. Vota’s Governor Campaign Tool gives authorised campaign teams a workspace for that internal coordination.

Kenyan governor aspirant and running mate reviewing a countywide campaign calendar with campaign coordinators
Governor and Running Mate Campaign Coordination Kenya practical campaign guide by Vota.

Important: Vota is internal campaign-operations software. It is not the Independent Electoral and Boundaries Commission (IEBC), an official nomination, eligibility, clearance or filing service, a voter register, a voting platform, a tally or results-transmission system, or an official results source. It does not select a running mate, provide legal advice, predict votes or guarantee nomination, support or victory.

Who needs a joint-ticket campaign workflow?

The main buyers are governor aspirants, running mates, campaign managers and county operations directors who have outgrown calls, separate spreadsheets and several unconnected messaging groups. Constituency and ward coordinators, event leads, communications reviewers, volunteer managers, issue-desk teams, authorised finance users, data-protection leads and incident reviewers need controlled access to the parts they own.

The Governor Campaign Management Platform remains Vota's broad commercial owner for countywide governor operations. This guide covers the narrower joint-ticket coordination workflow.

The workflow is particularly useful after a running mate joins an established campaign. It preserves earlier work while making the new reporting line visible. Vota’s Campaign Manager Software can help the appointed manager assign responsibility and review exceptions without giving every user unrestricted access.

Understand the constitutional one-ticket rule

Article 180 of the Constitution of Kenya provides that a governor is elected directly by registered voters in the county. Where two or more candidates are nominated, the candidate with the greatest number of votes is declared elected. Each governor candidate nominates a qualified person as the candidate for deputy governor, and IEBC does not conduct a separate election for that office. IEBC declares the nominee of the elected governor to have been elected as deputy governor.

That constitutional design has a practical campaign lesson: residents vote in the governor contest, not in two independent contests for the two members of the ticket. During the campaign, “running mate” is the clearest operational description. “Deputy governor” should be used when explaining the constitutional office or referring to a person who lawfully holds it—not as proof that an aspirant has already been elected or cleared.

Vota can record an internal running-mate workstream, shared approvals and authorised team roles. Creating that profile does not nominate anybody, establish eligibility or submit anything to IEBC, the Office of the Registrar of Political Parties (ORPP) or a political party.

Problems that appear when the two teams stay separate

A governor and running mate can cover more ground, but unconnected operations create avoidable risk:

  • Two calendars place the ticket in conflicting meetings or leave an area without the expected representative.
  • Ward coordinators receive different instructions from the governor team and running-mate team.
  • Public statements describe the same promise differently or publish unreviewed facts.
  • Field reports, community issues and event evidence remain in separate chats, so follow-up is duplicated or lost.
  • Staff copy supporter and volunteer records into personal devices to make the second team “complete.”
  • Expense requests move through informal channels without a visible owner, authorisation or receipt.
  • A party headquarters, candidate office and county field team cannot tell which decision is current.

For a party-sponsored ticket, Vota’s Party Campaign System can connect internal party and candidate work. It does not replace party nomination rules, authorised party decisions or official procedures.

Build one operating workflow in eight steps

1. Agree on decision rights before adding more users

Write a short operating charter that names who approves events, messages, expenditure requests, field assignments, issue responses and serious incident escalation. Give one person final operational ownership for each category. A shared system cannot solve a leadership dispute that nobody is authorised to decide.

Record temporary delegations when the governor aspirant or running mate travels. An approval should show the decision, reviewer, date and next action without exposing private leadership discussions to every volunteer.

2. Map the campaign across the county

Create campaign areas for constituencies or sub-counties, wards and other legitimate operating zones, then assign named coordinators. The map should help route tasks, events and reports; it must not become a tool for inferring ethnicity, religion, family circumstances or likely voting preference.

Use the same area names across both sides of the ticket. This prevents one team from reporting by ward while the other uses informal labels that cannot be reconciled. The map is an internal coordination structure, not an official IEBC boundary record.

3. Give each role the minimum necessary access

Separate leadership, campaign management, communications, field coordination, events, finance, issue review and incident handling. A running-mate scheduler may need the joint calendar but not every supporter contact or restricted incident attachment. Ward coordinators should see their assignments and reporting route rather than the whole county database.

Review access when responsibilities change, a consultant leaves or a device is lost. Role-based permissions reduce unnecessary exposure, but they do not by themselves make data handling lawful or secure.

4. Use one calendar with named owners and approvals

Every event should identify the purpose, area, organiser, expected ticket representative, time, logistics owner, approved message, safety route and follow-up deadline. When the running mate covers an event, the record should show that assignment instead of creating a second event copy.

The calendar is for responsible coordination, not a substitute for permits, venue consent, party approval or official campaign-period instructions. Current requirements should be confirmed through IEBC, relevant authorities and professional advice.

5. Maintain one reviewed message and commitment register

Keep approved talking points, evidence sources, corrections and county commitments in a controlled register. Identify which promises relate to county functions and which depend on legislation, county-assembly approval, budgeting, procurement or cooperation with the national government.

The governor aspirant and running mate can then speak consistently without pretending that a campaign promise is already a government programme. Record proposed commitments as proposals, not guarantees. Require a reviewer before either team publishes a changed figure, allegation or sensitive response.

6. Connect assignments to field reports and community issues

Use Campaign Management Software to give each assignment an owner, area, deadline, expected evidence and escalation path. Vota’s Campaign Operations Software can connect that work with events, field reports and issue follow-up so leadership sees one current status.

Treat community listening responsibly. A person who attends an event, raises a complaint or asks for information is not automatically a supporter. Separate observations from verified facts, restrict sensitive evidence and route matters outside the campaign’s role to appropriate channels without claiming the campaign delivered an official county service.

7. Run daily exception reviews and weekly ticket reviews

Daily reviews should focus on changed events, overdue reports, conflicting instructions, urgent issues, access changes and safety concerns. A weekly ticket review can examine completed work, repeated blockers, commitments awaiting evidence, unanswered community issues and decisions needed from leadership.

Track operational measures such as reporting timeliness, overdue assignments, event-readiness gaps and resolved handoffs. Do not turn attendance, contact totals, volunteer activity or field observations into forecasts of registered voters, turnout or votes.

8. Separate campaign spending and public resources

Record internal expense requests, authorisation, payment evidence and missing receipts with appropriately restricted access. Vota is not a bank, auditor, accounting service or official campaign-finance filing system, and an internal record is not proof of compliance.

For incumbents, the separation between campaign resources and county resources must be explicit. Section 14 of the Election Offences Act restricts the use of public resources for campaigning. County vehicles, staff, money, equipment and official programmes must not silently become campaign assets.

Protect people, privacy and peaceful participation

The Data Protection Act, 2019 and the ODPC Guidance Notes for Electoral Purposes are primary references for electoral data handling. Define a legitimate purpose and appropriate lawful basis, provide suitable notice, collect only necessary information, document its source, restrict access, secure it, respect applicable rights and choices, and set retention and deletion rules.

Do not build profiles from ethnicity, religion, health, disability, family circumstances or inferred political preference. Do not treat an official register’s availability for a lawful purpose as blanket permission to copy it into a campaign marketing database.

Both teams should follow one peaceful-conduct standard. Reject bribery, inducements, threats, harassment, discriminatory incitement, misinformation, destruction of opponents’ materials and interference with lawful meetings or election officials. The Electoral Code of Conduct in the Elections Act requires peaceful, non-intimidating conduct. Vota may route an internal incident report to authorised reviewers, but it is not an emergency service, police report, IEBC complaint or investigation system.

Buyer checklist for a governor-running mate coordination system

Before choosing software, ask whether the campaign can:

  1. Maintain one countywide structure with clear constituency and ward ownership.
  2. Operate a joint calendar while identifying who represents the ticket at each event.
  3. Give different roles appropriate access without sharing the full database.
  4. Record approvals for assignments, messages, commitments and expense requests.
  5. Connect field reports and community issues to named follow-up owners.
  6. Preserve corrections, handovers and decision history.
  7. Restrict incident, finance and personal-data records.
  8. Remove access promptly when a person changes role or leaves.
  9. Export useful operational reports without presenting them as polling or official election data.

Frequently asked questions

Can Vota choose or approve a governor’s running mate?

No. Selection and lawful nomination belong to the candidate and the applicable official or party processes. Vota only supports internal coordination after authorised users configure the workstream.

Is the running mate elected separately?

No. Article 180 states that IEBC does not conduct a separate election for deputy governor. Campaign teams should obtain current official guidance for nomination, qualification and documentation questions.

Can the two teams keep separate private databases?

Separate access views may be appropriate, but uncontrolled copies create conflicting records and privacy risks. Use one governed source with minimum necessary access, stated purposes and accountable handoffs.

Does coordinated field activity show which wards will vote for the ticket?

No. Operational reports are not representative opinion polling, an official register or a vote forecast. Vota does not score loyalty, predict turnout or determine an election result.

Coordinate the ticket without losing accountability

Start with one real workflow: a joint weekly calendar, a field assignment or a community-issue handoff. Confirm the responsible users, approval path, minimum information and closeout report. Then review Vota pricing and contact Vota for a demonstration of a governor and running mate campaign workspace.

Keep reading