Catch jurisdiction rule changes before they slow a permit down
Every night, WebRun opens PermitFlow, checks for jurisdiction requirement updates such as a new submittal item, a revised code cycle, or a changed fee schedule, matches each update against your open permits in that jurisdiction, logs affected projects to a Google Sheets tracker, and posts a Slack alert naming what changed and which jobs it touches.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I know when a jurisdiction changes a requirement that affects my open permits?
WebRun checks PermitFlow every night for jurisdiction requirement updates, such as a new submittal item, a revised code cycle, or a changed fee schedule, and matches each one against your open permits in that jurisdiction. It logs affected projects to a Google Sheets change log and posts a Slack alert naming what changed, so a rule update never blindsides a permit already in review.
- No open permit is blindsided by a jurisdiction rule change it never saw
- Every requirement update is matched to the permits it actually affects
- The change log gives one place to see every jurisdiction update, old and new
Built for permit expediters · permit expediting firms · architecture firm permit teams · construction project managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.permitflow.comin a real browser with your saved login - no setup, no API keys. -
1
PermitFlow - check for jurisdiction requirement updates
permitflow.com How to Automate PermitFlow
WebRun opens PermitFlow to check for jurisdiction requirement updates. - Open PermitFlow and check each jurisdiction profile for a requirement, code cycle, or fee schedule update since the last run
- Match each update against open permits filed in that jurisdiction
- Note which submittal stage or fee each change affects
Done when Every jurisdiction update this run is matched to the open permits it affects.
-
2
Google Sheets - log affected open permits
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log affected open permits. - Open the jurisdiction change log sheet
- Add a row for each requirement change with the jurisdiction, what changed, and the affected permits
- Mark whether it applies to permits already submitted or only new filings
Done when The change log reflects every jurisdiction update and its affected open permits.
-
3
Slack - alert the team to what changed
slack.com How to Automate Slack
WebRun opens Slack to alert the team to what changed. - Post an alert naming the jurisdiction and what changed
- List the affected open permits by project name
Done when The team has an alert for every jurisdiction change touching an open permit.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it update our permit applications automatically?
No. WebRun only flags the change and which open permits it touches. Deciding how to respond, such as amending a submittal, is always a human call.
What kind of changes does it catch?
Anything logged in PermitFlow's jurisdiction profile: a new submittal requirement, a revised code cycle, or a changed fee schedule, matched against your currently open permits in that jurisdiction.
What if a change only affects new filings, not our open permits?
It's logged in the sheet either way, but the Slack alert only fires when the change actually matches a permit you have open right now.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.