Turning Your Adopted ADU Code Into a Resident Self-Service Portal

Self-service, in this context, means a resident can get the first, repeatable answers on their own: what zone the lot is in, which setbacks apply to an ADU, how large an ADU can be, which plans fit, and what to do next. It does not mean a resident can get an approval, a determination or a permit without your office. Every screen in the portal says the results are preliminary and points to the planning department, and the last step of every visit is the one your office chooses.

What a resident sees is close to what the free lot check at aduinsights.com shows (lot lines, buildable area, rules with sources, plans to scale, a 3D view, a cost estimate and a site plan marked not for permit), but built from your sources, reviewed by your staff and carrying your name. How cities can use a free ADU lot check to answer resident questions covers the free version.

We start from the ADU ordinance your governing body adopted, as published by your official code host. Each standard becomes a rule record with:

• The rule as it applies to an ADU, such as the rear setback for a detached unit or the maximum floor area.
• The ordinance section, linked to the official code.
• The source excerpt, the exact sentence the value comes from, quoted word for word.
• The effective date of the provision and the date we retrieved it.
• A review date, after which the rule set must be confirmed again.
• A status, shown next to each finding: sourced and not yet reviewed, verified by the jurisdiction, estimated, unavailable, or needs professional review.

Codes rarely say everything in one place. A detached ADU might take its setbacks from an accessory structure table in one chapter and a corner-lot exception from another. Where applying a provision requires a reading, we record that reading next to the rule and flag it for staff. Staff decide how it is presented. Explanations come only from sourced rules; nothing is invented.

Where state ADU law sets standards that apply in your jurisdiction, we cite the statute alongside your code. California's HCD ADU Handbook and Colorado's HB24-1152 are the kind of sources we cite. Staff confirm how state and local rules are presented together.

The portal reads parcels and zoning from your own GIS services where you publish them, so lot lines and districts match your maps. Where you publish them, we can add:

• flood, wetland and wildfire layers;
• sewer and water service areas;
• other layers your staff consider relevant to ADU siting.

Where a layer isn't published, we use county and federal datasets and say which source is in use. Parcel lines from GIS are not survey-grade, and the portal says so: lot lines can be off by several feet, and a licensed surveyor sets the true lines. When a parcel, setback or rule is missing, the portal says it is missing and points the resident to your office instead of assuming the lot is eligible.

Pre-approved plans are now part of state policy in several places. California requires local agencies to run a program for pre-approving ADU plans and to post those plans on the agency's website (Gov. Code section 65852.27, summarized in the HCD handbook). Colorado's HB24-1152 created a grant program that can help supportive jurisdictions with the cost of developing pre-approved ADU plans, among other strategies; the Colorado Division of Local Government publishes the implementation guidance.

A portal puts those plans in front of the residents who need them:

• Your approved or pre-approved plans are placed to scale on the resident's lot, so they can see which ones fit within the setbacks.
• Plans carry neutral labels. Approval indicators appear only for plans your city has actually approved.
• If you don't have a plan set, the portal uses generic plan types (Studio, 1-Bed, 2-Bed) with no builder names.

The portal carries your jurisdiction's name, colors and contact details, and it is linked from your ADU program page. More important than the look is the ending. Every visit ends with your office, in the order you choose:

• contact Planning first, by phone, email or counter visit;
• book a pre-application meeting;
• go to the planning counter with a checklist;
• start an online submission through your permit portal.

Your handouts, fee schedules and application checklists can be linked at the point a resident needs them. The resident's next-step checklist follows the order your office wants, for example:

1. Save the preliminary site plan and summary report.
2. Confirm the rules for the lot with the planning department before paying for design.
3. Confirm lot lines and utilities: a licensed surveyor sets the true lines, and 811 is called before digging.
4. Have a licensed designer or engineer prepare permit drawings.
5. Apply, through your planning clearance and building permit links.

Your department's phone, email, office address and hours sit beside the checklist, with a plain invitation to contact Planning about an unusual lot, missing data or a result that looks wrong.

Nothing goes public until your staff have reviewed it. A set-up follows six phases, and each ends with staff review:

1. Discovery. Your program, your goals and the questions residents ask most.
2. Data review. Your GIS services, adopted code and plan sets.
3. Customization. Your name, colors, next step and resources.
4. Pilot and testing. Staff test real addresses they know before the public does.
5. Staff review. Rule-by-rule sign-off by a named approver at your jurisdiction.
6. Launch. Linked from your ADU program page.

Before launch, each jurisdiction's portal also gets the accessibility and security work described on the For Municipalities page, including a third-party accessibility audit against WCAG 2.1 AA and a non-map workflow for keyboard and screen-reader users.

ADU ordinances change often, through local amendments and state law. A portal that keeps showing old answers would do more harm than no portal, so the rule set is built around dates:

• Every rule shows the date it was checked. Residents and staff can see how current a finding is.
• Every rule set has a review date. As it approaches, the portal warns.
• Overdue means paused. When a rule set passes its review date without confirmation, the portal stops drawing conclusions and tells residents the rules are under review, until staff confirm them.
• Amendments are re-sourced and re-reviewed. When your code changes, we update the affected rules with the new section, excerpt and effective date, and your staff review them before they go live.
• Versions are kept. Rule versions and staff approvals are logged, so the jurisdiction can show what a resident saw on a given date.

Naming a content owner on your staff, and agreeing a review cadence, is part of the set-up.

The portal is offered as a demo and pilot set-up, configured per jurisdiction and reviewed by staff before launch. No city portal is live yet. The resident portal demo runs under three minutes and shows a fictional city name on a sample lot in Grand Junction, Colorado, with that city's published rules; Grand Junction is not a customer.

For the staff-time side of the decision, see How an ADU portal helps a planning department save time and improve applications. To walk through the set-up with addresses in your own area, request a demo tailored to your jurisdiction.