A connected building department

Your workflow.
Your knowledge.
A clearer way forward.

Give residents a clearer path through permitting and staff a more connected way to manage the work. Permitech GOV begins with your department’s process and a dedicated setup and calibration engagement.

One or two permit types to start. A defined scope. Staff-led decisions.

Designed around your department
  1. 1
    Department knowledge

    Sources, owners, permissions

  2. 2
    A prepared applicant

    Clear requirements and next steps

  3. 3
    Your team’s workflow

    Calibrated before activation

Illustrative workflow · department-led setupMotion reduced

The front door, in one minute

Zoning, parcel and forms, checked before it's filed.

Permitech GOV: The Front Door: how a pre-submittal layer sits in front of the system a department already runs. Plays on YouTube.
Watch the film on its own page

Two starting points. One department-led process.

Start where your department is.

The implementation scope defines which work Permitech carries and how it connects to the tools and procedures you already use.

Pre-submittal implementation

Help residents arrive prepared.

Map the requirements, forms, documents, and handoff for the selected permit types. Define how applicants prepare their information before continuing to your existing filing process.

  1. Reviewed department guidance
  2. Project preparation and completeness
  3. Handoff to your established filing process

Explore the implementation approach. Activation depends on the agreed scope and completed validation.

Knowledge with clear boundaries

Your expertise.
Your sharing decisions.

Bringing department knowledge together should make it more useful while preserving control over who can use it. Each implementation defines three distinct audiences.

Internal department use

Internal procedures and reviewed sources form the department’s own knowledge foundation. Private material is the starting point.

Resident-facing guidance

Choose which reviewed information belongs on public profiles, checklists, and applicant instructions.

Optional broader contribution

Decide separately whether approved knowledge may strengthen Permibot for other Permitech users. Participation does not require that permission.

Dedicated implementation

Setup is part of the work.

A useful permitting experience is calibrated with the people who run the department. The engagement produces a workflow map, reviewed source inventory, configuration, scenario results, and a launch acceptance record.

01 / Discover

Map the work.

Choose one or two permit types. Document how residents prepare, how staff review, and where follow-up accumulates.

02 / Configure

Make the process explicit.

Agree on source material, access roles, checklists, handoffs, records, and the responsibilities the deployment will support.

03 / Calibrate

Work through real scenarios.

Validate complete, incomplete, and correction examples with department staff. Resolve gaps and record what the team accepts.

04 / Activate

Launch with your team.

Train the people who will operate the workflow. Confirm support and agency acceptance before opening the agreed scope to residents.

A public presence that stays connected

Your department’s information deserves an owner.

The GOV approach includes verified department profiles and a managed update process for contacts, hours, forms, filing instructions, and common questions. Department requests carry a source and a review history.

The proposed service target is review within 24–48 hours. Publication authority, coverage, escalation, and response commitments are agreed during setup. Internal knowledge permissions remain separate from public-page changes.

Explore the existing Illinois department directory

Let’s define the right scope

Start with the work
you want to improve.

Tell us your department, current filing approach, and one or two permit types you would like to focus on. We will use that context to discuss requirements and define an implementation plan.

Available capabilities, integrations, security requirements, and the activation schedule are confirmed in the written scope. Resident intake, review, payments, and issuance require their own validated workflow.

Request an implementation consultation customerservice@permitech.io

For an initial inquiry, share workflow context. Keep resident records and private department documents out of the public form.

Read how setup and calibration work →