About this project
The public story should be tested against the public record.
Norwich CT Fire puts the governing documents, dated records and competing claims in one place. The operator's name is not published. The sources and methods are.
AUTHOR’S ACCOUNT
Why I started looking.
I’ve lived in Norwich for 20 years, in East Great Plain. In February 2026, I opened the news and learned that the City had closed Yantic’s volunteer fire department.
I knew very little about Norwich’s fire service. This time, I wanted to do more than shake my head at another City decision. I went to Yantic and spoke with Chief Bobby Allen and Deputy Chief Frank Blanchard. That conversation led me to request the Town Street video and related records.
I wanted to hear the City’s account too. I met with Chief Wilson, spoke with officials and volunteers, toured the firehouses, attended meetings and training, and started working through the reports, policies and governing documents.
The question I kept coming back to was simple: is this true?
What I found led me to support the volunteers and challenge the City’s explanation. I believe the case for the actions taken against them is much weaker than the public narrative suggests.
There are legitimate improvements to make. My objection is to the justification, the authority being claimed and the way this has been handled. This site brings together the records behind that view, including evidence that challenges it.
This is the operator’s account and perspective, not an independently verified statement of motive or legal finding.
Independence
Not the City's. Not a fire company's.
This independently operated site carries no advertising and is funded privately. The operator's identity is intentionally not published; claims should stand or fall on the linked evidence rather than the identity behind the page.
The site is not operated by, endorsed by or affiliated with the City, the Norwich Fire Department, a fire district or an individual fire company. It uses no City seal, department patch or official wordmark.
The project favors preserving Norwich's volunteer companies and does not claim to be neutral about that policy preference. Anonymity does not change the standard: primary records are linked, interpretations are labeled and material corrections are logged.
How I handle the record
An email proves what the email says. It does not prove everything people want it to prove.
For every important claim, the site asks four questions: What is established by a primary record? Who is making the claim? What narrow conclusion does the source support? What missing record, amendment, testimony or court ruling could change it?
- 01Show the sourceWhere possible, the original public record is displayed or linked—not merely described.
- 02Name the speakerCity position, volunteer position, court allegation, independent reporting and site analysis are not interchangeable.
- 03State the limitA public statement proves that it was said. An allegation proves that it was filed. Neither automatically proves the underlying assertion.
- 04Leave room to be wrongMissing records, later amendments, new testimony and final court rulings can change a responsible conclusion.
What the source labels mean
Charter, ordinance, policy, email, minutes, budget, CAD record, or court filing.
Proof of what was said, not automatic proof of the underlying assertion.
Established news coverage summarized in our own words and linked directly.
Our interpretation, comparison, arithmetic, or conclusion.
What the claim labels mean
Directly demonstrated by reliable evidence.
Material disagreement with identifiable supporting sources.
The available evidence does not answer it.
The available primary record conflicts with the claim as stated.
Corrections
If a material fact is wrong, the correction will be shown.
Send the page, the disputed wording and the supporting source. A material correction gets a dated note explaining what changed. Clarifications are labeled. Only spelling, formatting, broken links and changes that do not alter meaning are fixed silently.
Requests from City officials, career or volunteer firefighters, organizations, and residents are evaluated under the same evidentiary standard.
Public submissions are currently paused. A new submission channel has not been launched. The standards and existing corrections remain public.
Correction log
October 2, 2026: Four February written assessments and their February 24 transmission were located. A blanket statement that no written fire analysis existed was too broad. The reviewed incident packet contains 18 files covering 17 incident identities; the two 4323 files are different versions, not identical duplicates. See the updated five-minute guide and evidence inventory for scope and source notes.
Right of reply
If the site materially discusses you, your response belongs beside the story.
Named people and organizations may submit a concise response. Accepted replies are linked from the relevant article and follow the same rules against threats, defamation, private information and unsupported personal accusations.
Privacy
Public discussion is paused. Stored records remain private where intended.
The public forum and tag-registration interface are unavailable in this release. Existing community records and private profile emails are preserved; private emails are not displayed here. The operator's identity remains unpublished.
Optional GoatCounter analytics is enabled for aggregate page loads, referring domains and selected actions. It uses no analytics cookies. Only predefined page paths and action IDs are sent; calculator values, district selections, results, personal information, URL queries and full referrer URLs are excluded. The separate voluntary poll uses a browser cookie to let you update your answer. Network requests inherently expose an IP address and browser headers to the receiving service. Sessions and individual pageview storage are enabled in the analytics account, although this site's analytics requests currently opt out of session tracking. Cookie-free analytics is separate from session tracking. Aggregate counts have no automatic deletion schedule.
Poll protection uses a browser cookie, Cloudflare Turnstile verification, and a keyed fingerprint of the connection’s internet address to limit repeat voting. Your browser contacts our Cloudflare verification service directly. The application stores the fingerprint, not the raw address; verification tokens stay in memory and expire quickly. Address claims remain for the poll’s lifetime; attempt counters expire after 24 hours and are removed during later verified voting attempts. Brief verification records expire within ten minutes and are cleared during later verified voting attempts. Existing votes collected before these safeguards have no address fingerprint. Shared connections may share one vote; these checks cannot establish one person per vote. Turnstile processes connection and browser information under Cloudflare’s privacy notice.