The pre-application meeting is the single highest-leverage hour in most civil engineering projects. It's where the jurisdiction tells you what they'll require, where they'll push back, and what your actual approval timeline looks like, before you've spent a dollar on design. An applicant who walks in prepared can leave with a clear map of what their permit package needs to contain and a realistic picture of what the review will involve. An applicant who walks in unprepared can leave with the same meeting on their calendar and almost none of that information.

The meeting itself is usually free. The jurisdictional staff's time, the planner's engagement, the floodplain administrator's attention, all of it costs the applicant nothing at the point of scheduling. Most jurisdictions in North Carolina offer pre-application meetings routinely and even encourage them for any project that isn't a routine single-family permit. The leverage available in that hour, if you use it well, can save months of redesign and rework later.

What a Pre-App Meeting Really Is

A pre-application meeting is an informal conversation between an applicant's team and the jurisdiction's review staff, held before any formal permit application is filed. The purpose is to surface the project's requirements, identify potential issues, and establish a shared understanding of the path to approval. It is not a commitment by the jurisdiction, staff cannot promise an outcome, but it's an enormously useful signal about what that outcome is likely to be.

Depending on the jurisdiction and the project scope, the meeting may include:

Not every meeting has all of these attendees. On a straightforward site, it may be just a planner and a stormwater reviewer. On a complex mixed-use project in a historic overlay, it may be half a dozen people. The applicant's team should know who the jurisdiction has invited before the meeting and bring materials appropriate to that audience.

What to Bring to the Meeting

The worst use of a pre-app meeting is walking in empty-handed and asking "what are your requirements?" The review staff has already published the requirements; they're in the ordinance, the design manual, and the submittal checklist. Asking them to recite the document wastes everyone's time. The best use of the meeting is walking in with a specific proposal and asking the staff to respond to it.

A well-prepared applicant typically brings:

The goal is to make it easy for staff to engage with the project rather than describe the ordinance. The meeting then becomes a working session on the applicant's specific site rather than a generic orientation.

Don't Hide the Hard Questions

Applicants sometimes try to minimize potential concerns in pre-app meetings, hoping that not mentioning an issue will make it not an issue. This almost always backfires. Staff will find the issue eventually, at submittal, at a hearing, at inspection, and discovering it later is always more expensive than discovering it in the pre-app meeting. Bring the hard questions to the pre-app meeting, get honest answers, and plan the project around the reality.

The Questions That Matter Most

A good pre-app meeting is driven by good questions. The exact list depends on the project, but several categories matter on almost every civil site engagement:

Stormwater and Watershed

Zoning and Setbacks

Access and Transportation

Utilities and Infrastructure

Floodplain and Environment

Process and Timing

What to Listen For, and Write Down

The applicant's team should assign one person to take notes. Not casual notes, structured notes that capture what staff said about each of the questions above. After the meeting, those notes become the working document for the design team. Specific things to capture:

The notes should be distributed to the entire project team within 24 hours, and a summary memo should go back to the staff acknowledging what was discussed. That memo serves two purposes: it confirms the applicant's understanding, and it documents the commitments for the record.

Turning the Meeting into an Approval Roadmap

The deliverable from a good pre-app meeting isn't a list of notes, it's a roadmap. The applicant's team should leave with a clear answer to three questions:

  1. What does our permit package need to contain? The specific submittal items, calculations, drawings, and supporting documents.
  2. What is the expected review timeline? From submittal to approval, with realistic expectations about review cycles and conditions.
  3. What are the biggest risks to approval, and how do we mitigate them now? Technical studies, design decisions, community engagement, or other pre-submittal work that removes obstacles.

When those three questions are answered, the project has a real plan. When they aren't, the project is flying blind and will course-correct expensively later.

Key Takeaways