Atherton weighs tighter construction‑parking rules, enhanced fines and stop‑work enforcement

Staff and council spent the bulk of the meeting on a staff report about the cumulative impacts of overlapping construction projects. Fred (S8), the staff presenter, told the council that parking by construction workers is the town’s “biggest issue” and that when several large projects overlap the effects compound for neighbors. Fred said noise, dust and the potential to impede emergency vehicles are recurring concerns and that contractors often park on neighborhood streets because they lack on‑site space.

Fred summarized current tools: the Construction Operations Plan (COP), alternate parking plans, required signage and designated on‑site points of contact, administrative citations, and stop‑work orders for code violations. He told the council many builders comply but that a small share of projects produce the majority of complaints; he said some jurisdictions (cited: Hillsborough, Tiburon) prohibit or strictly limit off‑site parking for construction and use shuttle/parking‑lot approaches for large jobs.

The staff report proposed a menu of changes for council direction: require an on‑site, reachable point of contact; strengthen the COP and neighbor notification; consider an enhanced fee schedule to increase the cost of repeated violations; and use stop‑work orders as a cumulative enforcement remedy once a site triggers a threshold of repeated, documented violations. The city attorney, Monet (S10), cautioned that “stop work orders are traditionally only allowed for building code violations or safety issues” and that an enhanced fine structure is typically available only when tied to building or safety code violations (transcript quoted “Government code section 36,900” as permitting enhanced fines for such violations). Monet said ordinary parking violations may remain subject to standard fine limits (the transcript lists the typical $100/$200/$500 escalation for infractions).

Residents and council members gave concrete examples that shaped the discussion: one speaker described a concrete truck washout that killed landscaping and raised potential stormwater/NPPS concerns, and others reported repeated flat tires from nails and screws tracked from job sites. Speakers urged requiring truck washout controls, magnetic sweepers and periodic street sweeping as part of COP requirements; staff said these measures are already part of stormwater and COP compliance but acknowledged enforcement gaps.

Council members discussed thresholds for cumulative enforcement (e.g., three documented violations triggering additional remedies), whether violations should be counted per code section or per site, and how to define when off‑site parking should be disallowed (suggestions ranged from applying a dollar threshold for project value to categorizing projects by duration). Several members asked staff to return with comparative language from neighboring towns (Hillsborough was cited as an example) and with a concrete set of ordinance amendments and implementation options for council consideration. Staff also plans a developers’ roundtable to gather industry feedback.

What happens next: staff will gather comparative ordinances and data, draft specific COP and municipal code amendment options (including neighbor‑notification language, enhanced fines where legally permitted, and criteria for cumulative stop‑work intervention), and return to the council with recommendations. The council gave staff direction but did not adopt any ordinance at this meeting.