From the Local Government edition of October 3, 2026
Clariti case study: Honolulu CivCheck cuts residential plan-review cycles 58% and days-to-decision 55% (Q1 2026 sample)
Clariti (CivCheck) / City and County of Honolulu Department of Planning and Permitting · Municipal planning and building permitting · Honolulu, Hawaii, United States
- Publisher
- Clariti
- Original publication
- Undated vendor case study page (metrics labeled Q1 2026; related city award coverage July 2026)
- Source retrieved
- 2026-10-04
What happened
Clariti reports Honolulu DPP's CivCheck guided AI plan review reduced average plan-review cycles from 3.4 to 1.4 (−58%), corrections from 23.5 to 7.7 (−67%), and days to permit decision from 73 to 32.5 (−55%), with ~40.5 applicant days saved versus non-CivCheck applications. Figures compare 19 completed CivCheck residential permits to 17 non-CivCheck projects in Q1 2026; an earlier pilot on 145 pre-screened applications claimed ~70% residential plan-review time reduction. Director quotes emphasize applicant guidance before staff review, not autonomous approval.
Why it matters
Direct local-government permitting modernization with published cycle-time metrics—highly transferable as a measurement template, with caution on small completed-sample size and vendor authorship.
Evidence and measured results
Vendor-published metrics table and methodology note (19 vs 17 completed residential permits, Q1 2026); pilot claim of 70% review-time cut across 145 pre-screened applications; attributed quotes from DPP Director Dawn Takeuchi Apuna.
Limitations and uncertainty
Vendor-authored page; completed-sample n=19/17 is small; selection effects possible between CivCheck and non-CivCheck cohorts; Honolulu mandate coverage already in archive via other URLs—this page newly archives the detailed Q1 table.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-03; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Residential permit backlogs driven by incomplete or non-compliant submissions force repeated review cycles and long applicant waits.
- Stakeholders
- Planning & Permitting director
- Building officials/plan reviewers
- CIO/enterprise architect
- Mayor/CA housing lead
- Applicant/industry liaison
- Discovery questions
- What are current average review cycles and days-to-decision for residential permits?
- How many completed permits will be in any before/after evaluation cohort?
- Who owns final approval after AI flags?
- Will use be voluntary or mandatory for eligible residential types?
- Value hypothesis
- Guided AI pre-check can reduce correction cycles and calendar time if applicants remediate before staff review, but published gains rest on small Q1 2026 samples.
- Potential engagement
- Eight-week discovery: baseline metrics extract, code-rule coverage map for eligible residential types, and a pilot evaluation design with paired control permits.
- Unsupported claims
- Guaranteed 70% review-time cut for every jurisdiction
- Autonomous code-compliant permit issuance without human review
- That n≈19 completed permits generalizes citywide performance
Pre-sales engineering
Role takeaway
- Fit
- Strong for applicant-facing guided completeness/code-issue flagging ahead of human plan review; weak for discretionary zoning judgments.
- Architecture and integration
- Applicant portal → CivCheck guided checks → corrected package → DPP intake/plan-review systems; optional analytics on cycle counts.
- Prerequisites
- Digitized residential submittal path
- Codified check rules for eligible project types
- Baseline permit performance data
- Staff exception workflow
- Constraints
- Jurisdiction-specific building codes
- Small early completed-sample sizes
- Mandatory-use change management
- Public-records handling of plan sets
- Security
- Encrypt plan uploads; contractually prohibit vendor training on applicant documents; role-based reviewer access; retain logs for audit.
- Proof of value
- Replicate cycle/correction/days-to-decision metrics on local completed permits
- Compare intake rejects before vs after guided checks
- Measure staff hours per residential permit
- Track applicant remediation completion before first review
Delivery
Role takeaway
- Work
- Configure residential rule packs, run a measured pilot with control cohort, train intake/review staff, and decide voluntary vs mandatory rollout gates.
- Dependencies
- Vendor configuration support
- DPP process owners
- Legal/public-records review
- Applicant communications
- Ownership
- Department of Planning and Permitting director with IT security co-ownership of data controls.
- Skills and adoption
- Train reviewers to treat AI flags as triage aids; train applicants/industry on remediation workflow; keep human final review.
- Governance checkpoints
- Pilot evaluation report before mandate
- Security/privacy contract review
- Public metrics dashboard approval
- Expansion criteria for commercial types
- Acceptance criteria
- Statistically reviewed local reduction in average plan-review cycles vs baseline
- Documented human-final-decision policy
- No unauthorized vendor reuse of plan data
- Published limitations including sample size
- Risks
- Overgeneralizing vendor small-n results
- Applicant pushback on mandatory AI tool
- Rule drift as codes update
- Equity impacts if atypical projects are poorly handled
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Applicant-facing guided checks in front of human plan review; standardize rule packs; instrument correction cycles and calendar time as first-class telemetry.
Governance
Who approves, reviews and stays accountable for outcomes?
Treat vendor ROI slides as hypotheses until locally replicated; disclose sample sizes; keep human final decisions; stage mandatory-use only after measured pilots.
Security and privacy
What data, permissions and controls need testing?
Plan sets are sensitive; contracts should bar training on applicant documents and define retention aligned to permit records.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Aims to reduce rework for applicants and free reviewers for complex work; equity risk if atypical projects are poorly handled by rule packs.
Procurement
What should contracts, pricing and exit terms secure?
Demand local baseline replication, sample-size disclosure, and data-use prohibitions in contracts before sole-source or mandatory deployment.
Operating model
Which teams own the service once it runs?
Shifts incompleteness discovery earlier to applicants; staff become exception handlers over first-line completeness checkers.
Publication history
- 2026-10-03Local Government · Issue 285 resources
Stable resource ID: clariti-honolulu-civcheck-q1-2026-metrics