Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Code Compliance Permits topic
No spam. Unsubscribe anytime.
Wasilla planners discuss code‑compliance process and surge in permit activity
Summary
Commissioners pressed staff for clearer code‑compliance procedures and more detailed permit reporting after planner said the office processed more than 30 permits in two weeks and that some compliance procedures and software integrations need clarification.
Get email alerts on the Code Compliance Permits topic
No spam. Unsubscribe anytime.
Commissioners at the Wasilla Planning Commission on Feb. 11 pressed planner Wellman for clearer procedures on code compliance and asked for more detailed reporting on recent permit activity.
Commissioner Brown asked whether the commission would be notified when a case escalates beyond the code compliance officer, asking specifically whether the police department, the clerk’s office or a hearing officer is involved. Wellman said she had not yet worked through escalation to court or hearing‑officer stage for local cases and that some aspects involving the police department’s software integration remain unclear.
“Well, I say no only because I don't know. I don't know. I haven't gone through that process yet,” Wellman said when asked whether adjudicated cases are reported back to planning staff. She said staff have discussed common wording differences in the code and will review whether the draft Title 16 rewrite needs edits to clarify what constitutes a “violation” and what triggers enforcement steps.
Commissioners also raised operational concerns about a recent surge in permit approvals. Wellman told the commission that the office has been unusually busy and that more than 30 permits were processed in the prior two weeks. She said many approvals were administrative and that staff plan to produce comparative permit reports and spreadsheets to show permit types and trends. The planning office uses CitizenServe for permit intake but noted limitations: the current CitizenServe setup does not include fine‑grained subtypes (for example, distinguishing types of commercial tenants) without adding new fields.
Commissioner Brown and others urged staff to create trigger measures or GIS layers to detect clustering of certain uses — for example, multiple home‑based bed‑and‑breakfasts on the same street over time — so the commission and public‑works staff can evaluate infrastructure and land‑use implications. Deputy Director of Public Works Robert Walden and Director Eric Shaw were described as part of staff pre‑application reviews for infrastructure, septic and parking capacity.
Wellman described the office’s pre‑application meetings as a way to screen projects before full application reviews and said that larger or more complex commercial proposals are elevated to the commission. She gave a permit example of a proposed commercial freeze‑dried food kitchen, listed in the permit log as Prepper Bends at 490 South Knick Goose Bay Road; that application included multiple pre‑application meetings and cross‑department review.
The commission agreed to pursue clearer internal tracking so members can review quarterly or periodic permit reports and better understand how administrative approvals affect neighborhood character and public‑works capacity.
No public comments were received at the meeting and staff reported no hearings scheduled for the evening.

