The systems, rules, and operating record behind civic approvals.
Reporting on rules, public programs, platforms, services, implementation, records, and operating decisions across community development.
PayIt describes one resident profile across government services, including identity-sensitive transactions and licensing or permitting. A jurisdiction still needs filing-level proof of whether the signed-in person may act for the owner, contractor, business, or other applicant.
Cityworks' PLL documentation says permits and cases are audited by user, date, time, and change, while also saying administrators can limit auditing to selected groups or items. A jurisdiction should verify the configured event population, identities, prior values, retention, exports, and custody before relying on the log as a complete public record.
Clariti's 2026 buyer guide tells jurisdictions to inventory, cleanse, sequence, and prepare legacy data before implementation. Acceptance still requires the jurisdiction to prove population, meaning, relationships, retention, attachments, balances, workflow state, and cutover for each record class.
ePermitHub describes end-to-end document management for plan review, including integrations with permitting and construction tools. A defensible public record still needs a jurisdiction-owned identifier, authoritative version, transfer receipt, reviewer action, retention rule, public-record treatment, and final approved-set designation across every system boundary.
e-PlanSoft presents PDF Scout as a pre-review tool that can flag known file issues and reject files before review. A passed technical check still needs to remain separate from intake completeness, substantive plan review, correction disposition, jurisdictional approval, permit issuance, inspection, and occupancy authority.
GovPath says it launched after a merger of TruePoint Solutions and Gray Quarter; a public agency still needs an authoritative counterparty, assignment, authority, insurance, payment, support, and amendment record for every existing contract.
A 2026 City of Los Angeles record proposes extending Gartner project-management and IT consulting for BuildLA and the LA City Permitting System through March 2028. The contract record establishes proposed scope, term, funding, and governance—not go-live, migration completion, configured product behavior, production acceptance, service performance, or Clariti involvement.
Granicus documents permitting and licensing platforms with self-service access, workflow communication, real-time data, and mobile tools. A portal update can improve service, but the jurisdiction still needs a controlled record of what notice was issued, by whom, through which authorized channel, when service occurred, and which deadline followed.
OpenCounter says applicants can learn expected permits and project costs before applying. An estimate still needs a dated project scope, adopted fee authority, calculation trace, staff review, and final assessment.
Cloudpermit documents planning-and-zoning workflow and application circulation. Routing progress still needs the jurisdiction's record, reviewer analysis, findings, conditions, hearing, and decision authority.
GovSense documents mapped inspector locations and scheduled-inspection progress. Location can support dispatch, but it does not establish arrival, observation, result, approval, or safety.
ZoningHub describes a public-facing zoning research service that communities populate with code content and may pair with GIS. A parcel result can organize a first inquiry, but it is not an authoritative zoning determination for a specific property or proposal.
CentralSquare presents automated workflows for land-use planning, permitting, and inspections. A workflow status can coordinate work and show recorded progress, but it does not prove that every zoning, planning, infrastructure, environmental, legal, or project-specific condition has been satisfied by the authorized body.
BS&A documents permit workflows that link contractor and licensee records and notify staff about expiration, registration, money owed, and stop-work conditions. Those checks can focus review, but the jurisdiction's current source records and authorized official still determine whether a contractor may perform the named work.
Clariti describes CivCheck as guided AI plan-review software and states that every AI interpretation requires staff review and approval. That boundary should remain visible in the case record: an automated interpretation can focus reviewer attention, but the jurisdiction's authorized reviewer owns the finding.
Symbium presents computational-law software for property and permitting workflows, including automated checks against configured rules. A passing result can inform intake or review, but only the authorized jurisdiction can determine completeness, exercise discretion, impose conditions, and issue a permit.
Citizenserve presents complaint intake and code-enforcement case management within a broader municipal platform. A submitted complaint can start a traceable review, but it cannot establish that the reported condition exists, falls within the jurisdiction's authority, or constitutes a violation.
SAFEbuilt presents building-department, plan-review, inspection, code-enforcement, and community-development services for local governments. Supplemental or outsourced capacity can move work, but the jurisdiction still needs a durable record of engagement scope, assigned role, applicable code, reviewer action, decision, exception, and public handoff.
Cloudpermit documents scheduling, mobile and offline field inspections, notes, photos, results, status updates, reports, and reinspection workflows. Those records can make municipal inspection work more visible, but a status in the system does not establish the condition of unobserved work, future performance, or a broader safety conclusion.
Tyler documents electronic plan submission, concurrent review, markups, approval stamps, version control, workflow, and field access within Enterprise Permitting & Licensing. Civic teams still need one authority-controlled chain from applicant revision through discipline review, conditions, approval, issuance, field set, later revision, and final record.
Point & Pay presents payment services for government transactions, including permits and licensing. A successful transaction can establish payment-channel evidence, but the permit decision still belongs to the authorized agency workflow and its complete record.
Accela documents one transactional record object across applications, permits, cases, licenses, service requests, and work orders. An integration that copies a status without the agency's record type, workflow, related objects, and history can turn different civic processes into a misleading common field.
ISO 37122:2019 defines methodologies for smart-city indicators intended to complement ISO 37120. That city-level measurement framework does not supply a jurisdiction’s permit-cycle definition, platform baseline, implementation method, causal test, or vendor score.
OpenGov documents configurable forms, fees, routing, approvals, inspections, and applicant-facing workflows for permitting and licensing. Those provider-documented capabilities can support a jurisdiction’s process; they do not create legal authority, adopt a code, make findings, approve a plan, issue a permit, or decide an inspection result.
GeoReport v2 standardizes parts of location-based non-emergency intake and status exchange. Its request identifier and status do not establish a verified violation, inspection result, enforcement action, permit condition, or legal finding.
The International Energy Conservation Code supplies model energy-efficiency provisions. A permit system still needs the jurisdiction's adoption, edition, amendments, effective date, project path, required documents, reviewer decisions, and field evidence.
NIST presents the framework as a voluntary enterprise-risk tool, while its site identifies Version 1.1 as an initial public draft. Neither status supplies a municipality's governing disclosure, retention, or records rule.
The Building Permits Survey counts new privately owned housing units authorized in permit-issuing places. It does not measure application intake, review duration, inspections, construction starts, completion, code compliance, or a portal's performance.
The geospatial metadata standard helps preserve identity, extent, quality, lineage, and distribution without making a map legally controlling.
The federal address-data standard separates content, classification, transfer, and quality while recognizing local assignment rules. Permit systems need that provenance because a normalized string does not establish a parcel, structure, jurisdiction, or legal location.
A permit form is not accessible merely because its fields can receive input. WCAG 2.1 requires detected input errors to be identified and described in text, requires labels or instructions for user input, and addresses how component states and status messages reach assistive technology.
The model form ties review to a community's ordinance, effective flood map, proposed development site, and any map-change letter. A GIS result can inform that record, but it does not make the jurisdiction's permitting decision.
The 2026 interim rule extends compliance dates while preserving a direct need to inventory, test, remediate, procure, and govern accessible state and local digital services.
A permitting platform can organize applications, plans, comments, conditions, inspections, and records; the adopted code, local amendments, project facts, and authorized official still govern the decision.
The May 2026 release updates annual place, county, metro, state, and national records while reminding readers that permits authorized are not construction starts or completed homes.
SmartGov joined Granicus in 2024, placing an enhanced permitting product beside AMANDA's enterprise model and a wider digital-government portfolio.
The combined Avolve record includes ProjectDox and DigEplan, so buyers need to compare architecture, integration, document control, workflow, and implementation rather than treat the brand as one interchangeable product.
Acquisitions, integrated plan review, portals, and infrastructure announcements broaden the platform story while increasing the buyer's need to separate product availability from configured agency operations.
Grant-funded work can include process and permitting reform, but land cost, infrastructure, policy, displacement, financing, capacity, and local conditions remain part of the housing-production problem.
The 2026 update to the EPA-administered construction permit record is a reminder that a local land-development permit, state stormwater authorization, federal coverage, and site plan are separate controls.
Discovery, collections, query, coordinate reference, filtering, and feature identity give government buyers concrete tests for parcel and district services.
Accela, Clariti, OpenGov, Citizenserve, and Cloudpermit all publish applicant-guidance or completeness claims, while the required facts, documents, fees, professional judgment, and local rules remain jurisdiction-specific.
The decisive scenario is a resubmission with renamed sheets, partial replacements, conflicting comments, changed calculations, a late outside review, and an issued-set amendment.
PermitFlow, GreenLite, Permit.com, Pulley, Service First, and Milrose all operate on the applicant side; their useful scope ends where jurisdictional interpretation, licensed design, delegated review, and public approval authority begin.
