H-1B Employer-Employee Relationship RFE — What It Means

What an H-1B Employer-Employee Relationship RFE Actually Challenges

A denied H-1B petition often comes down to one regulatory question that has nothing to do with how impressive the job sounds: does the petitioning employer have the right to control the beneficiary's work? USCIS uses the term "employer-employee relationship" to mean something specific under the common-law employment framework, and when an adjudicator doubts that relationship exists, they issue a Request for Evidence targeting it directly. The RFE asks for documentation proving the petitioner will supervise the work, set the schedule, evaluate performance, and pay the beneficiary — not just act as a staffing agency placing someone at a client site.

The employer-employee relationship RFE appears most often in third-party placement scenarios: IT consulting firms staffing software engineers at client companies, staffing agencies placing specialists at hospitals or corporate offices, and any arrangement where the beneficiary's day-to-day work happens at a location the petitioner doesn't own. USCIS doesn't prohibit these arrangements, but it scrutinizes them because the regulatory test requires the petitioner to maintain control, and control is harder to demonstrate when someone else manages the work site.

An employer-employee relationship RFE requires evidence that satisfies 8 CFR 214.2(h)(4)(ii), which defines the relationship by reference to common-law agency principles. The regulation doesn't list a checklist, so officers evaluate the totality of circumstances — who hires, who fires, who supervises, who pays, who sets the tasks — and whether those facts collectively establish that the petitioner, not a third party, is the actual employer.

Why USCIS Issues This RFE — The Policy Behind the Scrutiny

The employer-employee relationship standard comes from a USCIS policy memorandum issued January 8, 2010, titled "Determining Employer-Employee Relationship for Adjudication of H-1B Petitions, Including Third-Party Site Placements." That memo interprets the H-1B regulation's requirement that the petitioner be a U.S. employer by applying the common-law test used in employment tax cases. Under that test, the key factor is whether the employer has the right to control the means and manner of the work — not whether it exercises that control daily, but whether it retains the right.

USCIS tightened enforcement of this standard during periods of H-1B program scrutiny, particularly targeting consulting and staffing models where the beneficiary works at a client location under client supervision. The agency's concern is that in such arrangements, the client company — not the petitioning employer — may be the true employer, making the petition a misrepresentation of the actual employment relationship. The RFE forces the petitioner to prove the relationship is real, not nominal.

The 2010 memo remains in effect as of 2026, and it set the framework adjudicators still follow: they look for contracts between the petitioner and the end client, work orders defining the assignment, reporting structures showing the petitioner retains supervisory authority, and evidence that the petitioner can reassign, discipline, or terminate the beneficiary without the client's approval. When these elements are weak or missing, the RFE issues.

What Evidence USCIS Expects in Response

An employer-employee relationship RFE typically requests several categories of documentation, all aimed at proving the petitioner controls the work:

Contracts and work orders. USCIS wants to see the agreement between the petitioner and any third-party client where the beneficiary will perform services. The contract should define the petitioner as the employer, not a staffing vendor, and it should show the petitioner retains authority over the beneficiary's duties, schedule, and performance. A Master Services Agreement covering multiple placements may not be enough — officers often want a Statement of Work specific to this beneficiary's assignment.

Organizational charts and reporting structure. Evidence that the beneficiary reports to the petitioner's employees, not solely to client personnel. This can include internal org charts, job descriptions for the beneficiary's supervisor (who must be employed by the petitioner), and communication records showing performance reviews and task assignments come from the petitioner.

Itinerary of services. When the work occurs at multiple client sites or the assignment is project-based, USCIS requires a detailed itinerary listing each location, the work to be performed, the duration, and the client for whom the work is done. The itinerary must cover the full validity period requested on the petition.

Evidence of the petitioner's business operations. Tax returns, business licenses, office leases, and employee rosters showing the petitioner is a functioning business entity with the capacity to employ the beneficiary. USCIS looks for evidence the petitioner has payroll infrastructure, supervisory staff, and operational control over its projects.

Payroll and benefits documentation. Proof the petitioner will pay the beneficiary's wages directly, withhold taxes, and provide employment benefits. This can include payroll records for other employees, benefits plan documents, and a letter from the petitioner's HR department confirming the beneficiary will be added to payroll.

The response should explain not just what the beneficiary will do, but how the petitioner will manage that work. Evidence that the client can terminate the beneficiary without the petitioner's involvement, or that the client alone evaluates performance, undermines the employer-employee relationship.

The Control Standard — What the Common-Law Test Measures

The common-law employment test evaluates multiple factors, none dispositive individually but considered together:

USCIS understands that in third-party placements, the client will exert some operational control — that's the nature of the assignment. The question is whether the petitioner retains ultimate authority. A contract stating the petitioner can reassign the beneficiary to a different project, or terminate the beneficiary for performance reasons without needing the client's consent, supports the employer-employee relationship. A contract that gives the client exclusive authority over the beneficiary's work does not.

Here's the Honest Answer: The Staffing Model Is Not Prohibited, But It Requires Airtight Documentation

Let's be direct: USCIS does approve H-1B petitions for beneficiaries working at third-party client sites. The employer-employee relationship standard does not ban consulting arrangements or staffing models. What it bans is petitions where the petitioner cannot prove it controls the employment relationship.

The difference between an approval and an RFE in these cases almost always comes down to how the contracts are written and what supervisory structure the petitioner maintains. A petition supported by a vague Master Services Agreement, no specific assignment details, and an org chart showing the beneficiary reports only to client personnel will draw the RFE. A petition with a detailed Statement of Work naming the beneficiary, a contract clause reserving hiring/firing authority to the petitioner, and evidence of regular performance reviews conducted by the petitioner's managers stands a far better chance.

This is not a loophole to navigate — it's the standard the regulation imposes. If the petitioner genuinely controls the work, the evidence should exist. If it doesn't, the petition may not satisfy the H-1B requirements regardless of how the response is drafted.

What If the Petitioner Is a Staffing or Consulting Firm?

Staffing firms face the employer-employee relationship RFE more often than direct employers because their business model inherently involves placing workers at client sites. USCIS does not categorically deny petitions from staffing firms, but it applies the control test strictly.

The petitioner must show it is not merely a placement agency. Evidence that strengthens the case includes: direct employment contracts with the beneficiary stating the petitioner can reassign them to other clients or internal projects; internal supervisory staff who conduct regular check-ins, performance reviews, and project oversight; and contracts with end clients that define the petitioner as the employer with retained authority over personnel decisions.

What weakens the case: contracts stating the client has sole authority to direct the beneficiary's work, approve time off, or terminate the assignment; lack of any internal supervisory personnel employed by the petitioner; or an itinerary showing the beneficiary will work exclusively at one client site for the full petition period with no indication the petitioner could reassign them.

If the staffing firm has employees working on internal projects, at the firm's own offices, or across multiple clients with the firm managing the rotation, those facts support the employer-employee relationship. If every worker the firm employs is placed at a single client site with no firm-side supervision, USCIS may view the firm as a labor broker, not an employer.

What If the Beneficiary Works Remotely or at Multiple Client Sites?

Remote work complicates the employer-employee relationship analysis because there is no single physical worksite USCIS can verify. The petitioner must document how it supervises remote employees: regular video check-ins with supervisors employed by the petitioner, project management systems the petitioner controls, and performance metrics the petitioner tracks.

Multiple client sites trigger the itinerary requirement. The petition must include a detailed schedule of which client the beneficiary will serve at each location, for how long, and what work will be performed. The contracts with each client should show the petitioner retains control across all placements. A vague statement that the beneficiary will work "at various client sites as needed" will not satisfy the standard — USCIS wants specifics covering the validity period.

What If the Initial Petition Was Approved and the RFE Comes on an Extension?

Prior approval of an H-1B petition does not bind USCIS on an extension filing. Adjudicators can and do issue employer-employee relationship RFEs on extension petitions when the underlying facts have changed or when new evidence raises questions about the arrangement.

Common triggers for an extension RFE include: the beneficiary has been working at the same third-party client site for the entire initial validity period, suggesting the client may be the true employer; the petitioner's business has shrunk (fewer employees, lower revenue on tax returns), raising questions about capacity to employ; or the contracts submitted with the extension show weaker supervisory authority than the initial petition.

The extension response must address the current facts. If the beneficiary has been at one client site continuously, evidence that the petitioner conducted performance reviews, managed the assignment, and retained the right to reassign the beneficiary can overcome the concern. If the facts genuinely show the client became the de facto employer, the extension may not be approvable under the current arrangement — the petitioner would need to restructure the employment relationship or have the client file its own H-1B petition as the actual employer.

How the Law Offices of Peter D. Chu Approaches Employer-Employee Relationship RFEs

Responding to an employer-employee relationship RFE requires reconstructing the legal framework around the actual working arrangement, then gathering evidence that fits each element of the common-law test. The response should not argue that the arrangement is permissible — USCIS already knows third-party placements can be permissible. It should prove, with documentation, that this specific arrangement satisfies the control standard.

The Law Offices of Peter D. Chu reviews the contracts between the petitioner and any end clients to identify control provisions and weaknesses. When contracts lack clear employer-authority language, the firm works with the petitioner and the client to draft supplemental agreements or addenda that clarify the supervisory structure. When the org chart shows only client-side supervision, the firm helps the petitioner document any oversight the petitioner's managers actually perform, even if informal, and formalize it going forward.

RFE responses also address evidentiary gaps. If the petition lacked an itinerary, the response provides one. If payroll documentation was missing, it's gathered. If the only supervisor listed is employed by the client, the firm identifies a petitioner-side manager and documents their role in overseeing the beneficiary's work.

The consultation fee for evaluating an RFE and advising on response strategy is $250. That session reviews the RFE language, the evidence already submitted, what the petitioner can produce, and whether the facts as they exist will support approval. Some RFEs are overcome with better documentation of an arrangement that genuinely satisfies the test. Others reveal that the arrangement does not meet the standard, and the petitioner must decide whether to restructure the employment or withdraw the petition.

The Denial Risk If the Response Fails

A denied H-1B petition based on failure to establish an employer-employee relationship is a substantive finding that the regulatory requirements were not met. It is not a procedural defect that can be cured by refiling with the same facts. If USCIS concludes the petitioner does not control the employment, a new petition with the same employer and same work arrangement will face the same issue.

Denial also affects the beneficiary's status. If the denial occurs while the beneficiary is in the U.S. on an expiring H-1B, they lose work authorization and must depart or change to another status. If the denial is on an extension filed before the current H-1B expired, the beneficiary may have a 60-day grace period, but that period does not allow work.

Some petitioners respond to an employer-employee relationship denial by having the end client file the H-1B petition directly, if the client is willing and the beneficiary will work exclusively for that client. That eliminates the third-party placement issue, but it requires the client to sponsor the visa — a different business relationship.

The Bigger Picture: Why This RFE Matters to the H-1B Program

The employer-employee relationship standard exists because the H-1B statute limits the visa to workers employed by a U.S. employer in a specialty occupation. Congress did not create the visa to allow staffing firms to supply temporary labor to clients who avoid the sponsorship obligation. USCIS enforces the standard to ensure the petitioner is the actual employer, not a pass-through.

From the agency's perspective, allowing nominal employer-employee relationships would undermine the wage protections built into the H-1B program. The Labor Condition Application requires the employer to attest it will pay the prevailing wage and provide working conditions that won't adversely affect U.S. workers. If the petitioner is not the true employer, those attestations are meaningless — the client controls the wage and conditions, not the petitioner.

Understanding that policy rationale clarifies what the RFE is actually testing: not whether the beneficiary is qualified, but whether the petitioner is genuinely employing them under U.S. labor law principles. The response should prove the petitioner is.

Disclaimer: This article provides general information about H-1B employer-employee relationship RFEs and the documentation USCIS evaluates under the common-law employment test. It is not legal advice, and reading it does not create an attorney-client relationship with the Law Offices of Peter D. Chu. The outcome of any RFE response depends on the specific facts of the petitioner's business arrangement, the contracts in place, and the evidence available. Consult a licensed immigration attorney to evaluate your specific situation and determine the best response strategy. Immigration law is complex, and errors in responding to an RFE can result in petition denial and loss of work authorization.

Schedule a consultation with the Law Offices of Peter D. Chu — 4615 Convoy St, San Diego, CA 92111 · 858-268-8823 · Mon–Fri, 8:30 AM–5:30 PM. Consultation fee: $250.