Permit Responsibility Matrix for Projects Crossing Charlotte and Mecklenburg Reviews

Owners can keep city and county review responsibilities visible by building a single shared record, often called a permit responsibility matrix, that tracks who submits, who responds, what must happen first, what is on hold, what inspection comes next, current status, and the final evidence for every system on the project, whether that system falls under City of Charlotte review or Mecklenburg County review.

This article summarizes what the City of Charlotte and Mecklenburg County publish about permitting and residential lot reviews as of the writing date. Permit categories, submission portals, review sequencing, and inspection requirements change, so owners and their project teams should confirm the current process directly with the City of Charlotte, Mecklenburg County Code Enforcement, and any other authority having jurisdiction before relying on this article for a live project.

What Current Public Sources Establish

The City of Charlotte publishes permitting information through its Planning and Development pages, including a Zoning Permitting section that covers how projects move through review within city limits. Charlotte also publishes an Individual Residential Lot Reviews page that addresses how single lot projects, such as a new house or an addition, are handled from a zoning and site perspective before construction can begin.

Mecklenburg County Code Enforcement publishes its own permitting page, which covers building code review and inspection functions that the county performs. Because Charlotte and Mecklenburg County are separate reviewing authorities with separate responsibilities, a single construction project, especially one that touches zoning, building code, and site elements, can require submissions to more than one office. The published pages describe what each authority reviews in general terms, but they do not replace a project-specific determination of which reviews apply to a given address, land use, or scope of work.

The City of Charlotte Zoning Permitting page describes city-level permitting and zoning review functions.
The City of Charlotte Individual Residential Lot Reviews page addresses lot-specific review steps for residential projects.
Mecklenburg County Code Enforcement publishes permitting information covering building code review and inspections.
Owners should confirm with each office which reviews apply before assuming a project is single-jurisdiction.

Inputs and Existing Conditions to Document

Before an owner or project team can build a useful responsibility matrix, they need to gather the existing conditions that determine which authority reviews which part of the project. This includes the property address, parcel identification, current zoning designation, and whether the project is inside Charlotte city limits, in Mecklenburg County outside the city, or in another jurisdiction that touches the same parcel boundary.

It also helps to document the scope of work in plain terms before contacting any office: is this a new structure, an addition, an interior renovation, a site change such as grading or drainage, or a combination of these. Recording this scope up front makes it easier to ask each authority a specific question rather than a general one, and it gives the project team a starting point for the matrix itself.

Property address and parcel identification number.
Current zoning designation and jurisdiction, city or county.
A plain-language description of the scope of work.
Any known prior permits, variances, or reviews tied to the same parcel.

Step-by-Step Owner and Project-Team Review

A practical way to build the matrix is to walk through the project system by system rather than trying to capture the entire scope in one pass. For each system, the owner or project team records seven fields: submission, response, prerequisite, hold, inspection, status, and final evidence. This structure keeps the record consistent even when different systems are reviewed by different offices or on different schedules.

Systems commonly tracked this way include zoning or land use review, building code review, site or grading review, and any specialty reviews that a given project may require, such as those tied to trees, stormwater, or utility connections. The exact list of systems that apply to a specific project should be confirmed with the City of Charlotte and Mecklenburg County Code Enforcement, since not every project touches every system.

Submission: what was submitted, to which office, and on what date.
Response: what the reviewing authority returned, and to whom.
Prerequisite: what must be complete or approved before this step can start.
Hold: what is currently blocking progress on this system.
Inspection: what inspection, if any, is tied to this system and its current state.
Status: a short, current description such as submitted, under review, or closed.
Final evidence: the document or record that proves this system reached closure.

Responsibilities, Dependencies, and Hold Points

One of the most useful things a responsibility matrix does is make dependencies visible. Some systems cannot move forward until another system clears a hold point. For example, a building code review may depend on a prior zoning determination, or a site review may depend on information from a separate utility or drainage review. When these dependencies are not written down, it becomes easy for an owner or contractor to assume a step is complete when it is only submitted.

The matrix should name who is responsible for each hold point, whether that is the owner, the design professional, the contractor, or the reviewing authority itself. This does not change who has legal authority to approve a permit or accept an inspection, since that authority rests with the City of Charlotte, Mecklenburg County Code Enforcement, or any other applicable jurisdiction. What it does is give the project team a shared, current view of where the project actually stands at any point in time.

Record which office holds authority for each review, city or county.
Record who is responsible for clearing each documented hold point.
Note any step that cannot start until a prior step is confirmed closed, not just submitted.
Keep the matrix updated at each status change rather than only at major milestones.

Common Coordination Failures

Several patterns show up repeatedly when city and county reviews are not tracked in one place. The most common is treating a submission as if it were an approval, which can lead a project team to schedule work or inspections before a review is actually closed. Another is losing track of which version of a plan set was submitted to which office, which can create confusion when a city comment and a county comment appear to conflict but are actually referencing different plan versions.

A third common failure is missing a prerequisite entirely, such as starting a building code submission before a required zoning or site determination has been resolved. A fourth is failing to preserve final evidence, such as a closed permit record or a final inspection record, in a place the owner can retrieve later, which becomes a problem at resale, refinance, or future permitting on the same parcel.

Keeping a single matrix that is updated as each system changes status is one practical way to reduce these failures, but it does not replace direct confirmation with the reviewing authority at each step.

Confusing a submitted item with an approved or closed item.
Losing track of which plan version was reviewed by which office.
Starting one review before a prerequisite review is actually resolved.
Failing to retain final evidence such as closed permits or final inspection records.

Questions for the Responsible Authority or Qualified Professional

Because permit categories, review sequencing, and inspection requirements can change and because they depend on the specific property and scope of work, owners should bring a short, specific list of questions to the City of Charlotte, Mecklenburg County Code Enforcement, or another applicable authority before relying on any general summary, including this one.

A design professional, engineer, or other qualified professional retained for the project can also help translate published requirements into the specific systems and prerequisites that apply to a given site. Their role is to help the owner ask the right questions of the reviewing authority, not to substitute for that authority's determination.

Which office, city or county, has review authority over each system on this specific project.
What the current prerequisite sequence is for this scope of work.
What documentation each office considers final evidence of a closed review.
Whether any recent changes to permitting categories or portals affect this project.

Next Action and Related CDG Service Resource

For owners managing a project that touches both City of Charlotte and Mecklenburg County reviews, the practical next step is to start the matrix early, before submissions begin, so that every system has a place to record its status from the first submission through final evidence. This is part of what construction management planning looks like in practice: keeping the record visible so that no single system is assumed complete without documentation.

Cooper Development Group works with owners on construction management planning across the Carolinas, including projects connected to /construction-management-lake-wylie-sc/. Related guidance on organizing permit records and version control appears on the CDG /blog/, and owners who want to talk through how a responsibility matrix might apply to a specific project can reach out through /consultation/. Any property-specific code, zoning, environmental, or design question should still be directed to the responsible authority or a qualified licensed professional before decisions are made.

Start the matrix before the first submission so every system has a record from day one.
Review related permit record guidance on the CDG blog.
Use the consultation page to discuss project-specific planning needs.
Always confirm property-specific requirements with the City of Charlotte or Mecklenburg County Code Enforcement.

Questions homeowners ask

What is a Charlotte Mecklenburg permit responsibility matrix?

It is a project record, built by the owner and project team, that tracks each system in a project, such as zoning, building code, and site review, across seven fields: submission, response, prerequisite, hold, inspection, status, and final evidence. It helps keep city and county review responsibilities visible in one place rather than scattered across separate emails, portals, or file folders. It does not replace the official review process itself, which remains with the City of Charlotte and Mecklenburg County Code Enforcement.

Does every project need both city and county permit review?

Not necessarily. Whether a project needs review from the City of Charlotte, Mecklenburg County, or both depends on the property location, zoning, and scope of work. The City of Charlotte publishes permitting and individual residential lot review information, and Mecklenburg County Code Enforcement publishes its own permitting page. Owners should confirm directly with each office which reviews apply to their specific parcel and project scope.

Who should build and maintain the responsibility matrix on a project?

There is no single required party named in the published city or county sources, so this is a practical planning tool rather than a regulatory requirement. In practice, the owner, the contractor, and any design professional involved in the project can share the matrix so that submissions, holds, and final evidence are visible to everyone on the team, even though final review authority always rests with the applicable jurisdiction.

Where can owners find current, official permitting requirements for Charlotte and Mecklenburg County?

The City of Charlotte publishes permitting information through its Zoning Permitting page and its Individual Residential Lot Reviews page. Mecklenburg County Code Enforcement publishes permitting information on its own site. Because requirements and portals can change, owners should treat these published pages as the starting point and confirm any project-specific requirement directly with the relevant office before submitting.

Plan the next step

Use this article as a planning aid, then confirm project-specific requirements with the responsible authority and qualified professionals. Review CDG's related service, construction articles, or consultation page when you are ready to organize the next decision.

Official sources and verification

Authority pages, forms, fees, review steps, and code references can change. Verify the current path for the property and scope before relying on a planning assumption.