The H-1B visa program remains one of the most closely monitored and data-driven systems within U.S. immigration law. Employers filing petitions under this category must comply with strict wage, reporting, and record-keeping rules that are supported by an extensive set of public datasets. These datasets, often referred to collectively as the H-1B employer database, are published by both the U.S. Citizenship and Immigration Services (USCIS) and the Department of Labor (DOL), offering insight into approvals, denials, job classifications, salary levels, and employer activity.

What this article is about:
This guide explains how employers and HR compliance teams can access, interpret, and apply H-1B data for workforce planning, pay benchmarking, and compliance management. It outlines how the official databases work, what information they provide, and how to integrate that data into internal systems to reduce risk and improve transparency, with attention to current policy concepts such as material change amendments, public access file (PAF) documentation, and anti-discrimination duties.

By understanding how the H-1B database functions, employers can:

• Benchmark salaries accurately against DOL prevailing wage levels and internal pay practices.
• Analyse petition approval and RFE trends by industry and occupation using USCIS Employer Data Hub releases.
• Identify regional wage differences by MSA to inform workforce location strategy and remote/hybrid arrangements.
• Strengthen audit readiness through consistent documentation practices, including timely amendments for material changes.
• Build internal dashboards to track visa status, expiry, and compliance metrics with privacy and access controls.

Section A: Understanding H-1B Data Sources

The datasets most employers call the “H-1B database” are not a single source but a constellation of official releases. Each source captures different attributes (approvals, wages, locations, occupations), is refreshed on its own cadence, and has scope limits that must be understood to avoid compliance or analysis errors. This section explains the core sources and their constraints so employers can interpret figures accurately and defensibly.

1) USCIS H-1B Employer Data Hub

The USCIS H-1B Employer Data Hub aggregates outcomes from Form I-129 H-1B petitions (both cap-subject and cap-exempt) adjudicated by USCIS. It reports approvals, denials, and withdrawals by employer (name/EIN), petition type (initial vs continuing), fiscal year, and worksite geography as reflected in the underlying LCA. The hub excludes pending cases and typically posts on a quarterly cycle that may lag one fiscal quarter.

Important scope limits: the hub does not publish wage figures, job-level detail beyond classification, reasons for denial/RFE, or a cross-reference key that ties petitions directly to specific LCAs. As a result, the hub is most reliable for trend analysis (e.g., approval ratios, initial vs continuing mix) when paired with DOL wage and worksite data.

Compliance note: treat hub statistics as directional. Use them to benchmark internal approval/RFE ratios and to prepare documentation for occupations that show higher scrutiny, but do not infer prevailing wages or pay policy from USCIS outcome data.

2) DOL OFLC LCA Disclosure Data

The Department of Labor’s Office of Foreign Labor Certification (OFLC) releases annual disclosure files of certified Labor Condition Applications (LCAs). These files include employer name and FEIN, SOC code, job title, wage level (I–IV), prevailing wage source, offered wage, full-time/part-time status, and worksite geography (city/county/state). This is the primary public source for wage benchmarking and location analysis.

Scope and caveats: the dataset lists certified LCAs only; it does not show denied or withdrawn LCAs, nor does certification guarantee USCIS petition approval. Multi-employee or multi-location LCAs can complicate interpretation. DOL may refuse certification where wage data is incomplete or FEIN verification cannot be confirmed.

Public Access File (PAF): employers must retain documentation of the prevailing wage source and wage rate in the PAF within one working day of filing, and keep it for the required retention period. Analysts should confirm that disclosure-file entries align with internal PAF records.

3) Prevailing Wage Data (BLS OES) vs Offered Wage

Prevailing wage determinations for H-1B generally use the Bureau of Labor Statistics Occupational Employment Statistics (OES) data as implemented by DOL, aligned to the SOC 2018 revision taxonomy. Employers must pay the higher of the prevailing wage or the actual wage paid to similarly employed workers. Comparing the offered wage on the certified LCA to the OES-based prevailing wage for the correct SOC and area is the lawful way to verify wage compliance.

Practice points: confirm the SOC code reflects the job’s primary duties (not just its title); confirm the wage area (MSA/county) matches the place of employment; and record the exact wage source/version in the PAF so audits can validate your figures against the then-current OES dataset.

4) PERM Data vs LCA Data

PERM (permanent labor certification for green cards) and H-1B LCAs serve different purposes and rely on distinct evidentiary standards. PERM filings often reflect longer-term roles with elevated requirements and, in practice, higher prevailing wage determinations. Using PERM data to benchmark H-1B salaries can overstate required wages. For H-1B pay policy and filings, rely on the LCA (and its underlying prevailing wage) for the specific SOC and worksite.

5) Identifiers and Codes (FEIN, NAICS, SOC, MSA)

Accurate linkage and analysis depend on consistent identifiers. FEIN distinguishes entities that share similar names; NAICS clarifies industry context; SOC codes map duties to the correct occupation and wage grid; and MSA/county anchors the geographic wage area. Internally, maintain crosswalks from company job architectures to SOC codes, and store worksite geocodes to avoid errors when employees move between locations or into hybrid/remote patterns.

Quality controls: deduplicate on FEIN + SOC + worksite + LCA number where available; reconcile HRIS titles to SOC duty statements; and flag records where the offered wage falls below the prevailing wage for the same SOC/area/level.

6) Data Gaps and Common Pitfalls

• Job title variance: inflated or vendor-specific titles distort comparisons; anchor to SOC duties.
• Multiple LCAs per role: common in project consulting; interpret ranges cautiously.
• Remote/hybrid worksites: wage areas are based on where work is performed; verify LCA coverage when home or client sites change.
• Update lags: USCIS posts quarterly; OFLC discloses annually; align dashboards to these cadences.
• No universal key: USCIS and DOL files lack a shared unique identifier; expect approximate joins and validate with internal case numbers.

Section A Summary: The H-1B “database” is an ecosystem of complementary sources. USCIS outcomes inform adjudication trends, while DOL disclosure files and OES wage tables govern lawful pay and location analysis. Understanding scope limits, update cycles, and identifier hygiene is foundational to compliance-grade benchmarking and defensible reporting.

Section B: Practical Use Cases for Employers

For employers managing H-1B programs, data becomes valuable when transformed into insight. The official datasets can inform pay equity reviews, headcount planning, location strategy, and risk forecasting. This section explains how employers can operationalise H-1B data for compliance and strategic advantage.

1) Salary Benchmarking

Benchmarking begins with aligning internal job titles to correct SOC codes and corresponding prevailing wage areas. Employers can compare offered wages on certified LCAs against DOL wage levels I–IV and market medians. Consistency across filings helps demonstrate good-faith compliance with 20 CFR §655.731, which requires payment of the higher of the prevailing or actual wage.

Best practice: record the prevailing wage source and wage level in the PAF; verify OES dataset year; and confirm that hybrid or remote employees are assigned the correct worksite geography. Use disclosure data to flag any offered wage below prevailing benchmarks and correct before submission.

2) Headcount and Cap Planning

The USCIS Employer Data Hub’s breakdown of initial versus continuing employment filings helps employers project upcoming renewals and max-out timelines (six-year statutory limit, subject to AC21 extensions). Analysing prior fiscal-year patterns enables resource allocation between cap-subject and cap-exempt roles.

Planning tools: integrate approval/denial ratios into workforce dashboards; tag petitions by fiscal year and type; and use expiry alerts at 90/60/30-day intervals to prevent lapses. Include portability and AC21 extension flags to maintain uninterrupted authorisation.

3) Location Strategy

H-1B wages vary substantially across Metropolitan Statistical Areas (MSAs). Employers using hybrid or remote models must ensure LCAs reflect the physical place of employment. Comparative analysis of OFLC wage data helps identify compliant, cost-efficient locations for expansion while avoiding underpayment risks.

Legal reminder: under Matter of Simeio Solutions (2015), any move outside the area of intended employment listed on the certified LCA generally requires an amended LCA and H-1B petition. Short-term placements of 30 days (up to 60 in limited cases) may qualify for the exemption in 20 CFR §655.735, provided all conditions are met and documentation retained.

4) Vendor and Third-Party Placement Monitoring

For consulting or project-based employers, LCAs referencing third-party worksites must match the employee’s actual location. DOL disclosure data reveals worksite cities and counties, allowing verification of consistency between filed and actual deployments.

Governance tip: maintain a register of client worksites linked to corresponding LCAs and contracts. Mismatches or expired LCAs at client locations are high-priority compliance risks, particularly during FDNS site visits.

5) RFE and Risk Forecasting

Patterns in USCIS data can help predict increased scrutiny. High RFE rates for certain SOC categories (for example, Computer Systems Analyst) indicate where officers question specialty occupation or degree relevance. Tracking such metrics allows employers to reinforce petition narratives before filing.

Action point: use historical employer-level data to compute RFE ratios by occupation and prepare documentation (e.g., degree equivalency, task correlation charts) addressing frequent inquiry themes.

6) Budgeting and Cost Modelling

Integrating wage, fee, and legal-cost data yields an accurate financial view of the H-1B program. Employers can forecast costs per employee, model location-based wage differentials, and project overall petition spend by fiscal year. Cross-referencing DOL wage levels against payroll data ensures ongoing parity and controls exposure to back-pay liability.

Internal controls: link petition and cost data; reconcile annually against USCIS fee changes; and preserve cost analyses for three years post-employment to evidence reasonableness in audits.

Section B Summary: Practical use of H-1B data turns compliance into foresight. Salary benchmarking secures wage integrity, headcount analytics enable timely filings, and risk trend tracking prepares employers for policy fluctuations. Structured interpretation of official datasets empowers HR and legal teams to anticipate and document every compliance obligation.

Section C: Compliance, Governance & Risk

The H-1B framework intertwines immigration control with labor standards enforcement. Employers who understand how public data reflects compliance obligations can proactively manage wage, amendment, and anti-discrimination risks. This section translates data awareness into concrete governance actions.

1) LCA Compliance Obligations

Each H-1B petition must rest on a certified Labor Condition Application (LCA) filed with the Department of Labor. Employers attest to paying required wages, preserving fair working conditions, avoiding strikes, and posting notice at the worksite in line with 20 CFR §§655.730–655.734. A compliant Public Access File (PAF) must be created within one working day of filing and include the certified LCA, wage rate statement, prevailing wage documentation, and posting proof.

Verification: Cross-check OFLC disclosure entries with internal records to confirm certification status and wage level alignment. Because disclosure data shows certified cases only, employers should independently track any withdrawn or rejected LCAs to maintain a full audit trail.

2) Wage Obligations and Nonproductive Status

Under 20 CFR §655.731(c)(7), H-1B workers must receive full wages even during nonproductive periods caused by the employer, a concept often called “benching.” The only lawful exception appears in §655.731(c)(9), where the lack of work results from voluntary leave or personal circumstances beyond the employer’s control. Employers should maintain written records identifying any unpaid nonproductive time and the reason.

Integrating payroll data into the internal H-1B database helps flag wage dips below certified levels, triggering compliance alerts. Wage adjustments following promotions or location changes should be reviewed against prevailing wage updates to ensure continued conformity.

3) Material Change and Amendment Requirements

A material change in an H-1B worker’s terms of employment—such as new worksite, duties, or wage—requires an amended petition under Matter of Simeio Solutions, 26 I&N Dec. 542 (AAO 2015). Employers failing to amend risk invalidating status. When changes involve new geographic areas, an amended LCA and H-1B petition must be filed before relocation.

Short-term placements: under 20 CFR §655.735, certain assignments of up to 30 days (or 60 days for travelers maintaining a U.S. base of operations) may proceed without new LCAs if all criteria are met and documentation is retained. A database-driven alert system can ensure amendments are filed promptly once material changes exceed permissible thresholds.

4) Employer–Employee Relationship Standards

USCIS requires evidence that the petitioner maintains control over the H-1B employee’s duties and supervision, even at client sites. Data patterns—such as frequent third-party worksite filings—can signal increased scrutiny. Employers must maintain contracts, Statements of Work, and supervision records demonstrating authority to assign, evaluate, and terminate employment.

FDNS coordination: site inspectors may contact end clients to verify placement details. Inconsistent contract language or outdated LCAs invite compliance inquiries. Maintain uniformity across petition documents and client agreements.

5) FDNS Site Visit Readiness

The Fraud Detection and National Security (FDNS) directorate verifies petition accuracy through unannounced inspections. Officers compare the employee’s actual worksite, duties, and wage to certified LCA data. A well-maintained internal H-1B database enables employers to instantly retrieve LCAs, wage proofs, and assignment letters, providing auditors with prompt, accurate responses.

Governance measure: retain electronic audit logs showing who updated or accessed immigration records. Such logs, preserved for three years post-employment, demonstrate compliance integrity under DOL and DHS oversight.

6) Anti-Discrimination and Fair Recruitment

Section 274B of the Immigration and Nationality Act prohibits discrimination based on citizenship or immigration status in hiring, firing, or recruitment. Employers must ensure equal access to positions for U.S. citizens and work-authorised individuals. Wage offers must be consistent across candidates of different nationalities where qualifications are equivalent.

Compliance controls: post the Department of Justice Immigrant and Employee Rights (IER) anti-discrimination notice in hiring areas and onboarding systems; maintain documented, neutral selection criteria; and train recruiters to avoid preference statements in job adverts. The DOJ actively investigates violations where H-1B sponsorship or nationality is used as a hiring filter.

Section C Summary: Public data and regulatory duties intersect. By linking USCIS and DOL information with internal payroll, HRIS, and case systems, employers can demonstrate continuous compliance. Proper amendment tracking, wage documentation, and anti-discrimination governance establish a defensible posture against audits or enforcement actions.

Section D: Building an Internal H-1B Database & Dashboards

Public data alone offers limited protection unless paired with disciplined internal record-keeping. Employers that centralise immigration, HR, and payroll information into an internal H-1B database gain real-time visibility into compliance risk, costs, and workforce continuity. This section outlines how to design, govern, and leverage such systems lawfully.

1) Core Data Schema

An effective H-1B database must capture all elements required for statutory reporting and audit defence. The recommended schema includes:

• Employee record: name, ID, role title, start date, status (cap-subject or exempt).
• Petition details: receipt number, filing type, validity period, decision outcome, RFE type.
• LCA information: SOC code, wage level, prevailing wage source, offered wage, MSA.
• Worksite information: address, city, state, client if applicable.
• Audit triggers: amendment indicators, max-out dates, nonproductive alerts.

Legal note: the database should include wage and prevailing wage records corresponding to each certified LCA and retain them for the statutory period required under 20 CFR §655.760.

2) Data Pipeline and Integration

Accuracy depends on integrating trusted data sources. Employers should create automated feeds from:

• USCIS Employer Data Hub – for approval/denial statistics.
• DOL OFLC disclosure data – for certified LCA details.
• Internal HRIS and payroll – for real-time wage and worksite updates.
• Attorney or case management systems – for petition and RFE records.

Deduplicate records using FEIN, employee ID, or petition receipt number. Where systems overlap, maintain reconciliation logs to show that data integrity checks are performed regularly. These records can be critical evidence during DOL or FDNS audits.

3) Quality Control and Governance

Data accuracy and confidentiality underpin compliance. Employers should designate a data custodian responsible for validating entries, enforcing version control, and managing retention under the Privacy Act of 1974. Access should be restricted to authorised personnel with audit trails preserved for at least three years post-employment.

Governance standards: implement change logs, encryption of personally identifiable information (PII), periodic quality audits comparing internal records with certified LCAs, and scheduled deletion protocols once retention periods expire.

4) Analytics and Key Performance Indicators (KPIs)

Transforming the database into a decision tool requires defined metrics. Typical H-1B KPIs include:

• Approval and RFE rates by job family, business unit, or location.
• Time-to-file and cycle time for petitions.
• Expiry forecasts for visas, LCAs, and I-94s.
• Average wage differentials (offered vs prevailing).
• Regional cost variance and wage distribution.

Quarterly dashboards aligned with USCIS data releases and annual BLS wage updates enable continuous monitoring. These metrics can be presented to HR and finance leadership as part of compliance and budget reports.

5) Automation and Alerts

Automation reduces manual error. Employers should configure alert systems for key triggers such as:

• Upcoming LCA or petition expiry (90/60/30-day tiers).
• Employee approaching six-year H-1B limit.
• Material duty or location changes requiring amendments.
• Nonproductive status exceeding permissible duration.

Integrating these alerts with calendar and case systems ensures timely action, preventing unlawful employment after expiry and maintaining compliance continuity across departments.

6) Executive Reporting and Oversight

Senior management should receive periodic reports summarising immigration program health. Dashboards can highlight:

• Quarterly compliance heatmaps showing exposure by department or geography.
• Variance between budgeted and actual petition costs.
• Forecasts of cap-subject needs and upcoming renewal volume.

Governance value: executive visibility reinforces accountability. Integrating financial, compliance, and workforce analytics transforms H-1B management from an administrative task into a strategic risk-control function aligned with business planning.

Section D Summary: A structured internal H-1B database converts static data into a living compliance system. Automation, privacy safeguards, and executive oversight produce a defensible audit posture and allow employers to plan with precision while meeting every statutory and documentary duty.

FAQs: H-1B Employer Data & Salary Database

Employers frequently encounter complex questions when using H-1B datasets for wage analysis, filings, and internal reporting. The following FAQs clarify common issues with reference to USCIS, DOL, and DOJ guidance.

1) What is the difference between prevailing wage and offered wage in LCA data?

The prevailing wage is the legally required minimum salary for a given occupation and location, established by the Department of Labor using OES or an approved alternate source. The offered wage is the rate the employer certifies on the LCA. Under 20 CFR §655.731, the H-1B worker must be paid the higher of the two. Employers should retain documentation of both figures in the PAF for audit defence.

2) How reliable are third-party “salary databases” compared with OFLC and USCIS sources?

Commercial pay surveys may assist in market benchmarking but are not authoritative for compliance. Only OFLC disclosure data and BLS OES wage tables are officially recognised for prevailing wage purposes. Private datasets can supplement internal compensation planning but must not replace statutory wage sources in filings or audits.

3) Can we use the H-1B database to predict our approval odds?

Historical data from the USCIS Employer Data Hub can indicate relative approval and RFE rates by occupation, employer, or fiscal year, but cannot guarantee outcomes. Use this intelligence to strengthen documentation for categories showing higher scrutiny—such as those with high RFE incidence—to mitigate risk.

4) How do remote or hybrid roles affect SOC, wage area, and amendment duties?

The wage area is determined by where the employee physically performs work. A shift to a new location outside the certified LCA’s area of intended employment typically requires both a new LCA and an amended petition, per Matter of Simeio Solutions (2015). Remote work policies must document each worksite and ensure payroll and tax records align with certified geographic wages.

5) When does a location or duty change require a new LCA or H-1B amendment?

An amendment is required when the change constitutes a material change—for example, relocation to a different MSA, a substantial shift in duties altering the SOC code, or significant variation in hours or salary. Minor project changes can be documented internally without refiling. When uncertain, consult counsel; failure to amend can invalidate status.

6) How do we benchmark new roles when titles don’t match SOC labels?

Align the position with the SOC code that best reflects its primary duties, not its title. The DOL’s O*NET database lists example tasks for each occupation. For hybrid roles, choose the SOC representing the highest level of responsibility. Maintain written rationale in the PAF to justify your SOC selection in case of audit.

7) What are the red flags that tend to trigger RFEs?

• Degree-field mismatch with the claimed specialty occupation.
• Job descriptions lacking detailed technical duties.
• Ambiguous employer–employee supervision at client sites.
• Low wage levels inconsistent with required qualifications.
• Repeated use of generic or recycled LCAs across varied roles.

Tracking these issues internally helps identify petition categories at higher adjudicatory risk and pre-emptively reinforce supporting documentation.

8) How should we evidence the employer–employee relationship for client-site roles?

Maintain contracts, assignment letters, timesheets, and performance reviews proving the petitioner’s right to control, supervise, and reassign the employee. These documents establish that the relationship meets the definition under 8 CFR §214.2(h)(4)(ii). Keep records consistent across client agreements and USCIS filings to avoid contradictions during site visits.

9) What belongs in the Public Access File and how long must it be kept?

Per 20 CFR §655.760, each PAF must contain the certified LCA, wage rate, prevailing wage source, posting proof, and benefits summary. It must be available for inspection within one working day of filing and retained for at least one year beyond the last date of employment under that LCA. Separate PAFs are required for each certified LCA, even for the same employee.

10) How often should we refresh our internal H-1B dashboards?

Refresh quarterly to align with USCIS Employer Data Hub updates, and annually when BLS releases new OES wage data. Automated ETL processes ensure alerts and analytics stay current, reducing the risk of relying on outdated figures during filings.

FAQs Summary: Understanding statutory wage sources, amendment triggers, and audit documentation duties allows employers to use H-1B data responsibly. Regular updates, correct SOC mapping, and proactive risk analysis ensure lawful, evidence-based immigration program management.

Conclusion

Using official H-1B data effectively transforms immigration compliance from a reactive obligation into a proactive management system. Employers that understand how USCIS, DOL, and BLS datasets intersect can forecast costs, benchmark salaries, and evidence compliance with confidence during audits or site visits.

Each dataset serves a unique purpose: the USCIS Employer Data Hub signals adjudication trends; DOL disclosure files validate wage compliance; and BLS OES wage tables define prevailing wage baselines. Integrating this data into internal dashboards allows HR, legal, and finance teams to maintain visibility over every element of the H-1B lifecycle.

• Map every role to the correct SOC code and prevailing wage area.
• Maintain Public Access Files within one working day of each LCA filing.
• Document employer–employee relationships for hybrid or offsite roles.
• Set 90/60/30-day alerts for LCA, I-94, and petition expiries.
• Restrict database access per Privacy Act standards and log all updates.

Embedding these measures ensures employers meet the documentation, wage, and record-keeping requirements of 20 CFR §§655.730-760 and USCIS guidance. A disciplined, data-driven approach builds a defensible position under FDNS or DOL scrutiny while improving equity and transparency across the workforce.

Conclusion Summary: An internal H-1B database should be more than an archive—it should function as a compliance engine that tracks, analyses, and governs the entire visa program. By merging statutory data with internal oversight, employers can manage risk, support fair pay, and plan strategically within the boundaries of U.S. immigration law.

Glossary

Useful Links