If you've bid a Maryland state contract recently, you already know the feeling: you win the work, then the compliance burden starts. Maryland prevailing wage requirements for general contractors are detailed, enforced, and unforgiving if your certified payroll process isn't tight. We've worked with GCs across the Baltimore–Washington corridor who have lost money — not from bad bids, but from prevailing wage violations discovered during audit. Fringe benefit miscalculations. Apprentice ratio failures. Subcontractors submitting incomplete or late certified payrolls. It adds up fast.
This post breaks down exactly what Maryland's prevailing wage law requires, where GCs consistently get tripped up, and how the right systems — including AI compliance tooling — can reduce that exposure without adding headcount.
what maryland prevailing wage law actually requires
Maryland's prevailing wage law is governed by the Maryland Code, Labor and Employment Article, §17-201 through §17-215. It applies to any public works contract with the state or a state agency where the contract value exceeds $500,000. Some counties and municipalities have their own prevailing wage ordinances with different thresholds — Baltimore City, Montgomery County, and Prince George's County each have local requirements that may apply even on smaller contracts.
The law requires that all workers employed on covered projects — including subcontractor employees — be paid no less than the prevailing wage rate for their trade and county as determined by the Maryland Commissioner of Labor and Industry. Those wage rates are published in a Wage Determination issued for each contract. You'll see separate rates for:
- Craft classification (carpenter, ironworker, plumber, pipefitter, electrician, laborer, etc.)
- County where the work is performed
- Whether the worker is a journeyman or apprentice
The wage rate has two components: the basic hourly rate and the fringe benefit rate. GCs can satisfy the fringe benefit component by paying it in cash (added to the hourly wage), by making bona fide contributions to qualifying benefit plans (health insurance, pension, vacation funds), or a combination of both. This is where a significant number of compliance errors occur — more on that below.
Certified payroll reports must be submitted weekly to the awarding authority. Each report covers every worker on the project for that workweek, their classification, hours worked each day, gross wages, deductions, and net pay. In Maryland, these are typically submitted using the federal WH-347 form or an equivalent approved format. Submittals are public record.
General contractors are responsible for their own payroll compliance and for collecting and verifying certified payrolls from every subcontractor on the project. That responsibility doesn't go away when you hand work off to a sub.
the specific problems general contractors face
Knowing the law and executing against it are two different things. Here are the five areas where we see Maryland GCs take compliance hits:
1. Fringe benefit credit miscalculation
The fringe benefit offset is legitimate — if you're contributing to a qualifying health plan or pension, that contribution can be credited against the prevailing fringe rate. But the calculation has to be done correctly at the individual employee level, each workweek. GCs running this through spreadsheets or estimating software that wasn't designed for certified payroll often get the math wrong. The Maryland Department of Labor (MDL) auditors know exactly where to look.
2. Incorrect trade classifications
A laborer performing work that should be classified as a carpenter — even inadvertently — triggers a back-pay obligation at the higher rate. Mixed-craft work is common on commercial GC projects. Foremen performing hands-on work need to be tracked separately. If your payroll system doesn't map job codes to certified payroll classifications automatically, someone has to do it manually every week.
3. Apprentice-to-journeyman ratio violations
Maryland prevailing wage law sets limits on how many apprentices can work on a covered project relative to journeymen in the same trade. Exceeding the ratio means the apprentices should have been paid journeyman rates. This is a retroactive liability issue — if you're over ratio in week 4 and catch it in week 12, you owe back pay for the entire period.
4. Subcontractor certified payroll failures
Your sub's compliance failure is your problem. As the prime contractor, you're responsible for ensuring subs are filing complete, accurate certified payrolls on time. GCs with multiple subs on a project — mechanical, electrical, drywall, concrete — often don't have a systematic way to track submission status. It becomes a manual chase every week.
5. Late or missing submissions triggering audit
Consistent late certified payroll submissions are a red flag for auditors. A pattern of late subs from one contractor often leads to a deeper look at wage rates and classifications. The audit process in Maryland is conducted by the MDL Division of Labor and Industry and can go back up to three years. Penalties include back wages, interest, and debarment from future public work.
how ai compliance tooling solves the operational problem
The compliance requirements themselves don't change — but the labor involved in executing them does. What AI tools bring to prevailing wage compliance isn't interpretation of the law; it's automation of the weekly operational workflow that GCs currently handle manually or with underpowered software.
Here's how our AI compliance employee approaches the problem:
Automated classification mapping. Workers are mapped to their correct prevailing wage trade classification based on the work being performed, not just their job title in payroll. The system flags discrepancies when the same worker appears under multiple classifications across subs.
Weekly certified payroll generation. Rather than exporting from payroll, reformatting, and manually filling the WH-347, the AI compliance employee pulls hours and pay data, applies the correct wage determinations for each worker, calculates fringe benefit credits, and generates a compliant certified payroll report — ready for review and signature.
Fringe benefit reconciliation. For each employee, the system calculates whether the employer's benefit contributions meet the fringe component of the wage determination or whether a cash supplement is required. This runs automatically every pay period.
Apprentice ratio monitoring. The system tracks the journeyman-to-apprentice ratio by trade in real time. If a project is approaching the allowable ratio threshold, it surfaces a warning before the violation occurs — not after.
Subcontractor submission tracking. Every sub's certified payroll status is tracked in a central dashboard. Missing or late submissions trigger automated reminders. GCs can see, at a glance, which subs are compliant for the current workweek and which aren't.
Audit-ready documentation. Every certified payroll submission, along with the underlying calculation logic, is stored with a complete audit trail. If MDL auditors come in three years later, you can produce a complete, timestamped record of every submission.
This is the operational layer that most GCs are currently handling with a mix of spreadsheets, emails, and a dedicated payroll admin who is always behind. The AI compliance employee doesn't replace your payroll team — it removes the manual work so they can focus on exceptions and edge cases.
what still requires human judgment
AI compliance tooling handles the operational workflow. It doesn't replace legal or HR judgment on the following:
Disputed classifications. If there's a genuine question about whether a specific scope of work falls under one trade classification or another, that's a legal and contractual question. Your labor attorney and the project's wage determination need to be consulted directly.
New wage determinations on project modifications. When a contract modification changes the scope of work, the prevailing wage determination may need to be updated. Whether the new work triggers a new wage rate or falls under the existing determination is a project-specific legal question.
Benefit plan qualification. Not every benefit plan qualifies for fringe benefit credit under Maryland prevailing wage rules. Whether your specific health plan or pension qualifies requires a legal review of the plan documents against the requirements of the Maryland prevailing wage law and, where applicable, the Employee Retirement Income Security Act (ERISA).
Sub selection and onboarding. Choosing subcontractors who are prepared to comply with certified payroll requirements — and onboarding them to your compliance system — still requires human judgment about contractor capability and relationship management.
Responding to audit findings. If MDL issues audit findings, the response strategy involves legal counsel, your payroll team, and potentially back-pay calculations that need to be reviewed and validated by a qualified professional.
The system handles execution. Judgment calls belong with your team.
the roi calculation: what compliance overhead actually costs
Most GCs don't have a clean number for what prevailing wage compliance costs them on a per-project basis. Here's a framework:
Labor cost to produce certified payrolls manually: A payroll admin spending 4–6 hours per week on certified payroll for a single project — pulling data, reformatting, reconciling fringe benefits, chasing subs — at a fully loaded cost of $35–$55/hour runs $140–$330 per week. On a 52-week project, that's $7,280–$17,160 in labor just for the administrative function.
Cost of a single violation: Back wages for a misclassified worker earning $30/hour instead of $45/hour over 40 weeks = $24,000 in back pay, plus interest, plus the administrative cost of the audit response. A significant apprentice ratio violation on a multi-trade project can easily reach six figures.
Sub coordination failure: A GC managing six subs who each submit certified payrolls late three times during a project creates audit exposure and internal coordination time. At 30 minutes per sub per follow-up, that's 9 hours across the project — and those are the visible hours, not the audit exposure.
The AI compliance employee costs a fraction of the payroll admin labor it replaces, and it eliminates the systematic errors that create audit exposure. For a GC running two or three public works projects simultaneously, the ROI case is straightforward.
how kjags advisors approaches this
We work with general contractors and specialty contractors in the Baltimore–Washington market who are running Maryland public works projects and need a compliance infrastructure that scales with their project load — without scaling their administrative headcount.
Our AI compliance employee is built specifically for the certified payroll and prevailing wage workflow. It integrates with your existing payroll system, maps workers to wage determinations, generates WH-347-compliant reports, and maintains a complete audit trail. For GCs managing multiple subs, the subcontractor dashboard brings all certified payroll submissions into one place.
If you're bidding Maryland state contracts and your certified payroll process is still manual — or if you've had a close call on a wage determination audit — let's talk. We'll walk through your current workflow and show you exactly where the exposure is and how the system addresses it.
kjags advisors builds AI compliance tools for construction contractors in Baltimore and Washington DC. Our AI compliance employee handles the certified payroll and prevailing wage workflow so your team can focus on building.