Prevailing WageNRS 338Compliance

NRS 338 Prevailing Wage Compliance Checklist for Las Vegas Contractors

By Kwabena Kesse, CPA · Founder, BuilderIQ Analytics · March 25, 2026 · 5 min read

Nevada Revised Statutes Chapter 338 requires prevailing wages on all public works projects exceeding $100,000. A single misclassification across 20 workers for 6 months is a $50K+ back-pay liability you won't see coming until the Labor Commissioner calls. Miss a wage classification, underpay by $0.50/hour, or submit certified payroll late — and the penalties compound daily.

This isn't theoretical. The Nevada Labor Commissioner actively audits public works projects in Clark County, Washoe County, and NDOT-funded work. Here's the complete compliance checklist every Las Vegas GC and subcontractor needs.

When Does NRS 338 Apply?

NRS 338 applies when ALL of these are true:
• The project is a public work (funded by state, county, city, school district, or public agency)
• The contract value exceeds $100,000
• The work is performed in the State of Nevada

Common public agencies in Las Vegas: CCSD (Clark County School District), NDOT (Nevada Department of Transportation), City of Las Vegas, City of Henderson, Clark County, Las Vegas Convention Authority, Regional Transportation Commission.

The Compliance Checklist

Before the Project Starts

Verify the project is classified as public works and confirm the prevailing wage determination from the Nevada Labor Commissioner. Watch for Clark County projects with layered funding — RTC-funded work on a CCSD campus can trigger multiple wage determinations on the same site.
Obtain the current prevailing wage rates for each trade classification. Rates are published by the Labor Commissioner and vary by county. Clark County rates differ from Washoe and rural Nevada — don't use the wrong county's schedule.
Classify every worker correctly before they set foot on site. An electrician doing pipe fitting work must be paid the higher of the two trade rates. Misclassification is the most common violation — and in Las Vegas, where trades overlap frequently on fast-tracked resort and casino work, it happens more than anywhere else in the state.
Include prevailing wage requirements in every subcontract agreement. As the GC, you are financially liable for your subs' compliance failures. On a CCSD project with 15 subs, that's 15 potential sources of violation landing on your balance sheet.
Post the prevailing wage rates at the job site in a visible location accessible to all workers.

During the Project

Pay workers at or above the prevailing wage rate for their trade classification. This includes the base rate PLUS fringe benefits (health insurance, pension, vacation).
Submit certified payroll reports weekly. Each report must include: worker name, classification, hours worked, rate paid, fringe benefits, and a signed certification.
Collect certified payroll from every subcontractor weekly. You cannot submit your payroll without theirs.
Track overtime correctly. Prevailing wage applies to overtime hours at 1.5x the base rate. Fringe benefits are paid at straight-time rate for all hours.
If a worker performs multiple trade classifications in one day, the safe practice is to pay the highest applicable rate for ALL hours that day. This is where payroll errors compound fastest — track classification changes daily, not weekly.

Ongoing Compliance

Monitor for rate changes. The Labor Commissioner can update prevailing wage rates during a project. Adjust pay promptly when new determinations are published — check the current statute for the exact compliance window.
Maintain payroll records for 3 years after project completion. The Labor Commissioner can audit up to 3 years back.
Respond to any worker complaints within 10 business days. Delayed responses escalate to formal investigations.

Penalty Exposure

What Non-Compliance Costs You:
Back-pay + penalties: Expect to repay the wage difference plus penalties that can reach thousands per affected worker
Daily compounding: Ongoing violations can accumulate significant daily penalties under NRS 338 (verify current penalty caps against the statute) — this is what turns a payroll error into a balance sheet event
Loss of public work eligibility: Repeat violators can be excluded from bidding on Nevada public projects for years — that's your NDOT and CCSD pipeline gone
Surety impact: A prevailing wage finding hits your financials and your surety sees it at renewal. It's not just the fine — it's the bonding capacity reduction that follows

The Nevada Labor Commissioner actively enforces prevailing wage violations across Clark County. Based on our experience reviewing contractor financials and industry patterns (these are practitioner estimates, not official Labor Commissioner statistics), the most common violation types rank roughly as follows:

  1. Worker misclassification (most frequent) — Paying a journeyman electrician as a helper saves $12/hr but the back-pay exposure when caught far exceeds the savings.
  2. Late certified payroll (second most common) — Subcontractors submitting payroll 2–3 weeks late. The GC is financially responsible for their subs' failures.
  3. Fringe benefit miscalculation — Paying the base rate but shorting the fringe component. This is often a bookkeeping error, not intentional, but the penalty doesn't distinguish.
  4. Overtime errors — Applying fringe benefits at overtime rate instead of straight-time. Small per-hour error, large cumulative exposure.

Davis-Bacon vs NRS 338

If your project receives federal funding (NDOT highway projects, HUD housing, federal buildings), both Davis-Bacon federal rates AND NRS 338 state rates may apply. In that case:

Rule: Pay whichever rate is HIGHER — federal or state — for each trade classification. This is determined trade-by-trade, not project-wide.

How to Stay Compliant Without the Headache

Manual prevailing wage tracking is error-prone. A single misclassification across 20 workers for 6 months creates a $50K+ back-pay liability that you won't discover until the audit.

Misclassification and late certified payroll account for the vast majority of prevailing wage violations. BuilderIQ Analytics targets both:

A single misclassification across 20 workers for 6 months is a $50K+ back-pay event you won't see coming until the Labor Commissioner calls. BuilderIQ shows you the gap the week it starts. Start your free 30-day trial →

About the Author
Kwabena Kesse is a licensed CPA (Nevada & North Dakota) with a Master's in Data Analytics and 13 years of experience in retail and commercial banking. He is the founder of BuilderIQ Analytics.
Disclaimer: For educational purposes only — not legal, financial, or professional advice. NRS 338 requirements, rates, and penalty provisions are subject to change — verify against the current statute before acting. Violation frequency estimates are practitioner observations, not official data. Software outputs are for informational purposes and should be verified by a qualified professional.