Every Screen Knows Which Election You Are In. Here Is Why That Matters.

A campaign plan with no election date in it is a wish list.

Kenya's general election falls on the second Tuesday of August every fifth year, which puts the next one on 10 August 2027. Everything before it is scheduled backwards from that date: registration, party membership, nominations, clearance, the campaign period, the code of conduct. Miss one and the rest of the plan is irrelevant, because you are not on the ballot.

The platform holds that as a single record, and everything else points at it.

One election cycle, and everything hangs off it

A volunteer is not just a volunteer. They are a volunteer for a cycle.

So is an agent assignment, a station's coverage figure, a candidate registration, a result submission and a campaign event. Each of them carries the cycle it belongs to, which is why a page can show you a coverage figure without you having to remember which election it counts.

This sounds like bookkeeping and pays off in two ways. It keeps 2027 work from being polluted by records left over from a by-election. And it means that when the cycle's dates change, they change in one place rather than in a hundred screens that each remembered their own version.

The dates the cycle actually carries

The record has room for the milestones a campaign has to plan against: when voter registration closes, when the campaign period opens and closes, and the window inside which candidates are cleared.

The platform validates that those dates make sense relative to each other and relative to the election date. A clearance window that closes after the election is a data entry error, and it is refused rather than saved and discovered later.

What the platform does not do is invent the values.

Why a gazette notice beats anything we could hardcode

Because the numbers and dates are not ours to decide.

Registration deadlines, nomination timetables, clearance windows and campaign spending caps are set by the IEBC and published by gazette notice before each election. They have moved before. They can move again, by regulation or by a court ruling, and any of that can happen after software has shipped.

A system that hardcodes a deadline is a system that lies confidently the moment the deadline changes. So the honest design is a record an administrator updates from the current notice, and an honest habit for a campaign: check the gazette for your seat rather than trusting anybody's summary, ours included.

For the shape of the calendar itself, the archive has the full sequence in Kenya's 2027 election calendar.

What your own calendar adds to it

The statutory dates are the frame. Your campaign's own dates go inside it.

Rallies, meetings, registration drives and door-to-door pushes are events on the platform, each with a place and a time and the people expected to turn up. They sit against the same cycle, so a coordinator looking at next week sees both kinds of date at once: what the law requires and what the campaign has committed to.

That combination is the thing a paper calendar cannot do, because the paper calendar in the office is not the one in the coordinator's pocket, and by March they disagree.

What to do about it now

Three things, none of which take an afternoon.

Find the current gazette notice for your seat and read the dates yourself. Not a summary, not a WhatsApp forward, the notice. Then put those dates into the cycle record so every screen in your campaign is working from the same set.

Then work backwards from each one and write down what has to be true a month before it. Party membership has to be settled before nominations. Agents have to be recruited long before they are deployed, which is the argument in assigning agents and reading the gaps.

Then set a reminder to check the notice again in a couple of months. In an election year the calendar is a moving object, and the campaigns that get caught are the ones that read it once in 2026 and never looked again.