Most schedule slippage on large projects in Maryland and Virginia surfaces during permitting, but it doesn't usually start there. By the time a project is sitting in agency review, the conditions for delay, incomplete impact analysis, mitigation that wasn't planned in parallel, and federal and state requirements that were treated as separate workstreams, have already been baked in months earlier. The permitting phase is where the consequences become visible, not where they originate.
That distinction matters because environmental permitting in both states routinely accounts for half to two-thirds of a project's total delivery timeline. For a project on a tight commercial schedule, this is the single largest variable in the plan, and the one most likely to be underestimated when development assumptions are first set. Treating permitting as a compliance step at the end of design, rather than a parallel track that begins during siting, is the most common reason large projects in this region miss their deadlines.
Any project that touches streams, wetlands, floodplains, or sensitive habitats will require approvals from multiple agencies operating on different schedules and subject to different statutes. At a minimum, that means federal review through the U.S. Army Corps of Engineers, state-level permitting through MDE in Maryland or DEQ in Virginia, and local approvals, particularly where tidal or shoreline work is involved. None of these reviews happens quickly, and none of them runs entirely independently of the others. Federal jurisdictional questions feed state requirements; state mitigation expectations shape federal documentation; local boards in coastal Virginia can weigh in on issues already addressed at higher levels.
The result is that what looks on paper like three sequential approvals is really one coordinated process with three points of failure. Projects that treat it as the former tend to discover the latter the hard way.
At the federal level, most projects in Maryland and Virginia move through Section 404 of the Clean Water Act, with some also requiring Section 10 authorization under the Rivers and Harbors Act. The path the project takes from there is what determines how long this layer adds to the schedule.
A Nationwide Permit verification, when a project qualifies, generally takes 45 to 90 days. An Individual Permit, when a project doesn't require one, can take 6 to 12 months or longer. The gap between those two timelines is significant, and the determination is usually made early in design, which means how the impacts are defined, avoided, and minimized in the first round of drawings has direct consequences on the schedule downstream. Projects that get this right tend to confirm their permit eligibility before submission and to document in detail the avoidance and minimization analysis. Projects that don't tend to spend months in coordination on endangered species or cultural resources issues could have been flagged earlier.
For an example of how this looks across a long-running multi-state program, RES has worked with Dominion since 2008 on more than 500 miles of transmission line projects in Virginia, West Virginia, and North Carolina, including the 96-mile Mt. Storm to Doubs 551 rebuild — a project that required USACE-approved wetland delineations, Clean Water Act permitting, and rare species coordination across multiple jurisdictions, with all approvals secured without delaying construction. Read the full Dominion case study.
Maryland uses a Joint Federal/State Application, a single submission that the U.S. Army Corps of Engineers and MDE both review. The intent is to streamline coordination, and when the application is complete, it does. When it isn't, the JPA structure means a single gap can hold up both agencies at once.
Nontidal wetlands and waterways permits typically run 6 to 12 months. Floodplain and waterway permits run closer to nine months. Where projects lose time is rarely in the substantive review; it's in the 45-day completeness review at the front end, which resets when information is missing, and in the back-and-forth that follows when mitigation concepts are submitted as placeholders rather than developed strategies. The projects that move through the JPA most efficiently come in with mitigation already designed, not because the regulation requires it that early, but because doing so removes the most common cause of resubmittal.
Virginia adds a layer of agency coordination that's worth understanding before a project starts. DEQ handles the bulk of state water quality and wetland permitting, but tidal projects also involve VMRC, and shoreline work in many jurisdictions is handled by a local Wetlands Board with its own review schedule and standards. General permits in Virginia run three to six months; Individual Permits run six to twelve or longer.
The most common failure pattern here is treating each of these approvals as a separate transaction. When jurisdictional determinations remain unresolved, when federal and state requirements conflict in ways not anticipated, or when local board comments arrive late and contradict earlier decisions, the schedule starts absorbing weeks at every handoff.
Across hundreds of projects in this region, the same handful of issues show up over and over: applications submitted before they were genuinely complete, environmental constraints identified after design had already locked in, mitigation strategies developed reactively rather than as part of the original site plan, and timelines that didn't account for seasonal restrictions or normal review cycles. None of these are regulatory surprises. They're planning gaps that compound, and the projects that consistently stay on schedule are the ones that close those gaps before the application goes in, not after.
This is also where the mitigation strategy stops being a downstream compliance task and starts being a scheduling tool. More on how wetland mitigation becomes a critical path solution.
The projects that hit their dates in Maryland and Virginia tend to look similar from a process standpoint, regardless of size or sector. They start the permitting strategy during early design rather than treating it as a compliance step at the end. They align federal, state, and local requirements upfront so that agencies aren't given conflicting information to respond to. They develop mitigation as part of the project plan rather than scrambling to assemble it after impacts are calculated. And they treat agency feedback as part of the process, comments are answered substantively and quickly, not pushed back against.
That last point matters more than it sounds. The agencies in both states are placing increasing emphasis on watershed-level impacts, resilience, and long-term environmental performance, and the documentation expectations have risen accordingly. Projects that meet that bar early tend to move; projects that don't tend to cycle through resubmittals.
Permitting requirements in Maryland and Virginia are not getting simpler, and the projects in the pipeline, particularly large industrial sites with significant water and habitat footprints, are not getting smaller. Understanding where the delays actually originate, and addressing them during the design phase rather than discovering them in agency review, is the difference between a project that moves on schedule and one that quietly absorbs six to nine months of avoidable delay.
If your project involves streams, wetlands, or floodplains in Maryland or Virginia, the permitting process will shape the schedule whether you plan for it or not. The question is whether you're planning around the real timeline or the one that exists on paper.