Permit Application Review: Permits Issued When Documents, Fees and Inspections Agree

Documents, receipts and inspections, all in place before a permit issues

An application at the intake desk becomes a permit only after it clears four gates. The documents required for its permit type are on file, the fee computed from the declared valuation has been paid, any prerequisite inspection has been confirmed, and the use is allowed where the work will happen or a variance has been granted. Missing any one puts the application on hold.

The trouble is where the evidence lives. Applications are in Salesforce, plans, forms and fee receipts are filed in Box, inspectors confirm prerequisite inspections by email to the desk's Outlook mailbox, and the fee schedule and intake rules are documents in Drive. A technician drafting a batch works from all of them at once, and when a valuation is corrected, the fee has to be recomputed and compared with what the receipt shows was paid.

Who works in the room

The permit room routes unaddressed messages to Nova, its default agent and the only one with a grant to the inspection mailbox, which the supervisor approved. A question about whether an application can issue therefore always reaches Nova. Fin owns anything about money and anything addressed to an applicant. When Nova finds a corrected valuation, it mentions Fin in the thread with the application number and the new figure, and Fin returns the recomputed fee before Nova proposes a disposition.

How an intake week runs

The intake rules and the fee schedule sit in Drive and in the room guidelines. Fees are carried in whole cents and dates in one format, so a computed fee and a receipt can be compared exactly.

When a valuation, a document or a variance arrives late

The changes that matter most move money. An applicant corrects a declared valuation from $180,000 to $214,000, and the fee moves up a bracket on the schedule. Fin recomputes it in whole cents, compares it with the receipt in Box and reports the balance due. An application that was ready to issue goes back to hold until the balance is paid, and Fin drafts the notice for a technician to send.

Other changes clear holds. Plans filed on Wednesday clear four applications that were waiting on documents. The zoning administrator grants a setback variance, so one referred application is re-run against every gate, not only zoning. Nova re-runs only the applications each change names and notes on every changed record which document or decision moved it.

What the checks catch

• An application proposed to issue on a receipt for the old fee after its valuation was corrected
• A prerequisite inspection marked passed in the draft batch with no confirmation in the Outlook mailbox
• A fee with a rounding difference, because it was computed in dollars rather than whole cents
• A variance that cleared the zoning gate while a required document was still missing
• A close-out count by permit type that does not match the current records

What stays with people

• Approving every disposition and fee before Salesforce is updated
• Granting variances and every other zoning judgment
• Sending every notice to an applicant, which Fin prepares as a Gmail draft
• Signing the per-type close-out

Integrations in this workflow

Kylon is not a permitting system and it does not replace one. It works across the tools the permit desk already uses and keeps the coordination between them in one room.

• Box
• Gmail
• Google Drive
• Outlook
• Salesforce
• Slack

• Salesforce holds each application with its type, valuation, fee, disposition and dates
• Box holds the plans, forms and fee receipts filed for each application
• Outlook is the desk mailbox where inspectors confirm prerequisite inspections
• Gmail carries hold and balance notices to applicants, each one a draft a technician sends
• Google Drive keeps the intake rules, the fee schedule, the drafted batch and the intake summary
• Slack is where inspectors and plan reviewers outside the room post quick updates

Where to start

Run the first week on a single permit type. Connect the Salesforce object that holds your applications, give Nova its grant to the inspection mailbox, and add one rule to the room guidelines: an agent may propose a disposition or a fee, and the supervisor approves every one before a record changes.

“A permit issues when the documents, the receipt and the inspection all agree, and the thread shows each one.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.