A point-by-point accounting of two written public comments submitted for the July 8 meeting — what staff engaged, what they promised, what went unanswered, and what was refused. Written testimony works. Here's the evidence, graded honestly.
Updated July 10, 2026
Source review completed July 10, 2026
Before the July 8 City Council meeting, the Albany Records Project's Greyson Paynter submitted two written public comments through the City's comment form, ahead of the noon deadline. One addressed the Development Code hearing (Planning File DC-02-26) and the related public-improvements ordinance (AMC 15.06). The other was a general comment about the evening's license plate reader briefing and one operations idea.
This article is the accounting. Not "did the council listen" in the abstract — but point by point: what staff engaged, what they committed to fix, what nobody touched, what was refused outright, and where our own testimony turned out to need correction. We publish the misses alongside the hits because the misses are what make the hits believable.
This is a companion to our July 8 meeting review, which covers the full meeting neutrally. This piece is necessarily about our own submission — read it with that in mind. Every quote below is from the meeting record; every effect claim is graded by the evidence.
Anyone can do what we did. The City's meeting-materials page links a public-comment form for each meeting; written comments are due by noon on meeting day. Written testimony enters the record whether or not you attend, and staff read it before the meeting — a fact the July 8 transcript proves, as you'll see. You don't need standing, a lawyer, or a group behind you. You need the packet, the statutes it cites, and specific page-level claims. Vague concern gets sympathy; specific defects get responses.
One caution from this experience: the record has layers, and each layer can spell your name differently. The testimony was submitted by Greyson Paynter. The definitive merged transcript correctly captures Heemstra's AMC 15.06 reference as "Mr. Paynter"; another transcript line still misspells the name. Whether the official record gets it right won't be known until the adopted minutes publish; we'll check them. The reminder stands either way: the record only knows what's written into it, and it's worth verifying how your name lands in the version that counts.
The DC-02-26 comment made one request — continue the items or amend them on the floor, because the packet as printed contained defects that shouldn't be codified — and backed it with specific claims. Here's what happened to each.
Engaged and confirmed on the record. The comment flagged that the single-room-occupancy density figure in ADC 3.080(20) didn't legibly show the state-required value. Planner Anne Catlin addressed it directly, attributing it to "the testimony letters that you received": "It's not 33 units, it's 0.33. I just crossed out the 5." That is a staff-confirmed correction, on the record, sourced to written testimony.
Engaged with commitments to add language. The comment said the packet was missing HB 2005's 30-day decision deadline for crisis-stabilization-center and psychiatric-hospital review, and HB 3560's child-care colocation path. Catlin acknowledged the point — "a question was raised in one of the gentlemen who testified or provided written comments that we weren't completely complying with the law" — and offered specific language for both, reading the proposed additions aloud. Offers from the dais are promises, not amendments; the August 26 packet is where they become real.
Engaged and deflected to a document we couldn't see. The comment said Article 11 still carried a repealed referee system for land divisions (ORS 197.370, ORS 197.375, and ORS 197.380 were repealed by HB 2138). Catlin answered that the language is "correct in that second version," but "it's possible he couldn't see any changes because" the tracked changes didn't render. She also referred to questions from Greyson Paynter about SB 974 inconsistencies. That answer may well be right. It is also, by its nature, unverifiable until the clean redline is published — which is why obtaining that document is our top records request.
Engaged and defended. On AMC 15.06, the comment argued the draft attached SB 974's deadlines to the wrong things — starting the 30-day completeness clock at fee payment instead of receipt, and placing a 120-day timeline on the applicant instead of on the City's review. Assistant City Engineer Aaron Heemstra responded to both by name, referring to Greyson Paynter's testimony ("that was one of the comments from Mr. Paynter as well"), and defended the drafting with his own readings of the bill: the fee is "part of the application," and the bill's developer-documentation clause supports the applicant-side timeline. Fair enough — that's engagement, not evasion. But it means the dispute is now about which clause of SB 974 governs which clock, with a mandamus remedy hanging on the answer. Competing oral summaries can't resolve that; a written side-by-side analysis in the August packet can.
Never addressed, by anyone, all night. Three points got silence: the finding that describes a different project (Exhibit B Finding 1.5 recites Climate Friendly Areas changes — noise-corridor setbacks, block and perimeter lengths — that appear nowhere in this package's own summary of changes); the bonus-unit provision's statutory cross-reference (the draft cites ORS 197A.520(5) where the middle-housing reference appears to belong to 197A.420(5)); and the two parallel code sections still showing the old 0.5 SRO figure. We note the pattern without assigning a motive: the points that got answers were the ones that could be fixed or defended easily. The points that went unanswered are the ones that would require conceding a defect in the adopting record. All three will be resubmitted in writing for August 26.
The big ask — granted, with honest caveats. The hearing was continued to August 26, which is what the comment requested. We do not claim sole credit. Staff's stated reason was the track-changes failure, discovered independently. But Catlin also said the continuance "will give a chance for me to address some public testimony that we heard today" — so the testimony is part of the stated basis, in staff's own words. And there's a second wrinkle: Catlin referred to "both of the testimony letters." Our general comment didn't raise the SRO issue — which means either staff counted our two submissions loosely, or a second written commenter exists whose testimony was also never acknowledged aloud. We've requested the count.
And the vote. The 15.06 ordinance advanced only 4–2, so it must return for a second reading (Albany Charter § 37(1) requires unanimity to adopt in a single night). Councilor Newton's dissent tracked the comment's fifth point — separate what state law requires from what the City is choosing — almost verbatim: "if state law requires 5 changes, let's just make those 5 changes... instead of packaging everything together." Did the comment cause that? We can't know, and we won't claim it. Newton may have arrived there independently; the position was in the air all night. What the record supports is alignment, not causation. That's the honest grade, and we'd rather under-claim than overreach.
The general comment made three asks before the evening's verbal-only briefing on license plate readers.
Put the analysis in writing: raised in the room, refused on the record. The comment asked the City to place any ALPR legal analysis in the public record, or to prepare a short public memo before giving ordinance direction. That exact request surfaced from the dais — Councilor Newton asked for the insurer's response and a written debrief — and City Attorney Sean Kidd declined: "no, I'm not going to put it in writing because... it becomes public record then... I would argue it's attorney-client privilege." The council then did precisely the sequence the comment cautioned against: it gave staff direction (explore a signage ordinance) off a briefing that exists nowhere on paper. One legal note residents should know: attorney-client privilege belongs to the client — the city — and a council can direct that a non-privileged options memo be produced for public decision-making. The request renews at the late-August work session.
Credit public research: not addressed. The comment asked that if the Albany Records Project's published ALPR materials informed the report, the work be credited. No attribution was given, and we can't establish that the materials were used. Logged and dropped.
The staff listening exercise: not raised. The comment proposed a low-cost internal exercise asking city employees where operational friction is — the kind of process failure that produced the broken packet. Nobody mentioned it. We'll keep offering it, because July 8 was its own best argument: the track-changes failure cost the public a full hearing cycle.
Because the SRO density point drew the meeting's clearest staff response, we went back after the meeting and verified it against the rendered packet page rather than extracted text. It holds.
Page 84 shows the amendment in proper redline markup: a strikethrough on the "5" of "0.5," with "33" inserted beside it as new text. Read literally, the amended sentence composes as "each SRO unit is considered 0. 33 dwelling units" — an orphaned decimal and a floating number — and at ordinary reading size the strikethrough is easy to read as deleting all of "0.5," which would make each SRO unit count as thirty-three dwelling units. The planner confirmed the intended figure from the dais: "It's not 33 units, it's 0.33. I just crossed out the 5."
The intent was never really in doubt. The problem is that intent isn't what gets codified — text is. Nowhere in the code text does a clean "0.33" appear; the only place the correct figure exists is the narrative summary, which is not the law. Two parallel sections still read 0.5. So the testimony's ask survives contact with the printed page intact, and becomes the August 26 test: the adopted text must legibly read 0.33, in all three affected sections. A density rule the public can't read off the page is exactly the kind of defect this continuance exists to cure.
Of the roughly fourteen distinct points across both letters: five were engaged by staff on the record and attributed to the testimony; two produced commitments to add language; one was deflected to a document not yet public; two were defended on the merits; three were never addressed; and one was refused outright. The requested continuance happened, for stated reasons that include the testimony. One dissenting argument aligned with the testimony's central severance point, causation unknowable.
That's what one resident's written comments did at one meeting — not everything, and not nothing. The pattern is the lesson: specific, page-cited, statute-backed claims get responses. Even the responses that defended the drafting engaged the substance. The only claims that vanished entirely were the ones nobody could answer comfortably — and those are now teed up, in writing, for August 26.
For the August 26 continued hearing: resubmit the unaddressed points (Finding 1.5, the bonus-unit cross-reference, the 0.5 sections) with the corrected SRO framing; verify staff's "already fixed in the second version" claims against the clean redline we've requested; put the SB 974 clock analysis in writing so the dispute is resolved on paper; renew the written-materials request before the ALPR work session; and check the official minutes for the correct spelling of Greyson Paynter. Every commitment staff made from the dais on July 8 is on our checklist, and the only question that matters in August is the one this whole episode teaches: does the paper match what was promised out loud?
Sources: written public comments as submitted July 8, 2026 (on file); July 8, 2026 agenda packet; definitive merged July 8 transcript supplied July 9; Albany Charter §§ 20, 37; Enrolled SB 974 (2025) § 1(2)–(4); Enrolled HB 2138 (2025) § 21 (repealer); Enrolled HB 2005 and HB 3560 (2025); ORS 197A.430.
This article is supported by public records, source review, and neighbor-funded records work. Source gaps stay visible until the next record closes them.