Measure an ADU program in separate stages, from first inquiry to application, permit and completed home, and report each stage on its own terms. A program can receive more inquiries without producing more completed homes, and it can improve application quality without immediately changing permit totals. A useful dashboard keeps those stages separate and explains what each measure can, and cannot, show.

Before evaluating a portal, preapproved-plan library or policy change, define the outcomes and data sources. Reporting requirements differ by state, and some states require jurisdictions to report ADU permits or production in specific formats, so align definitions with any official instructions that apply to you. Measurement should help staff improve the program without creating unsupported claims about housing production or time savings.

Agree on how the ADU program is measured

Decide whether a record represents an inquiry, parcel, application, permit or dwelling. One parcel may generate several inquiries, and one application may change over time. Counting every record as a new housing unit inflates the picture.

Create a short data dictionary with stage definitions, source systems, responsible staff and known limitations. Distinguish an issued permit from a completed dwelling and distinguish completion from confirmed rental use where that distinction matters to the program.

Record timestamps consistently

Use defined milestones rather than ambiguous “processing time.” If the program measures time from complete application to decision, say so. Do not compare it with another period measured from first inquiry to occupancy.

Identify pauses, resubmissions and applicant-driven delays according to the relevant rules and reporting purpose. Avoid changing definitions mid-report merely to make a trend look better.

Track cohorts as well as calendar totals

Annual counts answer how many events occurred during a period. Cohorts answer what happened to the group that entered at a particular stage. Both can be useful, but they address different questions.

For example, applications submitted late in a reporting period may not yet have had time to reach completion. Do not treat them as failed projects simply because they are unfinished at the report date. Show open cases and the observation period clearly.

For outside context, the U.S. Census Bureau's Building Permits Survey publishes residential permit data by place, though it is not designed to isolate ADUs. State guidance can add expectations of its own; California HCD's ADU housing-element guidance, for example, emphasizes realistic capacity and evidence about housing use and rents. Neither is a ready-made dashboard definition.

Measure the front door separately from permits

For an informational portal, track whether residents can complete supported lookups, understand next steps and find assistance when data are missing. Use privacy-conscious aggregate measures where appropriate. Portal visits are not applications.

Digital analytics can record selected actions; Google's key-event guidance explains one measurement mechanism. The agency still has to define what the action means and whether collection is appropriate under its policies and public-records obligations.

If staff-time savings are a pilot goal, establish a baseline and a consistent collection method. Record the type and duration of work sampled, while respecting staff and resident privacy. Do not extrapolate a small anecdote into an agency-wide savings figure.

What an experienced ADU builder sees in the process

Builders move many projects through permitting, and the delays they notice are often outside the planning counter. Measures worth adding to an ADU program dashboard include:

  • Review rounds per application. The number of correction cycles often says more about clarity of requirements than average days does.
  • Recurring correction items. If the same comments appear on many submittals, a handout, checklist or standard detail may fix them at the source.
  • Time waiting on other agencies. Utility capacity letters, fire access review, sewer or septic approval and separate districts can hold a project after planning is done. Track that wait separately so it is visible.
  • When fees become known. Applicants who learn connection and impact fees late are more likely to pause. Note the stage at which a reliable fee estimate is available.
  • Inspection scheduling and re-inspections. After issuance, the path to final inspection is part of whether a permit becomes a completed home.

Explain why projects pause or stop

Use a manageable set of documented reasons, such as financing, site constraints, utility costs, design changes, applicant timing or an unknown reason. Do not infer a reason merely because no permit appeared.

Review whether staff can apply categories consistently. Allow “unknown” rather than forcing every case into a confident explanation. A reliable small dataset can be more useful than a large one with unclear definitions.

ADU Insights for Cities

See it set up with your code

A resident ADU portal built from your adopted ordinance, parcel data and next steps, reviewed by your staff before launch.

Separate correlation from program impact

Permit totals can change because of financing conditions, construction costs, state law, staffing, demand or other programs. A before-and-after increase following a portal launch does not by itself establish that the portal caused it.

Report what was observed, describe the comparison and identify plausible limitations. If a stronger causal evaluation is needed, involve qualified analysts and plan it before implementation. Do not invent benchmarks or promise a specific improvement to justify procurement.

Publish a dashboard people can interpret

Show definitions, reporting dates, source coverage and revision notes. Explain incomplete records and differences from other public reports. Use aggregated information and review disclosure risks before presenting small geographic or demographic groups.

Connect findings to decisions: revise an unclear handout, improve a missing-data path, coordinate with a utility or investigate a recurring application issue. A dashboard is useful when it changes an identified workflow, not simply because it contains more charts.

Start the pilot with a measurement plan

Review the ADU Insights tools for municipalities and the planning-department portal article for the proposed workflow. Bring stage definitions and baseline questions to a municipal demo, and decide what evidence a pilot must produce before making outcome claims.