Skip to content
CAPPI
AI-assisted permitting workflow

Move permits from submittal to decision— faster.

Upload plan sets, run ordinance-backed review checklists, resolve findings, and export a complete decision record from one permitting workspace.

New commercial permit · Review

Plan set

1420 Central Avenue · Tenant improvement

18 sheets · Zoning and building review

Review progress

8 of 10

Parking and access verified

Front setback needs reviewer decision

Sec. 17.608Setback requirementsSec. 15.20Site plan standards

The challenge

Plan review still runs on tribal knowledge and PDF hunting.

Plan reviewers and planners check submittals against sprawling municipal codes by hand — slow, inconsistent, and hard to audit when a decision is questioned later.

Which rules apply?

Thousands of sections; only a subset fits this parcel, zone, and project type.

Where is the evidence?

The answer is often a dimension or note buried on one sheet of a long plan set.

Can we defend it?

Staff need the clause, the page, and a review trail — not a free-form AI guess.

Permitting workspace

The review desk, connected from intake through decision.

CAPPI brings the plan set, applicable requirements, reviewer findings, and final record into one traceable workflow.

Intake and extraction

Upload the submitted plan set and turn sheets, notes, and dimensions into review-ready project facts.

  • Source-page references for extracted facts
  • Project and jurisdiction context carried forward
  • A structured starting point for staff review

Ordinance-backed review

Run the jurisdiction's checklist against the plan set, with every requirement linked to its source.

Findings and decisions

Resolve exceptions, record reviewer judgment, and preserve the reasoning behind every outcome.

Decision package

Export a cited record for applicants, supervisors, appeals, and the permanent permit file.

GIS intelligence

Put the site plan on the parcel.

Reviewers register the drawing to the lot in three clicks. Zoning, overlays, and constructed setback rings share one map — linked to ordinance findings, not a separate GIS tab.

Parcel map

ParcelZoningSetback ringsSite plan
FOLSOM BLVDSITE PLAN · A1.05'
Sheet preview

SITE PLAN

APN 012-0034-005

R-1 · Sacramento GIS

Zoning PassFront setback Needs info
  1. 01Read the sheet

    The site plan is rasterized from the uploaded PDF so reviewers can click the same lot corners they see on the drawing.

  2. 02Match the parcel

    Three paired clicks register the sheet to public GIS — Sacramento parcel, zoning, and overlay districts, stored as a snapshot.

  3. Measure on the lot

    Setback rings and GIS assessment sit on the registered overlay. Findings stay advisory: Pass, Fail, Needs info — never “Approved.”

Built for applicants, too

The plan, the parcel, and the answer — one screen.

No mystery portal. Applicants can see what staff flagged, inspect the exact PDF or map context, and respond without breaking the review trail.

My application

1420 Central Avenue · Tenant improvement

Corrections requested

Finding 2 of 3

Front setback needs information

Confirm the dimension from the property line to the proposed addition.

Sheet A1.0§17.608

Your response

Revised A1.0 now labels the 15' front setback.

revised-a1.pdf

Reference

PDF Parcel map

SITE PLAN · A1.0

15'
  1. 01See the exact sheet

    Every finding opens beside the submitted PDF, already anchored to the page the reviewer cited.

  2. 02Flip from page to parcel

    The same reference pane moves from drawing to GIS context — parcel, zoning, and setbacks without losing the finding.

  3. 03Answer in context

    Applicants reply, attach the revision, and preserve one clean thread instead of chasing comments across email.

Applicant process

A clear path from application to response.

The public-facing workflow unfolds without mystery: prepare, submit, then respond in context.

My application

Draft

Project address

1420 Central Avenue

Application type

Tenant improvement

central-ave-plan-set.pdf

18 sheets · Ready for review

Front setback needs information

Reviewer linked Sheet A1.0 and §17.608. Reply or attach a revised sheet here.

  1. 01Receive the submittal

    Create the application, choose the jurisdiction, and enter the project details once.

  2. 02Check completeness

    Upload the plan set and see required sheets and missing information before review.

  3. 03Track and respond

    Follow review status, answer cited findings, and submit revisions in the same record.

Review process

Every review stage keeps its evidence.

The review desk moves from cited checks to accountable judgment and a complete decision record.

Review desk

Analyzing

Plan A1.0

Parking and access

Pass · Sheet C2.1 · §17.608

Front setback

Needs info · Sheet A1.0 · §17.608

Decision record ready

Findings, citations, reviewer judgment, and audit history included.

  1. 01Run cited review

    Evaluate the plan against applicable requirements with ordinance and source-page citations.

  2. 02Resolve findings

    Accept, revise, or override each finding while preserving reviewer notes and judgment.

  3. 03Issue the record

    Export the decision, findings, citations, and review history into a complete permit file.

Who it's for

Built for permits and civic planning teams.

CAPPI helps city and county staff move permit applications through a consistent, ordinance-backed review process.

Plan reviewers

Run cited checklists on submittals and keep a defendable decision trail on every finding.

Planners

Apply zoning and development standards consistently across every submitted plan set.

Permit technicians

Organize intake, completeness checks, applicant responses, and routing from one permit record.

City attorneys

Review the cited reasoning and decision history when a finding is challenged or appealed.

About us

The team behind CAPPI.

We build ordinance-backed permitting software so civic teams can review plans with clearer evidence and less PDF hunting.

Headshot of Ashley Etemadi

Ashley Etemadi

Co-founder

Ashley is a project manager for machine learning and generative AI projects and formerly a researcher at Harvard, examining applications of AI and XR for enhancing human judgment skills. She has spent 15 years advising Fortune 500 companies, growth-stage enterprises, and social impact ventures. At CAPPI, she focuses on product direction and implementation.

Headshot of Michael Ashenafi

Michael Ashenafi

Co-founder

Michael is a software engineer and researcher with a PhD in Information Technology from the University of Trento and research experience at Carnegie Mellon and the University of Pennsylvania. He brings a decade of building distributed systems and AI platforms across healthcare, federal, and SaaS into CAPPI — streamlining municipal permitting from proposal to construction.

Pricing

Start with the workflow that matters most.

Begin with one focused jurisdiction workflow, then expand when the team is ready.

Best place to start

Workflow pilot

Prove the permitting workflow with one jurisdiction, one review team, and a focused checklist.

Custom pricing

Discuss workflow pilot

Full deployment

Department rollout

Expand CAPPI across permitting teams, review types, and the jurisdiction's adopted requirements.

Custom pricing

Discuss department rollout

FAQ

Common questions from permitting teams.

CAPPI is built for staff workflows. Here is how we treat legal responsibility, privacy, security, and jurisdiction onboarding.

Is CAPPI legal advice?
No. CAPPI is an informational permitting and plan-review tool. It does not replace advice from a licensed attorney, code official, or authorized plan reviewer.
How does CAPPI handle data privacy?
Plan sets, findings, and review notes stay scoped to your organization's workspace. We do not sell customer data or use your plan submissions to train public models. Access is limited to authenticated staff accounts for your jurisdiction, and you control which projects are uploaded and retained.
How is data secured and encrypted?
Data in transit is protected with TLS. Stored plan files, review records, and credentials use encryption at rest on managed infrastructure. Production access is restricted, and authentication limits workspace access to authorized staff.
Where is our data stored, and can we retrieve it?
Plan sets, findings, and review history are stored securely in cloud storage on managed infrastructure. Your organization can request a full export of uploaded files and review records at any time, so you always have a complete copy for your archives and internal systems.
How do we onboard a new city, county, or municipality?
Onboarding typically starts with a scoped pilot: we identify the jurisdiction, the titles and checklists that matter for your permitting workflow, and the official code host to index. After the corpus and review checklist are configured, your team trains on sample projects, then expands to additional review types or neighboring jurisdictions as needed. Email contact@trycappi.com to start.

Get started

Try the workflow from either side of the counter.

Applicants submit and track plan sets; plan reviewers run cited checks, resolve findings, and close the decision record.