The Housing Accelerator Fund (HAF) is one of the most significant federal housing programs Canada has deployed in years. Administered by the Canada Mortgage and Housing Corporation (CMHC), it offers funding to municipalities, Indigenous governments, and other entities that commit to meaningful changes in housing approvals. In exchange for that funding, recipients are expected to demonstrate results. That means reporting, and reporting means data.
If your city received HAF funding or is considering applying, understanding what you need to track before you need to report it is essential. Scrambling to reconstruct permit histories after the fact is painful. Building the tracking infrastructure before approvals start flowing is not.
What the Housing Accelerator Fund requires
The HAF is structured around Action Plans. Municipalities receiving funding commit to a set of housing-enabling actions: zoning reforms, streamlined approvals, infill incentives, transit-oriented development policies. CMHC ties disbursements to demonstrated progress against those actions.
Reporting to CMHC typically covers:
- Units permitted and approved over the funding period
- Changes in approval timelines compared to baseline
- New housing supply enabled by policy or process changes
- Progress on specific action items from the approved Action Plan
The exact requirements depend on your agreement with CMHC and the actions your municipality committed to. But across most HAF agreements, permit-level data is the core evidence. Applications, approvals, unit counts, permit types, timelines: these are the numbers that prove the municipality did what it said it would do.
Where permit data fits into HAF compliance
Think of HAF reporting as a before-and-after story. CMHC wants to see that the policies and changes your municipality implemented actually produced more housing, faster. Permit data is the most direct evidence of both.
“More housing” means tracking units permitted by type: new construction, secondary suites, laneway housing, multi-unit conversions, accessory dwelling units. Your permit system captures permit type and unit count. The question is whether you can extract, aggregate, and present that data by time period in a format that maps to your Action Plan commitments.
“Faster” means tracking processing times. Application date, completeness review completion, technical review completion, approval date. The gap between application submission and final permit issuance is your processing time. HAF commitments often include targets to reduce this gap. Proving you hit the target means having the historical baseline and the current numbers side by side.
What most permit systems don’t give you out of the box
Most municipal permit systems record the data you need, but not necessarily in the form reporting requires.
Permit management platforms capture date stamps, permit types, applicant details, project values, and inspection outcomes. What they typically don’t do is aggregate that data into trend reports, calculate median processing times by permit category, or compare your current performance against a historical baseline.
That gap is where analytics tools earn their keep. A permit analytics layer sits on top of your existing permit data and surfaces the aggregated view: median approval time this quarter versus last year, unit count by housing type by month, applications in each pipeline stage. This is the data HAF reporting requires, and it needs to be available on demand, not reconstructed manually when a reporting deadline arrives.
Building your HAF reporting data model
Regardless of what tools you use, the underlying data model for HAF reporting has a few key dimensions:
Time: Every metric needs a date range. HAF reporting typically compares a baseline period (before funding) to a measurement period (during or after). Your permit data needs timestamps granular enough to slice by quarter or month.
Permit type: Not all permits count equally toward housing targets. Residential new construction, secondary suites, and multi-unit infill may each map to different Action Plan commitments. Your data model needs permit type as a primary dimension, not an afterthought.
Unit count: Many permits cover multiple units. A permit for a six-plex counts as six units, not one permit. HAF reporting typically measures units, not permit counts. Make sure your data includes unit count per permit, and that your aggregation sums units rather than permits.
Processing stages: If your Action Plan includes a commitment to reduce processing times, you need stage-level timestamps, not just the final approval date. The gap between application submission and completeness review is different from the gap between technical review and approval. Knowing where time accumulates is what lets you demonstrate targeted improvement.
The data residency question
HAF funds municipal governments. The permit data that supports reporting includes applicant names, property addresses, and project details. In British Columbia, FIPPA governs how this information is handled. Many provinces have equivalent legislation. Keeping permit data in Canada is not just a preference for most municipalities; it is a compliance requirement.
When evaluating permit analytics tools for HAF reporting, data residency should be a top consideration. Where does the data go when it leaves your permit system? Where is it stored and processed? Can you demonstrate Canadian residency in an audit? These questions matter for FIPPA compliance and for your municipality’s broader data governance obligations.
From reporting to improvement
HAF compliance reporting is not just a CMHC obligation. The same data that supports reporting also supports internal improvement. Processing time trends reveal where your approval workflow has bottlenecks. Unit count tracking reveals which housing types your streamlined approvals are actually enabling. Stage-level analytics reveal which departments are hitting review deadlines and which are lagging.
Municipalities that build strong permit analytics for HAF reporting often find they have built something more durable: an operational visibility layer for the planning department that outlasts the funding period.
The tracking infrastructure you put in place for HAF compliance does not go away when the agreement ends. It becomes the foundation for the next round of reporting, the next council presentation on housing supply, and the next evidence-based staffing or process decision your department needs to make.
Getting started
If your municipality has received or is pursuing HAF funding, the time to build your reporting infrastructure is before approvals start flowing. Reconstructing historical permit timelines is possible but expensive and error-prone. Starting with clean data capture from the beginning of the funding period means your end-of-period reports reflect reality.
A few practical starting points:
Check that your permit system captures date stamps at each stage, not just application and approval dates. If stage-level timestamps are not being recorded, that is a gap to close before it becomes a reporting problem.
Confirm that your permit type classifications map to the housing categories CMHC cares about in your Action Plan. Mismatched categories mean manual reconciliation at reporting time.
Identify how you will aggregate unit counts across multi-unit permits. This is often a manual step in systems that track permits rather than units.
For more on how permit analytics supports municipal reporting and planning, see our posts on permit approval-speed benchmarking across BC municipalities and FIPPA-compliant permit analytics for planning departments.
Steller turns your municipal permit data into clean reporting views for HAF compliance, processing-time benchmarking, and FIPPA-compliant analytics. Start for free.