For H-1B & employment practices
Five artifacts. One wage. Zero contradictions.
The LCA, the I-129, both support letters, and the Public Access File must all state the same wage, SOC code, and worksite. In ParaLeagle, they can't do anything else.
one wage · one SOC · one worksite
- I-129 (281 fields)
- LCA / ETA-9035E (107 fields)
- Attorney letter
- Company letter
- Public Access File
Failure mode
this is what draws an RFE.
The PERM workflow, in active development.
- ETA-9141 prevailing wage
- Recruitment tracking with dated evidence
- Audit-file assembly
- ETA-9089
PERM isn't a form — it's a choreography of deadlines and evidence. As we build it out, the same reminder engine and checklists that chase your family documents will run the recruitment steps and build the audit file, so the wage that DOL certifies is the wage USCIS reads. One fact store, both agencies.
50 petitions × ~6.6 hours of assembly ≈ 330 hours ≈ eight work-weeks of one paralegal's year, compressed into a spring window. (Model estimate — assumptions published.) The firms that pilot in the fall file differently in the spring.
RFE risk read
Before an H-1B files: a risk level (LOW / MEDIUM / HIGH), predicted RFE topics, wage benchmarks, comparable AAO non-precedent decisions from a proprietary corpus, evidence recommendations — and the engine's own disclosure of where its data is thin. Decision support, not outcome prediction. To our knowledge, no other attorney platform does this.
of a business practice's total week addressed
30–35% working band · model estimate — assumptions published. ~90% of the H-1B set covered today; the PERM workflow is in active development.