How this site is built

Where the record comes from

Five sources, each feeding different pages.

Approved minutes — Meetings, Votes, Members

The city publishes its minutes as PDFs through the CivicClerk portal. Only approved minutes are collected. A draft can still change on the floor. Each PDF is parsed into individual motions, each motion into the roll call underneath it, and each name in that roll call is matched to a member. The vote totals on the Members page are counted from those roll calls and nothing else.

Meeting recordings — Meetings

Where a recording exists, it is transcribed by speech recognition and published alongside the minutes. Speech recognition mis-hears names and technical terms; the transcript is offered as a searchable aid to the recording, not as a record of equal standing to the minutes. Some meetings appear here with a transcript before their minutes are approved, and those are marked.

Posted agendas — Meetings

Some meetings (special sessions, joint work sessions, the annual planning conference) are never minuted and sometimes never recorded. Leaving them out would show a gap on a night the council actually met, so each one gets a page built from the agenda the city posted beforehand. An agenda says what was to be taken up, not what was decided, and those pages say so at the top. If minutes are approved later, the record replaces the agenda.

The budget book — Budget

Figures come from the city’s own ClearGov budget data, at full precision with the account number attached, and are checked line by line against the published PDF budget book. Where the two disagree, the published book wins and the difference is noted on the page.

Tax notices — Tax

Rates and valuations come from the city’s Truth-in-Taxation notice, Utah County’s combined notice, and the Utah State Tax Commission. Where those three disagree on a figure, the page says so rather than picking one quietly.

What a machine wrote, and what it didn’t

This matters enough to state plainly rather than bury.

Never machine-written: vote counts, who voted which way, dates, budget figures, tax rates, and the text of the motion as the minutes recorded it. Those are read out of the source documents mechanically. If one of them is wrong, either the source is wrong or the parser has a bug, not a model.

Machine-written: the plain-English headline, summary and “what this means for you” note attached to each motion, and the prose summaries of transcribed meetings. The minutes record motions in the form “An Ordinance of Eagle Mountain City, Utah, amending Municipal Code 16.15 Concept Plans…”, which tells a resident nothing. A language model rewrites that into a sentence, working only from the parsed motion text. It can still misread emphasis or nuance. Where a headline and the motion text seem to disagree, the motion text is the record.

Motions with no clean machine-readable text are left out of the plain-English layer rather than published with scanning damage in them, so some older motions appear only in their original wording.

The projections are a model, not a forecast

The projections page is the one page on this site that is not a republication of anything. It is an independent planning estimate, built here, from the city’s adopted budget and adopted rate. Eagle Mountain City has not published, reviewed or endorsed it, and it should not be quoted as a city forecast. Its assumptions are stated on the page so they can be argued with.

How current it is

Minutes are collected as the city approves and posts them, which usually puts a meeting on this site a few weeks after it was held. Recordings appear sooner. The budget and tax pages update when the city or the county issues a new document, not on a schedule. Each page carries the date of the data behind it.

Corrections

Errors here are worth reporting, and get fixed rather than argued with. The most useful report names the meeting date and the figure, so it can be traced back to the source document. Where a correction changes something a reader may already have relied on, the change is noted on the page rather than made silently.

Send corrections to civicrollcall@gmail.com. The same address takes anything else about the site: a meeting that is missing, a document worth adding, a claim that is circulating. Everything sent there is read.

Who runs it

Civic Roll Call is published by an Eagle Mountain resident, independently, with no affiliation to Eagle Mountain City, to any candidate or to any campaign. It carries no advertising and sells nothing. The code that builds it, including every parser and every figure check described above, is open for inspection, and the address on this page reaches the person who runs it.