At this year's WERC Global 2026 conference in Chicago, one of the most important themes across several immigration compliance sessions was that employers are beginning to discover that their compliance programs may not be as comprehensive or reliable as they previously believed.

For years, many companies operated under the assumption that their H-1B and PERM compliance processes were working properly. Labor Condition Applications (LCAs) were filed, Public Access Files (PAFs) were maintained, PERM recruitment was conducted, and immigration attorneys provided instructions to HR teams. If there were no complaints or government investigations, there was little reason to question whether those processes were functioning as intended.

But the absence of government scrutiny does not necessarily mean a company has been compliant.

That distinction came up repeatedly during discussions about Department of Labor (DOL) enforcement, internal immigration audits, artificial intelligence, and coordination among federal agencies.

Three particularly sessions were relevant: Advanced: Auditing and Compliance, AI Meets Immigration Compliance: A Playbook for the Modern Mobility Team, and Immigration Compliance in the Crosshairs: Navigating DOJ IER, DOL, and EEOC Investigations.

Together, they highlighted an important shift in how employers should approach immigration compliance. Rather than treating documentation as something to collect and store, companies increasingly need to verify that their records are complete, accurate, consistent, and capable of withstanding scrutiny.

For employers sponsoring H-1B workers or pursuing PERM labor certification, that means taking a much closer look at the processes they may have relied upon for years.

DOL Immigration Audits Are Exposing Gaps in Previously Accepted Compliance Processes

One of the strongest takeaways from the conference was that having an immigration compliance program is not the same as knowing whether that program works.

This was especially apparent during the Advanced: Auditing and Compliance session, which addressed how companies can conduct internal reviews, prioritize findings, and improve their immigration compliance processes.

The panel, moderated by Carol Williams of Williams Immigration, included Ashlee Drake Berry of Casium, Michele Frangella of Charles River Associates, and Dominique Lelonek of Acuity.

A recurring question was whether employers are maintaining the right documentation and whether that documentation would actually stand up to an investigation.

Consider a company that sponsors hundreds of H-1B employees each year. Its immigration counsel prepares LCAs and sends posting instructions to the appropriate HR contacts. Someone at the company is responsible for completing the postings and maintaining the PAFs.

On paper, the process looks reasonable.

But an internal audit may reveal that some notices were posted at the wrong locations, posting confirmations were never returned, or supporting PAF documents were stored in separate systems.

The employer may have assumed those steps were completed because nobody had previously challenged the process.

This is one reason proactive immigration compliance audits are becoming increasingly important. Employers should not simply confirm that a PAF or PERM audit file exists. They should verify whether the documents inside it are complete, accurate, and consistent with applicable legal requirements.

What Should Employers Review During an H-1B Compliance Audit?

Under 20 CFR § 655.760, H-1B employers must make certain LCA-related documentation available for public examination.

A compliant PAF generally includes the certified LCA, wage-related documentation, an explanation of the employer's actual wage system, prevailing wage information, benefits documentation, and evidence of the required LCA notice. Additional requirements may apply depending on the employer's circumstances.

An internal review should therefore look beyond whether a folder labeled "PAF" exists.

Employers should consider whether:

• Every applicable LCA has a corresponding, complete PAF.
• Wage and benefits documentation is accurate and current.
• Required LCA notices were properly provided and documented.
• Posting records identify when and where notices were made available.
• Records are accessible for public inspection and government review.
• Retention schedules and any applicable preservation obligations are being followed.

The purpose is to identify discrepancies before an investigator does.

This is also why employers should consider comparing their internal LCA records against the government's public LCA data. A company may discover certified LCAs that do not appear in its internal inventory, or PAFs that are missing supporting documents.

The underlying issue is straightforward: instructions and reminders are not substitutes for documented compliance.

PERM Recruitment Requirements May Change as DOL Reexamines Traditional Hiring Practices

Another major topic at WERC Global was the possibility of significant changes to the PERM labor certification process.

During the Immigration Compliance in the Crosshairs session, panelists discussed the prospect of modernizing PERM recruitment requirements to better reflect how employers actually recruit workers today.

Traditional PERM recruitment procedures can involve newspaper advertisements and other methods that do not always resemble an employer's ordinary hiring practices.

Meanwhile, many companies primarily recruit through their websites, LinkedIn, electronic job boards, and digital applicant-tracking systems.

Panelists discussed the possibility that future PERM regulations could place greater emphasis on these modern recruitment channels and on whether recruitment is conducted fairly and consistently.

These were discussions about potential regulatory changes, not confirmation that new requirements have taken effect. Any future proposal, final rule, or other agency action would need to be evaluated on its own terms.

Nevertheless, employers should pay attention to the underlying compliance concern.

PERM Recruitment Should Be Consistent With Legitimate Hiring Practices

One point raised during the conference was that PERM recruitment should not be treated as an entirely separate hiring exercise disconnected from how the employer normally evaluates U.S. applicants.

Under 20 CFR § 656.10, employers make several important attestations, including that the job opportunity is clearly open to U.S. workers and that U.S. applicants are rejected only for lawful, job-related reasons.

That means compliance involves more than publishing advertisements and retaining screenshots.

Employers should examine whether their recruitment procedures give qualified applicants a meaningful opportunity to apply, whether the hiring criteria are consistent with the position, and whether applicant evaluations are documented appropriately.

This is especially important when PERM recruitment occurs after layoffs or workforce restructuring.

An employer may satisfy the technical advertising requirements but still face questions about the broader recruitment process, including how applicants were evaluated and whether the position was genuinely available.

The conference discussion reinforced the importance of reviewing those processes before new requirements or enforcement questions arise.

PERM Notice of Filing Compliance Is Another Area Worth Reviewing

Separate from recruitment advertising, employers must also comply with applicable PERM Notice of Filing (NOF) requirements.

Under 20 CFR § 656.10(d), where workplace posting is required, the notice generally must remain posted for at least 10 consecutive business days within the prescribed period before filing.

Employers must also use applicable in-house media, whether electronic or printed, in accordance with their normal procedures for recruiting similar positions.

For companies that routinely advertise internal opportunities through employee portals, intranets, or internal job boards, this can create an additional documentation obligation.

Importantly, electronic in-house media posting does not automatically replace the required physical workplace posting.

As employers prepare for potential PERM modernization, reviewing existing recruitment and NOF procedures is a practical place to start.

AI Is Becoming a Useful Immigration Compliance Tool, but It Cannot Replace Human Review

Artificial intelligence was another major topic at the conference, particularly in discussions about how immigration and global mobility teams can manage large volumes of data while preparing for audits and investigations.

During AI Meets Immigration Compliance: A Playbook for the Modern Mobility Team, speakers discussed how AI can support immigration operations, identify potential compliance issues, and improve visibility into employer records.

One particularly useful application involves H-1B Public Access Files.

Instead of manually opening hundreds of PAFs to determine whether each contains the required documentation, a company may use AI-assisted tools to inventory documents, identify potentially missing records, and flag inconsistencies for further review.

Another application involves comparing an employer's internal LCA inventory with publicly available DOL data.

This can help identify possible discrepancies between the LCAs the government has certified and the records the employer maintains.

AI-Assisted PAF Audits Can Reveal Missing Documents and Inconsistent Records

The potential benefits of AI-assisted compliance reviews include identifying missing documents, classifying records, comparing information across systems, and spotting patterns that may warrant investigation.

For example, if a company experiences several government site visits involving employees in similar roles or at the same location, reviewing those patterns could help the immigration team identify other employees who may need additional preparation.

Likewise, automated checks could flag inconsistent job titles, worksite information, or wage-related records for legal review.

But the speakers also highlighted an important limitation: AI can make mistakes.

An AI system might incorrectly report that a required document is missing because it cannot recognize a scanned signature. It might provide an inaccurate count of H-1B employees because it searched an incomplete dataset or misunderstood the request.

These errors illustrate why AI-generated findings must be verified.

The better approach is to use technology to identify possible issues while relying on qualified professionals to interpret the results, investigate discrepancies, and make legal determinations.

AI Compliance Tools Also Require Data Governance

Immigration records often contain sensitive personal and employment information.

Before introducing AI into compliance workflows, employers should understand where the data comes from, who can access it, how it is processed, and whether the system is appropriate for the information involved.

A useful AI compliance tool must operate on reliable data. If an employer's underlying LCA inventory is incomplete, the system may produce misleading results regardless of how sophisticated its analysis appears.

This leads to a broader lesson: AI works best when employers already have organized records and consistent processes.

Automation can strengthen a compliance program, but it cannot compensate for missing documentation or unclear internal responsibilities.

Coordinated Government Investigations Require a Company-Wide Compliance Strategy

The Immigration Compliance in the Crosshairs session addressed another important development: the increasing intersection of immigration enforcement with broader workforce and employment compliance.

The session featured Kelli Duehning of BAL, Alexander Maugeri of Jones Day, and April Williams of WilmerHale.

One of the central discussion points was that employers may receive inquiries from different government agencies concerning overlapping employment practices.

These can include the Department of Labor, the Department of Justice's Immigrant and Employee Rights Section (IER), and the Equal Employment Opportunity Commission (EEOC).

Although these agencies have distinct responsibilities and legal authorities, their investigations can involve related records, hiring decisions, and employment practices.

Inconsistent Responses Can Create Additional Problems

Consider a company that receives a government inquiry about recruitment practices.

Its HR department gathers documents and provides a response. Several months later, a different agency asks questions about overlapping employment decisions.

If the immigration team, HR department, legal department, and business leaders are not coordinating, their responses may describe the same events differently.

Even when those differences are unintentional, inconsistent statements can create credibility problems or require further explanation.

The panel emphasized the importance of understanding the broader scope of an investigation, coordinating among relevant stakeholders, preserving documents, and conducting an appropriate internal review before responding.

That does not mean delaying responses beyond applicable deadlines. It means ensuring that the company understands the facts and has a coordinated response strategy.

Some organizations may benefit from establishing an internal risk committee or similar cross-functional group that can quickly evaluate new immigration policies, investigations, and compliance concerns.

Such a group might include immigration counsel, HR, global mobility, employment counsel, and other relevant business stakeholders.

The goal is to avoid treating each government request as an isolated administrative issue when it may have implications across the organization.

Proactive H-1B and PERM Compliance Requires Better Systems, Not Just More Checklists

Across all three sessions, the most consistent takeaway was that employers need to become more proactive.

Many immigration compliance obligations are relatively straightforward when considered individually.

An employer must provide LCA notice, maintain a PAF, retain supporting documentation, and comply with applicable PERM recruitment and Notice of Filing requirements.

But these obligations become more complicated when a company sponsors hundreds or thousands of foreign national employees across multiple offices, remote locations, and third-party worksites.

A process that works for ten filings may become unreliable when scaled to a thousand.

Electronic LCA Posting Must Be Accessible and Documented

Under 20 CFR § 655.734, employers must provide required LCA notice to affected workers through an authorized method.

For electronic posting, simply placing a notice somewhere online is not necessarily sufficient.

DOL Field Assistance Bulletin 2019-3 explains that affected workers must be able to access the electronic notice and know where to find it.

This is particularly relevant when H-1B employees work remotely or at third-party client locations, where the population entitled to notice may extend beyond the petitioning employer's own workforce.

Employers therefore need to consider not only whether a posting occurred, but whether it was accessible to the appropriate workers and whether the company can demonstrate compliance afterward.

Public Access Files Must Be Complete and Available for Inspection

PAFs present a similar challenge.

The employer may have a certified LCA, but the PAF can still be incomplete if the wage documentation, benefits statement, actual wage memorandum, or posting evidence is missing.

Records also need to be available for public inspection as required by regulation.

For large employers, maintaining these files through shared drives, spreadsheets, and email chains can create unnecessary administrative work and make it difficult to verify completeness.

The same is true for record retention.

Employers should understand how long records must be retained, when applicable retention periods end, and whether documents must be preserved because of an ongoing investigation or other legal obligation.

A reliable compliance process should make those records easy to locate, review, and produce without requiring employees to reconstruct events from years earlier.

How LaborLess Helps Employers Strengthen H-1B and PERM Compliance

The discussions at WERC Global reinforced exactly why we built LaborLess.

Employers and immigration law firms need more than instructions explaining what must be done. They need practical systems that help ensure routine compliance tasks are completed, documented, and accessible when questions arise.

LaborLess helps address several of these administrative challenges through:

• Electronic LCA posting: Centralized posting workflows, automated posting removal, and documentation of posting activity, including support for remote and third-party worksite scenarios.
• Automated PAF generation and management: Creation and organization of Public Access Files, helping employers and law firms maintain required supporting records in a centralized environment.
• Detailed audit logs: Records of relevant posting and document activity, including timestamps and user actions, to support internal reviews and government inquiries.
• PAF retention management: Tracking retention periods and supporting automated destruction according to configured schedules, subject to applicable preservation requirements.
• PERM Notice of Filing posting: Electronic NOF posting workflows and supporting evidence to help employers document applicable in-house media posting requirements.

For immigration law firms, these capabilities also provide greater visibility into the administrative compliance processes their corporate clients are responsible for completing.

Instead of sending posting instructions and hoping that everything was handled correctly, law firms and employers can work through a more centralized, documented process.

Technology does not replace immigration counsel, determine whether PERM recruitment was lawful, or guarantee that a company will pass an audit.

It can, however, reduce preventable administrative errors and make it easier to verify that required steps were completed.

That distinction matters in the current enforcement environment.

The Main Takeaway from WERC Global 2026: Review Immigration Compliance Before the Government Does

The biggest takeaway from WERC Global was not that every employer has a major compliance problem - it was that many employers may not actually know whether their immigration compliance processes are working as intended.

Employers should be asking whether their PAFs are complete, whether LCA postings were properly documented, whether PERM recruitment and NOF procedures are consistent, and whether their records could withstand an internal or government review.

The companies that address these questions proactively will be better positioned to respond to whatever comes next.

At LaborLess, our goal is to make the administrative side of H-1B and PERM compliance easier to manage, document, and verify.

If your organization or immigration law firm is reviewing its LCA posting, PAF management, or PERM Notice of Filing processes, visit www.laborless.io or reach out to our team to learn how we can help.

Frequently Asked Questions About DOL Immigration Compliance

What are the biggest H-1B compliance risks for employers in 2026?

Common risks include incomplete Public Access Files, improperly documented LCA postings, inaccessible electronic notices, inconsistent wage documentation, and failures to maintain records for the required period. Employers with remote workers or employees at third-party worksites may face additional posting challenges. These risks are governed by existing H-1B regulations, regardless of whether new enforcement initiatives are announced.

What should employers review during an internal H-1B compliance audit?

Employers should verify that their LCAs and PAFs are complete, that wage and benefits documentation is accurate, and that required notices were properly provided. They should also examine posting evidence, record retention, and consistency between internal records and DOL data. The applicable PAF requirements are outlined in 20 CFR § 655.760.

Are PERM recruitment requirements changing in 2026?

PERM modernization was a significant topic at WERC Global 2026. Panelists discussed potential changes that could place greater emphasis on modern electronic recruitment channels and fair recruitment practices. However, conference discussions do not establish new legal requirements. Employers should continue following the regulations currently in effect while monitoring official DOL rulemaking.

Can AI be used to audit H-1B Public Access Files?

Yes. AI-assisted tools can help inventory PAF documents, flag missing information, compare records, and identify potential inconsistencies. However, AI findings require human verification because automated systems can misinterpret documents or generate inaccurate results. Employers should also establish appropriate safeguards for sensitive employee information.

How long must an H-1B LCA notice be posted?

When an employer uses the posting method, the required LCA notice period is at least 10 days, subject to the applicable regulatory requirements. Electronic notice must be practically accessible to affected workers, including relevant workers at third-party locations. See 20 CFR § 655.734 and DOL Field Assistance Bulletin 2019-3.

How long must a PERM Notice of Filing be posted?

Where the workplace posting requirement applies, a PERM Notice of Filing generally must be posted for at least 10 consecutive business days within the required 30-to-180-day period before filing. Applicable in-house media requirements must also be satisfied. Electronic in-house media posting does not automatically replace required physical posting. See 20 CFR § 656.10(d).

How does LaborLess help employers prepare for DOL audits?

LaborLess helps employers and immigration law firms automate electronic LCA postings, generate and maintain PAFs, preserve detailed activity logs, manage retention schedules, and document electronic PERM Notice of Filing postings. These capabilities make it easier to organize and retrieve compliance records, although legal review and broader audit preparation remain essential.

On October 16, 2026, the U.S. Departments of Justice (DOJ) and Labor (DOL) announced a major immigration enforcement settlement with Cloudera, a California-based technology company, involving allegations that the company discriminated against qualified U.S. workers during recruitment for positions sponsored through the PERM labor certification process.

The consequences were substantial: a two-year debarment from the PERM program, $1.4 million in back pay for affected U.S. workers, $600,000 in civil penalties, and additional compliance monitoring and reporting obligations. The settlement resolved allegations of unlawful recruitment practices without establishing that every allegation had been proven in court.

For immigration law firms, corporate immigration teams, and employers sponsoring foreign national workers, this is another significant reminder that the federal government is taking employment-based immigration compliance seriously.

The Cloudera settlement concerns alleged discrimination during PERM recruitment, not a failure to post H-1B Labor Condition Applications (LCAs), maintain Public Access Files (PAFs), or publish PERM Notices of Filing (NOFs). Those distinctions matter. But the case also illustrates the broader risks associated with compliance processes that are poorly implemented, inadequately monitored, or difficult to document.

And while LCA posting, PAF maintenance, and PERM NOF posting may seem like relatively minor administrative responsibilities compared with preparing an H-1B petition or employment-based green card application, they are also among the easiest obligations to mishandle.

The Cloudera PERM Settlement: What Happened and Why the DOJ Took Action

DOJ Alleged That Cloudera Used a Separate Recruitment Process That Prevented U.S. Workers From Applying

The DOJ's October 16 announcement described a coordinated enforcement resolution involving Cloudera, a Santa Clara-based data management company.

According to the government's allegations, Cloudera departed from its ordinary recruitment procedures when advertising certain positions connected to PERM labor certification applications.

For regular positions, the company used its public careers website and standard application procedures. But for positions undergoing PERM recruitment, DOJ alleged that Cloudera used a separate process that made it difficult, and in some instances impossible, for U.S. workers to apply.

The most notable allegation involved an email address designated for PERM-related applications.

According to the settlement agreement, Cloudera established an email account to receive applications from U.S. workers responding to PERM advertisements. However, that account could not receive emails from external addresses.

This meant that U.S. workers following the application instructions in the advertisements could submit their materials without those applications actually reaching the company.

DOJ also alleged that Cloudera did not advertise the relevant PERM positions through its public careers website in the same manner as comparable non-PERM positions.

The government concluded that these practices prevented certain U.S. workers from receiving fair consideration for the advertised positions. The allegations concerned recruitment activity occurring from at least March 31, 2024, through January 28, 2025.

The case is especially noteworthy because the alleged problem was not simply an incorrectly completed immigration form. It involved the actual operation of the employer's recruitment process.

An employer could have prepared advertisements, maintained recruitment documentation, and proceeded with a PERM application while still having a fundamental problem: qualified U.S. workers were unable to apply through the designated channel.

That distinction goes to the heart of employment-based immigration compliance. Having a documented process is not enough if the process itself does not function as required.

The Settlement Imposes a Two-Year PERM Debarment and $2 Million in Payments

The government's investigation led to a series of enforcement actions.

DOJ filed its discrimination complaint in April 2026, and DOL suspended processing of Cloudera's PERM applications in May. The settlement was finalized on October 13 and publicly announced on October 16.

Under the resolution, Cloudera agreed to several significant obligations:

Two-year PERM debarment: Cloudera agreed to a period of exclusion from the PERM program, following the earlier suspension of its labor certification processing.

$1.4 million back-pay fund: The company agreed to establish a fund to compensate eligible U.S. workers who were denied fair consideration.

$600,000 in civil penalties: Cloudera agreed to pay penalties to the federal government.

Enhanced compliance requirements: The company must revise relevant recruitment practices and comply with training, monitoring, and reporting obligations, including DOJ oversight extending for three years.

The agreement also requires Cloudera to conduct PERM recruitment in a manner consistent with recruitment for comparable non-PERM positions, including the use of ordinary recruitment channels and applicant-tracking procedures.

These measures demonstrate that the consequences of immigration compliance problems can extend well beyond financial penalties. They can affect an employer's ability to sponsor foreign national employees, require changes to internal hiring practices, and create years of additional government oversight.

Why the Cloudera Case Matters for Other Employers

The PERM program generally requires employers to test the U.S. labor market before sponsoring a foreign national worker for permanent employment in positions subject to labor certification.

That process must provide qualified U.S. workers with a genuine opportunity to apply and be considered.

The Cloudera case illustrates why regulators may examine not only whether recruitment was conducted, but whether it was conducted fairly and effectively.

A company might be able to produce copies of advertisements, recruitment reports, and internal instructions. Yet if the underlying application process was inaccessible, malfunctioning, or administered differently in a way that unlawfully disadvantaged U.S. workers, the existence of those documents may not establish compliance.

This is a lesson that extends beyond PERM recruitment. Employers need to understand whether their compliance procedures are actually being carried out, whether the people responsible for those procedures understand their obligations, and whether reliable evidence exists to demonstrate what happened.

For companies with substantial H-1B and PERM programs, those questions deserve attention before an investigation begins.

Federal Immigration Enforcement Is Increasing the Importance of H-1B and PERM Compliance

Project Firewall and the Cloudera Settlement Reflect a Broader Enforcement Strategy

The Cloudera settlement is part of a broader federal effort to scrutinize how employers use employment-based immigration programs.

In September 2025, DOL announced Project Firewall, an H-1B enforcement initiative emphasizing employer accountability, protection of U.S. workers, and increased coordination among federal agencies.

The initiative included expanded use of Secretary-certified investigations and collaboration among DOL, DOJ, USCIS, and other agencies. DOL specifically identified potential consequences of H-1B violations, including back wages, civil monetary penalties, and debarment.

Project Firewall focuses on H-1B compliance, while the Cloudera settlement addresses alleged discrimination during PERM recruitment. They involve different legal provisions and enforcement mechanisms, but both demonstrate that employers should expect government agencies to examine how immigration-related employment practices function in reality.

For immigration law firms, this creates an important opportunity to help corporate clients reevaluate processes that may have remained largely unchanged for years. An employer might have sophisticated immigration counsel preparing petitions and labor certifications while still relying on manual emails, spreadsheets, shared folders, and individual HR contacts to complete associated compliance obligations.

Those systems are not inherently unlawful. But they can make it difficult to identify mistakes, ensure consistent execution, or reconstruct what happened months or years earlier.

The more employees, worksites, and immigration matters an employer manages, the greater the potential for seemingly small administrative errors to accumulate.

Administrative Compliance Requirements Can Create Disproportionate Risk

Consider the difference between preparing an H-1B petition and posting the associated LCA notice.

The petition itself may involve detailed legal analysis, supporting evidence, wage determinations, and careful review by immigration counsel. By comparison, the LCA notice requirement can appear simple: make the required information available to affected workers for the applicable period and maintain evidence that notice was provided.

Yet the simplicity of the requirement can be misleading.

The employer must determine where notice is required, who needs access, how the notice will be delivered, when it must be available, and what documentation should be retained.

The same is true of PAFs and PERM Notices of Filing. These are relatively standardized compliance activities, but their execution depends on coordination among legal teams, HR departments, worksite managers, and sometimes third-party companies.

A single missed posting, incorrect date, incomplete file, or inaccessible electronic notice can create a compliance issue that might otherwise have been avoided.

This is precisely why immigration compliance technology can be valuable. It cannot eliminate every risk, but it can reduce dependence on manual follow-up and establish more reliable records of routine compliance activities.

H-1B LCA Posting Compliance: A Simple Requirement That Is Easy to Get Wrong

Electronic LCA Posting Must Reach the Workers Who Are Entitled to Notice

Under 20 CFR § 655.734, H-1B employers must provide notice of an LCA filing to affected workers through an authorized method, including physical posting or electronic notification.

For notice provided through posting, the applicable requirement is at least 10 days. Employers must also satisfy the regulation's timing requirements for notice in relation to the LCA filing.

Electronic posting can be particularly helpful for employers with remote employees or workers assigned to multiple locations. However, posting a notice somewhere online does not automatically establish compliance.

DOL's Field Assistance Bulletin 2019-3 explains that electronic notification must be practically accessible to affected workers and that those workers must know where to find it.

The guidance also addresses third-party worksites, where affected workers may include employees of a company other than the H-1B petitioner.

For example, an employer that places H-1B professionals at a client's office cannot necessarily satisfy the notice requirement by posting the LCA on an internal webpage accessible only to its own employees. The employer must consider how affected workers at the client location will receive appropriate notice.

Similarly, a publicly accessible website may not be sufficient if the intended workers have no reason to know the posting exists or cannot identify which notice applies to their worksite.

Manual LCA Posting Creates Recurring Documentation Problems

In practice, many immigration law firms and corporate immigration teams coordinate LCA postings through email.

An attorney or paralegal prepares a notice, sends it to an HR representative or worksite contact, and requests confirmation that the notice has been posted.

The recipient may then forward the notice to another employee responsible for physically posting it or placing it on an internal electronic bulletin board.

Although this process may satisfy the regulations when implemented correctly, it introduces several opportunities for mistakes.

The notice might be posted at the wrong location, displayed for an insufficient period, removed without documentation, or made available through an electronic system that affected workers cannot access.

Even when the posting was completed correctly, the employer may have difficulty locating the evidence years later.

A confirmation email stating that someone received the posting instructions does not necessarily establish that the notice was displayed properly for the required duration.

These issues become more complicated when employers manage hundreds or thousands of LCAs annually, especially across remote and third-party worksites.

The problem is not necessarily a lack of legal knowledge. It is the difficulty of consistently executing and documenting a repetitive compliance process across multiple people and locations.

Public Access File Compliance Requires More Than Storing a Certified LCA

H-1B Public Access Files Must Contain Specific Documentation

Under 20 CFR § 655.760, H-1B employers must make required LCA documentation available for public examination within one working day after filing the LCA.

A PAF is not simply a copy of the certified LCA. Depending on the employer and circumstances, required documentation includes information about the wage rate, actual wage system, prevailing wage determination, benefits, and evidence of compliance with LCA notice requirements.

Additional documentation may be required for certain employers, including H-1B-dependent employers and willful violators.

A PAF therefore brings together several separate compliance obligations.

An employer may have properly filed the LCA and paid the required wage but still have an incomplete public-access file because the wage memorandum is missing, the benefits documentation was never uploaded, or the posting evidence was stored in a separate email thread.

This creates a practical challenge during a government investigation or public inspection request. Someone must locate the file, identify missing documents, contact the relevant personnel, and determine whether the documentation can be reconstructed.

The more time that has passed since the original filing, the more difficult that process may become.

PAF Retention and Destruction Require Their Own Compliance Controls

Record retention is another area where employers benefit from having a defined process.

The PAF retention rules depend on the relevant employment and LCA circumstances, while certain underlying payroll records are subject to separate retention obligations.

Employers must therefore avoid both premature destruction of required records and uncontrolled retention that leaves large volumes of outdated documentation scattered across systems.

An organized process should identify the applicable retention period, account for relevant changes in employment circumstances, and ensure that authorized personnel can retrieve records while they must be maintained.

For immigration law firms managing PAFs on behalf of multiple corporate clients, centralized recordkeeping also reduces the administrative burden of responding to requests for historical documentation.

PERM Notice of Filing Compliance Is Distinct From Recruitment but Equally Important

PERM NOF Posting Has Its Own Regulatory Requirements

The Cloudera case concerns alleged discriminatory recruitment practices. It should not be confused with a PERM Notice of Filing violation.

Nevertheless, the settlement provides a timely reason for employers to review their broader PERM compliance procedures, including NOF posting.

Under 20 CFR § 656.10, employers generally must provide notice of a PERM filing to the appropriate bargaining representative or, where applicable, through workplace posting.

For the required workplace posting, the notice must be displayed for at least 10 consecutive business days within the prescribed period before filing the PERM application.

Employers must also satisfy applicable in-house media requirements, including electronic or printed communications used in the normal course of recruiting for similar positions.

These requirements differ from H-1B LCA posting rules. In particular, employers should not confuse the PERM NOF's 10-business-day requirement with the H-1B LCA notice period.

The NOF also has specific content requirements, and the employer must retain documentation demonstrating compliance.

PERM NOF Errors Can Occur Even When the Underlying Case Is Otherwise Well Prepared

A PERM application may involve extensive recruitment, prevailing wage analysis, and preparation of supporting documentation. Yet an error involving the NOF can still create a problem.

Examples include posting the notice for the wrong number of days, failing to account for holidays when calculating business days, using an incorrect notice, overlooking applicable in-house media requirements, or failing to retain evidence of posting.

These are not merely theoretical concerns. DOL's BALCA PERM case digest documents cases in which notice-related deficiencies contributed to denial of labor certification, including errors involving required notice content and timing.

For employers and immigration law firms handling substantial PERM volumes, the challenge is ensuring that each notice follows the appropriate process and that the supporting documentation can be produced when needed.

Electronic tools can simplify applicable electronic notice workflows, tracking, and recordkeeping. They do not eliminate any physical posting obligation imposed by the regulations.

That is why the most effective compliance approach combines technology with appropriate legal review and clear responsibility for completing each required step.

How LaborLess Helps Employers Strengthen H-1B and PERM Compliance

For nearly a decade, LaborLess has focused on helping immigration law firms and employers automate the administrative compliance processes associated with H-1B LCAs, Public Access Files, and PERM Notices of Filing.

These obligations are often treated as routine administrative work, but they involve strict timing, documentation, and recordkeeping requirements. LaborLess helps organizations manage those responsibilities more consistently and maintain evidence of compliance activities.

The platform provides several core capabilities:

- Electronic LCA Posting: Centrally manage electronic LCA notices across employer offices, remote worksites, and third-party client locations using websites, electronic bulletin boards, and QR-code-based access methods.

- Automated Posting and Takedown: Automate LCA posting periods and removal, with system-generated records documenting when notices were posted and taken down.

- Automatic Public Access File Creation: Generate and maintain PAFs alongside the LCA workflow, with centralized access to certified LCAs, wage documentation, benefits statements, posting evidence, and other required records.

- Detailed Audit Logs: Track relevant LCA and PAF activity, including user actions, document changes, and timestamps, to support internal compliance reviews and responses to government inquiries.

- PAF Retention Management: Track PAF expiration dates and automate destruction according to configured retention schedules, while allowing relevant dates to be updated when circumstances change.

- PERM Notice of Filing Management: Support electronic NOF posting workflows, automated posting and takedown, and supporting compliance documentation, while employers and counsel address applicable physical posting and other legal requirements.

- Centralized Compliance Records: Give authorized law-firm and employer personnel access to relevant records without relying on disconnected email threads, spreadsheets, or separate document repositories.

These capabilities can make a meaningful difference during an internal audit or DOL investigation.

Instead of asking several employees to reconstruct whether an LCA notice was posted, when it was removed, or where the supporting PAF documents were saved, the employer can retrieve records from a centralized platform.

LaborLess does not replace immigration counsel, conduct PERM recruitment, or determine whether an employer has satisfied every legal obligation. Its value is in automating administrative compliance steps, improving visibility, and preserving records that help demonstrate what was done and when.

Better Immigration Compliance Begins With Reliable Processes

The Cloudera settlement demonstrates the potential consequences when an employer's immigration-related hiring procedures do not operate as the law requires.

It also offers a broader lesson for companies sponsoring H-1B workers and pursuing employment-based green cards: compliance should be evaluated not only by the quality of the legal filings, but also by how reliably the employer performs the operational steps surrounding those filings.

LCA posting, PAF management, and PERM NOF posting may be small components of a much larger immigration program. Yet each has its own requirements, and each creates opportunities for avoidable mistakes.

Employers do not need to wait for a government investigation to identify weaknesses in these processes.

A practical review can begin by asking whether required notices are consistently made available to the correct workers, whether posting periods are accurately tracked, whether PAFs are complete and accessible, and whether the employer can readily produce reliable evidence of compliance.

Where the answers depend on finding old emails or asking individual employees to remember what happened, there may be an opportunity to strengthen the process.

Frequently Asked Questions About the Cloudera Settlement and Immigration Compliance

What was the Cloudera PERM settlement announced in October 2026?

On October 16, 2026, DOJ and DOL announced a settlement resolving allegations that Cloudera discriminated against qualified U.S. workers during PERM recruitment. The resolution included a two-year PERM debarment, a $1.4 million back-pay fund, $600,000 in civil penalties, and additional compliance obligations.

Why did Cloudera face a two-year PERM debarment?

DOJ alleged that Cloudera used recruitment procedures for PERM positions that prevented certain U.S. workers from applying or receiving fair consideration. One central allegation involved an email account that could not receive applications from external email addresses.

Does the Cloudera settlement involve H-1B LCA posting or Public Access File violations?

No. The announced settlement addresses alleged discrimination during PERM recruitment. However, it highlights the broader importance of maintaining effective employment-based immigration compliance processes, including separate H-1B and PERM obligations.

What are the most common H-1B LCA posting compliance risks?

Common risks include posting at the wrong location, failing to provide notice to affected workers at third-party worksites, using inaccessible electronic notices, miscalculating posting periods, and failing to retain sufficient evidence of compliance.

What is required in an H-1B Public Access File?

A PAF generally includes the certified LCA, wage-related documentation, prevailing wage support, an explanation of the employer's actual wage system, benefits documentation, and evidence of required notice, along with any additional records applicable to the employer.

How long must a PERM Notice of Filing be posted?

For the applicable workplace posting requirement, a PERM NOF must be posted for at least 10 consecutive business days within the regulatory period before the PERM application is filed. Employers must also comply with applicable content and in-house media requirements.

Can immigration compliance software prevent a DOL audit?

No. Software cannot prevent a government investigation or guarantee legal compliance. It can, however, help employers perform recurring administrative obligations more consistently, reduce manual errors, and maintain organized documentation for internal reviews or government inquiries.

On October 8, 2026, U.S. Secretary of Labor Keith Sonderling and Vice President JD Vance announced that the Department of Labor (DOL) announced the suspension of participation in the Permanent Labor Certification (PERM) program for eight major technology and IT services companies, including Microsoft, Adobe, Cognizant, Infosys, Tata Consultancy Services, Wipro, HCL, and Capgemini.

The announcement represents another significant development in the federal government's increasingly aggressive approach to employment-based immigration enforcement. It also raises immediate questions for employers sponsoring foreign national employees, immigration law firms managing corporate immigration programs, and H-1B workers whose long-term plans depend on employment-based permanent residency.

According to the announcement, the Department will stop accepting new PERM applications and processing pending applications involving the affected companies. The administration cited alleged program abuse and concerns about the displacement of American workers, with Microsoft and Adobe specifically identified in connection with ongoing federal investigations. These are government allegations, not findings of wrongdoing established against every company named.

This announcement reinforces a trend that employers and immigration attorneys have been watching for more than a year: H-1B compliance, Labor Condition Application (LCA) compliance, Public Access File (PAF) management, and PERM compliance are becoming increasingly important parts of corporate immigration risk management.

For companies that have historically treated immigration compliance as a series of administrative tasks, this is another reason to reconsider how those processes are managed, documented, and audited.

What Did the Department of Labor Announce on October 8, 2026?

Eight Major Technology and IT Services Companies Face PERM Suspensions

During the October 8 announcement, Secretary Sonderling identified six major global IT outsourcing and consulting companies whose participation in the PERM program would be suspended:

• Cognizant
• Infosys
• Tata Consultancy Services (TCS)
• Wipro
• HCL
• Capgemini

He also identified two U.S. technology companies, Microsoft and Adobe, citing multiple ongoing federal investigations.

The Department's announced action applies to new and pending permanent labor certification applications involving these employers. In other words, the affected companies cannot proceed through ordinary DOL PERM processing while the announced suspension remains in effect.

The announcement did not establish a definitive end date or publicly explain every procedural detail governing existing cases. Employers and employees affected by the suspension will therefore need to follow subsequent DOL guidance, formal notices, and any legal developments carefully.

What Vice President JD Vance Said About American Workers and Immigration Programs

Vice President Vance framed the decision around the administration's stated objective of protecting employment opportunities for American workers.

He singled out Microsoft, arguing that the company had pursued foreign-worker sponsorship while laying off U.S. employees. The administration presented this as evidence of problems in how employment-based immigration programs have been used.

These statements are significant because the government's concerns are not limited to whether a particular immigration form was completed correctly. They reflect a broader examination of the relationship between foreign-worker sponsorship, domestic recruitment, wages, layoffs, and employer hiring practices.

During the same announcement, officials also discussed investigations involving universities and the J-1 exchange visitor program. The Department's inspector general indicated that subpoenas had been issued in connection with those investigations.

The combination of PERM suspensions and university investigations suggests that the administration is looking across multiple employment-related immigration programs rather than focusing exclusively on H-1B petitions.

That distinction matters for immigration compliance teams. An employer's immigration program may involve H-1B sponsorship, PERM labor certification, employee worksite changes, wage determinations, recruitment, and public-access documentation. Although each process has its own legal requirements, they can become interconnected during a broader government review.

What Does the PERM Suspension Mean for Employers and Foreign National Employees?

PERM Is a Critical Step in Many Employment-Based Green Card Cases

The PERM labor certification process is administered by the DOL and is generally required before an employer can file an immigrant petition in many EB-2 and EB-3 employment-based green card cases.

The process is designed to test the U.S. labor market and establish that the employer has satisfied applicable recruitment and labor certification requirements for the sponsored position.

For many foreign national professionals, particularly H-1B workers, PERM is an important step toward permanent residence. It is also a process that requires careful planning because recruitment, prevailing wage determinations, filing timelines, and subsequent immigrant petition stages can take considerable time.

A suspension of PERM processing therefore affects more than an employer's ability to initiate new green card cases. It can also disrupt long-term immigration planning for employees whose cases are already underway.

Existing H-1B Status Is Not Automatically Revoked

The announcement does not, by itself, revoke existing H-1B approvals or terminate the H-1B program for the affected employers.

H-1B classification and PERM labor certification are separate legal processes. However, the inability to advance a PERM case may potentially have serious downstream consequences for employees approaching their H-1B time limits, particularly where continued eligibility depends on the timing or progress of employment-based permanent residence proceedings.

Affected employees should review their circumstances with immigration counsel.

The same distinction applies to employers. A PERM suspension does not necessarily eliminate continuing H-1B obligations, including LCA wage, notice, and recordkeeping requirements.

Why the PERM Suspension Matters Beyond the Eight Named Employers

Project Firewall Already Signaled a More Aggressive H-1B Enforcement Strategy

On September 19, 2025, the DOL announced Project Firewall, an initiative designed to strengthen enforcement of H-1B employer obligations and protect U.S. workers.

Under Project Firewall, the Department emphasized the use of Secretary-certified investigations, increased information sharing among federal agencies, and closer coordination with the Department of Justice, Equal Employment Opportunity Commission, and U.S. Citizenship and Immigration Services.

The DOL also identified potential enforcement consequences, including back wages, civil monetary penalties, and debarment from future participation in immigration programs.

Project Firewall was particularly noteworthy because it emphasized proactive enforcement. Employers could no longer assume that an investigation would necessarily begin with a worker complaint or an obvious filing irregularity.

The Department's approach also indicated that immigration compliance would be evaluated alongside broader employment practices, including wage protections, displacement concerns, and potentially discriminatory recruitment.

The October 2026 PERM suspensions fit within that broader enforcement direction. They involve a different immigration program and different legal requirements, but they demonstrate the administration's willingness to take significant action against major employers when it believes foreign labor programs are being misused.

For immigration law firms and corporate immigration teams, the practical implication is that compliance should be treated as an ongoing operational responsibility, not simply something reviewed when an H-1B petition or PERM application is filed.

H-1B and PERM Compliance Are Different, but Both Depend on Reliable Records

One important distinction is that PERM compliance and H-1B LCA compliance are not interchangeable.

PERM labor certification generally focuses on the labor market test, recruitment, wage requirements, and other conditions governing an employer's sponsorship of a foreign worker for permanent employment.

H-1B compliance involves a separate set of employer attestations and ongoing obligations, including wages, working conditions, required notice to affected workers, and maintenance of a Public Access File.

However, both programs depend on employers being able to demonstrate that they followed the applicable rules at the appropriate time.

This is where documentation becomes especially important. A company may have completed a required posting or recruitment step, but if it cannot establish when the activity occurred, what information was made available, and whether the applicable requirements were satisfied, it can face avoidable questions during an audit or investigation.

Reliable compliance records do not guarantee that a company will avoid government scrutiny. They do, however, help the employer and its counsel respond with a clear account of what was done and when.

H-1B LCA Compliance: Why Electronic Posting and Public Access Files Matter

Understanding the H-1B LCA Posting Requirement

Before an employer can sponsor an H-1B worker, it generally must obtain a certified Labor Condition Application from the DOL.

Under 20 CFR § 655.734, employers must provide notice of the LCA filing to affected workers through an authorized method, which may include physical posting or electronic notification.

The notice must be provided within the regulatory timeframe and, for posting methods, maintained for the required period of at least 10 days.

The DOL's Field Assistance Bulletin 2019-3 provides additional guidance on electronic LCA posting. Importantly, electronic notice must actually reach the intended audience through a method that makes the information available to affected workers.

This becomes more complicated when employees work across corporate offices, client sites, and remote locations.

An employer may have a well-established process for posting notices at its headquarters, but that does not necessarily establish compliance for employees working elsewhere.

The DOL has specifically recognized that affected workers may include employees of third-party companies working at the same location. Consequently, H-1B employers need to consider whether their notice procedures appropriately address third-party worksites.

The Compliance Risks of Manual LCA Posting

Many employers and immigration law firms still rely on email-based posting processes.

An immigration attorney sends the LCA posting notice to an HR contact, instructs that person to post it at the appropriate location, and requests confirmation once the posting is complete.

For remote employees, the process may involve asking someone to print a notice and post it at home. For third-party worksites, it may require coordinating with a client organization that has its own HR procedures and internal systems.

These arrangements can work when properly implemented. However, they create several recurring compliance challenges:

• Posting visibility: Was the notice actually accessible to the affected workers who needed to see it?
• Posting duration: Was the notice maintained for the required period, and can the employer demonstrate the start and end dates?
• Third-party worksites: Was the posting completed at the correct client location, rather than merely sent to a contact there?
• Remote work: Did the electronic or physical notice method appropriately account for employees working outside a traditional office?
• Posting evidence: Can the employer produce reliable documentation showing what was posted, where it was posted, and when it was removed?

The difficulty is not necessarily that HR personnel or attorneys are failing to perform their responsibilities. Rather, the process often depends on several people, multiple email threads, and separate systems that do not provide a centralized record.

An email confirming that someone was instructed to post a notice is not necessarily the same as evidence that the posting requirement was satisfied.

As government scrutiny increases, employers and law firms should consider whether their existing procedures provide sufficient visibility into the actual completion of compliance activities.

Public Access File Compliance Is Equally Important

H-1B employers must also maintain a Public Access File containing documentation required under 20 CFR § 655.760.

Required PAF documentation includes, as applicable, the certified LCA, wage-related documentation, an explanation of the employer's actual wage system, prevailing wage information, benefits documentation, and evidence of compliance with notice requirements.

The required public-access materials must generally be available within one working day after the LCA is filed.

A complete PAF is more than a folder containing a certified LCA. It is a collection of records that should demonstrate compliance with several separate employer obligations.

Common problems include missing wage memoranda, incomplete benefits statements, absent posting evidence, inconsistent documentation, and files that cannot be located promptly when requested.

Retention also matters. Under the applicable rules, required PAF records must be maintained for the appropriate period, with different retention rules potentially applying to payroll and other supporting records.

Keeping a PAF longer than required is not itself a violation. However, unnecessary retention can increase the volume of records an employer must manage and potentially produce during a review. Conversely, premature destruction can create a direct recordkeeping problem.

A reliable PAF management process should therefore address both completeness and lifecycle management.

PERM Notice of Filing Compliance: Another Area Employers Should Reevaluate

PERM Notice of Filing Requirements Under 20 CFR § 656.10

Although the October 2026 announcement concerns PERM labor certification, the suspension itself is not a finding that the affected employers violated Notice of Filing requirements.

Nevertheless, the announcement is a useful reminder that PERM compliance includes several important procedural obligations, including the Notice of Filing, commonly referred to as the PERM NOF.

Under 20 CFR § 656.10, employers generally must provide notice of the filing of an application for permanent labor certification to the appropriate bargaining representative or, where there is no such representative, through the required workplace posting procedures.

For the applicable workplace posting requirement, the notice must be posted for at least 10 consecutive business days, within the prescribed period before filing the PERM application.

Employers must also comply with applicable in-house media requirements, including electronic or printed communications used in the normal course of recruiting for similar positions.

The regulation expressly distinguishes PERM's 10-business-day posting requirement from the H-1B LCA regulation's 10-day language. Employers should not automatically assume the same timing rules apply to both programs.

Why PERM NOF Documentation Deserves More Attention

PERM Notices of Filing can appear administratively straightforward. Once the notice has been prepared, someone posts it, records the dates, and retains the documentation.

But as with LCA posting, the actual process can involve multiple departments and locations.

An immigration law firm may prepare the notice and send it to the employer. The employer may then be responsible for coordinating the posting, ensuring the notice remains visible, confirming the correct duration, and returning evidence to counsel.

Where the employer has numerous offices or multiple PERM cases underway, these activities can become difficult to track consistently.

A stronger PERM NOF compliance process should establish a reliable record of the notice, the posting location, the posting period, and the documentation supporting completion of the requirement.

Technology can assist with electronic components of this process, automated tracking, and evidence retention. It does not eliminate any physical workplace posting obligation that remains applicable under the PERM regulations.

That distinction is especially important for employers considering electronic PERM NOF tools. A compliant workflow must account for the complete regulatory requirement, rather than assuming that publishing a notice online is sufficient in every circumstance.

How LaborLess Helps Immigration Law Firms and Employers Strengthen H-1B and PERM Compliance

The enforcement developments of 2025 and 2026 reinforce why LaborLess continues to invest in H-1B and PERM compliance technology.

Many immigration compliance obligations are repetitive, document-intensive, and time-sensitive. They also frequently involve coordination among outside immigration counsel, internal HR teams, and employees working across multiple locations.

LaborLess helps immigration law firms and corporate employers automate these processes, reduce manual work, and maintain reliable compliance records through several core features:

• Electronic LCA Posting: Manage H-1B LCA postings across corporate offices, remote worksites, and third-party client locations through centralized electronic posting systems, including websites, internal portals, and QR codes.
• Automated Posting and Takedown: Track LCA posting periods, automatically remove notices after the required posting period, and maintain evidence of when notices were posted and removed.
• Automatic Public Access File (PAF) Creation: Generate and organize PAFs as part of the LCA workflow, including certified LCAs, wage documentation, benefits statements, and posting evidence.
• Comprehensive Audit Trails: Maintain records of posting activity, document changes, user actions, and timestamps, making it easier to retrieve documentation during internal reviews or government investigations.
• PAF Retention and Destruction: Manage PAF expiration dates and automate destruction based on configured retention schedules, helping employers maintain organized records without relying on manual reminders.
• PERM Notice of Filing (NOF) Compliance: Manage electronic PERM NOF postings, track posting periods, automate takedowns, and generate supporting audit documentation. Employers remain responsible for satisfying any applicable physical posting and other regulatory requirements.
• Centralized Compliance Management: Give immigration law firms and authorized corporate personnel access to relevant LCA and PAF records, reducing reliance on email chains, manual confirmations, and disconnected document repositories.

These features help employers and immigration law firms reduce administrative risk, improve audit readiness, and establish more consistent H-1B and PERM compliance processes.

Importantly, LaborLess automates administrative compliance workflows and documentation. It does not replace immigration counsel or make legal determinations about whether a particular LCA, PERM filing, or H-1B amendment is required.

So if you're an immigration law firm looking to automate H-1B LCA posting, Public Access File management, or PERM NOF compliance for your corporate clients, or an in-house immigration professional interested in managing these processes directly, visit LaborLess to learn more: https://www.laborless.io.

The regulations may evolve, and enforcement priorities will certainly change. But employers' need for accurate, accessible, and defensible immigration compliance records will remain.

Frequently Asked Questions About the October 2026 PERM Suspension and Immigration Compliance

Which companies were suspended from the PERM program in October 2026?

The DOL announced suspensions involving Cognizant, Infosys, Tata Consultancy Services, Wipro, HCL, Capgemini, Microsoft, and Adobe. The announcement affects the Department's acceptance of new and processing of pending PERM applications involving these companies, subject to further official guidance and developments.

Does the PERM suspension cancel existing H-1B visas?

No. The announced PERM suspension does not automatically cancel existing H-1B visas or approvals. However, it may affect employees' ability to advance employment-based permanent residence cases and could create longer-term immigration planning issues.

What is the difference between H-1B LCA compliance and PERM compliance?

H-1B LCA compliance concerns obligations associated with temporary H-1B employment, including wage attestations, working conditions, notice to affected workers, and Public Access File documentation. PERM compliance concerns labor certification requirements for many employment-based green card cases, including recruitment, prevailing wage requirements, and the Notice of Filing.

How long must an H-1B LCA notice be posted?

The H-1B LCA regulation requires notice for at least 10 days. Employers should review the applicable DOL guidance and consult counsel regarding the appropriate posting-period calculation and method.

How long must a PERM Notice of Filing be posted?

For the applicable workplace posting requirement, the PERM regulations specify at least 10 consecutive business days. The notice must also satisfy the regulatory timing and content requirements, and employers must address any applicable in-house media obligations.

What documents belong in an H-1B Public Access File?

A PAF generally includes the certified LCA, documentation of the employer's wage determination methodology, prevailing wage information, benefits-related documentation, and evidence of compliance with required notice procedures, together with other records required by the regulations as applicable.

Can immigration compliance software replace legal review?

No. Compliance technology can automate posting, recordkeeping, reminders, document management, and audit-trail generation. Legal determinations about H-1B eligibility, LCA coverage, PERM recruitment, required amendments, and other immigration obligations should remain with qualified immigration counsel and responsible employer personnel.

When is an electronic “in-house media” PERM Notice of Filing posting required?

This has been coming up more often since LaborLess launched PERM Notice of Filing posting, especially as employers and immigration lawyers think more conservatively about Department of Labor compliance. The answer is not quite as simple as “always” or “never,” because the rule depends on how the employer normally communicates similar job opportunities internally. But in today’s compliance environment, many immigration lawyers are taking a more conservative approach: complete the required physical PERM Notice of Filing posting, and also post electronically when there is a reasonable in-house media channel available.

That “belt and suspenders” approach is not about creating unnecessary work. It is about reducing avoidable risk. If a PERM case is audited, why give the Department of Labor any reason to argue that the employer failed to satisfy the Notice of Filing requirement when electronic posting can be handled, tracked, and documented cleanly?

Why PERM Notice of Filing Compliance Matters More Right Now

The PERM Notice of Filing requirement has existed for years, but the broader enforcement and regulatory environment has changed. Two developments in particular are making employers and immigration lawyers look more closely at how they document immigration compliance: the Department of Labor’s Project Firewall initiative and the Trump administration’s stated interest in modernizing the PERM labor certification process.

Project Firewall and the H-1B Compliance Signal

Project Firewall is the Department of Labor’s H-1B enforcement initiative focused on protecting U.S. workers and maximizing compliance with the H-1B visa program. DOL’s official Project Firewall page explains that the initiative prioritizes H-1B investigations involving displacement, inadequate recruitment of U.S. workers, misrepresentation of job duties or working conditions, and other potential abuses.

DOL’s Project Firewall announcement also emphasized a major enforcement shift: for the first time in the department’s history, the Secretary of Labor may personally certify the initiation of certain H-1B investigations. The announcement also notes that DOL will coordinate and share information with other federal agencies where permitted by law.

To be clear, Project Firewall is an H-1B enforcement initiative, not a PERM-specific rule. But it still matters for PERM compliance because it reflects a broader government posture: immigration-related labor compliance is being scrutinized more closely, and employers are expected to have records that prove they followed the rules.

For employers and law firms, the lesson is straightforward:

• Immigration compliance should be documented as the process happens.
• Wage, worksite, recruitment, and notice records should be consistent.
• Employers should not assume that a lack of complaints means a lack of audit risk.
• Compliance systems should create evidence that can be produced later.

That mindset applies directly to PERM Notice of Filing compliance, especially where the employer’s in-house media practices are unclear or inconsistently documented.

The Trump Administration’s Push to Modernize PERM

The second development is the Trump administration’s recent regulatory focus on PERM modernization. The federal regulatory agenda entry for PERM program modernization states that the Department of Labor is initiating rulemaking to modernize aspects of the permanent labor certification process. It also notes that the PERM regulations have not been comprehensively modified since 2004, while technology and industry recruitment practices have changed significantly.

That matters because the PERM process is built around labor market testing, recruitment, notice, documentation, and record retention. If DOL is looking to modernize PERM rules because recruitment practices have changed, then employers and immigration lawyers should be paying close attention to how internal notice is handled in a modern workplace.

DOL has also shown interest in wage-related changes affecting both PERM and H-1B. In March 2026, DOL issued a proposed rule revising prevailing wage methodology for the PERM, H-1B, H-1B1, and E-3 programs. That proposed rule is separate from the PERM modernization agenda item, but together these developments show that employment-based immigration compliance is an active regulatory priority.

For PERM-sponsoring employers, the practical point is not to predict exactly what future rules will say. The practical point is to recognize the direction of travel: DOL is focused on recruitment practices, U.S. worker protections, wage integrity, and employer documentation.

What Is the PERM Notice of Filing?

The PERM Notice of Filing is the notice an employer must provide when it files an Application for Permanent Employment Certification with the Department of Labor. In practical terms, it's designed to notify U.S. workers that the employer is filing a PERM labor certification application for a specific job opportunity.

The Department of Labor’s Foreign Labor Application Gateway explains that PERM includes pre-filing recruitment and Notice of Filing requirements, and that all employers must comply with the Notice of Filing rule at 20 CFR § 656.10.

For most immigration lawyers and PERM-sponsoring employers, the Notice of Filing process is familiar. But the “in-house media” piece is often less clearly understood, especially when companies use internal electronic systems, employee portals, intranet pages, Slack or Teams channels, HR platforms, newsletters, or internal job boards to communicate job opportunities.

The Two Main Parts of the PERM Notice of Filing Requirement

Under 20 CFR § 656.10(d), the PERM Notice of Filing requirement generally has two core components: the physical posting requirement and the in-house media requirement.

1. Physical PERM Notice of Filing Posting

In most non-union PERM cases, the employer must post the Notice of Filing at the facility or location of employment for at least 10 consecutive business days. The notice must be posted in a clearly visible and unobstructed location where U.S. workers can readily read it.

In plain English:

• The physical posting requirement still exists.
• The notice generally must be posted at the worksite.
• The posting must remain up for at least 10 consecutive business days.
• The location should be visible and accessible to workers.
• The employer should preserve proof that the posting actually happened.

Physical posting is often the part of the PERM Notice of Filing process that employers remember. Someone prints the notice, posts it near other workplace notices, takes a picture, confirms the start and end dates, and sends proof to the immigration lawyer. But that is not the end of the analysis.

2. In-House Media PERM Notice of Filing Posting

The same regulation also says the employer must publish the notice in “any and all in-house media, whether electronic or printed,” in accordance with the employer’s normal procedures for recruiting similar positions internally.

This language is where many questions arise.

The Department of Labor’s PERM FAQ on Notice of Filing explains that in-house media can be electronic or print, and that the employer should use its normal internal procedures for notifying employees of job opportunities in the occupation at issue. The FAQ also explains that the electronic notice does not always need to mirror the physical posting word-for-word, but it must provide sufficient notice, including key required information such as the rate of pay and the ability to submit documentary evidence to the Certifying Officer. See DOL’s PERM FAQ Round 10: Notice of Filing.

In plain English:

• “In-house media” can include electronic or printed internal media.
• The analysis depends on how the employer normally recruits similar positions internally.
• If the employer uses an intranet, internal job board, employee portal, newsletter, or similar system for comparable jobs, the PERM Notice of Filing may need to appear there too.
• The electronic notice should contain the required information and be documented.

When Is Electronic PERM Notice of Filing Posting Required?

Electronic PERM Notice of Filing posting is most clearly implicated when the employer normally uses electronic in-house media to advertise or circulate similar job opportunities internally.

For example, electronic in-house media may (but not necessarily - this is not legal advice!) include:

• Internal company job boards
• Employee intranet pages
• HR information systems or employee portals
• Internal newsletters
• Company-wide emails
• Slack, Teams, or similar internal channels
• Other electronic systems used to notify employees about openings

If the employer normally posts similar positions through one or more of these channels, then the PERM Notice of Filing should be published through those channels in accordance with the employer’s normal internal recruitment procedures.

The key question is not simply, “Does the company have an intranet?” The better question is: “Does the company normally use this in-house media channel to notify employees about similar job opportunities?”

That distinction matters. A company may have many internal communication tools, but not every tool is used for internal recruiting. The in-house media requirement is tied to normal internal procedures for recruiting similar positions, not every communication channel the employer happens to maintain.

Why Some Lawyers Post Electronically Anyway

Some immigration lawyers view electronic in-house media posting as required only when the employer actually uses in-house media for similar internal recruitment. That is a reasonable reading of the regulatory language.

But others are taking a more conservative approach. Even when the requirement may be arguable, they prefer to post electronically in addition to the physical posting whenever there is a clean internal channel available.

The logic is simple:

• PERM cases are document-heavy and audit-sensitive.
• Notice of Filing mistakes can create avoidable risk.
• DOL is actively focused on immigration-related labor compliance.
• Electronic posting can help document internal notice.
• A conservative process is often easier to defend than a minimalist one.
• If posting electronically is easy, the downside may be low compared with the compliance benefit.

This is the “belt and suspenders” approach. The employer still completes the physical Notice of Filing posting, but it also uses electronic in-house media to strengthen the compliance record.

Why the “Belt and Suspenders” Approach Makes Sense in Today’s DOL Environment

PERM compliance often comes down to documentation. If the Department of Labor asks what happened, the employer and law firm need to show clear evidence: what was posted, where it was posted, when it went up, when it came down, and whether the employer followed the required process.

That is why electronic in-house media posting can be so valuable. It creates another layer of evidence that the employer took the Notice of Filing requirement seriously.

A conservative electronic posting process can help answer questions such as:

• Was the Notice of Filing posted internally?
• Was it posted through the employer’s normal internal media?
• Did the posting contain the required information?
• Was the posting period tracked?
• Was proof captured and preserved?
• Can the employer produce evidence if the case is audited?

This is especially important in a period when DOL is both increasing H-1B enforcement through Project Firewall and signaling interest in modernizing PERM recruitment and compliance rules. Even though H-1B and PERM are different processes, both sit within a broader employment-based immigration compliance framework focused on wages, U.S. worker protections, employer attestations, recruitment, and documentation.

What Should Be Documented for Electronic PERM NOF Posting?

If an employer uses electronic in-house media for PERM Notice of Filing, the process should be documented carefully. A screenshot alone may not always tell the full story, especially if the employer later needs to prove the timing, location, accessibility, or contents of the notice.

A stronger electronic PERM NOF compliance record should capture:

• The text of the Notice of Filing
• The internal channel or platform where it was posted
• The date and time the posting went live
• The date and time the posting was removed
• Evidence that the posting was visible or accessible to the relevant employee population
• Confirmation that the posting remained available for the intended period
• Any related instructions, approvals, or confirmations

The goal is to create an audit-ready record as the process happens, instead of trying to reconstruct the facts months or years later from emails, screenshots, calendar reminders, and memory.

Electronic PERM NOF Posting Does Not Replace Physical Posting

One important point: electronic in-house media posting should not be treated as a replacement for the physical Notice of Filing posting in standard non-union PERM cases.

The physical posting requirement still matters. The in-house media requirement is an additional requirement when the employer uses in-house media for similar internal recruitment. For many employers, the safest approach is to treat the two as separate compliance steps:

• Complete the required physical Notice of Filing posting.
• Determine whether in-house media posting is required based on normal internal recruitment procedures.
• Consider electronic posting as a conservative additional step where appropriate.
• Preserve proof of both physical and electronic posting.

This distinction matters because some employers assume that “electronic posting” means the entire Notice of Filing process can become electronic. That is not necessarily correct. Electronic in-house media posting can help satisfy the in-house media component, but it does not automatically eliminate the need for physical posting where physical posting is required.

Why LaborLess Added PERM Notice of Filing Posting

This is exactly why LaborLess added PERM Notice of Filing posting.

Law firms and PERM-sponsoring employers needed a cleaner way to handle electronic PERM NOF posting without manually managing the process through email chains, PDFs, screenshots, calendar reminders, and follow-up messages.

LaborLess now helps law firms and employers:

• Post PERM Notices of Filing electronically
• Track the posting period
• Capture proof of posting
• Document the in-house media posting process
• Create a clearer audit trail
• Support a more conservative PERM compliance workflow

For immigration law firms, this also creates an opportunity to offer electronic PERM Notice of Filing posting as an additional compliance service to clients. Instead of simply asking the employer to handle the process manually, firms can provide a more structured, visible, and auditable workflow.

Final Takeaway: Why Leave the In-House Media Box Unchecked?

The in-house media requirement under 20 CFR § 656.10(d) is not new. But the way employers communicate internally has changed dramatically. Many companies now use electronic systems as their primary way to notify employees about internal opportunities. DOL itself has recognized that PERM has not been comprehensively updated since 2004 and that technology and recruitment practices have changed.

The practical takeaway is simple:

• Physical PERM NOF posting remains a core requirement.
• In-house media posting may be required when the employer uses internal media for similar recruitment.
• Electronic in-house media can include intranets, employee portals, internal job boards, newsletters, and similar systems.
• Project Firewall shows that DOL is taking a more aggressive posture toward immigration-related labor compliance, especially in the H-1B context.
• PERM modernization efforts show that DOL is looking closely at how recruitment and documentation rules should operate in today’s labor market.
• A conservative electronic posting process can help reduce ambiguity and strengthen the compliance record.
• Documentation matters just as much as the posting itself.

Why give the Department of Labor any reason to say the employer did not satisfy the Notice of Filing requirements?

Why leave the in-house media box unchecked if there is an easy, auditable way to do it?

If you handle PERM cases and want to learn more about how LaborLess now enables electronic PERM Notice of Filing posting, visit www.laborless.io or reach out directly.

At this year’s American Immigration Lawyers Association Annual Conference, LaborLess had the opportunity to sponsor a session called “Government Knocking: Preparing for FDNS, DOL and ICE Visits.” For anyone handling H-1B compliance, whether as outside immigration counsel or in-house at a sponsoring employer, this was one of the most relevant sessions of the conference.

The reason is simple: H-1B compliance is no longer just about getting the petition approved. It is about being able to prove, sometimes months or years later, that the employer did what it said it would do, that the employee is working where and how the petition described, that wage obligations are being met, and that the Labor Condition Application (LCA) process was handled properly from the beginning.

That has always been true under the law. But in the current enforcement environment, especially with the Department of Labor’s increased focus on H-1B compliance and Project Firewall, the practical risk feels very different. Employers and law firms should be preparing as if someone may eventually ask them to show their work.

FDNS Site Visits Are Likely to Become More Common in H-1B Cases

One of the strongest takeaways from the session was that employers should expect more Fraud Detection and National Security Directorate site visits, including in the H-1B context. USCIS’s Fraud Detection and National Security Directorate conducts site visits to verify information connected to immigration filings, and those visits can involve questions about the petitioning employer, the worksite, the job duties, and whether the beneficiary is doing the work described in the filing. USCIS explains the directorate’s role on its official Fraud Detection and National Security Directorate page.

That means the H-1B employee should not be treated as an afterthought in the petition process. As Allen Orr emphasized during the panel, the beneficiary should know what is in their file. Not just the generic job description, but the real details of the role, worksite, salary, and job duties.

For H-1B employers, that means the employee should understand:

• What job duties were described in the H-1B petition
• What work they actually do and do not perform
• How much they are supposed to be paid
• Where they are authorized to work
• Whether remote or hybrid work was included in the filing strategy
• When to tell HR or immigration counsel about changes

This matters because the employee is often on the front line of their own status. If an FDNS officer shows up or calls, the employee may be asked questions before the lawyer or HR team has time to prepare a response. If the employee’s explanation does not match the petition, that mismatch can become a problem even if the underlying case was approvable.

The best time to address this is before anything goes wrong. H-1B employees should understand that if they move, change worksites, change job duties, receive a salary change, change titles, or start working in a meaningfully different arrangement, they need to tell the company and immigration counsel immediately. Compliance is not just something that happens at filing. It has to be maintained during the entire H-1B employment period.

DOL Audits Are No Longer Just Complaint-Driven

The second major takeaway was the changing nature of Department of Labor enforcement.

Historically, many employers thought of DOL H-1B investigations as mostly complaint-driven. In other words, if no employee complained, they assumed the likelihood of an investigation was low. That was never a perfect assumption, but it is especially dangerous now.

Under the H-1B statute, the Secretary of Labor has authority in certain circumstances to certify an investigation into an employer’s LCA compliance practices. That authority is tied to the broader enforcement framework under 8 U.S.C. § 1182(n), which governs many of the wage, working condition, notice, and enforcement obligations connected to H-1B employment. DOL also maintains an official H-1B program page outlining employer obligations and worker protections.

For employers and immigration law firms, the practical takeaway is clear:

• H-1B audits may arise even without a worker complaint
• LCA compliance practices may be reviewed after filing
• Agency information-sharing can expose inconsistencies
• Wage, worksite, job duty, and posting records need to line up
• Employers should assume their records may eventually be compared across systems

Project Firewall has made this shift more visible. The point is not simply that DOL can investigate. The point is that employers should not assume that a lack of complaints means a lack of risk. Agencies are also sharing information more actively, and an issue in one system can create questions in another. DOL, ICE, the Department of Justice’s Immigrant and Employee Rights Section, EEOC, USCIS, and even tax-related information can overlap in ways that employers may not expect.

For companies, that means consistency matters. The LCA should match the petition. The petition should match the employee’s actual role. The wage records should match the wage obligation. The worksite should match the posting and filing strategy. When those pieces do not line up, the employer may have a difficult story to tell later.

LCA Posting Is Still a Core H-1B Compliance Requirement

One of the most practical issues discussed during the session was LCA posting, especially for remote workers. DOL’s H-1B regulations require employers to provide notice of the Labor Condition Application to affected workers. The specific notice rules are found at 20 CFR § 655.734, which explains when and how notice must be provided, including hard-copy and electronic notice options.

For traditional office environments, LCA posting was already operationally annoying. For remote and hybrid work, it becomes much more complicated. If the home is the worksite, the employer still has to think carefully about how notice is being provided to affected workers.

A few practical LCA posting questions employers should be asking:

• Was the LCA notice posted before the H-1B petition was filed?
• Was the notice posted for the required time period?
• Was the posting made at the correct worksite?
• If the employee works remotely, was the home worksite addressed?
• Was electronic posting used in a way that affected workers could actually access?
• Was proof of posting captured and saved in the Public Access File (PAF)?

During the session, Samantha Wolfe addressed a point that comes up often: DOL has previously made comments suggesting it does not “expect” employees to post LCAs on their refrigerators at home. But that type of comment is not the same as black-letter law. The regulation still requires notice connected to the place of employment, and employers should be cautious about relying on informal comments as a compliance strategy.

This is one of the strongest practical arguments for electronic LCA posting. DOL has recognized electronic notice as an option when it is provided in a way that is readily available to affected workers, and its Field Assistance Bulletin on electronic notice provides helpful guidance on this topic. Employers and law firms should review DOL Field Assistance Bulletin 2019-3, which discusses electronic posting in the H-1B context.

The takeaway is not that every remote work scenario is identical. The takeaway is that remote worksite posting cannot be ignored. Employers need a process that is repeatable, documented, and auditable.

Public Access Files Matter More Than Ever

The panel also reinforced something LaborLess has been focused on for years: the Public Access File is not an afterthought.

Under 20 CFR § 655.760, employers must make a Public Access File available within one working day after the LCA is filed. The PAF is the employer’s core evidence file showing that the LCA process was handled properly.

A strong H-1B Public Access File should generally include:

• A copy of the certified Labor Condition Application
• The wage rate paid to the H-1B worker
• A summary of the actual wage system
• The prevailing wage source and methodology
• A summary of benefits offered to U.S. workers and H-1B workers
• Documentation showing that LCA notice was provided
• Additional H-1B dependency or corporate documentation where required

This is where many employers struggle. The LCA may be filed correctly, but the proof of compliance may be scattered across emails, PDFs, folders, HR systems, payroll records, or old case management notes. That may work until someone asks for the file quickly. At that point, “I think it is somewhere” is not a compliance strategy.

For law firms, this creates a real question: if you are advising on the LCA and H-1B filing process, should you also be helping the employer manage the PAF process? The panelists suggested that law firms should strongly consider owning or managing more of that process because it is directly tied to the employer’s compliance story.

At minimum, the employer and law firm should know who is responsible for creating the PAF, when it is created, what goes into it, where it is stored, how posting proof is captured, and how the file will be produced if requested.

Wage and Hour Issues Can Become Expensive Quickly

Another important takeaway was that DOL Wage and Hour investigations can become very granular. The issue is not always whether the W-2 looks correct at the end of the year. In some cases, investigators may look at whether the required wage was paid properly during each relevant pay period.

That distinction matters. An employer may think it has satisfied the wage requirement because the annual compensation appears to meet the required wage, but if the employee was underpaid during certain pay periods, that can still create exposure. DOL’s Fact Sheet #62H explains that H-1B employers must pay the required wage and comply with the labor condition statements made in the LCA.

This can be especially risky in industries or roles where employers are used to paying by visit, by piece, by shift, or through other compensation structures that do not neatly align with H-1B wage obligations. Once Wage and Hour gets involved, the review can expand into back wages, interest, and payment plans. For employers operating on thin margins, that can be painful.

What H-1B Employers and Law Firms Should Do Now

The broader message from the session was clear: employers need to tighten their compliance documentation, and law firms need to make sure the process actually happens.

A modern H-1B compliance process should be:

• Transparent, so the employer and law firm can see what has been done
• Centralized, so records are not scattered across inboxes and folders
• Auditable, so evidence can be produced quickly if requested
• Consistent, so LCA, petition, payroll, and worksite records align
• Scalable, so remote work, hybrid work, and multiple worksites do not create chaos

That means H-1B compliance cannot live only in attorney inboxes, HR spreadsheets, or one-off emails asking someone to post something somewhere. It needs to be structured. It needs to be visible. It needs to create evidence as the process happens, not after the fact when everyone is trying to reconstruct what occurred.

For H-1B employers, this means reviewing LCA posting procedures, remote worksite posting practices, Public Access File workflows, wage records, and internal change-notification processes. For immigration law firms, it means helping clients understand that LCA compliance is not just a filing step. It is part of the ongoing risk management surrounding every H-1B case.

Final Thoughts: H-1B Compliance Needs to Be Proactive, Not Reactive

The key lesson from “Government Knocking: Preparing for FDNS, DOL and ICE Visits” is that employers should not wait until the government knocks to figure out whether their files are organized, their postings were done correctly, or their wage records match their obligations.

By then, it may already be too late.

If you handle H-1B compliance for clients, or you work in-house at a company that sponsors H-1B workers, and you do not have a streamlined, transparent, and auditable LCA compliance process, now is the time to fix that.

At LaborLess, we have spent a decade building a platform to help employers and immigration law firms manage electronic LCA posting, Public Access Files, and now PERM Notice of Filing compliance in a more organized, auditable way.

To learn more, visit www.laborless.io or reach out directly.

Regulations require that Public Access Files (PAFs) be maintained for at least one year after either the Labor Condition Application (LCA) expiration date or the last date of employment. But a more nuanced question often arises in practice: if employment ends before the LCA expires and the employer does not withdraw the LCA, which date actually controls the PAF retention period?

This is not just a technical compliance issue. It has become increasingly important as enforcement activity around H-1B compliance has intensified and as employers and immigration practitioners are expected to demonstrate not only that they understand the rules, but that they are operationalizing them correctly.

Why PAF Retention Questions Matter More Today

Increased Enforcement of H-1B Compliance

In recent years, the Department of Labor’s Wage and Hour Division has increased its focus on H-1B program compliance, including record-keeping and wage obligations. These enforcement efforts, sometimes referred to in industry discussions as “Project Firewall,” reflect a broader shift toward proactive, data-driven investigations of employers sponsoring foreign workers.

Official guidance from the Department of Labor emphasizes that employers must maintain proper documentation to demonstrate compliance with LCA requirements, including the creation and retention of Public Access Files:
https://www.dol.gov/agencies/whd/immigration/h1b

Industry Awareness and Audit Preparedness

At the same time, reporting from sources such as Bloomberg Law has highlighted an increase in immigration-related enforcement actions, particularly around documentation and wage compliance. As a result, organizations are taking a closer look at whether their internal processes—especially around PAF retention—would withstand scrutiny in an audit.

What the Regulation Actually Says: 20 CFR § 655.760(c)

The Governing Rule

The governing rule for Public Access File retention is set forth in 20 CFR § 655.760(c):
https://www.ecfr.gov/current/title-20/section-655.760

The regulation provides:

“The employer shall retain copies… for a period of one year beyond the last date on which any H-1B nonimmigrant is employed under the labor condition application or, if no nonimmigrants were employed… one year from the date the labor condition application expired or was withdrawn.”

Two Distinct Public Access File Retention Scenarios

Although the language is concise, it establishes two clearly different retention frameworks:

• If an H-1B worker was employed under the LCA
  The retention period runs one year from the last date of employment
• If no H-1B worker was ever employed under the LCA
  The retention period runs one year from the LCA expiration or withdrawal date

These two triggers are mutually exclusive, and determining which one applies is essential for compliance.

Applying the Rule to a Common Real-World Scenario

Scenario: Employment Ends Before LCA Expiration

Consider a situation where:

• An H-1B employee begins work under a valid LCA
• The employee leaves the company before the LCA expires
• The employer does not withdraw the LCA
• The LCA remains valid through its original end date

Which Date Controls PAF compliance?

In this scenario, the correct interpretation is that the last date of employment controls the PAF retention period.

Because the LCA was used (that is, an H-1B worker was actually employed under it) the regulation directs the employer to follow the employment-based timeline. The expiration or withdrawal trigger only applies where no employment occurred.

Key Takeaways

• Once employment occurs, retention is tied to employment, not the LCA lifecycle
• The LCA expiration date does not become the operative trigger in this scenario
• Withdrawal is not required to establish the retention timeline

Why This Distinction Is Often Misunderstood

Over-Reliance on LCA Expiration Dates

In practice, many employers default to using the LCA expiration date as the primary benchmark for retention. This is often because expiration dates are fixed and easier to track. However, this approach can lead to incorrect conclusions when employment ends earlier.

Simplified Guidance That Misses Nuance

Another source of confusion comes from simplified explanations, such as “retain the PAF for one year after termination or withdrawal.” While directionally correct, this type of guidance does not fully capture the conditional structure of the regulation, particularly the distinction between used and unused LCAs.

Practical Implications for Employers

Documentation Requirements in an Audit

In the event of a Department of Labor audit, employers may need to demonstrate that PAFs were retained for the correct period. This often requires supporting documentation, including:

• Payroll records showing the last date of wages paid
• HRIS data reflecting employment status
• Termination or resignation documentation

Without clear documentation, it may be difficult to substantiate that retention requirements were met.

Operational Challenges in Managing PAFs

Many organizations still manage Public Access Files through manual or decentralized processes. Common challenges include:

• Files stored across multiple systems or locations
• Inconsistent tracking of retention deadlines
• Lack of alignment between HR data and compliance documentation

These issues can make it difficult to apply regulatory rules consistently.

The Risk of Over-Retention and Under-Retention of PAFs

Over-Retention Risks

• Retaining files longer than necessary may create unnecessary data exposure
• Excess data retention can raise internal governance or privacy concerns

Under-Retention Risks

• Premature deletion of PAFs can lead to noncompliance findings
• Inability to produce documentation during an audit may result in penalties

Both risks stem from misinterpreting or inconsistently applying the retention rule.

Best Practices for Managing Public Access File Retention

Align Retention with Employment Data

Employers should ensure that retention timelines are based on actual employment dates rather than defaulting to LCA expiration.

Standardize Internal Processes

• Apply consistent retention calculations across all cases
• Establish clear ownership of PAF management within the organization

Maintain Supporting Documentation

• Keep employment records accessible and organized
• Ensure that documentation aligns with PAF retention timelines

Conduct Periodic Compliance Reviews

Regular internal audits can help identify gaps and ensure that retention practices are being applied correctly.

The Role of Technology in PAF Compliance

Benefits of Centralized Systems

Technology-driven solutions can significantly improve compliance by automating LCA posting and PAF creation, document retention tracking, and providing a clear audit trail for all actions

Reducing reliance on email-based and manual workflows helps eliminate inconsistencies and ensures that retention rules are applied uniformly across all cases. That's why platforms like LaborLess are designed to address these challenges by centralizing LCA posting and PAF management, allowing employers and law firms to maintain compliance more effectively.

While the regulation itself is clear, applying it consistently requires careful coordination between HR data, compliance processes, and documentation practices. As enforcement activity continues to increase, organizations that take a structured and proactive approach to PAF management will be better positioned to meet regulatory expectations.

So if you are reviewing your Public Access File processes or looking to improve your H-1B compliance framework, now is the time to ensure your retention practices align with regulatory requirements. LaborLess provides a centralized approach to LCA posting and PAF management, helping organizations standardize processes, maintain audit-ready documentation, and reduce compliance risk. Learn more at https://www.laborless.io.

Frequently Asked Questions

How long must a Public Access File be retained?

A PAF must be retained for one year beyond the last date of employment under the LCA, or, if no employment occurred, one year beyond the LCA’s expiration or withdrawal.

What happens if an employee leaves before the LCA expires?

The retention period is still based on the last date of employment if the employee worked under the LCA.

Does an employer need to withdraw the LCA?

Withdrawal is not required to determine the retention period when employment has occurred, but it may still be advisable for other compliance reasons.

What records should employers maintain?

Employers should retain payroll records, HR data, and termination documentation to support their retention timelines.

Why is this important now?

Increased enforcement and audit activity mean that employers must be prepared to demonstrate compliance with documentation and retention requirements.

If you handle H-1B cases—whether as an immigration lawyer or part of an in-house global mobility team—you’ve likely spent significant time thinking about Labor Condition Applications (LCAs) and Public Access Files (PAFs). But there’s a more nuanced question that doesn’t come up often enough: should an employee’s name be included in a Public Access File at all?

At first glance, this appears to be a straightforward compliance issue governed by the Department of Labor (DOL). However, when examined more closely, it becomes clear that this question sits at the intersection of regulatory compliance, privacy risk, and modern data management practices.

To answer it properly, we need to separate what the DOL explicitly requires from what may introduce unnecessary legal or operational risk. This distinction is critical, especially in today’s environment of heightened enforcement and growing scrutiny around employee data.

What Does the DOL Actually Require in a Public Access File?

The governing regulation for Public Access Files is 20 CFR § 655.760, which defines the exact documentation employers must maintain and make available. From a compliance perspective, understanding this list precisely is essential, as many organizations either include too little (creating compliance risk) or too much (creating unnecessary exposure).

Required Public Access File Contents (Per 20 CFR § 655.760)

A compliant Public Access File must include the following:

• The certified Labor Condition Application (LCA) (Form ETA 9035 and cover pages)
• Documentation of the wage rate to be paid to the H-1B worker
• A clear explanation of the employer’s actual wage system
• Documentation of the prevailing wage source (such as OES data or a private wage survey)
• A summary of benefits offered to U.S. workers in the same occupational classification
• Proof of LCA notice/posting, including the dates and method of notice
• A corporate structure statement, if multiple entities are involved
• H-1B dependency determination, if applicable
• Recruitment and non-displacement documentation, if the employer is H-1B dependent or a willful violator

What is equally important is what does not appear on this list. The regulation does not require employee names, personal identifiers, or any unnecessary personally identifiable information (PII). From a strict DOL compliance standpoint, including a beneficiary’s name is neither required nor explicitly prohibited. However, that absence is meaningful—it signals that the purpose of the PAF is to demonstrate compliance with wage and labor condition requirements, not to identify specific individuals.

Why the “Public” Nature of Public Access Files Matters

The defining characteristic of a Public Access File is that it must be accessible to the public. The regulation makes this explicit, stating: “The employer shall make a public access file available for public examination… within one working day after the date on which the labor condition application is filed” (20 CFR § 655.760(a)). This requirement fundamentally changes how employers should think about the contents of the file.

Unlike internal HR records, a PAF can be requested by virtually anyone, and the employer must provide access promptly. There is no requirement that the requester be affiliated with the company or have any specific purpose. As a result, anything included in the file should be treated as information that could become broadly accessible. When an employee’s name is included, that public file may effectively disclose more information than the employer would typically intend to share.

Privacy and Legal Risks Beyond DOL Compliance

While the DOL does not prohibit including employee names, other areas of law introduce important considerations. Employers today operate within a patchwork of privacy frameworks that increasingly emphasize limiting the collection and disclosure of personal data to what is necessary.

Key Privacy Considerations for Public Access Files

• State privacy laws: Laws such as the California Consumer Privacy Act and similar statutes in other states require organizations to minimize unnecessary disclosure of personal information and justify how data is used and shared.
• Common law privacy principles: Legal doctrines such as the public disclosure of private facts may create exposure if sensitive information is made broadly available without a legitimate need.
• Data aggregation risks: While individual data may seem harmless, combining an employee’s name with wage information and work location can create a detailed and potentially sensitive profile.

The key issue is not that including a name automatically violates a specific law, but that it introduces risk without providing a clear compliance benefit. In a regulatory environment that increasingly values data minimization, unnecessary inclusion of personal information can become a liability.

The Practical Impact of Including Employee Names

To understand the real-world implications, it helps to consider how information in a Public Access File interacts. A PAF is not a single data point; it is a collection of documents that, when viewed together, provide a detailed snapshot of an employment situation. If that snapshot includes an employee’s name alongside wage data and worksite information—particularly in cases involving remote work—it may reveal more than intended.

This is especially relevant in today’s workplace, where remote and hybrid arrangements are common and where home addresses may appear as worksites on LCAs. In such cases, including a name could inadvertently connect an individual to a residential location and compensation level in a publicly accessible document.

Best Practice: Apply a Data Minimization Approach

Given that employee names are not required, many practitioners are adopting a straightforward guiding principle: include only what is explicitly required by regulation. This approach, often referred to as data minimization, aligns with both compliance requirements and broader privacy expectations.

Why Data Minimization Is Effective

• It ensures full compliance with DOL requirements without adding unnecessary information
• It reduces exposure to privacy-related risks
• It aligns with modern data protection standards
• It simplifies internal compliance processes

Rather than asking whether something is allowed, this approach reframes the question to whether it is required. If the answer is no, it likely does not belong in a Public Access File.

The Bigger Challenge: Lack of Visibility Into PAF Processes

In practice, issues like this often highlight a broader challenge in H-1B compliance. Many organizations rely on manual processes to create and maintain Public Access Files, with responsibilities split between law firms and employer clients. As a result, there is often limited visibility into what is actually included in the file, whether all required documents are present, and whether unnecessary information has been added.

This lack of standardization can lead to inconsistencies across cases and increases the likelihood of both compliance gaps and unnecessary risk exposure. Over time, these small inconsistencies can compound, particularly in organizations handling multiple H-1B cases or working with multiple legal providers.

Modernize Your Public Access File Process with LaborLess

A more modern approach to PAF compliance focuses on centralization and control. By using technology to manage LCA posting and Public Access File creation, organizations can ensure that each file is consistent, complete, and aligned with regulatory requirements. Automated systems can be designed to include only required documentation, exclude unnecessary personal data, and maintain a clear audit trail.

So if you're handling H-1B cases and are not fully confident in how your Public Access Files are being created, maintained, or audited, it may be time to take a closer look at your process. LaborLess enables law firms and employers to post LCA notices electronically, automatically generate compliant Public Access Files, and maintain full visibility into compliance workflows. By centralizing everything in one place, you can ensure that your PAFs are complete, accurate, and aligned with both regulatory requirements and modern data practices.

Visit is at https://www.laborless.io and reach out to learn more!

FAQ: Public Access Files and Employee Names

Do DOL regulations require employee names in a Public Access File?
No. Under 20 CFR § 655.760, employee names are not listed as a required component of a PAF.

Is including an employee’s name a violation?
Not under DOL rules, but it may introduce privacy risks depending on the broader legal context.

Why are Public Access Files public?
They are required to be publicly accessible to ensure transparency and allow verification of compliance with wage and labor condition requirements.

Can a home address appear in a Public Access File?
Yes, if it is listed as a worksite on the LCA, which can raise additional privacy concerns when combined with other information.

What is the safest approach for PAF contents?
Limit the file to what is explicitly required by regulation and avoid including unnecessary personal data.

It’s H-1B cap season, which means Labor Condition Application (LCA) posting and Public Access File (PAF) compliance should be top of mind for immigration law firms, in-house legal teams, and global mobility professionals. While the requirements themselves are relatively straightforward, the way they are handled in practice, especially through manual processes, creates significant compliance risk.

In this article, we break down the most common LCA posting and PAF compliance mistakes, explain the underlying Department of Labor (DOL) regulations, and outline how organizations can modernize their approach to reduce risk and improve audit readiness.

What Are LCA Posting and Public Access File Requirements?

Before diving into common mistakes, it’s important to understand the regulatory framework.

Under the H-1B program, employers must file an LCA with the U.S. Department of Labor and comply with specific notice and record-keeping requirements. These rules are governed primarily by 20 CFR § 655.734 (Notice of Filing) and 20 CFR § 655.760 (Public Access File requirements).

• DOL LCA regulations: https://www.ecfr.gov/current/title-20/section-655.734
• DOL PAF requirements: https://www.ecfr.gov/current/title-20/chapter-V/part-655/subpart-H/section-655.760
• FLAG system (for LCA filing): https://flag.dol.gov/

At a high level, employers must:

• Provide notice of the LCA to workers at the worksite before or on the date of filing
• Ensure the notice is accessible and visible to affected employees
• Maintain a Public Access File with required documentation within one working day of filing
• Retain that file for specific regulatory time periods

Despite these clear requirements, the reality is that manual processes introduce gaps at nearly every step.

The Most Common LCA Posting Compliance Mistakes

LCA Not Posted (or Posted Incorrectly)

One of the most fundamental compliance failures occurs when the LCA is not posted at all, or not posted correctly. In a typical manual workflow, a law firm sends a PDF notice via email with instructions to print and post. From that point forward, the process depends entirely on the client. The notice may be placed in an incorrect location, not be visible to employees, or never be posted at all. The law firm often has no visibility into whether the posting actually occurred.

LCA Posted for the Wrong Time Period

DOL regulations require that LCA notices be posted for at least 10 days. While the consensus is that these are calendar days, tracking this manually is unreliable. Some companies remove postings too early, which creates clear noncompliance. Others leave notices posted indefinitely, which is not technically a violation but can expose the company to unnecessary scrutiny during audits.

No Confirmation from Client Before Filing

Many law firms wait for confirmation emails from clients that the LCA has been posted before submitting it through the FLAG system. When that confirmation is delayed (or never provided) it creates operational bottlenecks. The firm must follow up repeatedly, and the entire H-1B process can be delayed due to a lack of documentation or a clear audit trail.

Failure to Repost After Remote Work Moves

The rise of remote work has introduced a major compliance challenge. If an employee moves—even within the same metropolitan statistical area (MSA), and continues working remotely, the new location may be considered a new worksite. Under 20 CFR § 655.734, that triggers a new LCA posting requirement. In practice, many employers are unaware of this obligation, leading to inadvertent noncompliance.

The Most Common Public Access File (PAF) Mistakes

PAF Not Created Within One Working Day

DOL regulations require that a Public Access File be created within one working day of filing the LCA. In a manual workflow where documents and instructions are sent via email, this requirement is frequently missed. Even when guidance is clear, competing priorities and lack of centralized oversight often result in delayed PAF creation, placing the employer out of compliance.

PAF Missing Required Documents

The PAF must contain specific documentation, including the certified LCA, wage rate information, and a summary of benefits offered to U.S. workers. However, many law firms do not have direct visibility into whether clients have assembled these documents correctly. At the same time, companies often assume they are compliant without verification. This lack of transparency creates a high risk of incomplete or deficient files.

Improper PAF Retention

Under 20 CFR § 655.760, PAFs must be retained for:

• One year beyond the last date the H-1B worker is employed under the LCA, or
• One year from the date the LCA expires or is withdrawn

In practice, retention policies are inconsistently applied. Some organizations discard files too early, while others retain them indefinitely without a clear system. Both scenarios create unnecessary compliance and audit risks.

Storage of PII Without Oversight

Another overlooked issue is the inclusion of personally identifiable information (PII) in Public Access Files. While not always a direct violation of DOL regulations, including sensitive employee data can conflict with internal privacy policies or broader data protection standards. Many organizations are not actively monitoring this risk, which can lead to downstream compliance issues.

Why Manual LCA and PAF Processes Create Risk

The common thread across all of these issues is reliance on manual, fragmented workflows. Email-based processes, paper postings, and decentralized file storage create a system where:

• Responsibility is unclear
• Visibility is limited
• Documentation is inconsistent
• Audit readiness is weak

In today’s enforcement environment—particularly with increased scrutiny under initiatives like DOL’s enforcement efforts and FDNS site visits—these gaps are no longer theoretical risks. They are real exposure points that can lead to penalties, back wage liability, or debarment.

The Case for Electronic LCA Posting and PAF Management

Modernizing LCA and PAF processes through technology addresses these challenges directly. Electronic systems allow organizations to:

• Ensure LCA notices are posted correctly and consistently
• Track posting durations automatically
• Create Public Access Files immediately upon filing
• Maintain centralized, audit-ready documentation
• Monitor compliance across multiple entities and worksites
• Reduce reliance on manual follow-ups and email confirmations

By replacing fragmented workflows with a structured, transparent system, organizations can significantly reduce compliance risk while improving operational efficiency.

How LaborLess Helps Immigration Teams Stay Compliant

LaborLess was built specifically to address these challenges. Instead of relying on manual coordination between law firms and clients, LaborLess enables:

• Electronic LCA posting managed directly by the law firm or employer
• Automatic tracking of posting timelines
• Instant creation and maintenance of Public Access Files
• Centralized storage of all LCA and PAF documentation
• Clear audit trails for every action taken

For law firms, this means greater control over compliance and the ability to provide an additional, high-value service to clients. For employers, it means confidence that every step of the process is being handled correctly and consistently.

If your organization is still relying on manual LCA posting and PAF management—especially during H-1B cap season—now is the time to modernize your approach. Visit www.laborless.io to learn more or get started. LaborLess is onboarding new clients within 24–48 hours to ensure teams are fully prepared for cap season.

Frequently Asked Questions (FAQ)

What is the minimum LCA posting requirement?

Employers must post the LCA notice for at least 10 days in a location accessible to affected employees or provide electronic notice in accordance with DOL regulations under 20 CFR § 655.734.

When must a Public Access File be created?

A Public Access File must be created within one working day of filing the LCA, as required by 20 CFR § 655.760.

What documents must be included in a PAF?

A PAF typically includes the certified LCA, wage rate documentation, a summary of benefits, and other supporting materials required by DOL regulations.

How long must PAFs be retained?

PAFs must be retained for one year beyond the last date of employment under the LCA or one year from the date the LCA is withdrawn or expires.

Does remote work require new LCA postings?

Yes, in many cases. If an H-1B employee changes work locations, including remote work from a new address, it may trigger a new LCA posting requirement depending on the circumstances.

Why is electronic LCA posting better than paper posting?

Electronic posting improves visibility, ensures consistent compliance, automates tracking, and creates a reliable audit trail—reducing the risk of human error associated with manual processes.

If you work in immigration law or global mobility, you already know that H-1B compliance is getting more scrutiny than ever. Between increased enforcement initiatives like Project Firewall and growing coordination between agencies, what used to feel like “back-office admin work” is now front and center.

And yet… many teams are still handling Labor Condition Application (LCA) postings and Public Access Files (PAFs) the same way they did 10+ years ago.

So let’s break this down simply.

Why LCA Posting and PAF Compliance Matter More Than Ever

At its core, the H-1B program is built around a simple idea:

Protect U.S. workers while allowing employers to hire global talent.

To enforce that, the U.S. Department of Labor (DOL) requires employers to:

• Be transparent about hiring H-1B workers
• Pay appropriate wages
• Maintain documentation proving compliance

That’s where LCA posting and Public Access Files come in.

And importantly, these are not optional—they are explicit regulatory requirements under federal law.

What the Law Actually Requires: LCA Posting Rules Under 20 CFR

The rules for LCA posting are set out in 20 CFR § 655.734.

Here’s what employers (and their immigration lawyers) are required to do:

📌 Core LCA Notice Requirements

• Provide notice of the LCA to workers on or before the filing date
• Ensure notice is given to “affected workers” at the place of employment
• Maintain documentation showing how and when notice was provided

📌 Acceptable Methods of Notice

Under the regulations, notice can be provided through:

• Physical posting in two conspicuous locations at the worksite
• Electronic posting, including:
• Intranet postings
• Internal communication systems
• Other electronic means regularly used by employees

📌 Duration Requirements

• Notice must remain posted for at least 10 days
• The regulations do not explicitly distinguish between calendar vs. business days, so you can determine how conservative you want to be.

📌 Special Considerations

• Remote workers must be included in the notice process
• Notice must be accessible—not hidden or difficult to find

Breaking It Down Simply: What Good vs. Bad Compliance Looks (Written for a 5-year old!)

Let’s simplify the rules into something more practical:

• Posting before filing, good
• Posting after filing, bad
• Posting for 10+ days, good
• Taking it down early, bad
• Posting where employees actually look, good
• Hiding it somewhere obscure, bad
• Including remote employees, good
• Forgetting them, bad
• Keeping proof of posting, good
• “We think we did it…”, bad

When you look at it this way, the rules are not complicated. But execution is where most problems happen.

Public Access Files (PAFs): The Documentation That Proves Compliance

If LCA posting is about transparency, then the Public Access File is about proof.

Under 20 CFR § 655.760, employers must create and maintain a Public Access File for each H-1B worker.

📂 What Must Be Included in a PAF

A compliant PAF typically includes:

• A copy of the certified LCA
• Documentation of the wage rate paid
• Explanation of the wage system used
• Evidence of LCA posting (timing and method)
• Summary of benefits offered to U.S. workers vs. H-1B workers

📂 Timing Requirements

• The PAF must be created within one working day of filing the LCA

📂 Retention Requirements

• Must be retained for:
• One year beyond the last date of employment under the LCA, or
• One year from LCA expiration if no worker was employed
• Holding onto PAFs for longer than necessary isn't illegal, but it can expose you to more risk than is necessary!

What Good vs. Bad PAF Management Looks Like

Again, simplifying:

• Creating the PAF within 1 day, good
• Waiting to put it together later, bad
• Including all required documents, good
• Missing key documents, bad
• Keeping files organized and accessible, good
• Searching emails to rebuild them, bad
• Following retention rules, good
• Keeping everything forever (or deleting too early), risky
• Knowing exactly where PAFs are stored, good
• “We’ll figure it out if audited…”, bad

The Real Problem: Manual, Paper-Based Compliance

Even though the rules are clear, the process most firms still use is not.

Here’s what the traditional workflow often looks like:

• Law firm emails PDF notice and instructions
• Client is asked to print and post
• Law firm follows up (multiple times)
• Client confirms (or doesn’t)
• PAF instructions sent via email
• Client assembles documents manually

This creates a long list of risks:

• Was it actually posted?
• Was it posted long enough?
• Was it posted in the right place?
• Was the PAF created on time?
• Is it complete?
• Can it be produced during an audit?

And in today’s enforcement environment, those risks are no longer theoretical.

Why Electronic LCA Posting and Digital PAFs Are the New Standard

The regulations already allow for electronic posting. The issue is not legality—it’s adoption.

Modern compliance should look like this:

• Posting digitally once, good
• Relying on manual posting and follow-ups, bad
• Automatic tracking of posting duration, good
• Guessing how long something was posted, bad
• Instant PAF creation, good
• Delayed or incomplete PAF assembly, bad
• Centralized storage, good
• Scattered files across inboxes and folders, bad
• Full audit trail of actions, good
• No documentation of what happened, bad

The Project Firewall Reality: Compliance Is No Longer Optional

With initiatives like Project Firewall, enforcement is shifting from reactive to proactive.

That means:

• Audits can be initiated more easily
• Data across agencies is being shared
• Site visits and investigations are increasing

In this environment, compliance is no longer about checking boxes.

It’s about being audit-ready at any moment.

Why This Is Actually a Simple Problem to Solve

The irony is that when you strip away complexity, compliance becomes very straightforward:

• Tell workers properly
• Keep records properly
• Be consistent

The challenge isn’t the law—it’s the process.

And outdated processes are what create risk.

How LaborLess Helps Solve This

This is exactly why we built LaborLess.

LaborLess enables immigration law firms and in-house teams to:

• Post LCAs electronically and instantly
• Automatically track posting duration
• Generate compliant PAFs in real time
• Store all compliance data in one place
• Maintain a complete audit trail

In other words:

• Less guessing
• Less chasing
• Less risk

And much more confidence.

Ready to Modernize Your H-1B Compliance?

If any part of your current LCA and PAF process still involves:

• PDFs
• Email follow-ups
• Manual tracking
• Uncertainty

…it may be time to rethink it.

Visit www.laborless.io, fill out our contact form, and we’ll get back to you right away to get you started!

FAQ: H-1B LCA Posting and PAF Compliance

What happens if LCA posting is done incorrectly?

Employers may face fines, back wage liability, or debarment from the H-1B program under DOL enforcement authority.

Is electronic LCA posting allowed?

Yes. Under 20 CFR § 655.734, electronic posting is explicitly permitted if it reaches affected workers.

How quickly must a Public Access File be created?

Within one working day of filing the LCA, per 20 CFR § 655.760.

Do remote workers need to be included in LCA posting?

Yes. Employers must ensure notice reaches all affected workers, including remote employees.

Is over-retention of PAFs a violation?

Not necessarily—but it can increase audit exposure. Under-retention, however, is a clear violation.

What is the biggest compliance risk today?

Not knowing whether postings and PAFs were completed correctly—and not being able to prove it during an audit.

As H-1B cap season progresses and federal enforcement priorities continue to evolve, employers across the United States are becoming increasingly focused on H-1B compliance readiness. Recent policy developments and heightened scrutiny from the U.S. Department of Labor (DOL), including initiatives such as Project Firewall, have prompted many companies to conduct internal reviews of their Labor Condition Application (LCA) posting practices and Public Access File (PAF) management systems.

One clear trend emerging in 2026 is that employers are no longer waiting for an audit notice before evaluating their compliance infrastructure. Instead, organizations are proactively asking whether their existing processes can withstand detailed government inquiries. In many cases, these internal self-audits are revealing gaps in documentation tracking, retention management, and record accessibility.

Based on conversations with large H-1B employers and immigration law firms, three specific compliance expectations are becoming increasingly common.

1. The Growing Demand for Detailed LCA and Public Access File Activity Logs

Employers are increasingly anticipating that future H-1B audits will involve granular documentation reviews, not simply requests for the existence of a Public Access File. Government investigators may seek to understand how compliance records were created, maintained, and modified over time.

Organizations want the ability to clearly answer questions such as:

• When was a specific Public Access File created?
• Were any changes made to the file after its initial creation?
• Who made those changes and at what time?
• What documents were included in the file at a particular stage of the H-1B process?

These types of inquiries are difficult to address when PAFs are stored as hard-copy binders or static digital folders without version history. Even companies that have migrated to general cloud storage systems often lack structured audit trails showing how compliance documentation evolved.

To address this emerging need, LaborLess provides a comprehensive LCA and PAF activity log that automatically records:

• Each update made to an electronic LCA posting
• All modifications to the corresponding Public Access File
• The identity of the user who performed the action
• A precise timestamp documenting when the change occurred

This centralized audit trail helps employers and immigration counsel demonstrate a clear and consistent compliance history, supporting faster and more confident responses during a DOL investigation.

2. Managing Compliance Exposure Through Proper PAF Retention Controls

Another issue that frequently surfaces during internal compliance reviews relates to Public Access File retention timelines. The governing regulation, 20 CFR § 655.760, requires employers to retain PAF documentation for one year beyond the last date any H-1B worker is employed under the Labor Condition Application.

Failure to maintain the file for this minimum period is a direct violation of Department of Labor compliance requirements and can result in penalties or other enforcement consequences.

At the same time, retaining Public Access Files for significantly longer than required is not itself unlawful. However, doing so can increase an employer’s exposure during an audit. If older PAFs remain in the employer’s possession, the Department of Labor may still request access to those records even though the employer was no longer obligated to maintain them.

This has led many organizations to reexamine how they track and manage retention timelines. Employers are increasingly seeking compliance systems that ensure files are retained for the required duration—no less and ideally no longer than necessary.

LaborLess supports this approach through automated retention management features that allow users to assign expiration dates to each Public Access File. These timelines can be adjusted if an employee’s work authorization or employment status changes. Once the required retention period has passed, files can be securely removed from the system, helping employers reduce unnecessary audit exposure while maintaining regulatory compliance.

3. Improving Searchability and Secure Sharing of LCA and PAF Records

A third major concern for employers involves the practical challenge of locating and sharing compliance documentation quickly during an investigation. In many organizations, LCAs and Public Access Files are stored across multiple internal systems or maintained in physical filing cabinets. This decentralized approach can create delays and uncertainty when responding to time-sensitive document requests from government agencies.

Employers are increasingly prioritizing systems that allow compliance records to be retrieved using meaningful search criteria such as job title, worksite location, petitioning entity, or visa classification. They also want flexible options for securely sharing documentation with immigration counsel, auditors, or regulators.

LaborLess addresses this operational need through advanced search and reporting capabilities that enable users to identify and access relevant LCAs and PAFs within seconds. Once located, files can be downloaded, printed, or shared through secure digital links. This streamlined workflow reduces administrative burden and supports more efficient audit response strategies.

The Shift Toward Continuous H-1B Compliance Management

What is becoming clear in 2026 is that employers are beginning to treat H-1B compliance not as a periodic obligation, but as an ongoing operational responsibility. This shift is driven by a combination of regulatory uncertainty, increased enforcement activity, and the growing complexity of managing distributed workforces.

Organizations that rely on manual processes—such as emailing LCA notices for physical posting, maintaining paper Public Access Files, or tracking compliance timelines informally—are finding it increasingly difficult to maintain confidence in their audit readiness.

In contrast, centralized compliance technology platforms are helping employers create more structured and transparent workflows. By integrating electronic LCA posting, automated Public Access File generation, and lifecycle tracking into a single system, these platforms reduce the likelihood of oversight errors and improve coordination between legal teams and corporate stakeholders.

Preparing for Increased Enforcement in the H-1B Program

As employers prepare to move forward with selected H-1B cap petitions, the importance of audit readiness will continue to grow. Federal enforcement initiatives and evolving policy priorities suggest that government agencies may place greater emphasis on verifying employer compliance with longstanding regulatory obligations.

Companies that invest now in strengthening their LCA posting and Public Access File management processes will be better positioned to respond confidently to future audits. Modern compliance infrastructure not only reduces risk but also supports more efficient internal governance and improved communication between immigration law firms and their corporate clients.

LaborLess remains focused on helping organizations modernize their approach to H-1B compliance management through electronic LCA posting, automated PAF creation and retention tracking, and centralized compliance transparency.

To learn more about how LaborLess can support your immigration compliance strategy, visit www.laborless.io or connect with our team to request a demonstration.

Yet again, I've put together my annual round-up of the most interesting and important developments in immigration and global mobility tech. AI was a major topic. 2023 was the year AI showed up. 2024 was the year it started getting serious. But 2025 was the year it got funded.

Last year, the story shifted from "look what AI can potentially do" to "here's real traction and real money backing it up." Startups that were quietly building in 2023 and 2024 started raising meaningful rounds, landing enterprise clients, and in some cases, making bold strategic moves. Let's get into it.

Mobile Pathways secures $1M in funding for Pathfinder

Mobile Pathways secured a $1 million raise to help immigrants in court as asylum denial rates go up. This funding will go to Pathfinder, which will help attorneys with automated case status updates, new data-driven insights, and a centralized information system.

This was particularly exciting for me since I recently joined the Mobile Pathways as a Board Member, my first ever such position. I’m excited to help the organization use this funding and steer it toward a better future in the US.

Check out my interview with Mobile Pathways from a few years back (YouTube | Podcast)

Visalaw.ai raises $1.6M in seed funding

Visalaw.ai raised $1.6 million in seed funding led by Valor Ventures, accelerating the platform's mission to transform immigration law through generative AI. If you're not familiar with Visalaw.ai, it's built specifically for immigration law firms and offers AI-powered legal research, document drafting, summarization, and visa application construction.

What makes Visalaw.ai particularly interesting is what's under the hood. The platform has exclusive access to publications from the American Immigration Lawyers Association (AILA), including the AILA Practice and Procedures Manual, co-authored by co-founder Greg Siskind, which positions it uniquely among general-purpose legal AI tools. Siskind has noted that his firm has seen up to a 90% reduction in time spent drafting complex filings, such as EB-1 petitions.

Check out my interview with Visalaw.ai (YouTube | Podcast)

CaseBlink raises $2M, launches Studio

CaseBlink raised $2 million in pre-seed funding led by Tower Research Ventures, alongside leading VCs and immigration law firms, including Fakhoury Global Immigration. The raise came with the launch of Studio, described as the industry's first fully customizable AI drafting tool for immigration attorneys.

The CaseBlink platform covers end-to-end case preparation: document analysis and sorting, automated research, drafting of exhibit lists, legal briefs, and support letters, all compiled into a single ready-to-file PDF. At the time of the raise, they had over 50 law firms on the platform with more than 1,000 cases prepared.

Check out my interview with CaseBlink (YouTube | Podcast)

Gale raises $2.7M to automate H-1B applications

Gale raised $2.7 million in seed funding to automate administrative work for U.S. work visa applications, with an initial focus on H-1 B visas. The platform allows applicants to upload résumés and passports, automates much of the preparation work, and routes documents to a licensed immigration attorney for final review.

Gale is also building tools to monitor status-affecting changes, such as promotions or job title shifts, and working on HR system integrations to keep employers ahead of compliance requirements. That's the kind of ongoing value that keeps clients around well past the initial visa filing.

Check out my interview with Gale (YouTube | Podcast)

AffiniPay (Docketwise parent company) rebrands as 8am

In August 2025, AffiniPay rebranded to 8am — one of the more notable brand moves in legal tech this year. The Austin-based company, which serves more than 250,000 professionals across the U.S. and Canada, brought all of its products under the new name: 8am LawPay, 8am MyCase, 8am CasePeer, and, notably for this audience, 8am DocketWise.

If you've been following this series since 2022, you'll remember that Docketwise was acquired by MyCase in May 2022. Then, in June of that year, AffiniPay acquired MyCase. What started as a standalone immigration case-management platform has now been fully absorbed into a unified professional services company that has reported 217% revenue growth over the past three years.

The rebrand reflects a broader strategic shift from a payments company with acquired products to a platform integrating practice management, AI, embedded financial services, and payments under one roof. For immigration law firms using Docketwise, this is worth paying attention to, both in terms of what integrations might deepen and how the product might evolve as part of a larger platform.

Check out my first ever GMI Rocket show interview with the original Docketwise founder (YouTube | Podcast)

Boundless acquires Localyze

Boundless acquired Localyze, a European workforce mobility platform, creating (as the company says) a unified solution for navigating global workforce challenges. For those keeping track, this is Boundless's second notable acquisition, as they acquired Bridge back in 2023 to expand into enterprise immigration management.

The Localyze acquisition extends Boundless's reach into European cross-border mobility, meaning employers managing talent across the U.S. and Europe now have a single platform to work with. Boundless CEO Xiao Wang has been building toward a comprehensive global workforce immigration solution, and this acquisition is a significant step in that direction. The consolidation trend in immigration tech continues.

Check out my interview with Boundless and Localyze about the acquisition (YouTube | Podcast)

Candle AI receives investment from The LegalTech Fund

Candle AI received an investment from The LegalTech Fund and was selected to join the inaugural LegalTech Lab accelerator. While Candle AI isn't exclusively an immigration tool, it's worth including here because it's seen strong adoption among immigration attorneys specifically.

Co-founder Carl Davidson, a former lawyer, built it to address a problem he lived firsthand: the sheer amount of time legal professionals lose to client communication.

The product is an AI-powered email assistant that integrates directly with Gmail and Outlook, connects to existing case management systems, surfaces case and client details, and drafts context-aware client responses, all from inside the inbox.

For immigration attorneys who often manage high volumes of client correspondence across complex, ongoing cases, a tool that reduces inbox friction without requiring a platform switch is genuinely useful. The LegalTech Fund's backing is a strong signal of confidence in the product.

Check out my interview with Candle (YouTube | Podcast)Casium raises $5M

Casium raises $5M

Cassium raised $5 million in seed funding to help employers hire global talent faster — one of the larger early-stage immigration tech rounds this year. The company is focused on the employer side of the equation, streamlining the end-to-end process of sponsoring and managing international workers from visa filing through ongoing compliance.

CEO Priyanka Kulkarni has been building toward a platform that removes the friction and opacity from global hiring for employers and makes it less dependent on fragmented, manual processes and more predictable for both employers and employees. With a $5M seed, there's now a meaningful runway to build it out.

Check out my interview with Casium (YouTube | Podcast)

Tukki wins 43North and heads to Buffalo with $1M

Tukki was named one of the winners of the 43North competition, securing a $1 million investment and entry into the 43North accelerator program in Buffalo, New York. For those not familiar, 43North is a prestigious startup competition that drew over 1,000 applicants this year, and Tukki was among the eight finalists who pitched live on stage.

Tukki's platform helps founders and professionals navigate the U.S. visa process through a system that integrates attorney reviews, client updates, and case tracking in one place, rather than the usual scattered mix of emails, PDFs, and portals.

CEO and co-founder Ramiro Roballos is relocating to Buffalo to join the 43North ecosystem. The city's strategic location between the U.S. and Canada makes it a fitting base for a company at the intersection of cross-border talent and immigration tech.

Check out my interview with Tukki (YouTube | Podcast)

Lawfully launches Lawfully Intelligence

Lawfully launched Lawfully Intelligence, a new product designed to help users track and make sense of USCIS data releases. Anyone who has tried to do anything useful with USCIS processing time data knows how unwieldy it is. Lawfully Intelligence aims to surface that data in a format that's actually actionable for practitioners and applicants planning around case timelines.

Lawfully has been consistently iterating since their $2.5M seed round in 2022, and the launch of a standalone intelligence product signals that they're thinking beyond case tracking toward a broader data and analytics play.

Check out my interview with Lawfully (YouTube | Podcast)

LaborLess update - H-1B compliance audit tools and PERM NOF posting automation

While LaborLess did not raise funding (we are proud to be a bootstrapped company), we somehow found ourselves in the center of an H-1B compliance firestorm, specifically when the Trump Administration launched Project Firewall on September 19, 2025. As a result, interest in H-1B compliance software skyrocketed.

And as a good tech company does, we responded right away by releasing some new features to support our existing clients (and entice prospective clients to sign up for LaborLess) such as:

1. A self-serve detailed audit log of every action taken on an LCA posting and corresponding PAF,
2. Even easier ways to share PAFs in the event of an inquiry, and
3. Enhanced search functionality for users to more easily find LCA and PAF records.

In addition, we made considerable progress on a PERM NOF posting tool to enable immigration law firms to electronically post PERM Notices of Filing, specifically those tied to “in-house media” – a similar process to LCA posting.

As H-1B compliance needs continue to evolve, LaborLess continues to work with clients to release new features and tools to help them be audit-ready and generally confident.

If you’re an immigration law firm that handles H-1B visas, or a company that hires H-1B workers, please reach out to LaborLess to learn more!

2025 immigration tech conclusion

Looking across everything that happened in 2025, a few themes stand out.

First, the AI tools that were more experimental in 2023 are now raising real money and showing real traction. CaseBlink, Visalaw.ai, Gale, Tukki: these aren't ideas anymore. They have clients, a product, and investors. The window for "wait and see" in immigration AI is closing.

Second, the consolidation trend is still very much alive, as we can see from AffiniPay's rebrand and Boundless's acquisition of Loxalyze. The immigration tech landscape continues to compress as larger platforms absorb adjacent tools and capabilities. This creates both opportunities (better integrations, more comprehensive solutions) and risks (less competition, reduced optionality for firms).

Third, the employer and compliance side is getting more attention. Casium's $5M round, Gale's compliance-monitoring ambitions, and the ongoing evolution of LaborLess in response to the Trump Administration’s actions reflect a growing recognition that immigration tech is about much more than filing petitions. It's about managing ongoing compliance obligations across an entire workforce.

2025 was another strong year for the industry. And with AI adoption accelerating and more capital flowing in, 2026 will be an interesting one to look back on when this article comes out again in a year.

Thanks for reading!

As we move deeper into 2026, one thing is becoming increasingly clear: H-1B compliance is no longer something employers and immigration law firms can afford to treat casually.

At LaborLess, and since the US Department of Labor (DOL) announced "Project Firewall," we’ve been working with clients and small who are conducting internal Labor Condition Application (LCA) and Public Access File (PAF) self-audits.

The companies using LaborLess are organized, confident, and able to quickly access what they need as they get their organizations audit-ready.

But what we're hearing from the broader market is that employers (and thus their immigration law firms) relying on traditional LCA posting and PAF processes are still asking questions like: “Where are our PAFs located?” “Did we post this LCA for the required time?” “Who handled this case?” "Did we post the LCA for our remote employee?" The contrast is striking.

That gap highlights a bigger issue—and raises an important question for immigration law firms: If your client were audited by the Department of Labor tomorrow, would they actually be ready?

Emailing LCA posting and PAF instructions creates an illusion of LCA and PAF Compliance

For many immigration law firms, the current LCA and PAF workflow feels sufficient. The firm prepares the LCA posting notice, emails it to the client with instructions, asks for confirmation, and follows up with guidance on creating a Public Access File. From a legal standpoint, this may check the box.

But in practice, this approach creates a false sense of security.

Because when an audit happens, the Department of Labor is not asking whether instructions were sent. It is asking whether compliance actually occurred—and whether it can be proven quickly and clearly.

That’s where the cracks begin to show.

What May Happen During an LCA Audit by DOL

When a company is audited, expectations may vary. But most commonly, the employer must be able to produce a complete PAF, demonstrate that the LCA notice was properly posted for the required duration and in the right locations, and show that all required documentation is in place and accessible.

In theory, this should be simple. In reality, many companies struggle to answer even the most basic questions during an audit. Files may be incomplete, stored in multiple locations, or created inconsistently. LCA posting may have been delegated to an employee with little oversight. Documentation may exist, but not in a way that is easy to retrieve or verify.

For immigration law firms, this creates a difficult dynamic. Even if the firm provided clear instructions via email to their client, the outcome is still tied to the client’s execution of those instructions. The client has to post the LCA notice in two conspicuous locations for at least 10 days. The client has to create a PAF within one business day. The client has to complete, maintain and track that PAF.

And when an audit comes, the client needs to know where everything is.

The Problem with Manual, Paper-Based LCA Compliance Processes

Much of this uncertainty comes down to how compliance is handled. Traditional H-1B compliance processes rely heavily on manual execution and decentralized communication. This model introduces significant risk, especially in today’s enforcement environment.

Some of the most common issues we see include:

• LCA notices being printed and posted physically, with no verification that they were actually displayed correctly or for the required duration
• Remote or hybrid employees being asked to handle postings themselves, often without clear visibility or confirmation
• Public Access Files being stored in physical binders or scattered digital folders, making them difficult to locate during an audit
• Reliance on email confirmations as proof of compliance, without any centralized system to track or validate what was done

Individually, these may seem like small gaps. But together, they create a system where compliance is assumed rather than confirmed—and where audit readiness is uncertain at best.

What Being DOL Audit-Ready Actually Looks Like

Being audit-ready is not about sending instructions or hoping processes were followed. It’s about having a system in place that ensures compliance is executed consistently and transparently.

That means being able to confidently say that LCA notices were posted correctly and for the required period, that Public Access Files were created on time and contain all necessary documentation, and that everything can be accessed immediately if requested.

It also means that both the law firm and the employer have visibility into the process—not just at the beginning, but throughout the lifecycle of each case.

Without that level of control, audit readiness becomes reactive rather than proactive.

How LaborLess Changes the Equation

LaborLess was built to address exactly these challenges by giving immigration law firms and employers a centralized, automated way to manage LCA and PAF compliance.

Instead of relying on instructions and follow-up emails, LaborLess enables firms to actively oversee and participate in the compliance process alongside their clients.

With LaborLess, law firms can:

1. Post LCA notices electronically in a compliant manner and ensure they remain visible for the correct duration
2. Automatically generate and maintain Public Access Files, including required documentation and updates
3. Instantly access PAFs when needed, without relying on clients to locate or compile them
4. Ensure that beneficiaries receive their certified LCA copies as required
5. Maintain a clear, centralized audit trail showing exactly what was done and when

This approach transforms compliance from a fragmented, manual process into a structured and reliable system—one that supports both legal accuracy and operational efficiency.

What We’re Seeing Across the Industry

In conversations with immigration law firms, one theme comes up consistently: many firms recognize that their current approach leaves gaps, even if they’ve been working that way for years.

It’s not a question of legal expertise. It’s a question of infrastructure.

As H-1B enforcement increases, particularly with initiatives like Project Firewall, those gaps are becoming harder to ignore. And as clients become more aware of compliance risks, they are beginning to expect more than just guidance. They expect solutions.

Preparing for LCA and PAF Audits with LaborLess

The firms and companies that are best positioned moving forward are the ones that treat LCA and PAF compliance as an integrated, managed process, not an afterthought.

LaborLess makes that transition straightforward. Immigration law firms can get up and running quickly, adapt the platform to clients of all sizes, and provide a higher level of service without increasing internal burden.

So if your current process relies on emails, manual posting, and decentralized file storage, it may be time to take a closer look at whether that approach will hold up under scrutiny.

To learn more about how LaborLess can support your H-1B compliance strategy, visit https://www.laborless.io or check out demo here: https://www.laborless.io/demo.

In 2026, H-1B compliance, including LCA posting and Public Access File management, is under more scrutiny than ever before. With the Trump Administration's renewed focus on enforcement and oversight—especially through the U.S. Department of Labor’s new initiative, Project Firewall—employers and immigration attorneys must take a fresh look at even the most basic compliance questions.

One of those often-overlooked questions: Should LCA posting notices be posted for 10 calendar days or 10 business days? This detail may seem minor, but it can have serious implications during audits or investigations, especially in a climate of heightened enforcement.

Let’s explore what the regulations actually say, how the government has discussed this issue over time, and why now is the time to revisit your approach to LCA compliance—especially if you’re still relying on manual processes.

What the Regulations Say: 20 CFR § 655.734

The foundational regulation for H-1B Labor Condition Application (LCA) posting is 20 CFR § 655.734. This section outlines how and where LCA notices must be posted, and it applies to both hard-copy and electronic postings.

According to the regulation, employers must post the LCA notice:

At two conspicuous locations at each place of employment for 10 days or, in the case of electronic posting, using any “electronic means normally used to communicate with workers,” for the same duration.

However, the rule refers only to “10 days”—not specifically 10 business days, and not 10 calendar days. This ambiguity has sparked a long-running debate in the immigration compliance world.

So, how have agencies and practitioners interpreted it?

The DOL’s Field Assistance Bulletin on Electronic Posting

In 2019, the Department of Labor’s Wage and Hour Division published Field Assistance Bulletin No. 2019-3, one of the most detailed explanations to date on electronic LCA posting compliance.

This bulletin outlines what constitutes a valid electronic posting, including:

• Using intranet systems or digital bulletin boards to notify affected workers, and
• Ensuring the notice is accessible for the required 10 days.

Importantly, the bulletin once again uses only the phrase “10 days”, without clarifying whether that means calendar or business days. So while the FAB brought valuable guidance to the mechanics of electronic posting, it didn’t resolve the calendar vs. business day debate.

COVID-Era Guidance and August 2023 DOL FAQ

During the COVID-19 pandemic, remote work forced many employers to rethink where and how LCAs were posted. The DOL responded with a series of FAQs related to LCA posting and worksite changes in the context of remote work.

But 0n August 24, 2023, the DOL issued a new set of FAQs that explicitly stated they were meant to supersede all previous COVID-related guidance. Most critically, this new guidance referenced that LCA notices must be posted for 10 "calendar" days.

Although this language appeared somewhat casually (rather than in the context of a regulatory change) it was a significant moment for those of us who have followed this issue closely.

As the CEO of LaborLess and a former immigration attorney focused on H-1B visas, I saw this as the DOL’s first clear written statement that “10 days” means 10 calendar days in the context of LCA posting compliance. Of course it was not framed as an official clarification, so it may not necessarily be taken as "law", but for the sake of argument, one might say that it helped clarify the ambiguity that has surrounded LCA posting duration.

PERM: Where the “10 Business Days” Standard Might Come From

Part of the reason many immigration lawyers think that LCA posting notices must be up for 10 "business" days may stem from the PERM Notice of Filing (NOF) requirement, which is regulated under 20 CFR § 656.10. But that regulation clearly states that the PERM NOF must be posted for 10 consecutive business days.

In fact, the DOL’s own PERM FAQ guidance goes further, specifying that weekends and holidays do not count toward the 10-day minimum posting.

It’s likely that some immigration professionals, familiar with the PERM process, applied that same “10 business days” standard to H-1B LCA postings, specifically since the H-1B regulations never clarified otherwise.

But since H-1B LCA posting rules are distinct from PERM, and the DOL now appears to support a calendar-day interpretation in practice, it's a new consideration to keep in mind.

The difference between 10 calendar days and 10 business days may seem small—but in an audit, it could determine whether a company is found compliant or penalized for a technical violation.

It also raises a larger question: How confident are you in your LCA posting and PAF creation process?

Time to Rethink How LCA Compliance Happens

Even if you’ve interpreted the 10-day rule correctly, how you manage the overall process matters just as much.

Many companies and immigration law firms still:

• Email PDFs of LCA notices to clients and hope they get posted
• Ask remote employees to print and tape postings to their home office walls
• Store Public Access Files in binders, shared drives, or not at al
• Rely on emails for audit documentation and version control

This is not sustainable in an era of proactive compliance enforcement.

If there’s no centralized system to create, track, and validate the compliance lifecycle, especially with respect to LCA posting timelines and PAF completeness. employers are exposed to unnecessary risk.

How LaborLess Supports Modern H-1B Compliance

That’s why we built LaborLess. Our platform helps immigration law firms and H-1B employers:

• Post LCA notices electronically in a compliant, visible way that meets DOL standards
• Automate Public Access File creation, including all required documentation
• Track posting timelines and expiration dates to ensure timely compliance
• Maintain centralized visibility and audit trails for all stakeholders
• Auto-purge PAFs after their retention period to minimize liability

And later this year, we’ll be releasing a new module to support PERM Notice of Filing compliance—so you can bring the same level of confidence to your PERM cases as you do to H-1Bs.

To learn more or request a demo, visit www.laborless.io or explore more resources and insights on the LaborLess blog.

In late January, 2026, the Department of Labor’s Wage and Hour Division (WHD) published a new guidance PDF under its Project Firewall enforcement initiative. While the document itself is short, its implications for immigration law firms and H‑1B employers are significant. The guidance makes one thing unmistakably clear: H‑1B compliance enforcement is accelerating, and Labor Condition Application (LCA) notice is the first place regulators are looking.

In fact, the very first obligation listed in the guidance is not about wages, recruitment, or displacement. It is about providing notice of the LCA to U.S. workers on or before the date of filing. That ordering is intentional. It reflects how WHD views the compliance framework and mirrors what the LaborLess team has been saying for years, sometimes to the point of sounding like a broken record. LCA posting is not a technical afterthought. It is the foundation of H‑1B compliance, and it is one of the easiest areas for the government to audit.

Despite this clarity, there are still immigration law firms, and many employers they represent, that do not actually know whether LCA notices are being posted correctly, posted for the full required period, or documented properly in Public Access Files (PAFs). In an era of Project Firewall, that lack of visibility is no longer just uncomfortable. It is risky.

What DOL’s Project Firewall Means for H‑1B Employers and Law Firms

Project Firewall is WHD’s formal enforcement initiative designed to protect U.S. workers and maximize compliance with the H‑1B visa program. The guidance explains that the initiative strengthens WHD’s ability to hold employers accountable when they misuse the H‑1B program and to ensure that qualified American workers are not unfairly displaced.

What is particularly notable is not just what the guidance says, but how it frames compliance. The document emphasizes baseline obligations that apply to all H‑1B employers, before addressing additional obligations for H‑1B‑dependent employers and willful violators. At the top of that list is notice. From WHD’s perspective, if an employer cannot demonstrate that it properly notified U.S. workers, it raises immediate concerns about whether the employer is meeting its other attestations.

This matters because LCA notice is one of the easiest compliance elements for regulators to verify. Auditors do not need to infer intent or investigate complex wage calculations. They simply ask: Was notice provided? Where? For how long? And can you prove it?

Why LCA Posting Notice May Be a Primary Target in H‑1B Audits

LCA notice exists to ensure transparency. It gives U.S. workers visibility into the terms under which an H‑1B worker is being employed and an opportunity to raise concerns if something appears improper. Because notice is framed as a worker protection mechanism, failures in this area are treated seriously, even if there was no bad intent.

From an enforcement standpoint, LCA posting often becomes the entry point into broader investigations. If notice cannot be substantiated, WHD and other agencies such as FDNS may expand their review to include wages, job duties, work locations, and recruitment practices. In other words, notice failures can turn a narrow audit into a wide‑ranging inquiry.

H‑1B LCA Posting Requirements Under 20 CFR: What Employers Are Legally Required to Do

The obligation to provide notice of the Labor Condition Application is grounded in Department of Labor regulations at 20 CFR § 655.734. These regulations set out specific, affirmative steps that employers must follow. They are not guidelines or best practices; they are legal requirements.

Under 20 CFR § 655.734, H‑1B employers must ensure the following:

• Notice must be provided on or before the LCA filing date. Employers cannot file first and post later, unless it's the same day. Notice must occur no later than the date the LCA is submitted to DOL.

• Notice must be provided to workers in the same occupational classification. The obligation is to notify similarly employed U.S. workers at the place of employment, not the general public.

• Notice must be posted for at least 10 consecutive business days. This is one of the most common compliance failure points. Business days matter.

• Notice must be posted in two conspicuous locations or provided electronically. Employers may choose physical posting or electronic notice.

• Electronic notice must be reasonably calculated to reach affected workers. For remote and hybrid workforces, electronic posting is often the only defensible option, but it must actually be accessible.

• Each worksite requires notice. Multiple worksites mean multiple notice obligations.

The regulations do not require employers to prove intent. They require employers to prove process. During an audit, WHD may focus on how notice was provided, where it was accessible, and for how long. If those answers are unclear or undocumented, enforcement risk increases quickly.

H‑1B Public Access File (PAF) Requirements: The Evidence DOL Auditors Expect to See

If LCA notice is the trigger for scrutiny, the Public Access File is the evidence auditors rely on to determine compliance. DOL regulations require that a PAF be created within one working day of filing the LCA and made available to the public upon request.

A compliant H‑1B Public Access File must include, at a minimum:

• A copy of the certified Labor Condition Application.
• Documentation of the wage rate paid to the H‑1B worker.
• The prevailing wage source and explanation.
• The actual wage memorandum.
• Evidence of LCA notice to U.S. workers. This includes how notice was provided, where it was accessible, and the duration of posting.
• Benefit summaries if H‑1B and U.S. worker benefits differ.
• Clear retention and destruction practices. Holding PAFs too long can be as risky as destroying them too early.

From an enforcement perspective, the PAF is not a formality. It is the primary evidentiary record. Incomplete or reconstructed PAFs invite expanded audits and penalties.

The Compliance Gap Most Programs Still Have

In theory, employers are responsible for posting LCAs. In practice, many immigration law firms email posting instructions to clients and hope for the best. Once that email is sent, visibility is lost. Firms often do not know whether the notice was posted immediately, whether it remained up for the full 10 business days, or whether it was accessible to the right group of workers.

Under Project Firewall, hope is not a compliance strategy. Assumptions are not evidence.

Turning Compliance Into Proof, Not Guesswork

The WHD’s Project Firewall guidance may be short, but its message is loud. LCA notice is the first thing regulators care about, and it is the first thing they will check. If you are not confident that your H‑1B employer clients are posting notices correctly, for the right duration, and maintaining compliant Public Access Files, now is the time to address that gap.

This is exactly why LaborLess exists. LaborLess enables immigration law firms and H-1B employers to post electronic LCA notices, with automated posting duration tracking, and real‑time Public Access File creation. LaborLess creates verifiable, timestamped records so that if and when auditors ask questions, the answers may be even easier to produce.

Reach out to us at www.laborless.io and fill out our contact form. We reply right away and are happy to discuss how to modernize your LCA and PAF compliance before an audit forces the issue.

FAQ

What is Project Firewall?
Project Firewall is the Department of Labor Wage and Hour Division’s enforcement initiative focused on maximizing H‑1B compliance and protecting U.S. workers.

Why is LCA posting emphasized first in DOL guidance?
Because notice is a core worker protection mechanism and one of the easiest compliance elements for auditors to verify.

How long must an LCA notice be posted?
At least 10 consecutive business days, on or before the LCA filing date, under 20 CFR § 655.734.

Is electronic LCA posting allowed?
Yes. DOL regulations permit electronic notice as long as it is reasonably calculated to reach affected workers.

What happens if an employer fails to comply?
WHD may recover back wages, assess civil money penalties, and impose debarment from the H‑1B program.

How does LaborLess help?
LaborLess automates electronic LCA posting, tracks posting duration, and generates compliant Public Access Files, giving employers and law firms defensible proof of compliance.

For years, H-1B compliance at many immigration law firms has rested on a simple strategy: send the client emails with the information they need, you're all set.

These emails are usually filled with step-by-step instructions about posting LCA (Labor Condition Application) notices and creating  PAFs (Public Access Files). But in truth, these emails are not really ensuring H-1B compliance. What they do ensure, however, is that the immigration law firm has "CYA'd", or "Covered their a**".

With the Department of Labor’s new “Project Firewall” enforcement initiative gaining traction, this compliance-by-email model no longer cuts it.

Let’s break down how the process works today, where it falls apart, and why immigration law firms and employers need a better, tech-driven solution for 2026 and beyond.

The Typical LCA posting and PAF Compliance Workflow (And Where It Relies on CYA)

When a new H-1B case gets initiated, here’s what usually happens:

The immigration law firm prepares the LCA notice and emails it to the client with instructions on where and how to post it, how long it must be posted, and a request to confirm once it's done.
→ This is the first “CYA” email.

The client replies saying it’s been posted. The firm then proceeds to submit the LCA through the DOL’s FLAG system.

Within one working day, the law firm sends another email outlining how to create a compliant PAF—what to include, how to organize it, and how long to retain it.
→ This is the second “CYA” email.

The H-1B petition is filed with USCIS, the case is approved, and the process appears complete.

Or is it?

What Law Firms Don’t Know about

Here’s the hard truth: in most cases, immigration firms don’t actually know if the client:

Posted the LCA notice correctly

Made the LCA visible to remote or hybrid coworkers

Created the Public Access File within the required 1-day timeframe

Included all the required documents in the PAF

Stored it in an audit-ready location

There’s no real-time visibility. No digital audit trail. No centralized compliance dashboard.

Instead, the law firm relies on the client’s confirmation via email (if that)—and if something goes wrong, they point to those emails as proof that the firm did its job.

From a legal liability perspective, that might be sufficient.

But from a client service and risk management perspective? It's probably not.

Why This Matters More Than Ever: Enter Project Firewall

The Department of Labor’s Project Firewall has made one thing clear: H-1B employer compliance is now a federal enforcement priority.

Project Firewall gives the DOL expanded authority to initiate investigations—without needing a whistleblower complaint. It also increases coordination between the DOL, DOJ, USCIS, and EEOC, meaning that compliance gaps are more likely to be flagged, audited, and penalized.

For law firms, this puts new pressure on the traditional CYA model.

Because when a client is audited and the DOL finds a missing LCA posting or an incomplete PAF, the response “we sent you the instructions” won’t cut it.

And if the client’s company faces fines or reputational damage, they won’t blame themselves—they’ll blame their lawyer.

The Risks of Manual, Email-Driven LCA posting and PAF Compliance

Most law firms still treat LCA posting and PAF management as afterthoughts.

LCA notices are sent as PDFs, with a request to print and post them at physical worksites

Remote employees are often asked to print notices and post them at home—something the DOL has clarified as problematic

PAFs are left to clients to compile and store, without any centralized system or visibility

There’s no automatic PAF expiration or audit history

This creates risk—not only for employers, but for the law firms that serve them.

And with compliance enforcement on the rise, that risk is growing fast.

The Role of Technology in Fixing This

The solution isn’t more emails. It’s smarter infrastructure.

Just as law firms have adopted platforms for document collection, form filling, calendaring, and status tracking, H-1B compliance should be automated and centralized.

That means:

Electronic LCA posting that ensures notices are visible to affected employees, across all locations

Automated PAF generation within one business day of LCA filing, with templates, version control, and audit trails

Real-time visibility for the law firm and client, so there’s no guessing whether compliance steps were completed

Secure digital storage of PAFs, with automatic expiration and purge options after the retention period

Law firms can no longer afford to treat compliance as an email checklist. It’s time to treat it as a core part of legal service delivery—and a key risk area to control. Whether you're a large immigration law firm with massive corporate clients or a small or solo immigration law firm with SMB's filing just a few H-1Bs each per year.

The LaborLess Advantage

LaborLess was built specifically for this purpose. Our platform allows immigration law firms to:

Post LCAs electronically on behalf of their clients

Automatically generate and manage PAFs

Maintain transparency and control over every step of the compliance lifecycle

Audit-ready their practice while delivering real value to clients

And coming soon, LaborLess will expand to support PERM Notice of Filing compliance—bringing even more critical processes into a single, secure platform.

If you're ready to leave the "CYA" model behind and modernize your H-1B compliance, contact us at LaborLess, or explore more insights and how-tos on our blog. Because in 2026, compliance isn’t optional—and email instructions aren’t enough.