The problem is validated, the ecosystem is forming, and context must now become action.
We arrived at the Permitting Innovators Expo with a clear view of the problem we wanted to solve: permitting decisions take too long because the information needed to make them is fragmented across datasets, documents, systems, and people. Critical requirements are often discovered one discipline at a time, after an application is already moving through review.
We left with that diagnosis validated, but also sharpened.
Across presentations, demonstrations, and conversations with agency staff, consultants, technologists, and other solution providers, a common direction was emerging. Permitting teams need to identify project constraints earlier. They need information from disconnected sources brought together. They need greater visibility across reviews, clearer accountability, and a defensible record of how decisions were made.
That convergence matters. It means the problem is no longer being debated at the margins. An ecosystem is beginning to form around it.
It also raises the bar. Bringing project context forward is necessary, but it is not enough. The next challenge is turning that context into the actions agencies must take to reach a decision.
The problem is not simply a lack of data
Federal agencies already possess enormous amounts of information. The difficulty is that the information needed for a particular decision may be distributed across enterprise systems, local files, geospatial layers, land use plans, policy documents, prior authorizations, institutional knowledge, and multiple resource programs.
At intake, staff may not yet have a complete view of the project. They assemble it over time through searches, referrals, meetings, specialist review, and manual comparison. As that context develops, new conflicts, affected parties, studies, consultations, and procedural requirements emerge.
This creates what we think of as a sequence problem.
The issue is not always that an agency lacks the relevant information. The issue is that the information is not assembled, interpreted, and made usable at the moment it can do the most good. A requirement discovered late may have existed from the beginning. It only became visible after the process had already advanced.
That distinction is important. If permitting reform focuses only on shortening deadlines without improving how agency staff reach decisions, it risks placing tighter clocks on the same fragmented process. Faster permitting requires more than asking people to work faster. It requires giving them better decision infrastructure.
The strongest ideas at the Expo reflected this reality. Again and again, presenters focused on earlier screening, connected records, agency-controlled data, automated review, cross-team visibility, and traceability. The vocabulary varied, but the underlying diagnosis was remarkably consistent: too much relevant context arrives too late, and too much staff time is spent assembling it manually.
An ecosystem is forming
The Expo also made clear that no single product category will modernize permitting on its own.
Some solutions focused on application preparation and completeness. Others emphasized geospatial screening, environmental constraints, document review, case management, interagency coordination, public engagement, scheduling, compliance, or artificial intelligence. Large platforms offered broad workflow environments. Specialized teams went deep on individual parts of the process.
Taken together, these capabilities began to resemble the components of a future permitting ecosystem.
That may be more realistic than waiting for one system to replace every tool used by every agency. Federal permitting spans different statutes, missions, programs, geographies, data environments, and decision processes. Even offices within the same agency can have different operational needs. A universal platform may provide a common foundation, but meaningful automation still depends on understanding the work performed by a particular agency and the rules governing a particular decision.
The more practical path is likely to combine common standards with specialized capabilities that can work together. Existing systems of record will remain important. New tools should be able to exchange structured information, preserve provenance, and pass work from one system or participant to another without forcing staff to reconstruct the project each time.
We came away thinking less about a single monolithic platform and more about a coral reef: shared infrastructure that supports an ecosystem of agency systems, data providers, scientific tools, workflow applications, and emerging AI agents. The value of that infrastructure will depend not on how many shallow integrations it accumulates, but on whether it preserves the context and evidence required to coordinate real decisions.
Interoperability, in that sense, is not merely a technical feature. It is part of the operating model for modern permitting.
Earlier context is becoming the starting point
For Landica, one of the most useful lessons was also one of the most challenging.
Our core thesis has been that relevant land, resource, legal, and procedural context should be assembled when a project enters review, not months or years later. Automated geospatial screening can identify intersecting land statuses, existing rights, resource concerns, management direction, and potential requirements before the traditional sequence of review has fully unfolded.
The Expo strongly validated that direction. It also showed that we are not alone in pursuing it.
Earlier context is becoming a category expectation. Public data will become easier to access. Geospatial analysis will become more available. AI will make it easier to search regulations, plans, and project records. A map of intersecting layers, even a sophisticated one, will not by itself transform an agency process.
That does not make project screening less important. It makes it foundational.
The harder question begins after a system finds something.
What does the intersection mean for this project? Which management direction or authority controls? Is the result informational, a potential conflict, or a mandatory requirement? Who must review it? What communication, consultation, study, or notice must be initiated? Who owns the next step? What happens if a notice is returned, a response is disputed, or the underlying data is incomplete? How is the action documented, and can a later reviewer reproduce why it occurred?
Until those questions are answered, context has not yet become operational.
Context must become action
A permitting system should not stop at telling staff that something may matter. It should help them determine what must happen next.
That requires a connected progression:
Authoritative agency data becomes project-specific intelligence. Project intelligence triggers required action. Required action enters a coordinated workflow. The workflow produces a traceable record.
Consider a proposed right-of-way that overlaps or sits near existing authorizations. Identifying those rights is only the first step. Staff may still need to determine which holders are affected, verify contact information, prepare notices, route them for review, issue and track delivery, manage returned mail, record responses, address objections, and preserve the complete history in the case record.
A screening report can tell the reviewer where to look. A functioning decision system helps complete the work.
This is where agency knowledge becomes essential. The required action is not encoded in geometry alone. It comes from the relationship among data, law, policy, land use plans, program procedures, local practice, and human judgment. Technology should make those relationships visible and usable without concealing the source or removing the responsible official from the decision.
This is also why trust cannot be reduced to an “AI-powered” label. For consequential agency work, every finding should be reviewable. Staff should be able to see the source data, its effective date, the applicable direction or rule, the reasoning that produced the result, the action that followed, and the person who reviewed or approved it.
The goal is not to automate judgment away. It is to give people a stronger basis for exercising it.
Modernization should reduce work, not just digitize paperwork
The Expo featured impressive uses of document automation and generative AI. These capabilities can remove real administrative burden. But they also exposed an important risk: producing the same forms and reports faster is not necessarily the same as redesigning the process.
If a new system generates a large application more quickly but leaves agency staff to manually locate, interpret, and reconcile the same underlying information, the bottleneck has merely moved. In some cases, agencies may receive more material without gaining a better way to decide what matters.
Meaningful modernization should reduce the work required to reach a correct and defensible decision. It should eliminate duplicate searches, manual re-entry, avoidable handoffs, and late discovery. It should help staff act on information, not simply produce more of it.
That standard also gives the permitting technology community a better way to measure progress. “Faster” should not remain a general promise. We should be able to measure how long it takes to assemble an initial project context, how often affected rights are identified at intake, how many manual data touches a case requires, how quickly the next-action package is produced, and whether another reviewer can reproduce the basis for each finding.
Those are operational outcomes, not just software features.
What this means for Landica
The Expo did not change our mission. It made our next step more specific.
We remain focused on the agency side of permitting because faster applications do not automatically produce faster agency decisions. Agencies need tools that reflect how their staff actually review projects, interpret information, coordinate work, and build an administrative record.
We also do not believe a small company should begin by trying to replace the entire federal permitting stack. The better path is to build a foundation that can work across systems while implementing one high-value agency workflow deeply enough to prove measurable value.
For us, that means moving beyond project screening and into the work that screening should initiate. It means connecting agency-controlled data to explicit interpretation, required actions, notifications, assignments, responses, exceptions, approvals, and evidence. It means designing outputs that can enter existing agency systems rather than requiring every system around us to disappear.
The long-term vision is broad: a connected environment in which agencies can bring the full project context forward, coordinate the work required for a decision, and preserve a defensible history from intake through authorization.
The near-term responsibility is narrower: prove that approach through a real workflow, with real users, authoritative data, clear boundaries, and measurable outcomes.
The next phase of permitting innovation
The Permitting Innovators Expo showed a community moving from agreement about the problem toward experimentation with the solution. That is meaningful progress. Agencies, technology companies, consultants, and policymakers are increasingly working from the same premise: the current process is too fragmented, too manual, and too dependent on information arriving in sequence.
The next phase will require more than better interfaces, more data layers, or larger models. It will require a shared commitment to turning information into coordinated, reviewable action.
Faster permitting will not come from shorter clocks alone. It will come from helping agency staff see what matters earlier, understand why it matters, take the right action, and carry the evidence forward.
The problem is validated. The ecosystem is forming. Now context must become action.