Richmond Hill Voters Deserve More Than Campaign Promises

A searchable council voting record would give residents something municipal elections often lack: a clear account of what incumbents actually did in office.

By City Desk

Every election asks voters to look forward. Candidates publish platforms, make promises and explain what they intend to do if elected.

But when incumbents seek another term, voters should also be able to look backward.

How did each member of Richmond Hill Council vote when decisions about taxes, housing, transportation, public safety, development and major spending came before them? Did their votes reflect the positions they presented during the previous campaign? When their positions changed, did they explain why?

The answers may technically exist somewhere in council agendas, minutes, staff reports and meeting videos. But for most residents, they do not exist in a form that can be readily found, understood or compared.

Richmond Hill needs an accessible, searchable database of council voting records.

Municipal politics comes without a party label

At the federal and provincial levels, a candidate’s party affiliation gives voters at least a broad indication of the policies and governing philosophy that candidate is likely to support. The label is imperfect, but it provides a starting point.

Municipal candidates in Richmond Hill do not run under official party banners. That independence can be valuable, but it also makes the voter’s job harder. A campaign sign may offer a name, a photograph and a slogan without revealing much about how that person would govern.

 Mayor David West agrees that a more accessible voting record is needed and says the City had previously considered or attempted to establish one.

Residents must assess candidates one by one, often using campaign material written by the candidates themselves. For newcomers and less politically engaged voters, even learning the meaningful differences between several candidates can become a considerable research project.

In a non-partisan system, a councillor’s voting record is one of the closest things voters have to a political track record. It cannot tell us everything about a representative, but it can show patterns that campaign literature cannot.

Promises are important—but governing is the test

Campaign promises matter. They allow voters to compare stated priorities and give successful candidates a democratic mandate to pursue them.

But promises are not the same as a governing record.

Some are fulfilled. Others are delayed, diluted or abandoned. Circumstances sometimes change, and an elected official may reasonably change position after receiving new information. Council members must also vote on consequential issues that nobody anticipated during the campaign.

Changing one’s mind is not necessarily a betrayal. But voters should be able to see that a change occurred and hear the explanation for it.

A voting-record database would not eliminate the need to listen to candidates. It would allow residents to compare what elected officials said with what they later did.

Publicly available is not the same as publicly usable

Residents should not need to become municipal archivists to understand their council.

At present, following a significant decision can require someone to know the date of the meeting, locate the correct agenda, identify the relevant report, follow amendments to the original motion, search the minutes and sometimes watch part of a lengthy meeting video. Even then, the resident may discover only that a motion carried—not how every member voted.

That information is public in a technical sense. It is not necessarily accessible in a democratic sense.

A useful system would let a resident search by councillor, date or subject and see:

• What Council was asked to decide
• The final wording of the motion
• How every member voted, or whether someone was absent or declared a conflict
• Whether the motion passed or failed
• Any important amendments
• Links to the staff report, minutes and meeting video
• A short plain-language explanation of the issue

The goal would not be to tell residents whether a vote was “good” or “bad.” It would be to preserve the record and make it understandable.

The need is recognized inside City Hall

In a recent conversation with Strong Richmond Hill, Mayor David West agreed that a more accessible voting record is needed and said the City had previously considered or attempted to establish one. We have asked for more information about what was proposed and why it did not proceed.

Councillor Karen Cilevitz, who was part of that conversation, later provided a more specific commitment. She told Strong Richmond Hill that she had discussed the issue with the City Clerk several years ago. If re-elected, she said, she intends to bring forward a Member Motion in 2027 to amend the Procedure By-law and require recorded votes on staff-report agenda items, excluding the Consent Agenda and by-laws.

That would be a meaningful step. A councillor-by-councillor record cannot be made accessible if the individual votes are not recorded in the first place.

But it is still a campaign promise—and there is an appropriate irony in that.

We are proposing a database partly because campaign promises can fade from public memory once an election is over. The first commitment entered into the proposed database will therefore be the promise to help make such a database possible.

Entry No. 1: Council voting transparency

Commitment: If re-elected, Councillor Karen Cilevitz says she will introduce a Member Motion in 2027 seeking recorded votes on staff-report agenda items, excluding Consent Agenda items and by-laws.

Status: Promised during the 2026 election campaign; not yet introduced or implemented.

What happens next: After the new term begins, Strong Richmond Hill will track whether the motion is introduced, what wording it contains, how Council votes on it and, if approved, how the City implements it.

That is not intended as a “gotcha.” It is what routine democratic accountability should look like: record the commitment, follow what happens and report the result fairly.

Recorded votes are the foundation, not the finished product

Requiring more recorded votes would address only the first part of the problem.

A list buried in separate meeting minutes would remain difficult to search across several years. The City should publish voting information in a consistent and structured format that residents, journalists and civic organizations can search, sort and download.

The ideal outcome is not merely more paperwork. It is a public record that can answer ordinary questions:

• How did my councillor vote on a particular issue?
• Which members supported or opposed a major expenditure?
• Has a councillor taken a consistent position on housing or street safety?
• What happened to a commitment made during the last election?
• Was a councillor opposed, absent or in a declared conflict of interest?

Those distinctions matter. An absence should not be presented as a “no” vote, and a declared conflict should not be treated as an attempt to avoid a decision.

Context must accompany the numbers

A responsible database cannot simply count yes and no votes and turn them into a score.

Council motions are frequently amended. A councillor may support the objective of a proposal while opposing its cost, timing or implementation. A final motion can be materially different from the version initially presented. Confidential legal information may also influence a decision even when it cannot be disclosed publicly.

For those reasons, every entry should link to the official record and explain the decision in neutral language. Councillors should be invited to submit a concise explanation of their vote or flag a factual error. Corrections should be made transparently.

Strong Richmond Hill should also publish its inclusion rules. Not every procedural or unanimous vote deserves equal prominence. The database should prioritize consequential decisions involving taxation, major spending, housing and land use, transportation, street safety, public services and other matters of significant public interest. Routine items could still be retained without being portrayed as defining political tests.

The database should reveal a record, not manufacture a verdict.

From campaign statement to public record

Strong Richmond Hill already asks candidates about their policy positions and priorities. A voting database would allow that work to continue after election day.

Over time, residents could follow a complete democratic chain:

1. What did the candidate say during the campaign?
2. What proposal eventually came before Council?
3. How did the elected representative vote?
4. If the position changed, what explanation was offered?
5. What was ultimately implemented?

That would make elections less dependent on slogans, selective memories and last-minute advertising. It would also give councillors a reliable record of the positions they followed through on—not only a list of promises that went unfulfilled.

Democracy needs a memory

Richmond Hill voters should not have to choose between campaign advertising and their recollection of scattered controversies.

Council decisions shape the services residents receive, the taxes they pay, the streets they travel and the kinds of homes and businesses the city permits. Those decisions should form part of a durable, accessible civic record.

The City can help by recording individual votes more consistently and publishing them as usable public data. Strong Richmond Hill can help by organizing consequential decisions, adding context and connecting governing records with campaign commitments.

We will begin with the promise made about the database itself. Then we will follow it—from pledge, to motion, to vote and, residents should hope, to implementation.