Four to eight hours per site
Downloading, naming, searching, copying, and reconciling a single site file commonly consumes half a day before design starts.
STA 0+00 · Why this exists
A permit search finds documents. An engineer still has to build the design basis.
Today
The hard part
The numbers are conditional
A discharge value is meaningless without its permit sequence, node, storm, scenario, datum, and source page.
The stakes
Search results do not tell you what to do
The paid value is the synthesis: what the record establishes, which values are historical benchmarks, where documents conflict, and what must be confirmed before design.
STA 2+50 · How it works
Boundary in. Engineering kickoff brief out.
-
Scope
Map the district record set and price the file
Intersection is used for discovery, never as proof of parcel applicability.
-
Build
Resolve permit lineage and build the source index
Each permit action is tied to its permits, staff reports, calculations, plans, RAIs, as-builts, and completion records.
-
Reconcile
Normalize the numbers and test the record
Storm, scenario, node, datum, asset, sequence, and source stay attached to each value.
-
Deliver
State the conclusions and required confirmations
Recorded baselines, calculated relationships, conflicts, and open conditions — each tied to evidence.
STA 5+00 · The deliverable
A design-basis brief, not a search-results binder.
A concise engineering brief answers the kickoff questions. Its permit-lineage table, indexed source register, and cited record remain behind every conclusion.
01 · Design criteria
Storms, rates, stages, treatment, recovery, groundwater
Record values are normalized by scenario, cited to source pages, and paired with engineering interpretation.
02 · Permit lineage
Permit actions, supporting documents, dates, and page-level evidence
Each action gets a stable source group; each cited document gets a source ID that follows its values through the brief.
03 · Existing system
Ponds, controls, conveyance, outfalls, downstream assumptions
A field-verification checklist for the infrastructure the new design must find, protect, or replace.
04 · Judgment
Record-supported conclusions and required confirmations
Each open item states why it matters and how an engineer can resolve it.
Alongside the brief: a normalized workbook/CSV, supporting record, permit-lineage table, and indexed source register.
STA 7+50 · How the reading happens
AI does the file work. Evidence and review make the call.
AI-assisted extraction and reconciliation reduce the file work. The deliverable is an evidence-backed engineering briefing, not a list of search results.
Extract
Turn pages into structured facts
Every value keeps its permit sequence, document, page, and engineering context.
Reconcile
Compare the record across documents
Criteria, results, elevations, and system details are checked together, with conflicts kept visible.
Assess
State what the record supports
The brief separates documented baselines from present-day conditions that still require confirmation.
The public sample uses real district records. Every reported value is cited, and every derived value is identified as a calculation.
Scope the record set. Buy the engineering answer.
Scope a site
STA 10+00 · Start
Start design with the permit record already reconciled.
Draw or upload a boundary. See the intersecting district records and a firm price. Free, no account, no meeting.
Scope a siteAlready researched the site by hand? Send it. A side-by-side time and finding check is the best product test.