top of page

North Carolina Code Changes at the New Year: NC Codes Moves to DOL

2 days ago
10 min read

A code change at the turn of the year can feel routine until it affects a permit, inspection, plan review, or construction schedule. This year, North Carolina has an added layer to watch: certain code-related functions historically tied to the North Carolina Office of State Fire Marshal are moving to the North Carolina Department of Labor.


For contractors, designers, code officials, owners, developers, and anyone managing work in North Carolina, the change is not something to ignore or overstate. The codes do not suddenly become optional, and buildings do not get reviewed under a completely different universe of rules overnight. But the administrative home for code activity matters. It affects where guidance comes from, how updates are communicated, which agency handles specific questions, and how the state organizes code enforcement support.


This article explains what the move means in practical terms, what to watch at the first of the year, and how to keep projects moving while the state shifts code responsibilities from NC OSFM to DOL.


Wide-angle view of a residential construction site with lumber, safety markers, and a permit box near the entrance
Code changes often show up first in the field, where permits and inspections meet real construction work.

What is changing at the first of the year


The key change is administrative. North Carolina code-related responsibilities that have been associated with NC OSFM are shifting to the Department of Labor. In plain language, the state is moving the machinery behind certain code functions from one agency structure to another.


That may include how state-level code administration, code interpretation support, board activity, or related rulemaking processes are housed and managed. The exact effect on a specific project will depend on the kind of work involved, the permit status, the local jurisdiction, and the code edition being applied.


For most construction projects, the first point of contact will still be local. Building departments, inspectors, fire marshals, and permit offices remain central to day-to-day code compliance. A contractor will still submit plans where the project is located. An owner will still need inspections. A designer will still need to coordinate drawings with the adopted code.


The shift matters because state agencies set the framework around that local work. They publish guidance, support boards and councils, process updates, and help create the official code environment. When that framework moves, even if the field process looks familiar, the source of answers may change.


For anyone tracking North Carolina Code Changes at the New Year, the safest approach is to treat this as both a code compliance issue and an administrative transition.


Why the move from NC OSFM to DOL matters


Building codes work best when everyone knows three things:


  • Which code edition applies

  • Who has authority over a decision

  • Where to find official guidance


An agency move can affect all three.


The Department of Labor already has a public safety role in North Carolina, especially around workplace safety and labor-related enforcement areas. Moving code functions there may be intended to place more construction and safety oversight under a department that already works with regulated industries. Still, the practical concern is simple: regulated work needs clear lines of communication.


When a project team has a code question, delays often come from uncertainty rather than the rule itself. A plan reviewer may ask for clarification. A designer may need to know whether a provision applies to an existing building. A contractor may need to understand whether a new requirement affects work already permitted. If the agency structure changes at the same time, small questions can take longer to answer.


The move also matters for training and professional licensing areas tied to code enforcement. Code officials, inspectors, design professionals, and continuing education providers may see changes in forms, web pages, agency contacts, meeting notices, or published interpretations.


That does not mean every process changes on January 1. Many transitions keep familiar procedures in place while agency names and administrative routes change. The risk is assuming nothing has changed at all.


What should stay the same for most projects


The most important message is this: projects still need to comply with the legally adopted codes. A department change does not erase the North Carolina State Building Code, local inspection requirements, fire code obligations, accessibility rules, energy provisions, or trade-specific requirements.


In most cases, these items should remain familiar:


  • Permit applications through the local authority having jurisdiction

  • Plan review by the local or assigned review authority

  • Required inspections at scheduled stages of work

  • Correction notices when work does not meet code

  • Certificate of occupancy or final approval processes

  • The need to follow adopted building, residential, fire, mechanical, electrical, plumbing, fuel gas, energy, and existing building codes where applicable


Local jurisdictions will still have a major role. North Carolina has a statewide code system, but local inspection departments handle much of the day-to-day interaction with builders and owners. If a permit office tells a contractor what documents are needed, that instruction still matters.


The change also should not be read as permission to rely on informal guidance. A text message, outdated PDF, or old web page may not be enough. During a transition, official sources matter more than usual.


When agencies change, the rulebook may stay the same, but the path to the right answer can change quickly.

What may change in day-to-day practice


The most visible effects may be administrative rather than technical. That can still affect schedules. People often think of code changes as new fire ratings, energy requirements, stair dimensions, or electrical rules. Here, the first changes may look more like changed points of contact and updated processes.


Common areas to watch include the following.


Agency websites and official documents


Web pages may move. Forms may be revised. Older links may redirect or stop working. If a company has saved code resources in project templates, estimating files, or internal training materials, those links may need review.


This is especially important for:


  • Code interpretation pages

  • Board or council meeting schedules

  • Proposed rule notices

  • Guides for code officials

  • Continuing education resources

  • Inspection-related forms

  • State contact directories


A practical step is to update internal bookmarks after the new year and verify that frequently used documents come from the current agency source.


Code interpretations and guidance


State-level interpretations can shape how local officials apply a provision. If interpretation procedures move to DOL, project teams should confirm where to submit questions and where official responses will be posted.


A designer working on a difficult mixed-use building, for example, may need guidance on occupancy separation, egress, fire protection, or existing building provisions. If the question is sensitive, use the official channel rather than relying on older informal answers.


Board and council activity


Code updates often run through boards, councils, committees, and public notice processes. When those groups move administratively, meeting locations, agendas, staff contacts, and public comment instructions may change.


Anyone who follows pending amendments should keep an eye on official notices early in the year. This includes trade associations, large contractors, plan reviewers, manufacturers, engineers, architects, and code consultants.


Training and continuing education


Code officials and licensed professionals often depend on approved courses and required training cycles. If the state changes where code administration lives, training providers may need to update references, approval language, and course materials.


The topics may stay familiar, but the paperwork may look different.


Local coordination


Local departments may receive new instructions from the state. Some will communicate changes quickly. Others may update internal procedures over time. That can create short-term variation in how questions are routed.


For active projects, do not assume one town or county will handle the transition exactly like another. Ask early, document answers, and keep communication tied to the permit record when possible.


Close-up of printed construction code pages, a tape measure, and marked drawings on a plywood surface
A code transition is easier to manage when project documents are current and organized.

What contractors and project teams should do now


The best response is not panic. It is preparation. A few simple steps can reduce confusion during the first weeks of the transition.


Confirm the code edition for each active project


Every active job should have a clear answer to one question: which code edition applies?


That answer may depend on the permit application date, local policy, state adoption rules, and the type of work. For a project with a long design period, it is easy for teams to assume the code basis from early drawings still applies. Before submitting or resubmitting plans, confirm the applicable edition.


For each project, record:


  • Permit application date

  • Approval date, if already approved

  • Current review status

  • Applicable code edition

  • Any local amendments or special conditions

  • Any approved alternates, modifications, or interpretations


This record helps if a question comes up later.


Review internal templates


Many companies reuse the same notes, forms, and checklists. That saves time, but it can also carry old references into new work.


Review templates for references to NC OSFM, state contacts, code links, or outdated administrative language. This includes:


  • General notes on drawings

  • Code summary sheets

  • Inspection checklists

  • Permit cover letters

  • Bid exclusions and assumptions

  • Safety and compliance manuals

  • Training slides

  • Standard emails sent to owners or subcontractors


Do not change technical code language unless the adopted code has changed. But do update agency names and contact routes where they no longer match the current process.


Ask local officials how they want questions handled


Local building departments and fire officials may have specific guidance on how to manage state-level questions during the transition. A quick call or email can prevent wasted time.


Good questions include:


  • Should code interpretation requests still go through the local office first?

  • Has the state provided new contact information?

  • Are any forms changing after January 1?

  • Will pending applications be handled differently?

  • Are there local deadlines tied to the transition?


Keep the tone practical. Local offices may also be adjusting to the change.


Watch for official notices, not rumors


Transitions create rumor. Someone hears a process changed. Someone else hears the old process remains. Both may be partly true for different project types.


Use official notices from the state, local jurisdictions, and recognized code bodies. Trade groups can be helpful, but verify important claims before changing a project plan.


A good internal rule is simple: if the issue affects cost, life safety, schedule, or final approval, confirm it through an official source.


Protect project schedules


If a project needs approval near the first of the year, build in time for administrative friction. That does not mean expecting major delays on every permit. It means leaving room for updated forms, changed links, staff questions, or revised routing.


For projects with tight deadlines, submit complete documents. Missing information is always a problem, but it becomes more costly when agencies and local offices are adjusting to new procedures.


What owners and developers should understand


Owners and developers may not care which agency houses code administration until a schedule slips. The move from OSFM to DOL is a reminder that code compliance is not just a design issue. It is a project management issue.


A few risks deserve attention.


First, a project that spans the transition may have documentation from both sides of the change. Early correspondence might refer to NC OSFM, while later guidance may come from DOL. Keep both in the project file. Do not delete older approvals or assumptions because an agency name changed.


Second, do not pressure the team to treat uncertainty as a minor detail. If the architect, engineer, contractor, or code consultant asks for time to confirm a requirement, that may protect the project from a larger issue later.


Third, ask for a code status update during regular project meetings. It does not need to be long. A simple line item can cover pending permits, review comments, interpretations, inspections, and any agency transition issues.


Fourth, make sure contracts and schedules reflect the possibility of code-driven revisions. No contract can eliminate code compliance obligations. A clear process for handling changes is better than a fight later.


How this affects fire and life safety questions


Because NC OSFM has long been associated with fire safety and code support, many people will naturally wonder whether fire-related questions change.


The answer depends on the issue. Local fire marshals and inspection officials will still play a key role in fire prevention, construction inspections, occupancy approvals, and enforcement under applicable codes. State-level fire and building code administration may have new routes, depending on how responsibilities are assigned after the transition.


For project teams, the safest practice is to separate the technical question from the administrative question.


The technical question might be:


  • Does this building need sprinklers?

  • What fire-resistance rating applies?

  • Is this occupancy separated correctly?

  • Does the fire alarm design meet the adopted code?

  • Are access roads and hydrant locations acceptable?


The administrative question might be:


  • Which office reviews this?

  • Where is the official form?

  • Who issues the interpretation?

  • Is the local official or state agency the right first contact?

  • Where should appeals or formal requests be sent?


Answer both before making design decisions.


A practical checklist for January


Use the first few weeks of the year to clean up code administration across active and upcoming projects.


Task

Why it matters

Confirm the applicable code edition for every active project

Prevents confusion during plan review and inspection

Update saved links and agency contacts

Reduces time lost to old web pages or outdated forms

Review drawing templates and code summary sheets

Keeps submissions consistent with current agency references

Ask local jurisdictions about changed procedures

Local offices may receive new instructions from the state

Save official notices in project files

Creates a clear record if questions arise later

Track board and council activity

Helps teams plan for upcoming amendments or interpretations

Build extra time into early-year submissions

Gives room for administrative adjustments


This checklist is simple, but it catches the most common problems. Code transitions rarely cause trouble because no one knows the code. They cause trouble because teams use old assumptions after the process changes.


What not to assume


A change this visible can lead to overreaction. Avoid these assumptions.


Do not assume all codes changed on the same day.

An agency move is not the same as a full technical code update. Verify which rules changed, if any, before revising designs.


Do not assume local officials no longer matter.

Local authorities remain central to permitting, inspections, and enforcement.


Do not assume old approvals are invalid.

Existing permits and approvals may still stand, subject to normal rules. Keep records and confirm if a project has unusual timing.


Do not assume every answer will be immediate.

During the transition, some questions may take more time to route. Plan for that.


Do not rely on outdated files.

Old PDFs, saved forms, and bookmarked links can create mistakes.


The bottom line for North Carolina code compliance


The move from NC OSFM to DOL is a significant administrative shift for North Carolina’s code system. For many projects, the field experience may look much the same at first. Permits still need complete documents. Inspections still need to pass. Buildings still need to meet the adopted code.


The real work is making sure the right people are asking the right agency the right questions. That means checking code editions, updating documents, confirming local procedures, and watching for official state guidance as the new year begins.


This article is for general information only and is not legal advice or a formal code interpretation. For a specific project, rely on the authority having jurisdiction, current state notices, and qualified design or code professionals.


A smooth transition will come down to habits more than headlines: verify the source, document the answer, and keep code compliance visible from design through final inspection.


See attached documents form OSFM & DOL:




 
 
 

Comments


bottom of page