Methodology
How we know what we say
This is the Halifax Developments Map's source-of-truth document. Everything on the platform — every parcel, every permit, every zone, every photo, every analytical claim — comes from somewhere. This page names every kind of record behind it, says how fresh each kind is, says how confident we are in it, and tells you what we don't know.
If the platform tells you something and you want to verify it, this page is where you start.
Where the data comes from
The platform reads public records in four families: the municipality's planning and permit record, the province's parcel and assessment record, federal and statistical boundaries, and the public record a project makes for itself — the documents filed on it, what its owner announces, and photographs of the site over time. Every fetch is checked against the shape the source published last time; if the shape has changed, the fetch fails loudly rather than writing something wrong.
How to read the freshness column. Each category carries a band, not a timetable: more than once a day, daily, weekly, monthly, quarterly, annual, or snapshot, re-fetched on demand. A band is a floor, and it is enforced: a check in our build reads the deployed refresh schedule and fails if any band on this page is faster than the slowest refresh behind that category. The page is allowed to be conservative. It is not allowed to be optimistic. Categories that nothing refreshes on a schedule say so in words rather than naming a rhythm.
Municipal planning and permit records
| Category | What it tells us | How fresh | Confidence |
|---|---|---|---|
| Permits, issued and in progress | Every building, construction, water, engineering, land-use and right-of-way permit the municipality issues — type, status, dates and address — plus the construction road closures that go with them | More than once a day for the permit types that drive construction status; daily for the rest of the permit record; weekly for the reference records and street closures | Verified live |
| Site inspections (186,816 records) | Every inspection called on a permit, its type and its outcome. This is the record the platform reads construction phase from | Weekly | Verified live |
| Permit processing times (145,605 records) | How long each permit took, broken down by stage and by which side of the counter held it | Weekly | Verified live |
| Planning and subdivision applications (1,401 subdivision applications) | What is in front of the municipality, what it proposes, and how many homes it would add | More than once a day for the mapped applications; daily for the full application record | Verified live |
| Zoning districts (11,073 polygons) | The zone that applies to a parcel under the land-use by-law in force | Weekly | Verified live |
| Maximum building heights (1,822 polygons) | The statutory height ceiling, in metres and in storeys | Weekly | Verified live |
| Heritage properties and conservation districts (529 registered properties, 20 districts) | Registered heritage status, district boundaries, status and effective dates | Weekly | Verified live |
| Plan areas, by-law schedules and future land use (7,175 polygons) | Which community plan and detailed plan area a parcel sits in, and the future land use designated for it | Weekly | Verified live |
| Regional Centre overlays | The extra rules that apply only in the Regional Centre — bonus-zoning rates, view planes, streetwall heights, landmark sites, shadow-assessment areas, precincts, and pedestrian-oriented commercial streets | Weekly | Verified live |
| Floodplain overlay (1,011 polygons) | Where the floodplain overlay and its floodproofing requirements apply | Monthly | Verified live |
| Building footprints (171,800 polygons) | The municipality's own footprint for every building | Weekly | Verified live |
| Civic addresses (158,302 records) | The municipal address registry, and how an address resolves to a parcel | Weekly | Verified live |
| Community boundaries | The municipality's named communities, used to place a project in an area | Annual | Verified live |
| Draft re-zoning proposals under the federal Housing Accelerator Fund | Zoning changes proposed but not yet in force | Snapshot, re-fetched on demand — nothing refreshes it on a schedule | Snapshot, verified at last fetch |
| Planning case pages and the documents filed with them | The applicant and the project team, staff reports, the proposal in the applicant's own words, and the drawings and studies filed on a case | Daily for the case pages; weekly for the documents attached to them | Primary source for the project team; every document keeps its case reference |
Provincial parcel and assessment records
| Category | What it tells us | How fresh | Confidence |
|---|---|---|---|
| Parcel boundaries, from public municipal and provincial records | The parcel a project sits on — the boundary every other record is joined to | Full load 2026-05-19; re-fetched on demand — nothing refreshes it on a schedule | Static snapshot, verified at load |
| Assessment and ownership records, from Property Valuation Services Corporation | What a property is assessed at, the living units on the roll, lot size, and recorded sales | Annual for the assessment roll; quarterly for sales | Used selectively; ownership can lag a transfer |
Federal and statistical records
| Category | What it tells us | How fresh | Confidence |
|---|---|---|---|
| Building footprints, national fallback | Footprints extracted from national elevation data by Natural Resources Canada, used only where the municipal footprint is missing | Snapshot, re-fetched on demand; the publisher reissues it every few years | Fallback only, where the municipal footprint is absent |
| Census boundaries | Statistics Canada dissemination areas, used so that area boundaries follow the census rather than a line drawn across water | Snapshot, re-fetched on demand when the publisher reissues it | Static snapshot, verified at load |
The public record a project makes for itself
| Category | What it tells us | How fresh | Confidence |
|---|---|---|---|
| Developers' own public announcements | What a project's owner says publicly about it: project pages, renderings, unit mixes, stated timing | No scheduled crawl; read on demand during research | One source among several; never the only source for a material claim |
| Construction photography | Dated photographs of a site over time, which is how the platform shows a project changing | Daily; our own site photography continuously | First-party photography is fully attributable. Photographs from other sources carry a credit to the photographer or publisher on the image itself, and are never presented as ours |
| Street-level imagery | Street-level views of a parcel, including earlier years where they exist | On demand, at the moment it is viewed | One of the visual sources, used where our own photography does not exist |
How confident are we in any given claim?
Every attribute on the platform carries a visible confidence grade. The grades, from highest to lowest:
- Verified. Sourced from the municipal record, matched across two or more independent sources, no conflicting observations. This is the default for regulatory data (zone, max height, heritage status) and for permit data once permits are issued.
- Municipal source, single observation. Sourced from the municipal record with no corroborating source. Reliable but unaudited.
- Editorial source, corroborated. Sourced from a published announcement, a photo caption or a developer's own page and agreeing with at least one municipal source. We promote these from "editorial" to "corroborated" once a higher-priority source confirms.
- Editorial source, single-source. Sourced only from editorial material. We mark these explicitly in the interface with a "single-source" tag. They are shown, and they are flagged.
- Inferred. Derived rather than directly observed — for example, "current construction phase" derived from the most recent passed inspection of a known phase type. What was inferred, and from what, is stated on the attribute.
When two sources disagree, they are ranked in this order:
- The municipal regulatory record (zoning, max height, heritage, subdivision)
- What the permit applicant filed (permit-stage attributes)
- The developer's own public statement
- Documents filed on the planning case
- Photo-archive captions, read with an awareness of when they were written
- Contributor submissions
Higher-priority sources win by default. The platform shows the priority-resolved value as the displayed value, with a "see source history" disclosure that reveals every observation across every source and date.
Time-versioning — silent revisions are surfaced, not hidden
Project attributes change over time. The Abraham was filed by WM Fares in 2023; the most recent municipal record associates the project with Commons View Holdings. The transition wasn't announced publicly. The platform stores both observations with their dates and shows the change as a visible timeline rather than overwriting the historical record silently.
Same logic applies to other attributes — proposed unit counts that get revised between a development agreement and a building permit, developer names that change mid-project, architects-of-record that get swapped, project names that get renamed. If an attribute has had more than one distinct value across the platform's observation history, you'll see a "previously: X (until date Y)" line in the per-project drawer. This is the difference between a database that silently propagates revisions and a database that tracks them honestly. We chose the latter.
What we don't know — honest limits
We are confident about the data we publish, including its limitations. Some genuine gaps:
- The post-issuance duration in the permit processing record aggregates construction time and the applicant's own scheduling delay together. We can't currently separate "the building actually took 14 months" from "the building was done at month 10 but the final inspection wasn't called until month 14." We're working on a derivation from the inspection log that would distinguish these; for now, we report the aggregate and flag the ambiguity.
- The draft re-zoning proposals under the federal Housing Accelerator Fund were last republished by the municipality in April 2024. Nothing refreshes them on a schedule — they are re-fetched by hand, so the platform reflects an amendment only after that re-fetch, and the state of the draft between our snapshots is not stored.
- Construction photography does not cover every project. It is dense on the Halifax peninsula and on active mid-rise and high-rise projects; it is thin for single-detached, suburban, and Dartmouth and Bedford projects. The platform's photo timeline is correspondingly richer for some projects than for others.
- Older archival captions are unstructured. For photographs published before 2019 we can usually extract the project name, but not a reliable developer, builder or architect attribution. We mark that in the per-project source-history view rather than guessing.
- Documents only exist for projects that went through a case review. Smaller projects — a four-home infill under the Housing Accelerator Fund, for example — file no case documents, so for those projects we have no architect-of-record source. The platform shows no architect for them rather than inventing one.
- Inspection-derived construction phase doesn't apply to projects without an active permit. A project still at the application stage shows as "pre-construction" because there is no inspection log to derive from.
- A parcel boundary is a snapshot. Boundaries are re-fetched on demand, not on a schedule, so a very recent subdivision may exist as an application on the platform before its new boundaries do.
If you encounter a specific data quality issue on the platform — a wrong attribution, a missing photo, a zone misclassification — there's a "report a data issue" link on every parcel page. Reports are reviewed within a business week.
How fresh the data is
Freshness is published as a band, per category, in the tables above — not as a schedule. The bands, fastest to slowest: more than once a day, daily, weekly, monthly, quarterly, annual, and snapshot, re-fetched on demand for the categories nothing refreshes automatically.
Three things hold those bands honest. Each refresh checks the source's shape before it writes, and fails loudly if the shape has changed. A check in our build reads the deployed refresh schedule and fails the build if any band published here is faster than the slowest refresh behind that category — the page can under-promise, never over-promise. And every figure the platform shows you carries its own as-of date, so you can see how old the answer in front of you is without taking our word for the band.
The relationship with Helio Urban Development
The Halifax Developments Map is published by Helio Urban Development, a technology-led real estate company in Halifax. The platform is open to everyone, ad-free, and has no paid tier. The firm's revenue comes from developing projects for a fee — not from subscriptions, sponsored content, or paid placement on this platform.
This means a few things in practice:
- The platform is editorially independent. No developer pays for placement here. No developer's marketing claims override the data. If a project's municipal permit record conflicts with what the developer's own page says, the municipal record wins on the platform, with both shown for transparency.
- The platform does not advocate. We don't take positions on whether specific projects should be approved or denied. The platform is value-neutral on outcomes; it makes the data legible and lets readers form their own views.
- Helio publishes analysis on top of the data, on a regular cadence, under the firm's byline. The data is the foundation; the analytical posts and quarterly reports are how Helio does the analytical work it claims to do — in public.
- Helio will work with you on Halifax development questions that this platform doesn't fully answer. That's the firm's actual business. See Helio's services in HRM for how an engagement works and how to reach us.
Where to check us
- The map itself — every claim on it carries its grade, its as-of date and its source history
- The Halifax development glossary — the words used here, defined
- Browse the pipeline by area — the same record, read one neighbourhood at a time
Last updated: 2026-09-08 — rewritten to describe the record by category: what kind of public record each figure comes from, how fresh that category is as a band, how it is graded, and what it does not cover. Every published band is re-checked against the deployed refresh schedule by a gate in our build. Methodology changes are version-controlled and historical versions are retained. If you find an error in this document or in the platform's data, please tell us — corrections are published within a business week.
Common questions
Who tracks Halifax development?
The Halifax Developments Map does — a free, parcel-level reference to every active development in the Halifax Regional Municipality, published by Helio Urban Development and synthesized from municipal and public sources.
Where does the Halifax Developments Map data come from?
Public records, by category: the municipality's permits, inspections and permit-processing record; planning and subdivision applications; zoning, height, heritage, floodplain and plan-area records; building footprints and civic addresses; provincial parcel and assessment records; census boundaries; the documents filed on a planning case; developers' own public announcements; and photography. Each category is listed on this page with how fresh it is, how it is graded, and what it does not cover.
How current is the data?
Each category carries a freshness band, listed on this page: more than once a day for the permit types that drive construction status, daily for case pages and the rest of the permit record, weekly for the regulatory records and the bulk permit record, monthly for floodplain, quarterly and annual for assessment, and a plain snapshot, re-fetched on demand, where nothing refreshes on a schedule. The map reflects the latest successful refresh of each, and a check in our build fails if a band published here is ever faster than what actually runs.
Is the Halifax Developments Map free?
Yes. The map is open to everyone with no account — every project, layer, area and search, plus a few full project dossiers per visitor. A free account lifts that per-visitor dossier limit and unlocks the project intelligence layer; it is a rate limit, not a paywall, and there is no paid tier. Helio's revenue comes from development work, not the platform.
Built by Helio Urban Development — a technology-led real estate company in Halifax. Talk to us →