An H-1B Request for Evidence is the moment every staffing firm dreads. The petition you filed in April is sitting at a USCIS service center. Your candidate is waiting. Your client is asking for a start date. Then the notice arrives: a multi-page document asking for more evidence on issues you thought you had covered. You now have 87 days to respond, your attorney is about to invoice you, and your candidate is updating their resume on LinkedIn.
RFEs are not random. They follow patterns. USCIS adjudicators are trained to look for specific weaknesses in specific types of petitions, and IT staffing petitions sit at the top of the scrutiny list because of the third-party placement structure. If you understand the patterns, you can build a petition package that preempts most RFEs before they are ever issued.
This guide breaks down the seven most common RFE triggers for IT staffing firms and the documentation strategy that neutralizes each one.
What Is an RFE and Why Does It Matter?
A Request for Evidence is a formal notice from USCIS stating that the petition, as filed, does not contain enough evidence to make a decision. It is not a denial. It is a second chance to cure the weakness. The catch is that you only get one response, and the response has a hard deadline (usually 87 days from the issue date). If the response is late, incomplete, or insufficient, the petition is denied.
The operational cost of a single RFE is real:
- Attorney fees typically range from $1,500 to $5,000 for a well-built RFE response.
- Time between issue and approval can stretch 60 to 120 days, pushing start dates past October 1.
- Candidate attrition is common when bench consultants cannot start on time and take another offer.
- Client relationship damage occurs when promised placements slip.
For IT staffing firms filing dozens of petitions per cap season, a firm-wide RFE rate of 30 to 40 percent is not unusual. Reducing that to 10 to 15 percent is absolutely achievable with the right filing discipline.
Why IT Staffing Petitions Attract Extra Scrutiny
USCIS historically views third-party placement arrangements (where the H-1B employer is a staffing firm and the actual worksite is a client) as higher risk. The agency's concerns are rooted in a series of policy memos and the 2018 Matter of Simeio decision, all of which tightened documentation requirements for staffing firms. The adjudicator on your petition is looking for answers to questions like:
- Is the petitioner (the staffing firm) the actual employer, or just a pass-through?
- Is the end-client project real, specific, and long enough to justify H-1B employment?
- Does the staffing firm actually control the worker's day-to-day activities?
- Is the role genuinely a specialty occupation that requires a bachelor's degree in a specific field?
The seven RFE triggers below all trace back to one of these four questions.
Trigger 1: Specialty Occupation Challenges
This is the single most common RFE issued on IT staffing petitions. USCIS questions whether the role actually requires a bachelor's degree in a specific specialty, or whether any general bachelor's degree would suffice. The adjudicator is testing the "specialty occupation" threshold defined in 8 CFR 214.2(h)(4)(ii).
Typical RFE language asks the petitioner to demonstrate that:
- A bachelor's degree or higher in a specific specialty is the normal minimum for the role;
- The degree requirement is common to the industry in parallel positions at similar firms;
- The employer normally requires a degree for the role; or
- The nature of the specific duties is so specialized and complex that knowledge required to perform them is usually associated with a bachelor's degree.
How to preempt it
Include a detailed job duties breakdown that ties each duty to specific technical knowledge taught in the degree program. Generic titles like "IT Consultant" or "Computer Professional" are RFE magnets. Use specific, industry-standard titles: "Software Developer," "Data Engineer," "Cloud Solutions Architect." Support the specialty occupation argument with an expert opinion letter from a qualified academic or industry expert. Include job postings from similar firms showing a consistent bachelor's degree requirement in the same specialty.
Trigger 2: Employer-Employee Relationship (Right to Control)
When the worker will be placed at a client site, USCIS wants to see that the petitioning staffing firm, not the end client, is the true employer. This trigger traces back to the 2010 Neufeld memo, which remains influential even after subsequent policy shifts. The agency is looking for evidence that the staffing firm has the right to control the worker's day-to-day activities, not just issue paychecks.
Common RFE language demands evidence of:
- Who supervises the worker day to day;
- Who sets the hours and work location;
- Who provides the tools, equipment, and training;
- Who has authority to hire, fire, promote, and assign projects;
- Who pays the worker and handles tax withholding.
How to preempt it
Submit a detailed employer-employee relationship letter that explicitly addresses each right-to-control factor. Include the employment agreement between the staffing firm and the worker. Document the staffing firm's internal supervision structure: who the worker reports to, how performance is reviewed, how HR matters are handled. Include sample paystubs, benefit enrollment documents, and any tools or equipment provided. The goal is to show that the relationship would continue to exist even if the end-client engagement ended.
Trigger 3: End-Client Support Letter and Itinerary
If the worker will be placed at a client site, USCIS expects detailed documentation of the end-client project. Missing, vague, or template-style end-client letters are one of the fastest paths to an RFE. The agency wants to see that the project is real, the role exists, and the duration aligns with the petition validity period.
A deficient end-client letter typically:
- Is generic, undated, or signed by someone without clear authority;
- Fails to specify the exact job duties at the client site;
- Does not state the duration of the engagement;
- Does not confirm that the end client has a bona fide need for the role; or
- Does not include the client's contact information for verification.
How to preempt it
Get end-client letters on client letterhead, signed by a named manager with title and contact information. The letter should explicitly confirm the project name, the worker's role, the specific duties to be performed, the start date, the expected duration, and that the end client has a legitimate business need for the position. If the engagement is through a vendor chain (prime vendor to implementation partner to end client), document each link in the chain with master service agreements or statements of work. An itinerary showing the projected work location, duration, and description of services is required when the worker will perform services at multiple locations.
Trigger 4: LCA Wage Level Mismatch
Wage level issues are a fast-growing RFE category, especially under the new wage-weighted lottery. The adjudicator compares the wage level certified on the Labor Condition Application against the duties described in the petition and the beneficiary's qualifications. If those three data points do not align, an RFE follows.
Typical mismatches that draw RFEs:
- A "Senior Software Engineer" title with a Level 1 wage;
- Job duties describing complex system design paired with a Level 2 wage;
- A beneficiary with 8 years of experience and a master's degree filed at Level 1;
- Supervisory duties claimed in the petition but not reflected in the wage level.
How to preempt it
Make sure your LCA wage level matches the four-factor DOL analysis (experience, education, special skills, supervision) for the specific role and candidate. The wage level on the LCA, the duties described in the support letter, and the beneficiary's qualifications should tell the same story. For a deeper walkthrough, see our guide on Prevailing Wage Levels Decoded.
Trigger 5: Beneficiary Qualifications and Degree Equivalency
If the beneficiary's degree is from outside the United States, or if the degree field is not a direct match for the occupation, USCIS will ask for more evidence. Software developers with degrees in "Computer Science" are rarely questioned. Software developers with degrees in "Electronics and Communication Engineering" or "Mathematics" often are.
Common triggers in this category:
- Foreign degree without a credential evaluation;
- Three-year bachelor's degrees from India that require an additional year of education or experience to equate to a U.S. bachelor's;
- Degree field that does not obviously align with the specialty occupation;
- Experience-based equivalencies that lack documentation of the "three-for-one" rule (three years of relevant experience equals one year of college education).
How to preempt it
For every foreign degree, include a credential evaluation from a recognized evaluator (World Education Services, Educational Credential Evaluators, and similar). If the beneficiary's degree field is not a direct match, include an academic evaluation that maps the coursework to the specialty occupation. For experience-based equivalencies, include detailed employment verification letters documenting the beneficiary's specific duties and skills across each role. Transcripts, diplomas, and employment letters should all be in the package as a default, not on request.
Trigger 6: Maintenance of Status
For beneficiaries already in the United States (change of status or extension petitions), USCIS verifies that the beneficiary has maintained valid status continuously. Any gap, any period of unauthorized employment, or any prior status violation can trigger an RFE or an outright denial.
Common issues flagged:
- Gaps between H-1B approvals where the beneficiary did not maintain status through another valid visa category;
- Unpaid benching periods that violate the H-1B wage payment requirement;
- Unauthorized employment during OPT or STEM OPT;
- Untimely extension filings;
- Discrepancies between Form I-94 records and the beneficiary's employment history.
How to preempt it
Pull the beneficiary's complete immigration history: all I-797 approvals, I-94 records, prior LCAs, and pay history. If there are gaps, address them proactively in the petition with a detailed explanation letter. For H-1B beneficiaries, include paystubs covering every week of the petition validity period to demonstrate continuous wage payment and avoid the "benching" issue. If the beneficiary was on OPT, include the I-20s and EAD cards for each period.
Trigger 7: Employer Financial Ability
USCIS sometimes questions whether the petitioning staffing firm has the financial resources to pay the certified wage for the duration of the employment. This is more common for smaller staffing firms, newer entities, or firms that file a high volume of petitions relative to their reported revenue.
RFE language typically asks for:
- Corporate tax returns for the last one to two years;
- Audited or reviewed financial statements;
- Quarterly wage reports (DE-9 or state equivalent);
- Evidence of active client contracts and purchase orders;
- Bank statements showing operating cash flow.
How to preempt it
If your firm is newer, smaller, or files a high volume of petitions, include financial documentation proactively. Corporate tax returns, bank statements, and a list of active client engagements (with redacted client names if confidentiality requires) demonstrate that the firm can meet its wage obligations. A short letter from the company CFO or principal affirming the firm's financial capacity to pay the certified wage adds weight.
What to Do If You Receive an RFE
Even with the best preparation, some petitions receive RFEs. When one arrives, the response process should be methodical.
- Read the entire RFE carefully. Identify every specific issue raised. Do not respond only to the obvious ones.
- Calendar the deadline immediately. The response is due by the date on the notice, not postmarked by that date. Late responses result in denial.
- Engage immigration counsel early. A well-drafted RFE response references specific regulations, cites relevant AAO decisions, and structures the evidence to directly counter each issue raised.
- Over-document the response. If USCIS asks for evidence of specialty occupation, do not send one job posting. Send ten, plus an expert opinion letter, plus industry job classification data.
- Keep the beneficiary informed. RFE responses often require additional documentation from the candidate (updated resumes, additional employment letters, bank statements). Communicate clearly about what is needed and when.
- Learn from the RFE. After the petition is adjudicated, log the RFE category and root cause. Patterns across your firm's RFEs are gold for improving future filings.
How ElevateStaffing Reduces RFE Risk
RFEs are almost always the result of missing or inconsistent documentation. A centralized platform that tracks every document, deadline, and data point across your entire candidate pool is the single best defense.
ElevateStaffing.ai gives IT staffing firms:
- Candidate document lockers where degrees, transcripts, credential evaluations, I-94s, prior approvals, and pay history are stored once and retrievable instantly.
- LCA and wage level tracking that flags mismatches between title, duties, and wage level before filing.
- End-client project records tied to each candidate placement, with supporting letters, MSAs, and itineraries in one place.
- Maintenance of status dashboards that surface gaps, late extensions, and missed paystubs before they become RFE material.
- Audit-ready Public Access Files generated automatically from the LCA and wage data already in the system.
The staffing firms with the lowest RFE rates are not the ones with the biggest legal budgets. They are the ones whose data infrastructure makes a complete, consistent petition package the default rather than the exception.
The Bottom Line
RFEs are expensive, disruptive, and avoidable. The seven triggers above account for the vast majority of RFEs issued on IT staffing petitions. Build your filing checklist around them, document proactively, and file with a clean, consistent story across the LCA, support letter, and beneficiary evidence.
Want to see how ElevateStaffing catches RFE risks before you file? Book a free demo and walk through a real petition checklist with our team.
References
- USCIS Policy Manual — Volume 2, Part H (H-1B Specialty Occupations)
- 8 CFR 214.2(h)(4) — Specialty Occupation Regulations
- USCIS — 2010 Neufeld Memo on Employer-Employee Relationship (rescinded 2020, but reasoning still influential)
- USCIS Administrative Appeals Office — AAO Decisions on Specialty Occupation and Employer-Employee Relationship
- DOL Office of Foreign Labor Certification — LCA Wage Level Guidance
Disclaimer: This article is for informational purposes only and does not constitute legal advice. RFE responses and H-1B petition strategy should be prepared in consultation with a qualified immigration attorney.