Rebuild I-290B, NOID, and RFE Calendars Before Oct. 23

If your team still treats every U.S. Citizenship and Immigration Services deadline as a fixed calendar date, the October 23 change will make that habit expensive. The agency issued Policy Alert PA-2026-15 on September 23, 2026, and the alert becomes effective on October 23, 2026. The rebuild is a calendar correction. The channel decides whether the final day can move, and the deadline type decides whether the channel matters at all.

The cushion belongs to paper, not to the day count

The new guidance covers paper-based filings that USCIS receives on or after October 23, 2026. USCIS continues to count all calendar days for deadlines expressly measured in days, and a paper deadline ending when USCIS is not accepting paper filings shifts to the next business day.

That means the nominal day count is still the starting point. The receipt reality is the finish line. A printed date can be a useful reminder, but it is not the same as the date the agency can receive the filing. The team should keep both dates visible: the stated deadline and the date the filing is actually received. When the two dates differ, the calendar should show the later date as the working due date.

Some deadlines are measured in days, while others are tied to an event. The channel rule only helps the first kind. The checklist below turns the rule into a row-by-row test for appeals, notices of intent to deny, and requests for evidence where the notice states a number of days. Each item is a quick check for the filing channel and the deadline type.

• Apply the new rule only to paper filings received on or after October 23, 2026.
• Count calendar days for any deadline that states a number of days.
• Move a paper deadline to the next business day when the final day is a non-paper day.
• Do not move an electronic deadline; the submission timestamp is the receipt time.
• Do not roll an eligibility-date deadline tied to a 21st birthday, just because it lands on a weekend or holiday.
• Exclude benefits governed by different regulations, such as asylum applications, from this paper-deadline rule.

The first item keeps the team from sticking to a printed date that may not be the date USCIS can receive the paper. The second item keeps the count honest. The third item catches the landing-day problem. The fourth item stops the team from borrowing a receipt cushion for an online submission. The fifth item protects age-based deadlines. The sixth item keeps the rule from spreading to benefits outside its scope.

A row is ready when the team can say how the filing will be submitted, what the notice says, and what kind of deadline it is. If the notice is silent on the channel, the team should confirm the filing method before setting the due date. If the deadline type is unclear, the team should treat the row as unresolved and escalate it. The calendar should not leave uncertainty in a rounded date.

The I-290B example shows where the cushion lands

The I-290B filing deadline weekend question is the clearest illustration. In the agency's example, an I-485 denial mailed on August 2 gave a 33-day appeal window. The 33rd day landed on a Sunday, then Labor Day, so a Form I-290B appeal received the next Tuesday was treated as timely.

The appeal example also shows why the receipt date matters more than the nominal count. The team should use the example as a check, not as a substitute for the row test. The row test keeps the calendar honest when the final day lands on a difficult date.

The rebuild belongs before the effective date

Before the effective date, the team should reclassify every deadline row by channel and type. After that, the calendar should show the actual due date, not the nominal day count. A row should fail if the team cannot answer the channel question, the stated-deadline question, and the deadline-type question. The owner of the calendar should not be the person who drafted the response. It should be the person who can see the receipt date, the filing channel, and the deadline type together.