H-1B Site Visit Readiness: What FDNS Officers Actually Check (and How to Pass)

It is 10:14 on a Tuesday morning. Your office receptionist calls and says there is a federal officer in the lobby asking for your H-1B beneficiary. No appointment. No advance notice. The officer has a badge from USCIS and wants to verify that the employee is actually working, the job matches the petition, and the Public Access File is available on request.

This is the Administrative Site Visit and Verification Program, or ASVVP, in action. Officers from USCIS Fraud Detection and National Security (FDNS) conduct thousands of these visits every year, and IT staffing firms are disproportionately represented on their target list. A single poorly handled visit can trigger a petition revocation, a DOL referral, or in extreme cases, debarment from the H-1B program.

The good news is that site visits are highly procedural. Officers work from a standardized checklist, ask predictable questions, and make notes that become the basis of their report. If your firm understands the process, keeps documentation current, and drills your team for readiness, the visit becomes a non-event.

This guide walks through exactly what FDNS officers check, what they ask, what escalates a visit into trouble, and how IT staffing firms should prepare.

What Is an FDNS Site Visit?

The Administrative Site Visit and Verification Program is operated by USCIS Fraud Detection and National Security Directorate. Under ASVVP, FDNS officers or contracted investigators conduct unannounced visits to employers that have sponsored H-1B, L-1, R-1, or certain other nonimmigrant workers. The legal authority for these visits comes from 8 CFR 103.2(b)(9), which permits USCIS to verify the accuracy of information submitted in any petition.

Two important characteristics define these visits:

• They are almost always unannounced. The officer shows up with no prior notice. In rare cases, the officer may call ahead the same day, but you cannot rely on that.
• They are non-adversarial by design. The officer is a fact-finder, not an adjudicator. The goal is to verify or note discrepancies, not to litigate them on the spot.

That said, the report the officer submits goes directly to the service center that adjudicated the original petition and can become the basis for a Notice of Intent to Revoke (NOIR), an RFE on a pending extension, or a referral to the Department of Labor for wage and hour investigation.

What Triggers a Site Visit?

FDNS site visits fall into two broad categories:

Random ASVVP Visits

The majority of site visits are part of a randomized compliance verification program. Any employer that files an H-1B petition may be selected, regardless of size, history, or risk profile. These random visits are USCIS's way of maintaining baseline program integrity.

Targeted Visits

Some visits are triggered by specific risk factors. Common triggers include:

• A high volume of H-1B filings relative to the firm's size or revenue;
• A high rate of change-of-status or consular processing cases;
• Third-party placement arrangements, especially with long vendor chains;
• Complaints from former employees, competitors, or anonymous tips submitted to USCIS;
• Prior adverse findings on other petitions filed by the same firm;
• Anomalies flagged by USCIS data analytics (wage suppression patterns, inconsistent worksite reporting, mismatched DOL filings).

IT staffing firms check multiple boxes on this list by the nature of the business model, which is why the industry sees a disproportionate share of site visits.

What FDNS Officers Actually Check

The officer arrives with a printed copy of the approved petition and a structured checklist. The visit typically lasts 30 to 90 minutes. Here is what they verify in order.

1. That the Employer Exists at the Listed Address

The officer confirms that the address on the petition is a real business location, that it is operational, and that it is consistent with what was represented to USCIS. They note the exterior signage, whether the office is occupied, and whether staff can speak knowledgeably about the company. A suite that appears empty or shared with unrelated businesses raises immediate flags.

2. That the Petitioning Officer or HR Representative Is Available

The officer asks to speak with whoever signed the petition or a designated HR representative. They verify the person's role, how long they have been with the company, and their knowledge of the beneficiary's employment.

3. That the Beneficiary Actually Works There

The officer asks to see the beneficiary. For in-office placements, this means verifying the worker is physically present, has a workstation, and can be identified by coworkers. For third-party placements, the officer may travel to the end-client site or ask for documentation verifying the placement.

4. That the Job Matches the Petition

The officer asks the beneficiary to describe their daily work. They compare the answers against the job duties listed on the I-129 and LCA. A beneficiary who cannot articulate the technologies they work with, the projects they are on, or their reporting structure will draw attention. A beneficiary whose description differs materially from the petition creates a discrepancy that becomes part of the report.

5. That the Wage Is Being Paid

The officer verifies that the beneficiary is receiving the wage certified on the LCA. They may ask to see paystubs, W-2 forms, or payroll records. They also check that wage payments have been continuous, with no unpaid benching periods.

6. That the Public Access File Exists and Is Complete

The officer asks for the Public Access File (PAF) for the beneficiary. The PAF must be available within one working day of any request and must contain:

• A copy of the certified LCA;
• Documentation of the wage rate paid;
• Explanation of the actual wage system;
• Documentation of the prevailing wage source and methodology;
• Proof that the LCA notice was posted at the worksite or provided electronically;
• A summary of benefits offered to U.S. workers in the same position;
• A description of any changes in corporate structure since the LCA was filed.

7. That the Worksite Posting Was Displayed

The officer checks whether the LCA notice was posted at the actual worksite for ten business days before the LCA was filed, or whether the electronic notice requirements were met. For remote workers, this includes verifying that electronic notice was provided to affected workers via the method the firm uses to communicate with its employees (typically email or an internal portal).

8. That Corporate Changes Were Reported

If the firm has undergone a merger, acquisition, name change, or material change in ownership, the officer checks whether those changes were documented and whether any amended petitions were filed as required.

The Questions Officers Ask the Beneficiary

The beneficiary's interview is often the part of the visit where things go wrong. Officers ask open-ended questions to see whether the beneficiary's description of their job matches the petition. Common questions include:

• What is your job title?
• Who is your direct supervisor?
• What does your typical workday look like?
• What technologies, programming languages, or tools do you use?
• Where do you report to work physically each day?
• Who pays you, and how often?
• What is your salary?
• Who decides your work assignments?
• Who reviews your performance?
• Who hired you, and who interviewed you?

The beneficiary does not need to answer these questions perfectly. They need to answer them consistently with the petition. A worker who says "I am a data analyst" when the petition lists "Software Developer" creates a discrepancy. A worker who does not know their direct supervisor's name creates a discrepancy. A worker who says the end client pays them directly creates a discrepancy that implicates the employer-employee relationship.

Red Flags That Escalate a Visit

Certain findings will almost always escalate a routine visit into a referral, an NOIR, or a DOL complaint. Avoid these at all costs:

• Beneficiary is not at the listed worksite and no one can explain where they are.
• Public Access File cannot be produced. "We'll get it to you" is not an acceptable answer. The PAF is required to be available within one working day.
• Beneficiary describes duties fundamentally different from the petition. A software developer doing accounting work is a problem.
• Beneficiary cannot identify the petitioning employer. Common in long vendor chains where the worker has lost sight of who actually sponsors them.
• Wage discrepancies. Paystubs showing a wage lower than the LCA-certified wage, or extended periods with no wages paid.
• Material change to the worksite without a filed amendment. If the beneficiary has been working at a different location for 60+ days, an amended petition should have been filed.
• End-client staff deny knowing the beneficiary. In third-party placements, the client-site manager should be able to confirm the worker's presence and role.

The 30-Minute Pre-Visit Readiness Drill

You cannot predict when a site visit will happen. You can make sure you are always within 30 minutes of being fully ready. Run this drill quarterly with your compliance team.

Step 1: Pull Every Active H-1B File

For every current H-1B beneficiary, confirm the file contains the approved I-129, certified LCA, support letter, and Public Access File materials. Files should be organized by beneficiary name with a consistent naming convention.

Step 2: Verify the PAF Is Complete

For each PAF, check off the seven required components. Any missing element is a compliance gap. Update any documentation that has drifted out of date (corporate structure changes, new benefit summaries).

Step 3: Confirm Wage Payment Is Current

Pull the most recent paystubs for every H-1B beneficiary and confirm wages are being paid at or above the LCA-certified amount. Flag any beneficiary who has been in a non-productive status without wages for more than 30 days.

Step 4: Map Every Beneficiary's Current Worksite

For each H-1B worker, document the exact worksite where they are physically performing work today. Compare against the worksite listed on the most recent petition. Flag any worker whose location has changed without a filed amendment.

Step 5: Brief Every Beneficiary

Every H-1B worker should know: the exact title on their petition, their petitioning employer, their direct supervisor's name, who signs their paychecks, and how to respond professionally if a federal officer appears. Beneficiaries should know to tell the officer that they will cooperate fully but would like to contact HR or immigration counsel before answering questions in detail, especially if the visit happens unexpectedly.

Step 6: Brief Your Reception Team

Front desk staff should know that any visitor from USCIS, DOL, or DHS should be greeted politely, asked for identification, and escorted to the HR representative or compliance officer designated to handle these visits. Never tell an officer to come back another time or that the person they want is "out." Offer cooperation with a clear point of contact.

Third-Party Placements: The Harder Scenario

For IT staffing firms, many site visits happen at the end-client location rather than the staffing firm's office. This creates additional complexity because the officer may interact with client-side staff who are not your employees.

Key preparations for third-party placement visits:

• Notify the end client in advance that H-1B workers at their site may be subject to ASVVP visits. Provide them a point of contact at your firm to call if an officer arrives.
• Make sure the end client can identify your beneficiary as a contractor placed through your firm. Managers at the client site should know the worker's name, role, and staffing firm.
• Provide the end client with a redacted copy of the end-client support letter so they can corroborate the placement details if asked.
• Confirm the beneficiary has access to a quiet space to take calls or conduct the interview without disruption from client operations.
• Train your beneficiaries to contact your firm immediately if an officer arrives at their client site, even during the visit.

What to Do If a Visit Happens Today

If an FDNS officer arrives at your office or at a client site right now, here is the protocol:

1. Ask for identification. Note the officer's name, badge number, and contact information. Request a business card.
2. Cooperate, but do not rush. You are entitled to reasonable time to gather documents and coordinate. Do not refuse access, but do not fabricate or guess on answers you are unsure about.
3. Call your immigration counsel immediately. Many attorneys will offer to join by phone during the visit. Their presence often improves the tone of the interaction.
4. Produce the Public Access File. If the PAF is at a different location, explain and produce it within the one-working-day window.
5. Do not volunteer information beyond what is asked. Answer questions directly and factually, but do not go beyond the scope of the inquiry.
6. Take notes. Document who asked what, who answered, and what documents were produced. This becomes your record of the visit.
7. Follow up after the visit. If the officer identified any issues, address them immediately and in writing. A prompt follow-up letter can sometimes preempt an adverse finding.

How ElevateStaffing Keeps You Site-Visit Ready

Most site-visit failures are not dishonesty. They are organizational. Files are scattered across shared drives, paystubs live in a payroll system the HR person cannot access quickly, and the Public Access File was assembled three years ago by someone who has since left. In a 30-minute visit, that disorganization looks like non-compliance even when it is not.

ElevateStaffing.ai makes site-visit readiness the default:

• Auto-generated Public Access Files for every H-1B beneficiary, always current, always retrievable in one click.
• Worksite tracking that maps each beneficiary to their current physical work location and flags changes that trigger amendment requirements.
• Wage payment dashboards that confirm every H-1B worker has been paid at or above the LCA-certified wage, with alerts when payments stop.
• Beneficiary document lockers that make I-797 approvals, LCAs, paystubs, and petition packages accessible in seconds, not hours.
• End-client records that tie each third-party placement to the underlying MSA, statement of work, and end-client contact, so corroboration during a site visit is trivial.

The staffing firms that pass site visits cleanly are not the ones with the most elaborate policies. They are the ones whose systems make the right information instantly available to the right people, every time.

The Bottom Line

An FDNS site visit is not a crisis. It is a procedural event that either confirms your compliance posture or exposes its gaps. Treat it as the former by running quarterly readiness drills, maintaining current Public Access Files, tracking worksites in real time, and briefing both beneficiaries and reception staff on how to handle an unannounced visit.

Ready to see how ElevateStaffing keeps your H-1B program audit-ready every day? Book a free demo and walk through a real site-visit readiness checklist with our team.

References

• USCIS — Fraud Detection and National Security Directorate
• USCIS — Administrative Site Visit and Verification Program (ASVVP)
• 8 CFR 103.2(b)(9) — Verification of Information in Petitions
• DOL Wage and Hour Division — H-1B Public Access File Requirements
• USCIS Policy Manual — Volume 2, Part H (Worksite and Amendment Requirements)

Disclaimer: This article is for informational purposes only and does not constitute legal advice. Site-visit protocols and compliance strategy should be developed in consultation with a qualified immigration attorney.