Issue No. 3 · October 5, 2026
Hey host. If you host in Scottsdale, AZ, your registered emergency contact now has to pick up for noise complaints and other non-emergency calls too, not just true emergencies, and the rule already took effect on August 24. There's no grace period here: a contact who doesn't respond can trigger fines starting at $500 and climbing to $1,000 per 30-day period.
Slow week for STR regulation news: only one item cleared our confidence bar this week. Lean on the Best Practices section, STR Idea of the Week, and the ADU Tip of the Week below to round out this issue.
This Week's Regulation Changes
Scottsdale, AZ: The City Council unanimously amended Ordinance 4720 (Scottsdale Revised Code Section 18-172) on Aug. 24, 2026, so a short-term rental's registered emergency contact must now also respond to non-emergency complaints, like noise or parking disputes, not just true emergencies. The change is already in effect. Fines start at $500 and climb to $1,000 per 30-day period for a contact who doesn't respond. If you host in Scottsdale, confirm your registered contact actually answers for routine neighbor complaints, not just 911-level problems, and keep a simple log showing you responded. Source →
ADU Corner
Regulatory News
North Carolina (statewide, including Asheville): Gov. Josh Stein signed Senate Bill 445, the Regulatory Reform Act of 2026 (Session Law 2026-59), on Aug. 11, 2026. It requires every North Carolina city with 50,000 or more residents outside the coastal counties, a group that includes Asheville, to allow at least one ADU by right on any lot zoned for a single-family home: no special zoning approval, no minimum parking requirement, no inflated permit fee, and no size cap below 800 square feet. The by-right rule takes effect Jan. 15, 2027, and covered cities must adopt conforming local rules by July 1, 2027. If you're planning an ADU in Asheville, start watching the city's zoning code for its implementing ordinance over the next several months. Source →
ADU Tip of the Week: Utility hookups, not construction, blow ADU budgets
If you're planning an ADU, get a utility capacity assessment before you finalize floor plans, not after. Sewer and water laterals, and a separate electrical panel, are consistently the line items that blindside people, especially on older lots where the existing service was never sized for a second unit. Redesigning a floor plan around a surprise $15,000 electrical upgrade partway through is far more painful (and expensive) than designing around it from day one. Ask your contractor or a plumber/electrician for a capacity check as your very first step, before you fall in love with a layout.
Trend of the Week: STR actions by type
One new restriction logged this issue (Scottsdale, AZ). No new fees, bans/phaseouts, or court/legal actions this week.
STR Idea of the Week
Welcome guide as a compliance tool
Your welcome guide usually does double duty as a tourist pamphlet, but it's also one of the simplest tools you have for staying out of trouble with your local ordinance. If your jurisdiction caps occupancy, restricts parking, sets quiet hours, or requires a permit number to be posted, put all of that in writing in the guide itself, not just in a pre-arrival text a guest might skim past. A guest who signed off on a stated occupancy limit and quiet hours is a much easier conversation when something goes sideways at midnight, and a documented house rule is exactly the kind of thing that helps you if a neighbor's complaint ever turns into a city inquiry.
What to include
Occupancy limit, stated as a number, not "reasonable"
Quiet hours, with the exact start and end time
Parking rules: how many spots, where, and where not
Your permit or license number, if your city requires it to be posted
Best Practices
Setting up a responsive local-contact protocol
A growing number of cities (Scottsdale's new rule this week is a good example) now expect your registered local contact to answer for routine, non-emergency complaints, not just true emergencies. That's a meaningfully different standard than most hosts have set up for. This is general guidance, not legal advice, so check your own jurisdiction's specific requirements.
Local-contact protocol checklist
A named contact who can physically reach the property within whatever window your ordinance requires, not just a phone number that forwards to voicemail
A written response-time standard for your contact, even if your city doesn't specify one, so you have an internal benchmark
A simple log (a shared spreadsheet or notes app is fine) of every complaint call, when it came in, and how it was resolved
A backup contact who's briefed on the property and reachable if your primary contact is unavailable
The contact's name and number posted exactly where your ordinance requires it, not buried in your listing description
General guidance only, not legal advice: requirements vary by city and county. Confirm your own jurisdiction's specific requirements before an inspection.
Sponsor Spotlight
This spot is open
Be our founding sponsor.
This newsletter is built for short-term rental hosts dealing with regulation, pricing, and turnover, not a general travel audience. The founding sponsor gets this placement locked in at a rate that won't be offered again once the list grows.
Subscriber Photo
This week's featured photo
Submitted by Jim
Want to be featured next?
The first thing guests see: your welcome setup or local playbook
A clever storage, turnover, or safety hack you're proud of
The view or spot guests always mention in reviews
Your posted permit or compliance signage, done right
A pet-friendly or accessibility touch
A before/after from a fix or refresh
The photo we run each week wins its host a full year of the paid plan, free (a $70 value): localized alerts, the searchable archive, and direct Q&A included.
Want alerts for your own city, not just the national digest?
Personalized alerts the moment your city or state changes something
Searchable archive of every past regulation change, by jurisdiction
Deeper analysis: why it happened, what similar cities did next
Direct Q&A: ask a question, get it answered in an issue