Automating After-the-Fact Permits with GIS Workflows

Automating After-the-Fact Permits

After-the-fact (ATF) permits are filed when utility work was performed without prior right-of-way approval. They are administratively intensive — requiring spatial exhibits, legal descriptions, and county-specific documentation — and historically done by hand.

The Problem

A single ATF permit package for a Florida county typically involves:

1. Extracting the work area from ArcGIS Pro
2. Generating a scaled exhibit with parcel and ROW overlays
3. Calculating linear footage within each ROW
4. Writing the legal description for each parcel crossing
5. Populating the county's PDF form
6. Assembling the final package for submission

Done manually, this takes 45–90 minutes per permit. With a backlog of hundreds of permits, the math gets painful fast.

The Automated Approach

Using Python and the ArcGIS API for Python (arcpy), the workflow can be reduced to under 10 minutes:

import arcpy
from arcpy import env

# Clip work area to ROW boundaries
arcpy.analysis.Clip(work_area, row_layer, clipped_output)

# Calculate linear footage by parcel
arcpy.analysis.SummarizeWithin(parcel_layer, clipped_output, summary_table)

# Generate exhibit layout
aprx = arcpy.mp.ArcGISProject("permit_template.aprx")
# ... layout automation

FDOT Permit Integration

For FDOT right-of-way permits, the workflow connects directly to the FDOT permit portal API to retrieve permit numbers and pre-populate submission fields.

Results

GIS teams that have implemented this automation report:

• 62% reduction in per-permit processing time
• Near-zero spatial errors in exhibit generation
• Faster county approval due to consistent, standardized packages

Getting Started

The first step is identifying which permit types represent your highest volume. Start with those, build the automation, and expand from there. The ROI compounds quickly.