How it works
A structured pilot. Fixed fee. Phase-gated. Value visible in 60 days.
Every PermitPro engagement follows the same five-phase model. You control every gate. Nothing moves forward without your written sign-off. No surprises. No scope creep. No runaway invoices.
Watch the workflow
A permit drafted end to end, narrated.
The four-stage workflow
Four stages, any permit type
Stage 01
Intake and Document Classification
For directors and bureau chiefs
Every application, attachment, and supporting document is ingested and classified automatically. Completeness is checked against your jurisdiction's requirements. Deficiency notices are generated and ready for staff signature in minutes, not hours. Your reviewers spend their time on regulatory judgment, not document hunting.
For CTOs and IT
PermitPro ingests structured and unstructured documents via secure upload or API. Classification models are configured to your permit type and jurisdiction during Phase 4. No changes to your existing document management infrastructure are required.
Stage 02
Applicability and Eligibility Analysis
For directors and bureau chiefs
Regulatory logic cross-references applicant data against applicable thresholds, standards, and permit pathways. Flags are surfaced to your staff for review. No determination is finalized without human approval. PermitPro presents options; your staff decides.
For CTOs and IT
Applicability logic is encoded as configurable rule sets mapped to your regulatory framework during scoping. Rules are version-controlled and auditable. All logic is reviewable by your team at any time.
Stage 03
AI-Drafted Permit Generation
For directors and bureau chiefs
This is the capability that has never existed before, anywhere in the country. A complete, regulation-compliant permit draft: all conditions populated, all limits extracted, all citations included. Your staff reviews, applies professional judgment, and approves. The drafting burden is eliminated. The regulatory authority stays exactly where it belongs, with your team.
For CTOs and IT
Permit drafts are generated via configured workflow agents operating on validated data inputs. All outputs are logged, versioned, and traceable. Draft generation logic is jurisdiction-specific and does not cross-apply between permit types or regulatory programs without explicit configuration.
Stage 04
QA Review and Sign-Off
For directors and bureau chiefs
Structured review journeys with configurable checkpoints. Every output is traceable, auditable, and defensible. Every decision is logged. When a permit is challenged, you have a complete record of every step.
For CTOs and IT
Review journeys are configurable workflow sequences with role-based access controls. Audit logs are retained for a minimum of 12 months. All sign-off events are timestamped and attributed to named users.
Example workflow: permit drafting
See it in action: minor wastewater permit renewal
The following is a representative workflow based on the South Carolina Department of Environmental Services (SCDES) production deployment.
Without PermitPro
Estimated staff time: 90 to 100 hours
| Step | Who does it | Time |
|---|---|---|
| Locate and retrieve prior permit from file system | Permit writer | 30 to 60 min |
| Locate and retrieve application and supporting documents | Permit writer | 60 to 90 min |
| Review application for completeness against checklist | Permit writer | 2 to 3 hours |
| Draft deficiency notice if incomplete | Permit writer | 1 to 2 hours |
| Extract applicable effluent limits from regulatory tables | Permit writer | 8 to 12 hours |
| Cross-reference limits against historical permit conditions | Permit writer | 4 to 6 hours |
| Draft permit shell and populate all conditions | Permit writer | 15 to 25 hours |
| Internal QA review and revision | Senior reviewer | 4 to 8 hours |
| Format, finalize, and route for signature | Permit writer | 2 to 4 hours |
| Total | 37 to 62 hours per permit |
With PermitPro
Estimated staff time: 20 to 30 minutes
| Step | Who does it | Time |
|---|---|---|
| Application submitted via ePermitting portal | Applicant | — |
| PermitPro ingests and classifies all documents | Platform | Seconds |
| Completeness check run against jurisdiction rules | Platform | Under 2 min |
| Deficiency notice drafted and queued for staff review | Platform | Under 2 min |
| Applicable limits extracted from regulatory database | Platform | Under 5 min |
| Full permit draft generated with all conditions populated | Platform | 10 to 15 min |
| Staff reviews draft, applies professional judgment, approves | Permit writer | 15 to 20 min |
| Permit routed for signature | Platform | Seconds |
| Total staff-engaged time | 20 to 30 minutes |
The regulatory judgment didn't change. The manual burden was eliminated.
The five-phase pilot
The five-phase engagement model
| Phase | Name | Duration | Gate |
|---|---|---|---|
| 1 | Software Setup and Licensing | ~5 days | Written acceptance sign-off |
| 2 | Pilot Scope Validation | ~10 days | Signed Scope Validation Memo |
| 3 | Data Ingestion and Alignment | ~15 days | Model readiness confirmation |
| 4 | Agent and Workflow Configuration | ~40 days | Internal QA sign-off |
| 5 | Testing, UAT, and Acceptance | ~15 days | Pilot acceptance sign-off |
Every phase is a fixed fee. Total pilot timeline: approximately 85 business days from notice to proceed.
Phase 1: Software Setup and Licensing
For directors and bureau chiefs
We provision your dedicated PermitPro environment, configure user access, and validate system connectivity. You provide written acceptance before Phase 2 begins. Nothing moves forward without it.
For CTOs and IT
AWS us-east-1 / us-east-2 environment provisioned. SAML 2.0 / ADFS federation configured for single sign-on with your existing identity provider. No new credentials required for end users.
Phase 2: Pilot Scope Validation
For directors and bureau chiefs
We facilitate a structured scoping workshop with your program staff. Together, we select 1 to 3 pilot use cases, map your current workflows, and produce a signed Scope Validation Memo: a written agreement on exactly what PermitPro will do, for which permits, with which data, and what the outputs will look like. Nothing in Phase 4 is built that isn't in this memo.
For CTOs and IT
Use cases locked and documented. Data schema requirements defined. Integration touchpoints identified. No configuration begins until scope is signed.
Phase 3: Data Ingestion and Alignment
For directors and bureau chiefs
We conduct a Data Readiness Assessment, catalog your data sources, and assess quality against defined thresholds. One structured remediation cycle is included. Your data is ingested and model readiness is confirmed before configuration begins.
For CTOs and IT
Data Readiness Assessment conducted against five thresholds: completeness (80% or more of fields populated), legibility (machine-readable), currency (active permit term), consistency (uniform units), attribution (traceable to source facility and date). One remediation cycle included. Additional cycles are time and materials with your approval.
Phase 4: Agent and Workflow Configuration
For directors and bureau chiefs
Our engineers configure PermitPro's regulatory logic engine for your specific regulatory framework. Workflow journeys are built, tested internally, and validated before your staff ever touches the system.
For CTOs and IT
Agent configuration is isolated to validated use cases and jurisdictions. No cross-program logic is applied without explicit authorization. All configuration is documented and version-controlled.
Phase 5: Testing, UAT, and Acceptance
For directors and bureau chiefs
We deliver a user acceptance testing (UAT) environment and structured test scripts. All feedback is triaged: bug (remediated at no cost within the pilot), enhancement (deferred to future task order), or out of scope (logged and deferred). You provide written acceptance sign-off.
For CTOs and IT
UAT capped at 15 business days. Bug triage is structured and documented. No enhancements are absorbed into the pilot fee without a signed change order.