- The prevailing wage is an early decision that constrains the SOC code, recruitment, and the offered wage for the whole case.
- The SOC code and wage level must match the job's actual duties and requirements — overstate them and the wage climbs; understate them and the case is vulnerable.
- A wrong determination is expensive to unwind, so the analysis belongs at intake, not at filing.
In a PERM case, the prevailing wage feels like a back-office number — something the Department of Labor issues, the employer agrees to pay, and everyone moves past. In reality it is one of the earliest and most consequential decisions in the case. It fixes the wage floor, it reflects a chosen SOC code, and it sets the level against which recruitment must be conducted. Get it wrong and you do not adjust a figure; you often start over.
This is a walkthrough of how the determination is built, where it goes wrong, and why the analysis belongs at the very beginning.
What the Determination Actually Decides
A prevailing wage determination answers one question — what workers in this occupation, at this skill level, in this area, are typically paid — but it does so through a chain of choices. The occupation is expressed as a SOC code. The skill level is a wage level, one through four, driven by the job's requirements and duties. The area is the place of intended employment. Each choice moves the number, and each choice has to be defensible against the job as it is actually described in the rest of the case.
The SOC Code Is the Whole Ballgame
Choosing the SOC code is choosing the occupation the case lives in. Pick a code that is too senior or too specialized and the wage climbs, sometimes past what the employer will pay. Pick one that is too junior to capture the real duties and the case becomes vulnerable — the job description, the requirements, and the wage will not line up, and that mismatch is exactly what an audit examines.
The code has to be the honest center of the role, not the cheapest plausible label. Everything downstream — the wage level analysis, the recruitment, the audit file — assumes the code is correct.
Wage Levels and the Requirements Trap Medium Risk
The wage level rises with the job's requirements: education, experience, supervisory duties, special skills, and unusual conditions each push it up. This creates a tension that defines PERM practice. The requirements that make a strong, specific job also make a higher wage. The requirements that keep the wage affordable can make the job look generic — or can fail to match the foreign worker's qualifications.
The level is not something to reverse-engineer from a target wage. It is read off the job, and the job has to be real.
"You do not choose the wage. You choose the job honestly, and the wage follows. Trying to do it the other way around is how cases unravel."
Failure Mode: Treating the Wage as a Last Step
When the wage analysis is left until recruitment is drafted or the offer is made, two bad things happen. Either the determination comes back higher than the employer budgeted and the case stalls, or the requirements were set without regard to the wage and now the job description, the recruitment, and the wage tell three different stories. Both are expensive. A new determination means new processing time; reframing the role can mean re-recruiting.
Do the Analysis at Intake
The practices that run clean PERM cases settle the SOC code and wage-level analysis before they draft anything. At intake they confirm the duties, the minimum requirements, the worksite, and the foreign worker's qualifications — and they check that those four things produce a wage the employer will actually pay. If they do not align, that is a conversation to have on day one, when the options are still open, not after a determination is in hand.
- Confirm the real minimum requirements, not the ideal ones.
- Map duties to a SOC code that an auditor would also choose.
- Pressure-test the wage level against the budget before recruitment.
- Make sure the foreign worker meets the requirements as stated — no more, no less.
Run PERM cases that hold up.
GentleCase keeps the SOC code, wage level, requirements, and recruitment on one connected record, so the wage analysis happens at intake and the audit file defends itself. Book a walkthrough of your PERM workflow.
