PROCESS / WORKFLOW

Catch common plan issues before they become permit delays.

PlanSmartAI™ is used before permit submission to help teams review plans, address gaps, and submit with clearer expectations—without disrupting existing workflows.

01 Foundation

Used upstream of formal permitting

PlanSmartAI fits into the planning and coordination Phase—after plans are assembled but before they are formally submitted. It helps teams identify common documentation gaps, coordination issues, and code-related risks early, when changes are still manageable.

PlanSmartAI does not replace reviewers or alter agency processes. It helps teams prepare more complete submissions before plans reach the permit desk.

02 Flow

A simple, repeatable review loop

  1. Upload your plan set

    Teams upload a plan set they are preparing for submission. This may include architectural drawings and related documentation required for review. This step happens before formal submission.

  2. Run a review

    PlanSmartAI analyzes the plan set to surface potential issues such as missing references, inconsistent details, zoning conflicts, or other common review triggers. The goal is not to “approve” plans, but to bring visibility forward—highlighting areas that often generate reviewer comments later.

  3. Assess flagged gaps, conflicts, and risks

    Teams review structured findings, prioritize what to address, and clarify documentation as needed. Output is structured findings—not a pass/fail decision.

  4. Revise and re-run as needed

    Multiple review passes are expected. Re-running analysis is intentional and supported so teams can test changes and confirm improvements before submission.

  5. Submit with more confidence

    Once teams are ready, plans are submitted through normal channels. PlanSmartAI’s role ends at submission.

03 Iteration

Why multiple reviews are expected

Iteration is part of the process. Permitting delays rarely come from one major mistake—they come from small issues that surface late. PlanSmartAI is designed to support iterative review while plans are still flexible.

  1. 01 Run an initial review
  2. 02 Revise select areas
  3. 03 Re-run analysis to confirm improvements
  4. 04 Submit with fewer surprises

This approach mirrors how successful projects already operate—just earlier and with more visibility.

04 Post-submit

PlanSmartAI steps out after submission

  • Municipal reviewers apply their own criteria and processes
  • PlanSmartAI does not intervene or participate
  • Findings remain a team reference, not an official record

This separation preserves agency authority while allowing teams to submit with greater confidence.

05 Plans

How this connects to plans, reviews, and credits

On the Plans page, we explain what a review is, why re-runs matter, and how usage varies by project—so pricing can stay aligned to workload instead of one-off feature gates.

06 Next step

See how this fits your workflow

PlanSmartAI is built to align with how teams already prepare plans—by adding an upstream review step, not restructuring the entire process.