Permitting intelligence · Phoenix pilot

Rules move.
Stay ahead.

Track official permitting-source updates, understand what needs review, and turn changing requirements into an organized action list. Without refreshing a dozen government tabs.

01 Official sources02 Reviewable changes03 Actionable checklists
RULECURRENT / MONITOR ILLUSTRATIVE DATA
Jurisdiction workspace
Phoenix, Arizona
● PILOT REGION
04SAMPLE SOURCES
03DEMO SIGNALS
01PILOT CITY
Illustrative update queue
↗
Documentation reviewExample scenario · Electrical
↗
≋
Permit checklist auditExample scenario · Mechanical
↗
◇
Submittal criteria reviewExample scenario · Building
↗
MONITOR VERIFY EXPLAIN ACT
Stop hunting. Start knowing.

Regulation changed.
Now what?

RuleCurrent is designed to close the gap between finding a possible update and deciding what to do with it. Every important item should be tied back to an official source before it becomes an actionable alert.

01 / MONITOR

Official-source watch

Jurisdiction-specific monitoring instead of rumor, forum posts, and disconnected bookmarks. Phoenix is the initial pilot — not a claim of nationwide coverage.

02 / EXPLAIN

What changed, clearly

Reviewable summaries show the relevant source, the potential impact, and the questions your team should confirm before relying on an alert.

03 / EXECUTE

From update to checklist

Turn verified findings into discipline-aware review steps. Your licensed professionals remain responsible for design and permitting decisions.

Interactive workflow preview

The change is only
the beginning.

Choose a discipline to preview how RuleCurrent can frame a possible update. All scenarios here are illustrative — not live permitting news or an official interpretation.

◇ SAMPLE SCENARIO · NOT A REAL ALERTPhoenix pilot

Electrical documentation review

If an authority updates an electrical submittal requirement, the system could flag the affected permit workflow, attach the official source, and suggest what the design team should verify.

Suggested verification workflow
  • Open the jurisdiction’s original published guidance
  • Compare the requirement to the active drawing set
  • Confirm applicability with the authority having jurisdiction

This demo uses sample scenarios. Live subscriber items are detected against the official sources on the RuleCurrent watchlist and verified before they are sent.

Proposed pilot packaging

Clarity you can
budget for.

Pilot pricing for the Phoenix launch. Subscriptions open with the pilot — request access below and we will confirm your start date by email. No payment is taken on this page.

Pulse Solo
$49 / month

For the solo expediter or small firm filing in Phoenix.

  • Weekly digest + material-change alerts
  • Full Phoenix watchlist
  • Every item linked to its official source
Join interest list
Pulse Pro
$199 / month

For high-volume Phoenix filers.

  • Everything in Firm
  • Alerts filtered to your filing types
  • Quarterly watchlist review with our team
Talk about the pilot
Accuracy is the product

Source-linked,
or it doesn't ship.

Every RuleCurrent item is checked against the live official City of Phoenix source at publish time — never written from a scrape, a screenshot, a third-party summary, or memory. If we cannot establish a change from the city's own publication, the item does not go out.

FORMAT

Every item, same five parts

What changed · the official source (direct link) · the source's own effective or posting date · who it affects · the action checklist — what your firm does differently on its next filing.

CORRECTIONS

Corrected visibly, always

If an item is ever wrong or goes stale, the correction goes to every subscriber, marked as a correction, the record is amended, and the incident is logged. That policy is part of what you are buying.

BOUNDARIES

Information, never authority

RuleCurrent is not affiliated with the City of Phoenix or any agency. We never guarantee an approval, a timeline, or an outcome, and nothing we publish is legal advice or engineering judgment. The city's documents govern — we point at them, accurately and fast.

Sample Pulse item — real, verified November 1, 2026

Electrical / HVAC — NEC GFCI enforcement deferred to March 1, 2027

What changed: The City of Phoenix is deferring enforcement of the 2023 NEC 210.8(F) Exception 2 GFCI requirement for HVAC equipment, to ensure adequate product availability. Full enforcement will now take effect March 1, 2027.
Official source: City of Phoenix — Building Construction Codes · Source posting date: not stated on the source page · RuleCurrent verification date: November 1, 2026
Who it affects: Electrical and HVAC filers on Phoenix projects with outdoor HVAC equipment.

  • Carry March 1, 2027 as the enforcement date in project standards — not the original date
  • Confirm equipment GFCI-protection availability per project before specifying
  • Open the source page and confirm the notice is still posted before relying on this item
Phoenix first. Expand with proof.

A better way to follow the rulebook.

RuleCurrent is opening its Phoenix pilot. The watchlist is built from official City of Phoenix sources, verified item by item. Request access and we will confirm pilot start dates by email — no payment until your subscription starts.

Independent tool · Not affiliated with the City of Phoenix

This form opens your own email app with your request addressed to info@rulecurrent.com — nothing is stored on this website.

Jeremy Mills, Founder and CEO of Apex Grid Engineering
Jeremy "Chico" Mills — Founder & CEO
Serial entrepreneur · USAF veteran

Jeremy Mills is the founder and owner of 10+ companies, led by Apex Grid Engineering.

An Apex Grid Engineering PLLC company.