The NAICS code assigned to a contract is set by the contracting agency during procurement, not by the contractor. For many compliance purposes, you work with what the agency gives you. But how you apply that NAICS code to your wage determination lookup, and whether the resulting WD actually covers the work you are performing, has direct consequences for the wage rates and fringe obligations you are required to meet. Getting this wrong means building your entire compliance posture on an incorrect foundation.
This is not a hypothetical edge case. NAICS mismatches in wage determination lookups appear in DOL audit findings across IT support, security services, facilities management, and other common govcon service categories. The mismatches often persist for the entire contract period because nobody rechecks the WD-to-NAICS connection after contract start.
What NAICS Codes Actually Do in the SCA Context
Under the Service Contract Act, wage determinations are geographic. The applicable WD for a covered contract is determined primarily by the place of performance: county, state, and locality. The SCA does not use NAICS codes as the primary selection criterion for the applicable wage determination the way some contractors assume it does.
However, NAICS codes are significant in a different way. The DOL uses NAICS-like industry and service type classification when determining which occupational wage survey data applies to specific types of service work. And when a contracting officer is selecting or verifying a wage determination through SAM.gov, NAICS codes are used as a search filter that narrows the applicable WDs. If the contracting officer uses a NAICS code that does not accurately reflect the service work being procured, the WD they incorporate into the contract may not cover the occupational categories your employees actually work in.
The practical risk: a WD pulled for a specific NAICS code may list wage rates for occupations relevant to that industry category. If your workforce includes occupations that are not covered by the WD's occupational listings, those employees may be working under a WD that does not set a minimum wage rate for their specific duties. This does not relieve you of the SCA fringe obligation, but it creates an ambiguity in what minimum wage rate applies.
The Most Common NAICS Mismatch Patterns
In data management and IT operations contracts, we see mismatches when a contract is coded under a NAICS code for computer programming services when the work is actually IT support and help desk operations. The wage occupational structure for these two categories differs. Computer programming classifications may generate different WD occupational listings than information technology support technician classifications, and the wage rates are not interchangeable.
In facilities management, contracts for general building maintenance are sometimes coded under janitorial services NAICS codes when the workforce includes general maintenance mechanics, HVAC technicians, or electricians who should be classified under different occupational categories with distinct wage rates. A WD pulled for janitorial services NAICS may not list the maintenance mechanic or HVAC technician occupational categories that your workforce actually fills, leaving those classifications outside the WD's explicit coverage.
In security services, a single NAICS code may be applied to a contract that includes both unarmed guard services and armed security officer services, but the WD occupational listings and applicable wage rates for armed vs. unarmed security are different. Using a single NAICS-driven WD that covers only one of those categories means half your covered workforce may be operating under misapplied wage rates.
What Happens When the WD and the Work Do Not Match
When an auditor finds that the WD incorporated into a contract does not contain wage rate listings for the occupational categories your employees are working in, the investigation enters conformance territory. Under the SCA implementing regulations at 29 CFR Part 4, if an employee's job duties do not match any occupation listed in the applicable WD, the contractor is supposed to initiate a conformance proceeding with the contracting agency to establish an applicable wage rate for that unlisted classification.
Most contractors do not initiate conformance proceedings when they should, either because they are unaware of the obligation or because they have incorrectly assumed their employees fit within the existing WD classifications. When an investigation finds employees working in unclassified positions without a conformance proceeding having been initiated, the investigator's approach is to calculate back wages based on the closest comparable classified occupation in the WD, which may be higher or lower than what was actually paid.
The conformance requirement is also the correct answer when you realize mid-contract that a NAICS-driven WD mismatch has left some occupations without explicit coverage. Filing the conformance request with your contracting officer before an investigation is always preferable to having the auditor establish a conformance rate retroactively.
Verifying Your Contract's NAICS-to-WD Connection
The verification process at contract start should include comparing the occupational listings in the incorporated WD against the actual job duties of your covered workforce. You are looking for two things: employees whose duties clearly match a listed occupation, and employees whose duties do not clearly map to any listed occupation.
For the unmapped employees, review the SCA Directory of Occupations for the closest applicable classification. If the closest classification requires a conformance proceeding because it is not in your current WD, initiate that process immediately. Do not wait until a renewal or modification. The conformance obligation exists from the moment you identify the gap.
If you are reviewing a contract where the NAICS code in the solicitation or contract documents seems inconsistent with the actual work, raise it with the contracting officer. There is a process for requesting a WD correction or substitution if the incorporated WD does not match the service work being performed. This is not a complaint; it is a legitimate contract administration request. Contracting officers can and do correct WD mismatches when the issue is identified and documented properly.
Multi-NAICS Contracts and the Portfolio-Level Problem
Contractors holding large portfolios of covered contracts face a compound version of this problem. Each contract has its own NAICS code and its own WD. Some contracts may cover the same occupational categories under different WDs because the NAICS codes differ between contracts. The compliance implication: the same job title at two contracts may have different minimum wage obligations if the applicable WDs list different rates for that occupation, even if the employees are performing essentially the same work.
This is not a contradiction or error. Different geographic WDs legitimately produce different wage rates for the same occupation across different localities. But when the WD difference is driven by a NAICS mismatch rather than a genuine geographic wage differential, the compliance picture becomes distorted. Two employees doing identical work in the same location may be on different wage schedules because their contracts were coded under different NAICS categories.
When we build contract records in CVRD Health, the NAICS code is a stored field for each contract, and we cross-reference it against the occupational listings in the WD to flag potential conformance needs before the contract period begins. This is not a complete substitute for legal judgment on conformance questions, but it surfaces the issue at the right time, before payroll runs, rather than after an audit request.
A Note on What NAICS Codes Do Not Govern
The H&W fringe rate under SCA is set by All-Agency Memorandum and is not NAICS-specific. The same national H&W floor applies to covered service employees regardless of the NAICS code assigned to their contract. NAICS code errors affect the occupational wage rate portion of the SCA obligation, not the H&W fringe rate itself. This means a NAICS mismatch can produce an incorrect wage rate for an employee's occupation while the fringe obligation is calculated correctly from the AAM rate, or vice versa. They are separate inputs that need to be verified independently.