An OpenCounter cost estimate is not a jurisdictional fee assessment

Give estimate a defined project scope

OpenCounter's official record says its portals let applicants explore project feasibility, permit requirements, and costs before applying. That can improve early planning, but the result depends on the facts the portal collected and the rules configured at that time. Record property or parcel, jurisdiction, project type, use, size, units, construction value, work categories, applicant selections, existing conditions, date, portal version, and any facts the tool did not ask.

Estimated, assessed, invoiced, paid, credited, refunded, and final are different states. A user may change scope after the estimate. Staff may identify another review, permit, impact, utility, inspection, outside-agency, or professional charge. Adopted schedules may change, and a jurisdiction may have thresholds, minimums, caps, deposits, valuation tables, waivers, credits, or project-specific agreements that need authorized review.

Trace every amount to adopted authority

For each displayed amount, preserve the charge name, department or collecting entity, governing schedule or other authorized source, edition and effective date, unit, rate, quantity, valuation basis, minimum or maximum, multiplier, rounding, deposit status, tax or surcharge treatment where applicable, formula, assumption, and explanatory text shown to the user. Keep the portal rule separate from the adopted authority it represents.

Unknown should not silently become zero. If the portal cannot determine a charge, mark it excluded, conditional, pending, outside scope, or subject to review and explain what evidence can resolve it. A total without its components can create false precision, especially when several departments or external entities own different fees. Preserve the calculation trace and source date so staff can explain or correct it.

Reconcile estimate to the application record

When an application begins, link the estimate identifier and version to the submitted project scope without copying its conclusions forward. Record changes in parcel, use, valuation, area, units, work type, required permits, review path, effective fee schedule, waiver or credit request, and responsible staff. The official assessment should name its authority, reviewer, calculation date, charge population, adjustment, appeal or correction path, and relationship to the invoice.

Test incomplete inputs, boundary parcels, mixed uses, phased work, duplicate permits, changed valuation, future effective dates, waived or credited charges, a fee owned by another agency, staff correction, portal rule update, canceled application, resubmission, payment reversal, and refund. The public record should communicate what the estimate can and cannot answer without promising approval or a final price.

Keep OpenCounter inside its documented boundary

The registered OpenCounter source establishes current public positioning for pre-application guidance about project location, permits, process, and expected cost through applicant portals and jurisdiction integrations. It does not establish zoning or code compliance, complete permit scope, adopted fee authority, configured accuracy, staff determination, official assessment, invoice, payment, approval, issuance, or project outcome.

Civic Permit Review reviewed the official record on August 26, 2026 and did not operate OpenCounter. Jurisdictions should demonstrate one representative project from public inputs through rules and fee sources, estimate, saved version, application handoff, staff scope correction, assessment, waiver or credit, invoice, payment, receipt, amendment, refund, retention, and accessible explanation. Authorized planning, permitting, finance, legal, technology, records, and accessibility owners retain their decisions.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Civic Permit Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.