CallNYC.org

Context

On January 30, 2016, the New York City Council held a 1-3 p.m. hackathon at Civic Hall focused on constituent services.^[1][2]

The Council described the gathering as its first CouncilStat hackathon.^[2]

After the fuller CouncilStat dataset was released, Jamie developed CallNYC.org as an independent public-facing interpretation of those constituent-services records.^[3][4]

What was unclear

The data carried civic signal, but a public dataset was not yet a resident pathway. A person still needed to understand what an issue meant, which office or district context might matter, what next step was reasonable, and where the source data could mislead.

The surviving promotional graphic uses the branding 'New York City Council Hackathon.'^[5]

That source documents the visible event brand, not a longer formal registration title.

What I did

Jamie built the independent prototype, organized records into issue pathways, and translated administrative categories into public-facing guidance. A person could enter through a recognizable concern instead of first understanding the complete dataset. CallNYC was not commissioned by the Council, documented as a formal hackathon submission, or presented as an official City service.

What became usable

The prototype organized constituent-services records into issue pages, district context, and possible next steps. It treated data translation as a product and information-architecture problem: map a difficult source to the decisions a person needs to make, build a bounded pathway, and keep limitations inside the product.

Outcome and evidence

Politico New York covered CallNYC on March 14, 2016, connecting Jamie's independent project to the January gathering and the later fuller CouncilStat data release.^[3]

CallNYC paired 61 resident-facing issue pages with recognition posts directed to 26 Council accounts. A full-population disposition pass recovered attributable interactions from at least 19 serving Council member accounts, including public reposts and six member-authored posts or replies.^[6][7]

The public repository preserves the implementation. Together, the prototype, reporting, and source trail show a small but complete civic product: source data, information architecture, interface delivery, iteration, public documentation, and explicit scope limits.

Sources and notes

These notes preserve what each source supports and where its limits remain. See something that needs correction? Contact Jamie.

View 7 source notes

1. [1] Civic Hall announcement of a January 30, 2016, 1-3 p.m. New York City Council hackathon focused on constituent services.

   Original post

   The archived Civic Hall page preserves the embedded social post. It is not a recovered Civic Hall calendar listing or event-detail page.

   Boundary: This source does not establish a recovered Civic Hall calendar listing, a dedicated event-detail page, the complete formal event title, the agenda, the participant roster.

   Return 1

2. [2] New York City Council event-day post from Civic Hall identifying the gathering as the Council's first CouncilStat hackathon.

   Original post

   The source supports the narrower 'first CouncilStat hackathon' wording, not a broader historical superlative.

   Boundary: This source does not establish broader historical hackathon superlatives, the full agenda, a complete attendee list, formal winners, CallNYC as an official submission.

   Return 1Return 2

3. [3] Miranda Neubauer, 'Website provides new information about council members' focus,' Politico New York, March 14, 2016.

   The reporting connects Jamie to the January event, the fuller data release, and his independent development and iteration of CallNYC.

   Boundary: This source does not establish CallNYC as an official Council product, CallNYC as a formal hackathon submission, CallNYC as a documented winner.

   Return 1Return 2Return 3

4. [4] Public CallNYC source repository.

   The repository documents the surviving implementation of the independent, archived prototype.

   Boundary: This source does not establish official Council ownership, formal hackathon submission status, current resident-service guidance.

   Return 1Return 2

5. [5] NYC Council-branded promotional graphic reading 'New York City Council Hackathon' and displaying labs.council.nyc.

   The graphic supports the visible event branding, not a longer formal registration title.

   Boundary: This source does not establish a longer formal registration title, the agenda, breakout structure, participant roster.

   Return 1

6. [6] CallNYC X population disposition and URL manifest, July 15, 2026.

   A public-safe machine-readable manifest of 110 population dispositions, 84 posted URLs, engagement summaries, and named public-official interaction ledgers; raw post bodies and session data are excluded.

   Boundary: This source does not establish 110 recovered post bodies, individual account authorship, permanent platform metrics, formal endorsement, reasons the three records were not recovered.

   Return 1

7. [7] New York City Council, minutes of the stated meeting, September 28, 2016.

   The official roster corroborates that the 19 named people in the bounded CallNYC ledger were serving Council members in 2016.

   Boundary: This source does not establish control of social accounts, authorship of every post, endorsement of CallNYC, a complete engagement census.

   Return 1