Skip to content

FeatureAI

AIPermit intakeDenverRef. denver-civcheck-startsmart-2026-11

Denver opens an AI completeness check for permit applications, using the CivCheck tool that caught 87% of in-scope intake errors in Seattle's test

StartSmart moves the completeness check to the applicant's side of permit intake, before the city receives the package. In Seattle's test on 29 past residential applications, CivCheck caught 48 of the 55 in-scope reasons reviewers had given for rejecting them.

Seattle test, in-scope intake errors caught
87%48 of 55, March to October 2025
Launched
Nov. 5, 2026Building permits and site plans
Cost to applicants
FreeVoluntary during evaluation
Denver contract
$4.6 millionApproved 10 votes to 1, March
Seattle intake test  |  Rejection reasons by outcome

CivCheck caught 48 of the 55 intake errors its checks covered; 35 fell outside the checks

90 REJECTION REASONS LOGGED BY SDCI REVIEWERS55 IN SCOPE OF THE 34 CONFIGURED CHECKS48CAUGHT BY CIVCHECK, 87%7MISSED35OUTSIDE THE CHECKS4EXTRA FLAGS48 CAUGHT, 87% OF 55 IN SCOPE7 MISSED35 OUTSIDE THE 34 CHECKS4 EXTRA FLAGS, WAIVED BY SCREENERS
CaughtMissedOutside the configured checksExtra flag
One square per rejection reason SDCI reviewers logged on 29 historical small residential applications, March to October 2025. Applicants did not use the tool during the test. Source: City of Seattle, CivCheck AI Pre-Screening Pilot Report.

The City and County of Denver launched StartSmart: Application Intake Assistant on November 5, 2026. It is a free web tool that reads a building permit or formal site development plan application before it is submitted and flags missing or incomplete items against the city's intake requirements. Denver built it with CivCheck, the AI pre-screening product that Seattle tested on 29 past residential applications in 2025. In that test, CivCheck caught 87% of the in-scope reasons city staff had given for rejecting those packages at intake. The workflow it changes is permit intake, the gate a package has to pass before plan review starts.

What it doesStartSmart checks a package in four steps, and Denver says only the second uses AI

Today a permit coordinator, or the architect's team on a design-build job, uploads the plan set and forms to E-permits, Denver's online permitting portal, and waits for an intake screener to say whether the package is complete. Denver says an incomplete package comes back with a request to resubmit, and that exchange can run for days. StartSmart moves the completeness check to the applicant's side, before the city receives anything.

StartSmart  |  Order of work, from Denver's FAQ

Only the extraction step uses AI; the checks run on fixed rules the city wrote

  1. Step 1UploadThe applicant creates a free account on CivCheck's Denver portal, using the same email as the E-permits account, starts a project and uploads the PDFs.
  2. Step 2Extract AIAI reads the plan sheets and forms and pulls out dimensions, labels and required data fields. Denver says this extraction is the only step that uses AI.
  3. Step 3CheckThe extracted data runs through fixed rules the city wrote for that project type. Each flag carries an explanation and a citation to the requirement behind it, and the applicant either fixes the document or explains the item.
  4. Step 4ReportThe tool writes a pre-screening report, watermarks the checked documents and creates the E-permits record, where the applicant finishes and submits. Intake staff read the report alongside the package and still decide whether it is ready for review.
Source: City and County of Denver, StartSmart: Application Intake Assistant.

Denver calls the rule checks deterministic, meaning the same sheet gets the same pass or fail every time. The city says the rules do not change with usage, and uploaded documents are not used to train AI models.

Denver lists architects, engineers, contractors and homeowners as users and says the person who knows the design best should run the check. On a GC-pulled permit that is usually the project engineer or design manager who assembles the package. The tool covers first submissions only. Reviewer corrections and resubmittals stay in E-permits.

Eligible applications are LOG building permits for commercial, multifamily, single-unit, two-unit, ADU and industrial work, including the Main, Intermediate and Walk Through tracks, plus residential interior remodels and formal site development plans. Denver says more application types are expected in 2027.

Evidence so farSeattle's test on 29 past applications is the closest measurement

The evidence is Denver's announcement and FAQ, a March 2026 Denverite report on the contract, and a June 2026 evaluation report from Seattle's Innovation & Performance team on its own test of CivCheck. Denver is in an evaluation period, and results from its own use of the tool are not yet public.

Denver's stated goal came up when the City Council approved a $4.6 million contract for the tool in March, 10 votes to 1. Robert Peek of the planning department told the council the city approves 37% of applications on first review and hopes to reach 80% with the new technology, Denverite reported. Councilmember Sarah Parady asked the planning department to review the contract after a year.

Denver  |  Applications approved on first review

Denver approves 37% of applications on first review and hopes to reach 80%

37%APPROVED ON FIRST REVIEW NOWGOAL 80%0%50%100%37%APPROVED ON FIRST REVIEW NOWGOAL 80%0%50%
Share of applications, as the planning department told the City Council in March 2026. Source: Denverite.

Seattle's test is the closest measurement. From March to October 2025, CivCheck staff loaded historical applications for small residential projects, such as townhouses, single-family homes and ADUs, and Seattle Department of Construction and Inspections (SDCI) reviewers compared the output with their own decisions. Applicants did not use the tool during the test. These results come from Seattle's report:

Seattle plan review test  |  1,262 checks on 57 applications

CivCheck agreed with reviewers' final decisions on 91.7% of plan review checks

91.7%6.4%PASSED BY CIVCHECK, SENT BACK FOR CORRECTION BY REVIEWERS1.9%FLAGGED BY CIVCHECK, APPROVED BY REVIEWERS91.7%6.4%PASSED BY CIVCHECK,SENT BACK BY REVIEWERS1.9%FLAGGED BY CIVCHECK,APPROVED BY REVIEWERS
How CivCheck's checks compared with Seattle reviewers, March to October 2025
StageApplicationsWhat was comparedResult
Intake screening2990 rejection reasons logged by SDCI reviewers35 outside the 34 configured checks
Intake screening2955 in-scope rejection reasons48 caught by CivCheck (87%)
Intake screening2955 in-scope rejection reasons7 missed by CivCheck
Intake screening29Extra flags4 topographic survey flags that screeners had waived
Plan review571,262 zoning and ordinance/structural checks91.7% agreement with reviewers' final decisions
Plan review571,262 zoning and ordinance/structural checks6.4% passed by CivCheck but sent back for correction by reviewers
Plan review571,262 zoning and ordinance/structural checks1.9% flagged by CivCheck but approved by reviewers
Zoning and ordinance/structural checks, March to October 2025. Source: City of Seattle, CivCheck AI Pre-Screening Pilot Report.

The 87% figure is recall, the share of real intake problems the tool flagged. It applies to the 34 completeness checks Seattle configured. Another 35 of the 90 rejection reasons fell outside those checks, so a package that passed the pilot setup could still have come back. The four extra flags were topographic surveys that screeners had waived, including one for basement-only work on a steep lot.

Seattle then modeled what pre-screening would do to calendar time, assuming applicants fix every flagged item before they submit. Scenario A uses the checks from the pilot. Scenario B assumes every intake check is automated and removes one full plan review cycle.

Seattle model  |  Middle housing permits, median calendar days

With the pilot checks, Seattle's model cuts median intake time from 54.5 days to 29

DAYS TO PASS INTAKE SCREENINGACTUAL, NO PRE-SCREEN54.5A: PILOT CHECKS29B: ALL INTAKE CHECKS8DAYS TO PASS PLAN REVIEWACTUAL, NO PRE-SCREEN161A: PILOT CHECKS146B: ALL INTAKE CHECKS117060120180MEDIAN CALENDAR DAYSDAYS TO PASS INTAKE SCREENINGACTUAL, NO PRE-SCREEN54.5A: PILOT CHECKS29B: ALL INTAKE CHECKS8DAYS TO PASS PLAN REVIEWACTUAL, NO PRE-SCREEN161A: PILOT CHECKS146B: ALL INTAKE CHECKS117060120180MEDIAN CALENDAR DAYS
Actual, no pre-screenScenario A, pilot checksScenario B, all intake checks
Seattle's modeled effect of CivCheck pre-screening on middle housing permits
MeasureActual, no pre-screenScenario A, pilot checksScenario B, all intake checks
Median calendar days to pass intake screening54.5298
Average intake review cycles2.551.751
Average intake reviews (zoning plus ordinance/structural)3.863.342
Median calendar days to pass plan review161146117
Median correction cycles to pass plan review3.723.392.72
Modeled, assuming applicants fix every flagged item before they submit. Both panels share one scale in days. Source: City of Seattle, CivCheck AI Pre-Screening Pilot Report.

The intake rows are where the model moves most, from a median of 54.5 days to 29 with the pilot checks. Plan review moves less, because about six review teams work in parallel and the overall time only drops when the slowest review gets shorter. Seattle's authors say each review cycle takes about a month, and they recommended a production pilot limited to completeness screening.

The report also lists which code checks failed most often in the sampled applications. Smoke and carbon monoxide alarm issues each turned up in 8 applications in the ordinance/structural sample, an error rate of 44%. Maximum lot coverage was the most common zoning miss.

Seattle sample  |  Most common code issues

Maximum lot coverage turned up in 75% of the zoning sample, and smoke and CO alarms in 44% of the structural sample

Most common code issues in Seattle's sampled applications. Bars share one scale in percent of applications.
CheckApplicationsApps.Error rateRateBarIssue type
Zoning review
Maximum lot coverage975%Code noncompliance
Trees: caliper inches867%Missing information
Building height650%Missing information, code noncompliance
Front yard650%Code noncompliance
Floor area ratio542%Code noncompliance
Rear yard542%Code noncompliance
Ordinance/structural review
Carbon monoxide alarms844%Code noncompliance
Smoke alarms844%Code noncompliance
Fire separation distance (non-sprinklered)528%Code noncompliance
Fire separation distance between buildings (detached ADUs)317%Code noncompliance
Required heating317%Code noncompliance
Stairway: handrail317%Code noncompliance
Applications with the issue and error rate, by check. Source: City of Seattle, CivCheck AI Pre-Screening Pilot Report.

How to measure it on your projectsDenver's dashboard showed 58 days from submittal to approval, so measure intake on its own

Track intake attempts per application and calendar days to intake acceptance. The first counts how many times a package goes to the city before it is accepted for plan review. The second runs from the first upload to the acceptance date in E-permits. Both come from E-permits records you already keep.

Capture the baseline from your last several Denver applications before your team runs its first StartSmart check, and list every intake rejection reason by sheet or form. Once you start using the tool, log how many flags led to a document change, how many the city waived, and what intake still caught after a clean report. Those last two counts match the misses and extra flags in Seattle's results.

Pilot log  |  Metrics for a StartSmart pilot

Six counts, three to capture before the first StartSmart check and three after

Metrics for a StartSmart pilot on Denver permits
MetricDefinitionBaseline to capture
AIntake attempts per applicationTimes a package goes to the city before it is accepted for plan reviewYour last several Denver applications from E-permits records
BCalendar days to intake acceptanceDays from the first upload to the date the city accepts the package for plan reviewThe same applications and their E-permits dates
CIntake rejection reasonsEach reason the city gave for returning a package at intakeA list by sheet or form for the same applications
DFlags your team acted onShare of StartSmart flags that led to a document changeStarts with the first StartSmart submission
EFlags the city waivedStartSmart flags that intake staff set aside for the projectStarts with the first StartSmart submission
FItems intake still caughtRejection reasons the city gave after a clean StartSmart reportStarts with the first StartSmart submission
The first three rows come from E-permits records a contractor already keeps. Compiled by Construction Metrics.

Keep intake separate from the rest of review time. Denver's review time dashboard showed an average of 58 days from submittal to approval over the prior 90 days in its opening view on November 8, a figure that counts city time and applicant time together. It also lists 90-day estimates by discipline, which is where most of a permit's calendar time sits after intake.

Denver  |  Review tasks, prior 90 days

Initial review estimates run from 1 to 3 days for Landmark to 13 to 30 days for Forestry

Initial review, estimated daysResubmittal review, estimated days
Denver review tasks, prior 90 days, as shown on November 8, 2026. Bars share one scale in days.
Review taskInitial reviewsInitial, est. daysEstimated daysResubmittalsResubmittal, est. days
Forestry9313 to 307712 to 31
Parkview1116 to 284about 16
Fire48015 to 221569 to 15
Energy26312 to 222068 to 14
Architectural48211 to 184045 to 13
Urban Design828 to 18315 to 10
Structural56311 to 174066 to 14
Zoning (Commercial)64511 to 175405 to 8
Plumbing28510 to 171565 to 12
Mechanical3829 to 162304 to 10
Transportation3887 to 15855 to 14
Access Control1145 to 15693 to 7
DDPHE3939 to 14507 to 12
Electrical8138 to 144554 to 8
SUDP1,3967 to 141,3695 to 8
Zone Lot Verification3068 to 13265 to 11
Residential7576 to 135045 to 13
Zoning (Residential)6936 to 135565 to 12
Landmark4711 to 3914 to 7
0102030days
Reviews completed and estimated days by review task, sorted by the longest initial estimate. Parkview resubmittals are shown as a point at about 16 days. Source: City and County of Denver, Average Plan Review Times, as shown on November 8, 2026.

The same before-and-after method appears in our post on measuring RFI turnaround before an AI pilot, and UpCodes' AI Plan Review runs a similar code check from the design side.

First step on one job

For your next Denver submission, write down the first upload date, every intake rejection reason and the acceptance date, then pull the same three items for the last three packages your office submitted without the tool.

Availability and costStartSmart is free to applicants, and CivCheck has worked with 13 jurisdictions

StartSmart is free for applicants, with no fee per account or per project. It is voluntary during Denver's evaluation period, and the city says any decision to require it would come with stakeholder engagement and advance notice. The StartSmart and E-permits accounts are separate.

Seattle's report says CivCheck, now owned by Clariti, has worked with 13 jurisdictions across North America. Seattle's 2026 budget includes funding for a production pilot of completeness screening.

Data behind this page: check accuracy, intake scenarios, common errors, Denver review times and pilot metrics (CSV).