How an ADU Portal Helps a Planning Department Save Time and Improve Applications

Most ADU inquiries start in the same place. A resident has heard ADUs are allowed and wants to know whether one fits on their lot. To answer well, staff look up the parcel, confirm the zone, find the right code section, explain the setbacks, and often explain the difference between what the code allows and what a particular lot can hold.

That work is valuable, but much of it repeats. The same code sections are explained many times a week, to residents who are at the very start and may not go further. Meanwhile, the residents who do apply sometimes arrive with site plans built on the wrong setbacks or an outdated rule, which costs a review cycle.

State law raises the stakes on both ends. California requires a local agency to approve or deny a complete ADU application within 60 days, and when it denies one, to return a written list of deficient items and how to fix them within that period (HCD ADU Handbook). Colorado's HB24-1152 requires subject jurisdictions to approve qualifying ADUs administratively. When review time is fixed or administrative, better first submittals matter more.

The mechanism is simple. A resident enters an address and the portal shows:

• the lot lines and zone from your GIS data;
• the setbacks that apply to an ADU, drawn on the lot, with the buildable area that remains;
• the size limit and other standards, in plain language, each cited to your code section with the exact wording and the date it was checked;
• your approved or generic plans placed to scale, showing which fit;
• the next step your office wants them to take.

A resident who would have called to ask "can I build one?" gets a sourced, preliminary answer first. Some will decide the project isn't for them. Others will call with a narrower question, such as how a corner-lot exception applies or whether an existing shed can be converted. Those are the conversations that need staff. Whether this reduces call volume in your jurisdiction is something to measure, not assume, which is why we start with a pilot.

The portal produces a scaled site plan sheet with a north arrow, setbacks and distances to the lot lines and the house, stamped "Preliminary · Not for permit · Not a survey". It is not a plot plan for permit, and it says so. What it gives a pre-application meeting is a shared starting point: the resident, their designer and staff are looking at the same lot, the same setbacks and the same cited rules.

That changes the meeting. Instead of starting from a blank parcel, staff can correct a specific placement, confirm a reading of a specific section, and point to the specific documents the application will need. Residents also see your fee schedule, handouts and checklist at the moment they need them, because the portal links them from the next-step panel.

The next-step checklist also sets the order. It tells residents to confirm the rules for their lot with your office before they pay for design, to have a surveyor confirm the true lot lines and to call 811 before digging, and to have a licensed designer or engineer prepare permit drawings. Residents who follow that order reach the application stage with fewer surprises, and your office is involved before money is spent on drawings, not after.

When several staff members answer the same question, small differences creep in. A portal answers from one rule set that your staff have reviewed:

• One source for each rule. Every value cites the ordinance section, quotes the source excerpt and shows the effective date.
• One status for each finding. Verified by the jurisdiction, sourced but not yet reviewed, estimated, unavailable, or needs professional review.
• One review cycle. When the rule set passes its review date, the portal warns; when it is overdue, it stops drawing conclusions until staff confirm the rules.
• One record. Rule versions and staff approvals are logged, so the jurisdiction can show what a resident saw on a given date.

Consistency also covers neighborhoods. Every resident gets the same information in the same format, whichever part of the jurisdiction they live in. Turning your adopted ADU code into a resident self-service portal explains how the rule set is built and reviewed.

A resident portal is public web content from a local government, so accessibility is not optional. The U.S. Department of Justice's Title II rule on web and mobile accessibility adopts WCAG 2.1 Level AA as the technical standard for state and local government web content. The Section 508 standards, which apply to federal agencies, are another common reference point. Your counsel can confirm which dates and obligations apply to your jurisdiction.

The portal is designed toward WCAG 2.1 AA:

• keyboard operation, including moving a plan footprint on the lot;
• labeled controls, readable contrast and reduced-motion support;
• a text and table view of the lot, rules and placement, so no one has to use the map;
• a staff-assisted path by phone or email.

A third-party accessibility audit and the non-map workflow are part of preparing each jurisdiction's launch.

On privacy, residents don't need an account to explore. A data-use notice appears before the first lookup. Retention and records settings are agreed with each jurisdiction, so they fit your records schedule and public-records obligations. Reporting to the city is aggregate (searches, completed analyses, plan downloads, calculator use, referral clicks to official resources), with small groups suppressed and no identifiable addresses in public reporting.

A city portal has to be fair to every builder and designer in the jurisdiction, and to residents who haven't chosen one. The municipal version is built that way:

• no builder names, ads, rankings or sponsored placements;
• no "contact a builder" path, and no resident information passed to any builder;
• no lead capture: the database refuses lead records for a municipal portal;
• neutral plan types or your own approved plans, never a builder's named plans;
• a referral directory only if your city supplies one, shown in neutral order.

ADU Insights is owned by Origin ADU, a design-build ADU company. Its owner also co-owns God's Country Development, which builds ADUs in Grand Junction and Mesa County. We disclose this in every municipal agreement, and the portal is built so that no builder, including those, receives preference or resident information.

The honest way to judge ADU program software is to try it on your own addresses and measure it. A pilot is scoped to one jurisdiction or one program, set up with your code, data and next steps, and tested by staff against the questions they actually get. Success measures are written down before it starts, for example:

• completed searches and usable preliminary reports;
• referral clicks to your official resources;
• rule accuracy on test parcels your staff choose;
• accessibility defects found and fixed;
• resident satisfaction;
• planning-staff time, against a baseline measured before launch.

The portal is offered today as a demo and pilot set-up, configured per jurisdiction and reviewed by staff before launch. No city is using it yet. The resident portal demo shows the experience on a sample lot in Grand Junction, Colorado, under a fictional city name; Grand Junction is not a customer. In the meantime, residents can already use the free lot check at aduinsights.com, as described in How cities can use a free ADU lot check to answer resident questions.

For more on the policy side, the American Planning Association's ADU resources and HUD's ADU case study are useful background. To see the portal on addresses in your area, read For Municipalities and request a demo tailored to your jurisdiction.