Summary
Between May and July 2026, New York City's Commission on Government Efficiency, a 15-member charter revision commission, ran ten public hearings across the five boroughs, heard hundreds of witnesses, and filed five ballot questions for the November 3 general election. OCC Research tracked the entire cycle with a governance memory system: a structured, citable record of who testified, what they asked for, and what the commission did with it, published as a bilingual public dashboard at occresearch.org/coge.
This case study reports what that record shows. Four findings stand out:
- 1The commission engaged most of what it heard, but the loudest ask did not reach the ballot. Of 21 recurring themes, four reached the November ballot; the most-raised theme of the cycle, open primaries with 33 witnesses, was deferred to a future commission, with reasons the report spells out.
- 2Written testimony, not hearing appearances, is what entered the record's citations. One witness's spoken Brooklyn testimony was never footnoted, while her two written submissions were cited four times, once as the sole source for a final-report recommendation.
- 3The official record ran weeks behind the process it documents. As final-report drafting began, two of twelve meetings had official transcripts posted; the final meeting's transcript link pointed to the wrong file for roughly two weeks.
- 4Every ballot question can be measured with data the city already publishes, and each one exposes a data gap. The subject of ballot question 1, revocable consents, has no public dataset at all.
The Setting
The Commission on Government Efficiency (COGE) was appointed by Mayor Mamdani in 2026 with a mandate to propose efficiency-related charter amendments for the November 3 ballot. It had roughly eight weeks of public process: a June 4 kickoff, ten borough hearings from June 9 to July 13, a preliminary staff report released July 2 and adopted July 6, and a final meeting on July 23 at which the commission approved five ballot questions, its final report, and the filing resolution, each by a 15-0 roll call.
OCC Research followed the cycle as an independent observer. Our purpose was not advocacy for any proposal. It was to test a thesis: that public institutions lose the connective tissue between what they hear and what they decide, and that a structured memory of the process, built while the process runs, changes what the public can know.
What OCC Built
The system behind the dashboard is a scoped-down governance memory system (GMS v0) with three components:
Proposal Lifecycle Metadata (PLM): commissioners, resolutions, hearings, votes, and the charter chapters under review, each stored as a structured record with a resolvable identifier.
Recurring Themes and Frictions (RTF): patterns across testimony, built up hearing by hearing. Each theme carries its witness count, supporting quotes tied to specific speakers and meetings, and source chips that link claims to verifiable external documents.
Outcome Review Anchors (ORA): a scaffold keyed to the November 3 ballot, designed to populate once outcomes exist. The measurement framework below is, in effect, ORA's plan.
The workflow: hearing audio and official transcripts are ingested, each witness and claim becomes a structured record checked against a fixed format, names are corrected against adopted minutes, and every claim on the public page is checked against its source before publication. Editorial standards were enforced line by line: plain English, hedged predictions, precise attribution (one witness means one witness), and quotes attached only to points they actually support.
Two numbers describe the resulting record: 21 recurring themes tracked across ten hearings, and, after the final report appeared, a report-check appended to every theme stating what the commission did with it.
Did the City Listen? What the Record Shows
The question that organized our analysis came from a Manhattan florist's plea at the first hearing: listen before legislating. After the final report, we checked every theme against it.
| Witnesses | Theme | Where it landed |
|---|---|---|
| 33 | Closed primaries shut out unaffiliated New Yorkers | Deferred with reasons |
| 28 | Contract-registration delay makes firms finance the city | Partly on the ballot |
| 21 | Build in-house digital teams instead of renting them | In the commitments |
| 20 | Write AI rules into the charter | Not in the final report |
| 20 | One accountable leader for the city's technology | Partly in |
| 20 | MWBE firms are certified but shut out of contracts | Not in the final report |
| 20 | Remove outdoor dining's revocable-consent requirement | On the ballot |
| 16 | Streamlining must not become a “fast pass for exploitation” | In the report, explicitly |
| 16 | Civil service hiring is the bottleneck under everything else | Deferred, plus commitments |
| 16 | Prescriptive procurement timelines; pay nonprofits on time | Partly, outside the charter |
| 15 | Protect oversight agencies' budgets and independence | Deferred with reasons |
| 14 | Untangle the rules that stall street redesigns | On the ballot |
| 12 | Consolidate fragmented permitting into a single authority | On the ballot |
| 8 | Counter-theme: do not streamline away the council's checks | Partly heeded; changed outcomes |
| 6 | Stop treating nonprofit stewards like concessionaires | Deferred with a named path |
| 5 | Set targets, not rigid rules, for the rainy day fund | On the ballot |
| 5 | Proportional representation | Not in the final report |
| 4 | Give the city a comprehensive plan | Not in as asked |
| 4 | Make the city budget legible and comparable | Not in the final report |
| 1 | Listen before legislating | In the report's method |
Reading the scorecard, three patterns emerge.
Volume did not decide outcomes; jurisdiction did. The four themes that reached the ballot ranked 7th, 12th, 13th, and 16th by witness count. The two most-raised themes, open primaries and contract registration, were constrained by things the commission said were outside an efficiency mandate or governed by state law. The final report is candid about this: on elections it concedes that “the bulk of testimony the Commission received on this issue was to promote open primaries,” recounts how the 2003, 2010, 2024, and 2025 commissions each declined or were rejected by voters, and concludes electoral reform did not fit an efficiency mandate. The preliminary report did not include the issue; the final report engages it and says no, with reasons.
Engagement, not adoption, is the honest measure of listening. Almost every theme with a substantial witness count got a written answer of some kind: a ballot question, a commitment by the administration (the 2-for-1 hiring restriction lifted, OMB review timelines, DCAS exploring new IT titles), or a deferral with stated reasons. By the standard of “did testimony leave a trace in the written record,” the commission's final report scores well. By the standard of “did the most-requested changes happen,” it does not. Both statements are true, and a memory system's job is to keep them distinguishable.
The counter-testimony mattered. The eight witnesses who warned against streamlining away the council's checks, and the labor witnesses who asked that notification requirements survive any reform, can point to specific guardrails in the final package. Minority positions left fingerprints, which is worth knowing in a process that could otherwise be scored only by majorities.
A witness-level trace: how testimony actually travels
One witness illustrates the mechanics of impact better than any aggregate. A technologist and former city employee testified in person at the June 11 Brooklyn hearing on civil service hiring filters and the city's spending on outside digital services. Her spoken testimony was quoted on our dashboard and became part of the hearing's public story. The final report never footnotes it.
What the report cites, four times, are her two written submissions of June 24 and July 10: on DCAS workforce planning, on reporting hiring metrics to find bottlenecks, on making civil service information navigable, and, as the only witness cited on the point, on replacing the charter's outdated technology-office references with a framework built around the Office of Technology and Innovation. None of it reached the ballot; the hiring points were answered with administration commitments and the technology-governance point was engaged and left to ongoing work.
The lesson for anyone who testifies: the hearing gets you heard, the written follow-up gets you cited, and neither guarantees the ballot. A memory system makes that whole arc visible, which no single document in the official record does.
The Official Record Ran Behind the Process
Every hearing had a stenographer, and the commission posted videos with automatic captions quickly. The official transcripts moved slower, and the gap is documentable because OCC logged the commission's meetings page throughout, and the Internet Archive's Wayback Machine captured it independently.
- 1Jun 4 → ~Jun 22Kickoff meeting's official transcript posted about eighteen days later.
- 2Jun 9 → ~Jun 17First Manhattan hearing's transcript posted about eight days later.
- 3Jul 9 · Jul 12Wayback Machine captures show exactly two official transcripts posted, out of eleven meetings held.
- 4Jul 12 – Jul 14The June 22 Queens transcript appears, on or about the day of the final hearing, per its filename date and OCC's logged scrapes.
- 5Jul 13The posting lag is raised on the record at the final hearing and answered on the record; the exchange is memorialized verbatim in that hearing's official transcript. Eight of twelve meetings have no posted transcript as final-report drafting begins.
- 6by Jul 26All public hearings' transcripts are posted, most after the final report was drafted and the ballot set.
- 7Jul 26 – Aug 7The link labeled “July 23 Meeting Transcript” points to the July 13 hearing's file; the meeting that adopted the ballot questions has no accessible official transcript.
- 8Aug 7The genuine final-meeting transcript is posted, fifteen days after the meeting, and the link is corrected.
Two methodological notes. First, the city's own server metadata could not establish this timeline: a site redeploy on July 14 stamped every PDF with that date, so independent captures (Wayback, logged scrapes, filename dates) were the only way to reconstruct the sequence. Second, we report the sequence and let it speak; whether the posting pace was reasonable for a compressed eight-week process is a judgment we leave to readers.
The systemic point is not about any person or office. It is that a deliberative process and its official record ran on different clocks, and for the crucial stretch, the drafting of the final report, the public record trailed the deliberation it documents. An institution that wants its process to be auditable in real time needs its record to keep pace with its decisions, or needs someone outside the institution keeping the clock. This cycle, the latter is what happened.
The Five Ballot Questions
On November 3, New Yorkers will vote yes or no on five questions filed by the commission (exact texts, plain-language abstracts, full amendment text):
1 · Streamline the use of public space (ramps, benches, planters, cafes): revises revocable consent, removes the mandatory public hearing, modernizes notice, and merges the sidewalk and roadway cafe applications into one process the commission projects at about two months, against today's six to eight months for sidewalk cafes and three to five for roadway cafes.
2 · Reform the contracting process: procurement transparency, a simplified pre-contracting questionnaire, delegated contract approvals, and a simplified client-services plan, aimed at small businesses and nonprofits.
3 · Speed up street safety projects, office leasing, and activation of city land: simplifies review of street safety projects and fast-tracks the sale or lease of modest city properties, air rights over city-owned landmarks, and office leases.
4 · Simplify building permitting: a centralized construction permitting hub (one digital front door across the more-than-a-dozen agencies involved), broader certificate-of-occupancy authority within DOB, and waterfront permitting consolidated into DOB.
5 · Require contributions to the rainy day fund: sets a reserve target of 12% of city tax revenue, directs a contribution formula developed in consultation with the Comptroller, and aligns withdrawal criteria with state law.
How to Know If They Worked: A Measurement Framework
Each question makes an implicit empirical promise. Each promise can be checked against data the city already publishes, and in every case the checking also reveals a gap worth closing. Datasets below are on NYC Open Data unless noted; all were verified live in August 2026.
The promiseCafe permitting drops from six-to-eight months to about two; public input survives the loss of the mandatory hearing.
Baselines todayThe commission's own processing-time figures (6–8 months sidewalk, 3–5 roadway); 2,056 locations in Dining Out NYC Locations, updated daily; permitted street events in NYC Permitted Event Information.
Success metricsMedian application-to-approval days for the merged cafe process; count and borough distribution of active cafe consents (equity check: do gains reach beyond Manhattan); volume of DOT's promised “alternative methods” of public input.
The gapThere is no public dataset for revocable consents, the very instrument Question 1 amends, and the sidewalk cafe dataset has been frozen since 2023. If the question passes, DOT publishing application-level processing data should be the first accountability ask; without it, the two-month promise cannot be independently verified.
The promiseLess burden, more transparency, faster internal approvals.
Baselines todayMOCS itself testified that end-to-end procurement runs 312 days for bids and 387 for proposals. The Comptroller's office reports that 90.7% of human-services contracts arrived late for registration in FY24, up from 88.5% in FY23, with nearly 40% more than a year late. The Recent Contract Awards feed captured 3,203 award notices totaling roughly $25.5 billion in FY26.
Success metricsShare of contracts registered after their start date (the retroactivity rate); days from solicitation to registration by agency and method; interest paid on late payments; MWBE award share. Sources: Checkbook NYC, the Comptroller's vendor contracting and payment dashboard, and the annual contracts summary reports.
The gapMOCS's Agency Procurement Indicators stopped appearing on the open data portal after FY15; the current indicators live in PDF reports. The single most useful transparency step this question could trigger is per-contract milestone data published in open, sortable form, which is exactly what the human-services witnesses asked for at Staten Island.
The promiseDangerous intersections get fixed faster; surplus property stops sitting idle.
Baselines todayRoughly a thousand Vision Zero street improvement corridor projects recorded since the program began (SIP Corridor and companions); 85,546 crashes, 49,634 injuries, and 229 deaths citywide in 2025 (Motor Vehicle Collisions); 3,089 city-owned parcels categorized “property with no use” in City Owned and Leased Property, the surplus inventory the fast-track targets.
Success metricsStreet improvement projects completed per year and, if the city will publish it, design-to-construction duration; injuries and deaths at treated locations before and after (the collisions data supports this directly); the count of no-use parcels moving to disposition or activation per year; time-to-lease for city office space.
The gapProject-level timeline data for street redesigns is thin; the Capital Projects Dashboard covers budgets and schedules at a coarser grain. A before/after safety evaluation is the strongest test this framework proposes, and the data for it already exists.
The promiseOne digital front door replaces a maze of more than a dozen agencies.
Baselines todayFor jobs approved in the first half of 2026 in DOB NOW job filings (n=4,588), the median filing-to-approval time inside DOB was 16 days, but the median filing-to-first-permit time was 80 days, with a 90th percentile around 485 days. Those figures cover DOB's own pipeline only.
Success metricsThe honest one does not exist yet, and that is the point. Today no dataset captures a project's full journey across DEP stormwater review, Parks tree protection, FDNY, DOT, and DOB; the fragmentation the question targets is mirrored in fragmented data. If the hub is built, its own logs become the measure: median end-to-end days from first submission to final permit across all agencies. Interim proxies: DOB NOW medians above, and certificate-of-occupancy issuance (DOB NOW CO).
The gapThe hub should be born with a public performance dataset. Writing that expectation into implementation, not the charter text, is where advocacy attention could go next.
The promiseThe city saves by rule, not by mood.
Baselines todayThe Revenue Stabilization Fund holds about $1.97 billion, has had no target balance and no mandated deposits since its 2020 creation, and the FY27 preliminary plan proposed drawing $980 million, roughly half of it. The question's 12%-of-tax-revenue target sits inside the range the Comptroller's own proposal argued for (10% minimum, 16% goal). Against tax revenues on the order of $80 billion, the target implies a reserve near $9–10 billion, roughly five times today's balance.
Success metricsThe fund's balance as a share of tax revenue, year over year, against the 12% target; whether the contribution formula is adopted on schedule and deposits actually follow it in each adopted budget; withdrawal events checked against the stated criteria. Sources: the Comptroller's quarterly cash reports, the annual comprehensive financial report, and the State Comptroller's plan reviews.
The gapThe fund's balance is published in PDFs and press releases, not as an open, downloadable series on the data portal. A one-table dataset would make this the easiest question of the five to hold accountable.
Cross-cutting
Passage itself is measured first: certified results from the NYC Board of Elections (vote.nyc) after November 3. Beyond passage, two lenses apply to every question: equity (do faster cafes, permits, and dispositions distribute across boroughs and communities, all of the above datasets carry geography) and the counter-theme from the hearings (do the council's checks and public-notice functions demonstrably survive, which is a records question as much as a policy one).
What This Says About Governance Memory
The through-line of this case study is that every one of its findings required connecting records that no single institution keeps connected: testimony to footnotes, footnotes to ballot outcomes, hearing dates to transcript posting dates, charter promises to open datasets. None of the individual facts were hidden. The connections were simply nobody's job.
That is the case for governance memory systems in one sentence: the connections should be somebody's job. This cycle, a one-person research practice with a structured pipeline could hold a fifteen-member commission's full public record, check its final report against every recurring theme, reconstruct its publication timeline when server metadata failed, and hand the next phase, outcome measurement, a ready framework. The system's outcome-review scaffold now has its anchor: November 3, five yes/no questions, and the baselines above recorded before the vote, which is the only time baselines can be recorded.
Method and Limitations
Sources: official transcripts and minutes (nyc.gov), meeting videos, the preliminary and adopted final reports and appendices, Wayback Machine captures of the commission's meetings page, OCC's logged scrapes, and the NYC Open Data and Comptroller sources linked above. All dataset figures were queried in August 2026 and reflect data as of that date; the DOB timing figures cover filings approved January–June 2026 and carry the usual caveats of administrative data (professional certification paths, still-pending filings not yet counted). Witness counts reflect OCC's theme attribution, not an official tally. Our analysis reflects the concerns most raised in testimony, not external polling or program data, and whether any measured change is attributable to a ballot question rather than concurrent reforms is a question the before/after designs here can inform but not settle.
Governance that remembers. Institutional Memory as a Service.
Have thoughts or feedback on this research?
Othman@occresearch.org