Pre-Filing Evidence Checklist for H-1B, L-1, and PERM

The deadline is before filing

The deadline to fix is before filing, not after a denial letter lands. USCIS issued Policy Alert PA-2026-05 to update Policy Manual guidance on evidence, RFEs, and NOIDs. Under that alert, an officer may deny a benefit request when required initial evidence is missing, without first issuing an RFE or NOID. It covers requests already pending or filed from August 5, 2026 onward, unless a different regulation or agency policy says otherwise.

The package you file must stand on its own. The sponsor controls the initial record before the officer ever asks for anything, so the exposure is direct. The initial record is the part of the file the team can fully control at filing. The sponsor should not wait for the officer to identify the gap.

The policy reaches employer petitions, including H-1B and I-140, plus I-130, I-485, and I-765 filings. For a mobility team, the same completeness discipline applies across the filings that keep workers moving. Treat each filing as if the initial package is all the officer will see.

Run a short pre-filing audit

A pre-filing audit works best as a gate, not a research project. The owner should be able to answer a short set of questions before the filing goes out: Is the case in scope? Is the initial evidence complete? Is the response calendar ready? The answers should be yes, yes, and yes. The tracker should show the owner, the filing date, and the response deadline before the package leaves the office. If a question cannot be answered, hold the package.

For each petition type, the form's initial-evidence list is the starting point. The audit should compare the file to that list line by line. If an exhibit is missing, the fix is before filing, not after a denial. For employer filings, the sponsor's proof belongs in the initial package. The officer should not have to hunt for the employer-specific record. If the proof is buried, the package is not ready. The audit should be repeatable by another reviewer without a long explanation. The record should be short and dated: petition type, form used, exhibits checked, missing items, and the date the file was closed before sending. The owner should see the record without opening the full file.

RFE response deadlines are no longer a flat 12 weeks; officers set them case by case, with 12 weeks only as a ceiling, so the tracker must capture the deadline on the letter. The response calendar should be built from the letter, not from habit. If the deadline is shorter than the team's standard turnaround, the filing date may need to move.

Use the checklist as the gate

Use this list before any filing goes out. Each item is a quick test, not a project.

• Mark the case in scope.
• Confirm every item the form lists as required initial evidence is present, legible, and consistent.
• For H-1B and I-140 employer petitions, attach the employer-specific proof the form requires at filing.
• Calendar the officer-set RFE deadline.
• If you respond by mail, add only 3 days under 8 CFR 103.8(b), regardless of location; the 14-day international grace period is gone.
• Get a named sign-off that the package is complete enough to survive denial without an RFE.

The list is short on purpose. It should be the last step before the package is sent, not a substitute for the audit. If an item fails, the package stops. The reviewer should not need to know the case history to run it. The notes should show what was checked, what was missing, and who cleared the gap.

Make the sign-off accountable

The sign-off should be a named person, not a team. That person confirms the package can survive a no-RFE denial. The named person should be able to explain the file to another reviewer the next morning without a long briefing. The tracker must also show the response deadline and the mail-service calculation. If either is missing, the filing is not ready.

Include the date, the scope, and any exceptions. If there is a known gap, note why the filing is still appropriate. Keep the tracker next to the filing package so the sign-off is visible. Keep it in the file, not in an email thread where it can be missed. If the answer is unclear, hold the filing before submission.