Audit: factual and framing checks on the police-budget draft

What27s right

- Front-loads the most newsworthy elements: staffing requests, raise request, and the Axon bundling proposal. - Uses direct quotes and attributes them to recorded speakers.

Problems & fixes

1) Speaker-name consistency Issue: The transcript uses varied spellings and informal references ("Raelyn" vs. "Raylan"). Fix: Use the city staff names exactly as the transcript first introduces them and, where unsure, use the role ("Finance director") rather than risk misidentification.

2) Contract numbers and savings need confirmation Issue: The draft cites first-3-year and current contract numbers directly from the presentation but these figures were given as estimates and vendor quotes were described as not yet confirmed. Fix: Describe savings as "presented by the chief" and flag them as estimates pending vendor confirmation; avoid asserting confirmed buyout terms until the vendor provides them in writing.

3) Fire-district fiscal effect nuance Issue: The draft implies a simple dollar swap if the fire district forms. In reality, levy base changes, timing and asset transfers complicate the net effect. Fix: Explain the mayor/finance caution: the fiscal outcome depends on how property-tax base changes and the timing of transfers; council asked staff for a detailed model.

4) Public-records workload estimate Issue: Article summarizes public-records strain raised elsewhere in the meeting but did not quantify the workload or note who quantified it. Fix: Attribute the workload claim to the City Attorney and Clerk and note that staff promised to provide more detailed counts and cost estimates.

Severity: low-to-medium (clarifying rather than corrective).