For developers, permitting delay is usually experienced in one way: time. The project takes too long, the agency is difficult to read, comments come back in rounds, new issues appear after earlier issues were supposedly addressed, and the process rarely feels linear. From that vantage point, it is easy to conclude that the agency is slow, disorganized, or simply unwilling to move at the pace the moment requires.
That frustration is understandable. In many cases, it is earned.
But if the objective is to understand why projects on federal land take so long to adjudicate, that explanation is not sufficient. It treats delay as a matter of attitude or effort, when in many cases the deeper problem is structural—something we’ve examined in more detail in our analysis of why permitting on federal land is structurally complex. The burden on agencies is not just workload. It is the combination of fragmented authorities, incomplete internal tooling, uneven technical capacity, and a review model that tends to identify conflict only after a project is already in motion.
This matters for two reasons. First, developers who do not understand the agency’s operating conditions will continue to misread what is happening inside review. Second, agency leadership that is serious about improving permitting cannot limit itself to minor process adjustments if the underlying operating model is the real constraint.
The federal permitting conversation increasingly recognizes this broader point. The Permitting Institute has consistently emphasized that federal permitting is not a single coordinated system, but a set of overlapping requirements that must be interpreted and applied together. That framing is important because it shifts the discussion away from blaming individual offices and toward understanding how the system itself produces delay.
A developer often approaches permitting as if the agency is applying a known checklist to a proposed use. That is rarely how it actually works on federal land.
In practice, the agency is operating within a layered body of management direction that has accumulated over decades. Resource Management Plans establish land use allocations and management decisions. Manuals and handbooks govern internal interpretation and procedure. Instruction Memorandums can change practice or provide interim direction. Federal statutes and regulations continue to apply across the whole structure. Project-specific stipulations, prior decisions, withdrawals, valid existing rights, species constraints, mineral issues, and local land status conditions may all affect how a parcel can be used and what conditions would attach to any authorization.
Multiple agencies may be involved in permitting decisions, and coordination among them can be challenging.
— U.S. Government Accountability Office
The core difficulty is not merely that there are many sources of direction. The difficulty is that they are not organized in a way that makes them directly usable at the parcel level, resulting in overlapping layers of direction that interact in ways that are not always visible upfront, as discussed in our breakdown of how regulatory layers create complexity. A specialist is not reading one source and moving forward. They are often reconstructing the applicable rule environment from multiple documents, issued across different periods, housed in different places, written for different purposes, and not translated into a unified decision-support structure. That is one reason the national permitting conversation keeps returning to fragmentation. The Permitting Institute has framed the problem as a system made up of overlapping statutory and regulatory requirements rather than a single coherent machine.
That framing becomes even more important when you drop from Washington-level policy debate into field-level adjudication. At the field office, “fragmentation” is not a talking point. It is daily operating reality. The question is not simply whether a rule exists. The question is whether the reviewer knows it applies here, can find the relevant direction quickly, can determine whether it has been superseded or modified, and can reconcile it with other land status conditions affecting the same project area. That work is analytical. It is interpretive. And too much of it is still manual.
A second problem is that a great deal of permitting capacity sits in people rather than in systems.
There is a tendency, especially from outside government, to assume that if the rules are written down then the process should be straightforward. But anyone who has worked in land use knows that written direction is only part of the picture. The actual work depends heavily on judgment: what needs to be elevated, which conflict matters most at this stage, how a certain office has historically handled a recurring issue, what supporting information will likely be needed before another discipline can move, and what the agency is really trying to resolve when it asks for additional material.
That kind of knowledge used to be built through longer apprenticeship structures. Senior specialists passed down not just formal instruction, but operating context. They helped newer staff learn how to navigate the difference between what a document says in theory and how a field office must apply it in practice.
When that bench thins out, the problem is not simply that offices have fewer people. The problem is that the agency loses interpretive continuity. Newer specialists are left to work through a body of direction that assumes more internal context than they may yet have. That is especially difficult in an environment where training is uneven, GIS capability is inconsistent, and teams may be composed largely of people with only a few years in role. This is not a hypothetical workforce issue. Across the federal permitting system, staffing and project-management capability continue to be identified as real constraints. The Permitting Council’s FY 2023 and FY 2024 performance reports explicitly list staffing, limited project-management skillsets, and the challenge of integrating improved practices into existing agency processes as ongoing barriers.
That matters because permitting is not only legal review. It is applied land analysis under institutional constraints. If experienced personnel leave faster than practical knowledge is being codified, the system becomes more dependent on whoever still knows how to navigate it. Over time, that makes outcomes slower, less predictable, and more variable across offices and reviewers.
This is where many external critiques of agencies miss the mark. They see case-tracking systems, dashboards, and internal databases and assume the government has digital infrastructure for permitting. In reality, much of that infrastructure is administrative rather than analytical.
There is a major difference between a system that tells you where an application sits and a system that helps identify all of the constraints bearing on that application. The first is workflow visibility. The second is actual adjudicative support. Agencies have more of the former than the latter.
That distinction is increasingly visible even in federal permitting reform efforts. The Permitting Council’s recent reports stress transparency, dashboards, recommended best practices, training, coordinated project planning, and project-management support. At the same time, those same reports acknowledge ongoing problems with project-management skillsets, policy change, and the limited integration of adaptive management into agency processes. In other words, even reform efforts are still grappling with the gap between process oversight and the deeper analytical burden inside review.
For land agencies, that burden is intensely spatial. A project is not just a form package. It is a footprint intersecting management decisions, environmental sensitivities, preexisting rights, access realities, tenure conditions, and operational constraints. If the internal toolset does not surface those interactions early and coherently, the burden falls back on staff to assemble the picture manually. That slows everything down, but more importantly it means the system keeps discovering its own problems in sequence instead of exposing them early.
Developers often ask a reasonable question: if the agency knows what it needs to evaluate, why can’t those issues be resolved upfront?
Part of the answer is that federal permitting is not organized around a single front-loaded determination. It is organized around discipline-based review. Realty, planning, NEPA, biology, cultural resources, minerals, engineering, and other functions each examine the project through their own authorities and concerns. Some coordination occurs, of course, but the process still tends to move by discipline and by stage rather than by one consolidated, simultaneous evaluation at the beginning.
That distinction matters. A sequential review structure does not merely take time. It produces a certain kind of time. It produces a timeline in which issues are often discovered after prior work has already been done. A route can appear workable at one stage and then become more complicated once another discipline identifies a conflict. A revision made to address one issue can create new questions elsewhere. The process becomes iterative because the structure invites iterative discovery—a pattern where risk is surfaced progressively rather than upfront, which we explored in why permitting on federal land is structurally complex.
That does not mean every office is doing something wrong. It means the design of review itself creates rework. CEQ’s own citizen guidance has long emphasized that NEPA is meant to support informed decision-making, not paperwork for its own sake. But in practice, informed decision-making is only as efficient as the system’s ability to assemble relevant information early enough for it to shape project design before multiple downstream reviews are already underway.
This is also why “faster permitting” can be a misleading slogan. If the same process continues to identify constraints late, then compressing deadlines will not remove the source of friction. It may simply increase pressure on staff who are already dealing with fragmented guidance, limited analytical tooling, and uneven internal capacity.
The current permitting structure developed over time in an environment where information was not easily aggregated or analyzed in a single place. Land use plans existed as documents. Constraints were interpreted by individuals. Coordination across disciplines happened through routing and review, not through shared, real-time analysis.
Under those conditions, a sequential process was a practical approach. Each discipline reviewed the project when it reached them, based on the information available at that stage. If new issues were identified, the project was revised and moved forward again. The process assumed that information would be discovered as review progressed, because there was no reliable way to assemble all relevant constraints at the outset.
That assumption is still embedded in how permitting is structured today.
What has changed is the technical environment around it. It is now possible to evaluate multiple layers of land use, policy, and constraint at the same time. Spatial data can be linked directly to planning decisions. Conflicts between designations, resource considerations, and existing rights can be identified early, before a project moves into formal review.
The permitting process has not been restructured to consistently use those capabilities. It still operates as if constraint identification must occur through staged review, even in cases where the underlying information could be assembled earlier.
This creates a mismatch. The system continues to discover issues over time, not because that is the only way to do it, but because that is how it was originally designed to function.
The time required to complete NEPA reviews can vary widely depending on project complexity and the level of analysis required.
— Congressional Research Service
Another reason this problem is getting worse is that developers have modernized faster than agencies have.
Private-sector project teams now expect spatial intelligence early. They use geospatial tools, environmental datasets, modeling software, and internal screening workflows to evaluate opportunities before significant capital is deployed. That does not mean they know every federal constraint. It means they increasingly expect that serious project issues should be identifiable upstream.
Agencies, by contrast, are often still operating with a model that assumes many of those issues will be resolved during adjudication. That mismatch creates tension. Developers think they are bringing a serious project into a system that should be able to tell them quickly whether it works. Agencies are receiving projects into a review structure that may still need to discover the full set of implications over time.
The result is not just delay. It is misalignment. Developers interpret iterative review as avoidable agency inefficiency. Agencies experience the same iterative review as the natural consequence of how public-land authorization actually works under current conditions. Neither side is fully wrong, but they are operating with different assumptions about when clarity should exist.
The federal permitting debate reflects this gap. The Permitting Institute has repeatedly argued that predictability and transparency matter to developers and financiers, especially when projects move through multi-year approval cycles. That point is important for this post because it helps explain why frustration is intensifying. The market is demanding earlier certainty, while the public-land permitting structure still tends to generate certainty gradually.
If the system is producing delay because it identifies constraints late, then improving performance within that system will have limited impact. The more meaningful change is to move constraint identification earlier in the lifecycle.
Early coordination among agencies can help identify and resolve issues sooner in the process.
— Council on Environmental Quality
It means shifting from a model where issues are discovered during review to one where they are understood before an application is submitted, addressing the same late-stage risk patterns described in our analysis of structural permitting complexity. It means starting with the project area and identifying the relevant management context upfront. What decisions apply to the land, what constraints exist, how those constraints interact, and what implications they have for project design.
Doing this requires more than better coordination. It requires structuring information that currently exists in documents and institutional knowledge into a form that can be applied consistently and early. Without that, the system will continue to rely on manual reconstruction during adjudication.
The conclusion here is not that agencies need to work faster or that developers need to be more patient. The conclusion is that a significant portion of the burden currently carried by agencies is the result of when and how information becomes usable.
Right now, much of the critical information that determines how a project will be evaluated exists, but it is not structured in a way that makes it accessible at the point where it would have the most impact. It is distributed across plans, manuals, maps, and individual experience. As a result, agencies spend a significant amount of time reconstructing that information during review, and developers encounter it incrementally through revisions.
Landica is focused on that specific problem. The objective is not to replace agency processes or reduce the rigor of review. It is to change the starting point of that review by making the relevant constraints visible and usable earlier.
If land use plans, policies, and constraints can be structured, linked to specific geographies, and surfaced at the time a project is being defined, then both sides of the process begin from a more complete understanding. Developers can design with those constraints in mind before submission. Agencies can evaluate applications without having to rediscover the same issues project after project.
That does not eliminate complexity. It changes how that complexity is managed.
Instead of being resolved through multiple rounds of discovery, it can be addressed earlier, with fewer revisions and clearer expectations.
That is where the opportunity is. Not in making the current system marginally faster, but in reducing the amount of avoidable work that the system is currently required to perform.
