How do developers track permits across multiple jurisdictions today?

Honestly, mostly manually. Each jurisdiction has its own permit portal (or, in smaller cities, a phone call or counter visit), and a person on the team periodically checks each one. There is no native portfolio view across cities, and the portals don't proactively alert you when status changes. This is the core weakness of the current landscape and why a monitoring agent that watches public filing and status sources across all your active jurisdictions is the meaningful upgrade — it does the checking continuously instead of relying on someone remembering to look.

Can Procore track building permits?

Yes — Procore handles permits as part of construction project management, where you log permit records and keep them alongside RFIs, submittals, inspections, and the schedule. That works well once a project is permitted and building, and Procore's well-documented API lets external status flow in cleanly. The limitation is that Procore tracks the permits you enter; it doesn't go monitor the jurisdiction's portal on your behalf, and it's lighter on the pre-permit entitlement phase. It's a strong system of record for construction, best paired with a monitoring layer that watches the jurisdiction.

What is the difference between entitlement tracking and permit tracking?

Entitlement tracking covers the pre-permit approvals — rezoning, variances, conditional-use permits, site-plan review, environmental sign-offs — that a project must clear before it can even apply to build. It's the longest, riskiest, most jurisdiction-specific stretch and has the worst native tooling. Permit tracking usually refers to following a submitted building-permit application through a jurisdiction's review queue. Most developers need both, plus a way to treat permits as construction tasks. Knowing which job you're solving determines whether you need a government portal, a project-management tool, or a cross-jurisdiction monitoring agent.

Are government permit portals enough, or do I need separate software?

For a developer active in a single jurisdiction, disciplined use of that jurisdiction's portal plus its notification emails is a legitimate, zero-cost approach — the portal is the authoritative source of truth. The portals fall short the moment you're active in two or more jurisdictions: there's no portfolio view, quality varies dramatically between cities, and none of them proactively tell you when something changes. That manual overhead across multiple jurisdictions is precisely where a monitoring layer earns its place, sitting on top of those same portals rather than replacing them.

What does a permit-tracking AI agent actually do?

It continuously monitors the public filing and status sources for every project in your pipeline, normalizes the messy jurisdiction-specific formats into a single view, and surfaces the meaningful changes — an application advancing, stalling, or drawing a correction request — to the people who need to act, before a slip becomes a missed date. It is decision-support, not legal or entitlement advice, and not a system of record. The jurisdiction's official portal stays the authority and your project-management platform stays the record; the agent removes the manual checking and the schedule risk that hides between them.

How does permit delay affect a development deal's returns?

Permitting and entitlement timelines feed directly into your carry costs, interest reserve, and the construction lender's schedule assumptions. On a leveraged development, an unanticipated month of delay usually costs far more in carry and reserve burn than any tracking tool. That's why permit status should be evaluated as a risk-management input across the lifecycle — from underwriting timeline assumptions through IC diligence and lender reporting — and why the cost of monitoring should be priced against the carry it protects, not against a software line item.

Best Permit & Entitlement-Tracking Tools for CRE Developers in 2026

Q: What is the best permit-tracking software for real estate developers?

There is no single category leader, because permit tracking spans three different jobs: entitlement tracking before a permit exists, building-permit status tracking in a jurisdiction's queue, and treating permits as tasks inside a construction project. Government permit portals are the authoritative source for any one jurisdiction. Procore and Northspyre track permits well as part of broader project and cost management. The genuine gap — continuous monitoring of permit and entitlement status across multiple jurisdictions — is what NextAutomation's permit-tracking agent was built for. The right answer depends on how many jurisdictions you operate in and whether you're tracking entitlements or just construction permits.

Q: Does Northspyre track permits and entitlements?

Northspyre is a development cost-management and project-intelligence platform, so permitting appears there as a milestone with a date and a cost impact — the right framing for a developer thinking about carry and schedule risk. It's a strong fit for managing the financial side of getting a project entitled and ready to build. Like Procore, though, it tracks the milestone you maintain rather than providing a live feed of jurisdiction status. It tells you the permit milestone is at risk to your budget; a monitoring agent tells you the city issued a correction notice this morning.

Ask a developer where their deals die and you'll rarely hear "construction." You'll hear entitlements and permitting — the months-long stretch where a project sits in front of a planning department, a zoning board, an environmental review, or a building-permit queue, and nobody on the team knows the real status until something slips. Carry costs accrue on the land loan. The construction lender's timeline assumptions quietly go stale. And the answer to "where is the permit?" is usually a person refreshing a county website.

That is the uncomfortable truth about permit tracking in 2026: most of it is still manual. There is no single piece of "permit-tracking software" the way there's a clear category leader for construction management or investor portals. Instead there's a landscape — government permit portals, project-management platforms with permit modules, jurisdiction-specific tools, and a newer category of AI agents that monitor filings across jurisdictions so a human doesn't have to. This guide maps that landscape honestly and tells you where each option genuinely fits.

One disclosure up front: permit and entitlement monitoring is a category NextAutomation built specifically for CRE developers, so we feature our permit-tracking agent prominently below. We've tried to be useful anyway — naming what each alternative does well, where it stops, and where you'll still need a person in the loop. Read it as a developer's working map, not a sales page.

First, define the problem you're actually solving

"Permit tracking" gets used loosely for three different jobs. Knowing which one you have determines what tool you need:

Entitlement tracking (pre-permit): Following a project through rezoning, variances, conditional-use approvals, site-plan review, and environmental sign-offs. This is the longest, riskiest, most jurisdiction-specific stretch — and the one with the worst tooling.
Building-permit status tracking: Knowing where your submitted permit application sits in a jurisdiction's review queue, what corrections were requested, and when it's likely to issue. This is what government portals expose, with wildly varying quality.
Permit-as-a-construction-task: Treating permits as line items inside a project schedule and document log, alongside RFIs, submittals, and inspections. This is what project-management platforms handle.

Most developers need all three, which is why no single tool covers the whole job — and why the manual gap sits squarely in the first two. With that framing, here's the landscape.

The landscape at a glance

Option	What it covers	Best fit	Honest limitation
NextAutomation permit-tracking agent	Monitors entitlement & permit filings across jurisdictions; surfaces status changes and schedule risk	Developers running multiple projects across multiple jurisdictions	Decision-support, not a system of record; pairs with your PM platform
Government permit portals	The authoritative status of your application in that one jurisdiction	Single-jurisdiction developers; the source of truth everyone checks	No multi-jurisdiction view; manual checking; quality varies by city
Procore	Permits as part of construction project management, docs & schedule	Teams already running construction on Procore	Tracks permits you log; doesn't monitor the jurisdiction for you
Northspyre	Development cost & project intelligence with milestone tracking	Developers managing budgets & pre-construction milestones	Cost/analytics focus; permit status is a tracked milestone, not a feed
Jurisdiction-specific permit tools	Accela, Tyler/EnerGov, OpenGov and similar civic-tech back ends	Whatever your city/county happens to run	You don't choose these; coverage and exports differ everywhere

Integration tiers: NextAutomation sits above your stack as the automation layer. Procore and Northspyre both expose documented APIs — see the Procore integration and Northspyre integration details. Government portals are checked, not integrated.

The options, ranked by job

1. NextAutomation permit-tracking agent — best for multi-jurisdiction monitoring

This is the lane we built, and it addresses the gap the rest of the landscape leaves open: nobody else continuously monitors entitlement and permit status across the jurisdictions a developer is active in. The honest description of "tracking" everywhere else is a person periodically loading a county website. The permit-tracking agent automates that monitoring — it watches public filing and status sources across the jurisdictions your projects sit in, detects when an application advances, stalls, or draws a correction request, and flags schedule risk to the team before it shows up as a missed date.

What it is not: a system of record, a substitute for your jurisdiction's official portal, or legal/entitlement advice. It's decision-support. The official portal remains the authority; the agent removes the manual checking and the "who was supposed to be watching this?" failure mode, and feeds clean status into whatever PM platform you already run. For developers with one project in one city, the manual approach may be enough. For anyone juggling a pipeline across counties, this is where the time and risk savings concentrate.

2. Government permit portals — the authoritative source everyone checks

Every jurisdiction's own portal is the source of truth, full stop. If the city says the permit is in plan review, it's in plan review. The catch is that quality is wildly uneven: some major metros offer searchable, near-real-time status with email notifications; many smaller jurisdictions still require a phone call or an in-person counter visit. None of them give you a portfolio view across cities, and none of them tell you proactively when something changes — you have to go look.

For a single-jurisdiction developer, disciplined portal-checking plus the jurisdiction's notification emails is a legitimate, zero-cost approach. The moment you're active in two or more jurisdictions, the manual overhead compounds, and that's where monitoring automation earns its place — sitting on top of those same portals rather than replacing them.

3. Procore — permits inside construction project management

Procore is the construction-management standard, and it handles permits as part of the project's document and schedule fabric — you log permit records, attach them to the schedule, and keep them alongside RFIs, submittals, and inspections. If your team already runs construction on Procore, treating permits as tracked items there keeps everything in one place. Procore also has one of the best-documented APIs in the real estate tech ecosystem, so status from a monitoring layer can flow into it cleanly (see the Procore integration).

The honest limitation: Procore tracks the permits you enter — it doesn't go watch the jurisdiction on your behalf. It's a system of record for the construction phase, strongest once a project is permitted and building, and lighter on the pre-permit entitlement marathon that precedes it. For a deeper look at the construction layer, see our guide to the best construction management software for CRE developers.

4. Northspyre — development cost intelligence with milestone tracking

Northspyre sits earlier than Procore, at the development cost-management and project-intelligence layer — budgets, anticipated costs, and pre-construction milestones. Permitting shows up there as a milestone with a date and a cost impact, which is exactly the right framing for a developer thinking about carry and schedule. If you're managing the financial side of getting a project entitled and ready to build, Northspyre's milestone and analytics view is a strong fit, and it exposes a modern API (see the Northspyre integration).

The honest limitation: like Procore, Northspyre tracks the milestone you maintain — it isn't a live feed of jurisdiction status. It tells you that the permit milestone is at risk to your budget; it doesn't tell you the city issued a correction notice this morning. That live-status job is the gap a monitoring agent fills.

5. Jurisdiction-specific permitting platforms — the back ends you inherit

Behind many government portals are civic-tech platforms like Accela, Tyler Technologies' EnerGov, and OpenGov. You don't choose these — your city or county does — but it's worth knowing they exist, because their structure determines how cleanly status can be read and whether notification or export options are available. Some expose structured public data; others are essentially a web form over a database. The practical takeaway for a developer: coverage and data quality are a property of the jurisdiction, not something you procure. A good monitoring approach has to handle the messy reality that every jurisdiction's back end is different.

Buyer decision criteria

If you're deciding how to handle permit and entitlement tracking, weigh these in order:

How many jurisdictions are you active in? One — manual portal-checking is defensible. Two or more — the multi-jurisdiction view from a monitoring agent is the differentiator.
Are you tracking entitlements or just construction permits? Entitlement tracking has the worst native tooling; that's where automation and discipline matter most.
What's already your system of record? If you live in Procore or Northspyre, choose a monitoring layer that feeds them rather than a parallel tool that fragments your data.
Who is accountable for status today? If the honest answer is "whoever remembers to check," you have a process risk that no system of record fixes — monitoring does.
How much does a slipped date cost you? On a leveraged development, a month of unanticipated carry usually dwarfs any tooling cost. Price the tool against the carry, not against a SaaS line item.

Where AI changes the answer

For most of permit tracking's history, the only real options were "check the portal" or "log it in your PM tool and hope someone updates it." AI changes the answer in one specific, honest way: it can do the continuous, cross-jurisdiction checking that no human reliably sustains across a pipeline.

A permit-tracking agent monitors the public filing and status sources for every project in your pipeline, normalizes the messy, jurisdiction-specific formats into one view, and surfaces the meaningful changes — an application advancing, stalling, or drawing a correction — to the people who need to act. Crucially, this is decision-support, not advice and not a system of record. It tells you faster, more completely, and without anyone having to remember to look. The official portal stays the authority; your PM platform stays the record; the agent removes the manual gap between them and the schedule risk that hides there.

It also doesn't replace anything you already pay for. It sits on top of Procore, Northspyre, and the jurisdictions' own portals — reading their status, feeding clean data forward. That's the whole pattern of useful AI in CRE: augment the stack you have, don't rip it out.

Lifecycle fit: where permit tracking touches the deal

Permit and entitlement status isn't an isolated construction concern — it ripples across the whole development lifecycle:

Sourcing & acquisition: Entitlement status and permit history are diligence inputs — a partially entitled site carries different risk and value than raw land. Knowing where comparable projects sit in the queue informs the bid.
Underwriting: Your timeline assumptions — and therefore your carry, your interest reserve, and your return math — depend on realistic entitlement and permit durations. Real status data tightens those assumptions.
IC & diligence: The investment committee wants the entitlement risk laid out honestly. A clear, current view of where every approval stands belongs in the memo.
Capital raise & lender reporting: Construction lenders and equity partners both want milestone confidence. Proactive permit-status reporting builds credibility and avoids the awkward surprise update.
Asset management & delivery: Once building, permit and inspection status feeds the schedule and the delivery date that ultimately drives lease-up and stabilization.

Because it touches each stage, permit status is exactly the kind of cross-stage signal that benefits from being monitored automatically rather than reconstructed manually each time someone asks.

The bottom line

There is no tidy "permit-tracking software" category leader because the job spans three different problems and several systems. Government portals are the source of truth but offer no portfolio view. Procore and Northspyre track permits well as part of the broader project, but they track what you log — they don't watch the jurisdiction for you. Jurisdiction-specific back ends are something you inherit, not procure. The genuine gap — continuous, cross-jurisdiction monitoring of entitlement and permit status — is the one a permit-tracking agent was built to fill, as a decision-support layer on top of everything else.

For the broader picture of how this layer fits the full development and investment toolset, see our pillar guide to the complete CRE software stack, and the companion construction management guide for the build phase that follows permitting. If you want to map which monitoring and automation gives your pipeline the fastest payback, our free roadmap call is the right place to start.