FOR NEWSROOMS AND INVESTIGATIVE DESKS
You already cover the update. We connect what it's part of.
A newsroom we work with told us directly: the first version of this was “update me”, things that happened, most of which they already knew. That's their strength already, and it's not where they needed help. So we rebuilt around threads: a topic on the record across multiple meetings and several weeks, with the date it started, the material perspective and explainer pieces are actually made of, not another item on the list.
One intake form. One live thread on your beat. No cost, no call required.
WHAT THIS LOOKS LIKE FOR YOU
99%
of these documents are invisible to search
4,400+
jurisdictions on continuous watch
0
records requests needed, all already public
IN YOUR VOCABULARY
A thread is not a document. It's where a story started.
One meeting is an item. The same topic returning meeting after meeting, over weeks, dated from the first time it appeared, that's a thread, and it's closer to the shape a real story has.
THE THREAD
The topic connected across meetings, not one at a time
A budget line, a zoning question, a grant application, the same subject returning meeting after meeting, with the date each one starts. One document is an item. Three meetings over nine weeks is a thread, and it reads as one.
BEYOND THE UPDATE
Built for the coverage you don't already have
Every thread we surface is tagged by which of your own reader needs it actually serves. We're not trying to beat you at “this happened”, you already do that well. We're pointed at what's harder to staff: perspective, connection, the deeper piece.
THE RECORD, READ FORWARD
Where a thread started, before you had to go looking
By the time a topic is obviously a story, the record already shows where it began. We hand you that starting point and every meeting since, so the reporting time goes into the piece, not into reconstructing the timeline.
A REAL THREAD, NOT A MOCKUP
This is what a thread actually looks like.
One town, one topic, pulled straight from a real weekly delivery, not a constructed example. Three meetings, nine weeks, before most readers knew a moratorium was even being discussed.
Brunswick Data Center Moratorium
Town Council · Brunswick, ME · on the record 1 June – 3 August · 3 meetings over 9 weeks
WHAT THE RECORD SAYS
The Town Council will hear public comments to approve a Data Center moratorium and will take any appropriate action. The moratorium would take effect immediately upon adoption and remain for 180 days to allow for drafting an amendment to the Brunswick Land Use Ordinance and other Town codes. Staff are seeking direction on whether a contract zoning approach would provide sufficient oversight or if additional resources should evaluate an outright prohibition.
THE THREAD, MEETING BY MEETING
JUNE 1 · TOWN COUNCIL · PUBLIC HEARING
The Council hears public comment on a proposed 180-day moratorium on certain data centers, to give staff time to research and draft ordinance language.
JUNE 23 · SUSTAINABILITY COMMITTEE
The Sustainability Committee takes up the AI Data Center Moratorium and its own role in the matter, the thread widens to a second body before the Council acts.
AUGUST 3 · TOWN COUNCIL
The moratorium comes back for a vote, the thread's third meeting, nine weeks after the first, and the point where most coverage of this would actually start.
OUR READ
If you are a resident of Brunswick, this affects you because the Town Council is considering a temporary ban on data centers while they decide how to regulate them.
SERVES: UPDATE ME · EDUCATE ME
Real town, real meetings, real dates, condensed from an actual weekly delivery. Every claim above traces to a public agenda; none of it is a mockup.
WHERE IT PLUGS IN
START HERE · NO COST
Tell us your beat. We will find one thread already forming in the record.
Newsroom budgets are not our pricing model. Send us the beat and the geography and we will run one assessment free, source links included.
WHO WE SERVE