Condition 14: construct the noise berm along the east property line before occupancy. The hearings officer reads it into the record. The planner copies it into the staff report. Somewhere between the staff report and the final approval letter it disappears — a renumbering in the last revision, or a paragraph dropped in reformatting; nobody knows. The project gets its certificate of occupancy. Five years later a neighbor calls about noise, the code enforcement officer pulls the file, and no one can establish whether the berm was ever required. The hearing minutes say one thing, the approval letter says another, and the planner who would have known is retired.
That is the whole argument. When a large project gets approved, the approval almost never says just yes. It says yes, subject to conditions — road improvements, water commitments, noise limits, monitoring, decommissioning, payments tied to milestones. Those conditions are promises made in public and relied on by neighbors. Then the hearing ends, and the promises go into a PDF.
How Conditions Dissolve
Nobody decides to ignore conditions of approval. They dissolve. The conditions live in a final order, not in any system staff open daily. No one person owns verifying them — the planning director assumes public works is watching the road improvements, and public works assumes that was the applicant's engineer. Deadlines pass silently because nothing was set to fire. A trigger like prior to occupancy depends on whoever signs the certificate of occupancy remembering to check a document they may never have seen. And when staff turn over, the reason a condition exists leaves with them. Years later a complaint arrives and reconstructing compliance is archaeology: hearing minutes, an old staff report, an email thread someone may still have.
What a Conditions Register Is
A conditions register is a simple idea: every condition of approval becomes a tracked record. Each entry carries:
- The condition text and its source — which approval, which hearing, which page of the minutes
- The responsible party — applicant, agency, or third party
- The trigger — a date, a milestone, or an event like occupancy or first operation
- The evidence required to call it satisfied — an as-built drawing, a noise measurement at the property line, a recorded easement
- Current status, including the honest ones: pending, satisfied, waived, modified, disputed
- A history of who verified what, and when
Nothing on that list is complicated. What's rare is having all of it in one place, kept current. With a register, Condition 14 has a row, a trigger tied to occupancy, and an empty evidence field that somebody has to explain before the certificate goes out.
Why the Spreadsheet Version Fails
Most agencies that track conditions at all track them in a spreadsheet, and it works until it matters. Three versions circulate and nobody is sure which one the assistant planner last updated. Nothing fires when a deadline approaches. A status flips from pending to satisfied with no record of who flipped it or what they looked at. The evidence — the test report, the photo of the finished berm — sits in someone's inbox, not attached to the condition. For commitments that may be litigated, appealed, or pulled in a public records request, the tracking has to be as durable as the commitment.
Where This Bites Hardest
The register matters most exactly when projects are large: data centers, industrial water users, multi-year phased build-outs. Those approvals carry the most conditions — megawatts by phase, will-serve letters, water rights, noise measured at the property line, decommissioning funding — on the longest timelines, with the most public attention. A phase that opens in 2031 will be checked against promises made at a hearing in 2026, by staff who were not in the room. They need something better to consult than the minutes.
Conditions of approval are the public's half of the bargain. If nobody tracks them, they were never really conditions — they were suggestions. A register is how a promise made at a hearing is still a promise, and provably kept, ten years later.