Data behind the housing element and general plan annual progress report

Reference article · 6 min read

Every January, planning staff start assembling the annual progress report on the general plan and its housing element. California law directs cities and counties to report each year on the status of the general plan, progress toward implementing it, and progress toward meeting the regional housing needs allocation, with the report going to the state planning office and to the Department of Housing and Community Development (HCD) on forms the department publishes and periodically revises. The numbers themselves are not new. They already exist in permit issuance records, certificate of occupancy records, entitlement files, and affordability agreements.

The problem is shape, not availability. The report wants units, not permits; it wants three separate milestone dates per unit; and it wants an affordability status that most permitting systems never capture, because affordability is created by a recorded covenant rather than by a building code action. Agencies that instrument the permit system for these fields turn the report into a query. Agencies that do not spend several weeks each winter counting by hand.

What the report actually asks for

The forms are organized around distinct populations of records, and confusing them causes most of the rework:

• Applications. Residential development applications submitted during the reporting year, with units proposed, units approved or disapproved, and whether a streamlined or ministerial pathway was requested.
• Unit actions. Units that received an entitlement, a building permit, or a certificate of occupancy during the year, broken out by income category and by deed-restricted status.
• Programs and narrative. Status of each housing element implementation program, progress on other general plan elements, and supplemental items such as sites rezoned, density bonus projects, accessory dwelling units, and units demolished or lost.

Form structure and instructions change between cycles. Confirm the current version with HCD before building anything against it.

Three dates, not one

Entitlement, building permit issuance, and certificate of occupancy are reported separately, and the same unit legitimately appears in three different reporting years. Your permit system must store each as a discrete, dated field on the record, tied to the official action rather than to a record modification timestamp.

Common failure points: entitlement dates captured only in the planning case management system and never joined to the permit record; certificates of occupancy issued as temporary and then final, with no rule about which one counts; and permits that expire, are voided, or are reissued under a new number, producing duplicates or dropped units.

Counting units, not permits

• Store a unit count on every residential record. A permit for a forty-unit building is one permit and forty units. Reporting from record counts undercounts production badly.
• Separate demolished or lost units. They are reported on their own and affect net progress.
• Find your ADUs. Accessory and junior accessory dwelling units are frequently issued under a residential addition or alteration record type, where they disappear from any query filtered on new construction.
• Write down your edge case rules. Mixed use, live-work, group quarters, single room occupancy, and phased projects all require a local counting convention. Document it, apply it consistently year over year, and keep the note with the submitted file.

Affordability is a covenant, not a checkbox

A building permit record almost never knows whether a unit is income restricted. That fact originates in a regulatory agreement, an inclusionary housing agreement, a density bonus agreement, a tax credit regulatory agreement, or a local funding contract, and it usually lives with the housing division or successor agency.

Capture at minimum: deed-restricted yes or no, unit counts at each income level used by the state form, the recorded agreement or instrument number, the restriction term, and the funding source. Non-deed-restricted units reported as affordable need a documented basis, such as an approved affordability study or rent survey. Name one office as the source of truth for these fields, and link records by assessor parcel number plus project identifier so the join survives address changes.

Streamlining determinations and program status

Capture at intake whether an applicant requested a streamlined ministerial pathway, which statute was invoked, the date of the determination, and the outcome. Reconstructing that from correspondence a year later is slow and error prone. The same applies to application completeness dates and approval or denial dates.

Housing element program status is not permit data at all. Keep a simple register keyed to your adopted program numbers, with a responsible department, milestone dates, and a short status note updated during the year. This is also the record your agency relies on if implementation is ever questioned.

Instrumenting the permit system

1. Write a data dictionary naming each reported field, its source system, its owner, and the workflow step where it becomes known.
2. Add the fields to residential record types and make them conditionally required at that step, not at closeout.
3. Add validation: units by income category cannot exceed total units, and deed-restricted units require an agreement identifier.
4. Build a unit-level reporting view with one row per unit per milestone, exposed to your analysts rather than buried in the transactional schema.
5. Map that view to the current state template and run the export monthly, so gaps surface in March rather than in January.
6. Archive a copy of every submitted file and its underlying extract for reconciliation against cumulative allocation progress.

What to ask vendors and how to start

Before your next permitting procurement or upgrade, ask:

• Can we add and edit configurable fields on residential record types without vendor custom code, and are those fields immediately reportable?
• Do we get direct read access to a reporting database or documented views, or a documented API that returns unit-level data with all milestone dates?
• How does the vendor handle changes to state reporting forms, and who bears that cost?
• What are our data extract and ownership rights, including at termination?

A useful evaluation exercise is to hand a candidate system your last submitted report and ask how it would reproduce those totals from its own records. HQT works with state and local agencies on permitting data models, reporting extracts, and integrations between land management, housing, and finance systems.

Frequently asked questions