A campaign promise tracker example is not a list of campaign slogans beside green and red checkmarks. Done properly, it is a public record of what a candidate said, what authority they hold once elected, what evidence exists, and whether residents can reasonably call the promise kept, broken, stalled, or still in progress.
That distinction matters most in city government. A mayor can announce a goal on Monday, direct an agency on Tuesday, and face a Council vote, state restriction, court challenge, or budget shortfall by Friday. Accountability should not erase those constraints. It should document them clearly, then assess whether the administration took the actions it said it would take.
What a Campaign Promise Tracker Measures
A credible tracker starts with a precise promise. “Make the city safer” is a political objective, not a measurable commitment. “Hire 500 additional school safety staff by the end of the first fiscal year” is a commitment that can be tested against hiring records, budget lines, and agency reporting.
The first task is to preserve the original language and context. Was the statement made in a campaign speech, policy plan, debate answer, interview, or mailer? Did the candidate set a deadline, dollar amount, geographic scope, or eligibility rule? Those details prevent a common failure of political accountability coverage: treating an administration’s broad policy direction as proof that a specific promise was fulfilled.
A useful tracker separates four related but different things:
- The promise: What the candidate explicitly committed to do.
- The governing authority: Whether the mayor can act alone, needs the City Council, depends on Albany, or requires federal approval.
- The implementation record: Executive orders, budget proposals, legislation, agency rules, contracts, appointments, and public performance data.
- The current status: A plain-language judgment supported by the record.
This structure gives readers more than a verdict. It shows the chain of evidence behind the verdict.
A Campaign Promise Tracker Example
Consider a fictional mayoral candidate who says: “Within my first year, I will create a citywide free bus pilot on the ten routes with the slowest service.”
A tracker should first log the statement as made, including its date and source. It should then identify the governing reality: the mayor may advocate for and help fund transit initiatives, but the Metropolitan Transportation Authority is a state-controlled authority. The mayor cannot unilaterally order a citywide fare policy.
That authority question changes how the promise should be evaluated. If the mayor submits funding in the city budget, negotiates with the MTA, and obtains approval for a pilot on ten qualifying routes, the item could be labeled kept. If the mayor funds a pilot on two routes while claiming the full pledge is complete, partially kept is more accurate. If the administration announces a task force but never proposes funding or reaches an agreement with the MTA, the item may be stalled.
If the mayor abandons the proposal, directs resources elsewhere, or publicly rejects the policy after taking office, the tracker can label it broken. The explanation should state what changed and cite the relevant actions. A broken promise is not automatically proof of bad faith. Conditions change. Revenue falls. A state partner refuses cooperation. But voters still deserve a record of the gap between the commitment and the outcome.
A concise tracker entry might read like this:
Promise: Create a free bus pilot on ten of the city’s slowest routes within one year.
Authority: Shared. City funding and mayoral advocacy are possible; MTA approval is required.
Evidence reviewed: Campaign policy plan; adopted city budget; MTA board materials; agency announcements; ridership and route-speed data.
Status: Partially kept.
Finding: The administration secured funding and MTA approval for three free routes. Seven promised routes were not included by the one-year deadline. The original target was not met, though implementation began.
This is more useful than either a celebratory headline or a blanket accusation. It tells a resident what happened, what remains undone, and why the rating is what it is.
Status labels need rules
Status labels carry editorial weight. They should be defined before a tracker begins, not adjusted after a politically convenient result.
Kept should mean the administration completed the core commitment within the stated terms, or delivered a substantially equivalent outcome when the original wording allowed flexibility. Partially kept should mean meaningful action occurred, but a material part of the pledge remains incomplete. In progress fits a promise with a longer timeline when documented implementation is underway and milestones are being met.
Stalled is different from merely unfinished. It means there is no meaningful recent progress, a deadline has passed without sufficient action, or a required next step has not occurred. Broken should be reserved for commitments the administration has clearly abandoned, reversed, or failed to pursue after a reasonable opportunity to act.
There are edge cases. A promise may be impossible to complete because a court blocks it or the state legislature rejects required authority. That does not make the item disappear. A tracker can note: blocked by external action while separately evaluating whether the mayor made a documented, sustained effort to deliver it. Accountability is strongest when it distinguishes inability from inaction.
The Evidence Standard Behind the Scorecard
Campaign trackers become unreliable when they rely on press releases alone. An announcement is evidence that an official announced something. It is not necessarily evidence that the policy exists, is funded, or produced results.
The strongest records use primary documents wherever possible: enacted budgets rather than proposed budgets; signed executive orders rather than preview statements; legislative text and vote records rather than descriptions of a bill; procurement notices and contracts rather than intentions to procure; agency datasets rather than unsupported performance claims.
Secondary reporting can add context, particularly when it documents negotiations, implementation problems, or disputes. But a reader should be able to see the basis for the status without accepting an outlet’s interpretation on faith.
Dates matter as much as documents. A mayor who proposes a program in the final week of a term has not delivered the same result as a mayor who launches it early enough for residents to use it. Track both the promise deadline and the dates of key actions: announcement, budget submission, approval, launch, first public results, and any revision or cancellation.
The tracker should also record changes to the original pledge. Administrations often reframe commitments after taking office. A promised “universal” benefit may become a limited pilot. A pledge to hire staff may become a plan to authorize positions without filling them. Those changes are not minor drafting choices. They are the substance of the accountability item.
Avoiding the Two Biggest Tracking Errors
The first error is grading rhetoric instead of governing. A mayor can repeat a promise at multiple press conferences without advancing it. The tracker should reward completed actions and verifiable milestones, not repetition.
The second error is demanding powers an office does not possess. New York City’s mayor controls a large executive branch, but not every force shaping city life. The City Council legislates and approves budgets. State government controls major policy areas and authorities. Courts can halt programs. Labor agreements, procurement rules, and federal grants can shape timing and cost.
A rigorous tracker does not use these facts as excuses. It uses them to assign responsibility correctly. If a mayor promised something requiring Albany, the relevant question is not simply whether Albany acted. It is whether the mayor pursued the commitment through the available tools: public advocacy, budget leverage, negotiations, legislative partnerships, or alternative policy design.
Why the Tracker Must Stay Live
A campaign promise is often judged too early or too late. Early in an administration, a policy can look stalled before its budget cycle begins. Late in a term, a program may exist on paper but have little measurable effect. A static scorecard cannot capture that movement.
A live tracker should update when new evidence changes the factual record, and it should preserve a visible history of prior ratings. If an item moves from in progress to kept, readers should be able to see what happened. If a claim once rated kept is later undermined by implementation data, the correction should be just as visible as the original rating.
That is the value of an accountability dashboard such as ReviewMamdani.com: it treats municipal oversight as a continuing public record, not an election-season exercise. The standard is simple but demanding: show the promise, show the authority, show the evidence, and explain the judgment.
The best tracker does not tell residents what to think about a mayor. It gives them a disciplined way to see whether power was used as promised, where progress is real, and where a public commitment still requires an answer.