Permitting Quick Wins That Work in Locked-Down Government IT
Part three of the 2026 Permitting Technology series
Skip right to the EPIC Permitting Quick Wins Guide →
EPIC's Landscape Report documented 300+ permitting tools, with more than 75% carrying API capabilities. The Framework post gave you a way to diagnose which part of your system is broken — which phase, which system type, whether it's even a technology problem at all.
This post is about what happens when the diagnosis points to something fixable and your IT environment says no.
The Abundance Paradox, as described in the Landscape Report, plays out at the enterprise level: all the tools exist, but none of them connect. But most permitting teams live with a smaller, more immediate version of the same problem. The tools that could help you exist. You just can't install them, configure them, or get IT to prioritize them before next fiscal year.
Every conference presentation on permitting modernization assumes you have things you don't. Budget for new software. IT staff who return your calls. Authority to change processes. A technology environment where you can actually install, configure, or build something.
Meanwhile, back at the office, you're submitting help desk tickets that disappear into a queue, working around SharePoint restrictions nobody can explain, and watching modernization initiatives stall because "IT needs to review it first."
This gap between what's recommended and what's possible isn't talked about enough. So let's talk about it.
Three IT Realities
The Framework identified ten system types. Most of them — applicant portals, case management systems, collaboration platforms with permit-specific workflows — require software you almost certainly can't provision on your own. What you can actually use depends less on the diagnostic and more on what your IT environment allows.
Most permitting teams operate in one of three environments, and knowing which one you're in determines what improvements are actually achievable.
Fully Locked Down: You have shared network drives, Microsoft Office desktop apps, Outlook, and not much else. SharePoint site creation requires approval. Power Automate is disabled. Forms might work, might not. Any request to IT takes months and might still come back "no".
Standard M365: You can use SharePoint lists, Teams channels, and basic collaboration features. Forms work. Maybe Planner. But Power Automate is restricted, Power BI requires a license you don't have, and anything that touches external systems is off the table.
Open Modern Stack: You have access to automation tools, can create workflows, build dashboards, and integrate systems. This environment exists, just not in most government agencies.
Most permitting-improvement advice assumes you're in the third category. When you're in the first or second, that advice isn't just unhelpful. It's demoralizing. You know what would work. You just can't do it.
Working Within Constraints
The IT environment you're in isn't just a limitation. It's the actual design brief. Once you work within it rather than against it, different solutions become visible.
In a fully locked-down environment, you can still create a standard folder structure that everyone uses, cutting the time staff spends hunting for documents. You can develop Word templates for common communications (deficiency notices, acknowledgment letters, decision documents) so staff aren't drafting from scratch every time. You can build an Excel tracker that gives you visibility into deadlines and workload. You can write "How Do I" guides for the ten procedures staff ask about most often.
None of this requires IT approval, a budget, or authority beyond your own work and maybe a conversation with your supervisor.
These aren't transformational changes. But they reduce daily friction, protect institutional knowledge, and show that progress is possible, which matters when you're eventually making the case for larger investments.
The Maintenance Trap
There's a reason many improvement efforts fail even when they launch successfully: nobody accounts for maintenance.
That SharePoint site with all your procedures? Without someone curating it, the content goes stale within months. The Excel tracker showing permit status? If updates fall behind, it becomes worse than useless: applicants check it, see outdated information, and lose trust. The document library everyone was excited about? It becomes a dumping ground where nothing is findable.
Before starting any improvement, ask: who will maintain this, and how much time will it take? If the honest answer is "nobody" or "we'll figure it out later," scale back your ambition. A simple system that stays current beats a sophisticated system that decays.
This is especially true in locked-down environments where you can't automate maintenance. If status updates require manual entry into a spreadsheet, someone has to enter them every day or week. If that someone is already at capacity, the system will fail.
What You Can Do Without Authority
Maybe you're not in a position to change processes at all. You're a permit reviewer who sees problems clearly but reports to someone who won't prioritize improvement. You have no authority over systems, standards, or procedures.
You can still make a difference. Use consistent file names in your own work, even if others don't. Create personal templates for communications you send repeatedly. Track the time you spend on inefficient processes — specific numbers like "I spent four hours last week searching for documents" make the case for change better than general complaints.
Propose small experiments: "Can I try this approach on my next three projects?" Small pilots are easier to approve than system-wide changes. Find allies who share your frustrations. One person asking for improvement is easy to dismiss; a small group asking the same thing gets attention.
And document the problems you see. When leadership eventually decides to invest in improvement, that documentation becomes the roadmap.
A Resource Built for Reality
The Framework post noted that state agency teams tend to control more of their own stack than federal teams do — the same diagnosis that surfaces a fight at a federal agency surfaces a to-do list at a state agency. This guide is built for that to-do list, specifically the version you can execute in a locked-down IT environment.
We developed the EPIC Permitting Quick Wins Guide for teams operating under these constraints. It catalogs seven tactical improvements organized in two tiers:
Foundation Quick Wins (do these first):
Internal Knowledge & Documents
Communication Templates
Pain-Point Quick Wins (pick based on your situation):
Applicant Experience & Guidance
Self-Service Status Tracking
Deadline & Workflow Visibility
Comment & Response Efficiency
Performance Visibility
Each quick win includes a Starter Option designed for fully locked-down environments and a Growth Option for teams with more flexibility.
The guide is honest about prerequisites, maintenance requirements, and what success looks like. It includes a section on agile improvements for people without authority. It's organized around a sequencing principle: some improvements (organizing internal knowledge, standardizing communications) create the conditions that make other improvements stick, so do those first.
It won't close the gap between permitting modernization ambitions and what government IT actually supports. But it offers a path forward that works within those realities rather than pretending they don't exist.
