All templates

Automated PermitFlow Project Intake Checklist

The moment a new project is created in PermitFlow, WebRun reads the project type and jurisdiction, builds an intake checklist in Google Sheets with the required documents and fee schedule, drafts a kickoff email to the client listing exactly what to send over, saves it in Gmail for your review, and posts a Slack note assigning an expediter.

Runs on WebRun · Strict Lockdown policy
Within minutes of each new project in PermitFlow WebRunorchestrates each step
1 PermitFlow read the new project's type and jurisdiction
2 Google Sheets build the intake checklist
3 Gmail draft the client kickoff email
4 Slack assign an expediter
In short

How do I set up a new permit project as soon as it comes in?

The moment a new project lands in PermitFlow, WebRun reads its type and jurisdiction, builds an intake checklist in Google Sheets with the required documents and fee schedule, and drafts a client kickoff email listing exactly what's needed, saved in Gmail for your review before it sends. It also posts a Slack note assigning an expediter, so the file starts moving on day one.

  • Every new project gets a complete requirements checklist within minutes
  • Clients get a drafted kickoff email instead of a delayed manual one
  • No new project sits unassigned overnight

Built for permit expediters · permit expediting firms · general contractors · architecture firm permit teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.permitflow.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    PermitFlow - read the new project's type and jurisdiction
    permitflow.com
    WebRun in PermitFlow: read the new project's type and jurisdiction
    WebRun opens PermitFlow to read the new project's type and jurisdiction.
    • Open the new project in PermitFlow and read its type, jurisdiction, and scope of work
    • Pull that jurisdiction's required document list and fee schedule
    • Note anything already uploaded versus still needed

    Done when The new project's requirements and current documents are captured.

  3. 2
    Google Sheets - build the intake checklist
    google.com
    WebRun in Google Sheets: build the intake checklist
    WebRun opens Google Sheets to build the intake checklist.
    • Open the project intake tracker
    • Add a row or tab for the new project listing every required document and its status
    • Include the jurisdiction's fee schedule for the project type

    Done when The new project has a complete intake checklist in the tracker.

  4. 3
    Gmail - draft the client kickoff email
    gmail.com
    WebRun in Gmail: draft the client kickoff email
    WebRun opens Gmail to draft the client kickoff email.
    • Draft a kickoff email to the client listing exactly which documents are still needed
    • Include the jurisdiction's typical fee schedule so there are no surprises
    • Save it as a Gmail draft. Leave it unsent for your review

    Done when The new project has a drafted kickoff email waiting for approval.

  5. 4
    Slack - assign an expediter
    slack.com
    WebRun in Slack: assign an expediter
    WebRun opens Slack to assign an expediter.
    • Post a note announcing the new project with its jurisdiction and scope
    • Assign an expediter based on current workload

    Done when The new project has an assigned owner posted in Slack.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.permitflow.com
ScheduleRuns automatically on this cadence
Within minutes of each new project in PermitFlow
DeliveryHow each run's result reaches you
Intake checklist · Google Sheets, Slack
OutputWhat each run produces - A Google Sheets intake checklist for the new project, a drafted client kickoff email, and a Slack note with the assigned expediter.
Checklist + drafts
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it email the client without my approval?

No. The kickoff email is saved as a Gmail draft, never sent automatically. You review it before the client ever sees it, so the ask matches your usual tone.

How does it know what documents a jurisdiction requires?

It reads the jurisdiction profile and requirements PermitFlow already tracks for that project type, so the checklist matches what that specific AHJ actually asks for.

Who gets assigned to the new project?

WebRun suggests an expediter based on current workload and posts it in Slack. Reassign it any time, the suggestion is a starting point, not a lock.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.