Permitting is a sequence, not a submission

Permitting appears in most capital programs as a bar with a duration. Somebody has asked how long the authority takes, received an answer, and entered it. The bar is usually about the right length, and the program is still wrong, because the duration was never the constraint.

What governs a permitting path is sequence. Applications are not independent. Each one requires information that only exists once something else has been decided, designed, surveyed, or granted, and several of them cannot legally be filed until an earlier determination is in hand. Treating the path as a set of parallel reviews produces a program in which the last permit arrives long after the schedule says construction began.

The dependencies that are usually missed

Three dependency types account for most of the slippage.

Consents that require another consent. A discharge authorization frequently cannot be assessed until the water supply arrangement is defined, because the volume and quality being discharged depend on what is coming in. An air permit may need the final equipment selection, which needs the load, which needs the process. These are not review delays. They are ordering constraints, and no amount of expediting removes them.

Consents that require completed technical work. Environmental and traffic determinations rest on studies, and studies rest on baseline data. Some baseline data can only be collected in a particular season. A survey window missed in spring is not recovered by adding resources in July; it is recovered the following spring, and the program absorbs a year.

Consents that require a decision the owner has not made. Where an application must state a capacity, a phasing plan, or a cooling approach, the application cannot be filed until that is settled. Filing with a placeholder is worse than waiting, because a material change after submission often restarts the clock rather than amending the file.

Why the duration estimate is misleading

A stated review period describes the authority's target for a complete, uncontested application. Most programs never test that number under those conditions.

Requests for further information stop the clock and are common. Statutory consultation periods run on their own calendar regardless of project urgency. Where a determination is appealable, or a hearing can be requested by a third party, the distribution of outcomes has a long tail that an average duration conceals entirely.

A permitting program built on average review times is a program built on the assumption that nothing will be contested. That is a forecast about other people's behavior, presented as an engineering input.

The practical consequence is that a permitting path should be modeled as a network with named predecessors, not as a row of bars, and it should carry float explicitly rather than by hope.

What a usable permitting map contains

The map that survives contact with a real program has four things in it.

Every required consent, listed by name and issuing authority, including the minor ones. Minor permits are disproportionately dangerous because nobody assigns them an owner.

For each consent, what must exist before it can be submitted — the decision, the design deliverable, the study, or the prior approval. This is the part that converts a list into a sequence.

For each consent, what it blocks. A permit that gates site mobilization is a different object from one that gates final occupancy, and they should not carry the same priority.

An accountable name against each, on the owner's side. Where responsibility sits only with a consultant or contractor, the owner learns about a problem after it has become one.

How the sequence gets recovered when it slips

Once a permitting path is late, the options are narrow and all of them cost something.

Scope can be split so that early works proceed under a consent that is already granted, which buys time but fragments the procurement and often the design. The program can be resequenced around the outstanding determination, which works only if the affected work is genuinely severable. Or the completion date moves.

What does not work is escalation. An authority is not a supplier, and it does not respond to commercial pressure or to the project's financing calendar. The leverage an owner has over a permitting path exists almost entirely before submission — in the completeness of the application, the quality of the pre-application engagement, and the discipline of having made the decisions the application depends on.

That leverage is spent early or not at all.