PermitScope Book a walkthrough
Working with civil engineering firms across South Carolina

Turn a project folder into cited permits, schedules and proposals.

PermitScope reads the files an engineering firm already keeps, where they already live, and builds the project's permitting record: every permit the work triggers, the schedule those permits set, and the proposal to deliver it. Each value points back to the file and page it came from.

Book a walkthrough Sign in
Fig. 1How a project moves through PermitScopeSheet 1 of 1

The language model reads the documents. Written rules decide what applies, and every output cites its source.

42requirements screened on one project, each with its rule and citation
60design commitments carried from its permits into the plans
10owner documents, each with who signs it
7deliverables from the same run, in Word, Excel and CSV
51.5 GBreal project folder of 5,950 files, inventoried in 0.7 s
0.8%of that folder's bytes read to find the permit material
The first four are one run of the fictional example sewer project. The last two were measured on a design partner's real project folder.

Engineering firms already have the answers, spread across the project folder.

The proposal, the fee workbook, permit applications, comment letters and meeting minutes all sit in the folder. Turning them into a current picture of the project still means someone re-typing them. On one design partner's project, that cost looked like this.

48 GB

in one reference project's folder, with the project's identity typed again into separate files across it

Rev. 51

of one project's weekly status report in Word, with the permitting section rewritten by hand each time

3 of 4

in-house Excel and VBA tools built to automate this work that stalled

One record of the project, and the work built from it

Permitting comes first because it sets the schedule and the fee. Each piece reads from the same cited record, so the proposal, the register and the deliverables never disagree.

Permitting matrix

Every permit, consultation and design requirement the project triggers, with its rule, agency, fee and citation.

42 requirements · 60 commitments on one project

Proposal and workplan

The permitting tasks, hours and fee for the proposal, drafted from the matrix in your firm's rates and wording.

tasks · hours · fee

Schedule and watch

Lead times turned into a timeline, and the Federal Register and Corps notices that touch the project, ranked by relevance.

lead time · basis · sequence

Register and portfolio

Every permit on the project with its status and next submittal, and one view of what is due across all of a firm's projects.

status · next submittal · overdue

Plan review

A submitted stormwater plan checked against the agency's own checklist, with the page that answers each item.

item · answer · page

Deliverables

The PER permit section, the owner's signature packet, the commitments register, the permit tracker and the folder plan.

7 documents in Word, Excel and CSV

Built to run where the files are

Firms have good reasons to be careful with AI on project work. PermitScope was designed around those concerns from the start.

0.7 s

to inventory every file in it: a 51.5 GB real project folder, 5,950 files

0.8%

of its bytes read to find the permit material

Measured on a real project folder.
  • Raw files never have to leave your network.A local agent reads the folder in place, on the firm's own machines.
  • Only the pages that matter are read.Each workflow knows which facts it needs and which documents usually hold them, and reads only those pages and lines.
  • A ledger of every read.What was read, and what was sent to which model, is recorded for each project and can be exported.
  • Local models.Reading runs on pinned, permissively licensed models, and each project shows how many tokens went to a hosted service.

Every value can be checked

A requirement is only useful if an engineer can verify it in a minute. Here is one line from a fictional example project, opened up. The engine runs end to end on 13 example projects across 11 counties and 7 funding programs.

NPDES Construction General Permit SCR100000

Greenville County (delegated plan review), then SCDES Bureau of Water

● Required
Why
1The scope states 14.2 acres of land disturbance. The threshold is 1 acre.
Order
2Plan review goes to Greenville County first. SCDES will not issue coverage until the county approves.
Lead time
310 to 28 days, as published by SCDES
Source
4SCDES CGP SCR100000 (2026) · effective 2026-03-30 · retrieved 2026-09-12
Design
7 design commitments, including a 30-ft undisturbed buffer to waters of the U.S. during construction
  1. 1The trigger is quoted from the document, in the units it was written in.
  2. 2Sequence is stated when one approval has to come before another.
  3. 3Lead times name their basis: a regulation, an agency timeline or a practitioner estimate.
  4. 4Citations are dated, and a stale one is flagged.

Who it's for

Civil and site engineering firms, starting with water, wastewater and site development. It is built for the engineer of record, not for the owner or the agency.

  • Project managersA current permit register and the permitting part of the proposal, without rebuilding them from memory.
  • Project engineersEvery requirement with its rule and the sentence that triggered it, and the design commitments to carry into the plans.
  • Drafters and co-opsThe owner's signature packet, with who signs each document and the agency form it goes with.
  • PrincipalsOne view of what is overdue and what is waiting, across every project.
  • Firm ITFiles that stay in place, and a record of what was read and where it went.

It produces the documents firms already deliver

Every export comes from the same run, so the PER section, the owner's packet and the tracker agree with each other.

  • MDFull screening report
  • MDDOCXPER permit subsection
  • CSVXLSXCommitments register
  • DOCXOwner documents packet
  • XLSXPermit tracker
  • XLSXPermitting fee proposal
  • ZIPPermit folder plan

Questions

Anything else, write to hello@permitscopehq.com.

What does it read?

Scopes of work, preliminary engineering reports and project summary spreadsheets today, and the project folder itself through the local agent. PDF and Word are read directly; a summary spreadsheet is read without a language model.

Where does our data go?

Raw project files never have to leave your network. The local agent reads them in place, and every read is logged with what was sent to which model.

Does it make determinations?

No. It is screening for the engineer in responsible charge. A jurisdictional determination still comes from the Corps, and the matrix tells you which ones to request.

Which states does it cover?

South Carolina in depth, down to county and municipal ordinances, with the federal programs as they apply there.

Can we try it on our own project?

Yes. We will set up a walkthrough on a project like yours. A past project or one of our fictional examples works too if you would rather not share a live one.

We're onboarding a small group of engineering firms this year.

Tell us about your permitting workload and we will set up a walkthrough on a project like yours.

Book a walkthrough Sign in

or write to hello@permitscopehq.com