I-129 deference repeal: comment by Nov 13, then rebuild extensions

Protect the comment date before the rule change

If your extension pipeline leans on prior approvals, the first date to protect is November 13, 2026. DHS and USCIS proposed dropping the regulation at 8 CFR 214.1(c)(5), which now lets an officer carry forward a prior approval when the same facts support an extension. The proposal was published in the Federal Register on October 14, with comments routed to regulations.gov under DHS Docket No. USCIS-2026-0529. Until a final rule takes effect, the current deference rule remains in force.

Materiality is a portfolio call, not a policy debate

The proposal would reach every Form I-129 petition, including the H-1B, L-1, O-1, TN, E, and P categories. That reach puts the comment decision with the team that owns the filing calendar. DHS put the affected volume at about 208,000 petitions per year and projected that ending deference could lift the RFE rate by about 3 percentage points, or about 6,000 additional RFEs each year. In the past four fiscal years, RFE cases ran 64 days longer on average. If that pressure would move your processing dates, the proposal is material.

If the materiality call is yes, submit the comment before the deadline. The comment should explain how the deference change would affect your filings, not whether you support the policy. Keep it short, factual, and tied to the Federal Register docket.

Inventory the pipeline before the comment is filed

Start with the extension files that will be filed soonest. Group them by category, work location, and filing date. If a group would be affected by the proposed change, treat the proposal as material. The comment decision should be made before the filing calendar does it for you. A short internal memo can capture the volume, the processing risk, and the evidence gap. It does not need to be a legal opinion. It needs to be a record that the team looked at the pipeline and made a call. The memo should name the owner and next filing date.

Rebuild each extension as if the prior approval never existed

The practical fix is to stop treating the prior approval as evidence. Apply the same rebuild to every extension file. The file should answer the core questions without the old approval: what the job actually is, why the beneficiary qualifies, and how the employer is organized to support the role. Build the extension so the officer can approve it from the evidence in front of them.

The checklist below is the one to keep in each case folder. Each item is a minute-level test, not a full audit. The evidence standard is simple: the file must prove the extension on its own.

• Confirm the job description states the principal duties, not just the title.
• Confirm the beneficiary's credentials match the stated role requirement.
• Confirm the employer's org chart shows the reporting line and the employee's place in the structure.
• Confirm the work location, hours, and salary match the petition and the actual assignment.
• Confirm any required license, registration, or credential is current and attached.
• Confirm the employer's support documents show the ability to pay the stated wage.
• Confirm the petition explains why the extension is needed and how long the role will continue.
• Confirm the employer's organizational documents show the entity that is filing and the entity that will employ the beneficiary.
• Confirm the beneficiary's status history is consistent with the extension request.
• Confirm the file can stand alone: remove the prior approval and the remaining evidence still explains the role and the beneficiary.

The last item is the one that matters most. If the prior approval is removed, the remaining file should still make sense. If it does not, the gap is visible before filing. Fix the gap while the file is still in your control.