- Most worksite visits come from FDNS and are usually unannounced — preparation has to happen before the visit, not during it.
- The officer is verifying that the petition matches reality: job title, duties, wage, and worksite.
- A designated contact and a current petition file turn a stressful visit into a five-minute confirmation.
For most of a case's life, USCIS is a mailing address. Then one morning an officer from the Fraud Detection and National Security directorate — FDNS — walks into a client's lobby and asks to confirm a few things about an employee. The visit is brief, usually polite, and entirely routine from the agency's side. From the employer's side, it is a pop quiz they did not know was scheduled.
Your job is not to be in the room. It is to make sure that, months before the officer arrives, the client knows exactly what will happen and what to do.
Where Site Visits Come From
The administrative site visit program sends FDNS officers to verify information in approved petitions — most often H-1B and L-1. Visits can be random, but they are also triggered: a new petitioner, a third-party worksite, an amended petition, or an inconsistency flagged during adjudication. They are typically unannounced. An officer who calls ahead is the exception, not the rule.
What the Officer Is Checking
The officer's task is verification, not investigation. They are confirming that the petition you filed describes the job that actually exists:
- Does the beneficiary work here, in the role and at the worksite the petition described?
- Do the actual duties match what was filed?
- Is the beneficiary paid the wage stated in the petition and the LCA?
- Does the organization exist as represented — real space, real operations, real supervision?
None of this is hard to confirm when the petition was accurate and the file is current. All of it is hard when the role drifted, the worksite changed, or no one at the company has seen the petition since it was signed.
Failure Mode: No One Knows What Was Filed Medium Risk
The classic bad visit is not fraud. It is a receptionist who has never heard of FDNS, a manager who describes duties that do not match the petition because the job evolved, and an HR contact who is traveling. Nothing was wrong with the case. The visit went badly because the company was not ready to confirm its own facts.
"The officer is not trying to catch anyone. They are trying to confirm the truth. Make the truth easy to confirm."
The Preparation That Works
Preparation is a short list, done once and kept current:
Site-visit readiness
The right of an employer to have counsel present varies and the officer may proceed regardless, so the realistic goal is not to stage-manage the visit. It is to make sure the people present can calmly confirm facts that are already true and already on file.
After the Visit
Have the client note who came, what was asked, and what was provided, then send it to you the same day. If anything surfaced that suggests the petition and reality have drifted — a new worksite, expanded duties — that is a signal to evaluate an amendment now, not after the next notice arrives.
Keep every petition audit-ready.
GentleCase keeps the petition, LCA, and approval on one case record, flags material changes that may require an amendment, and gives your client team a single source of truth for the day an officer shows up.
