Build a Filing Extension Contingency Plan

List each filer, return type, reporting year and obligation, including agency filing, recipient furnishing and relevant state reporting. For every row, record the verified original deadline, internal production target and source owner. Give uncertain deadlines an explicit verification task rather than carrying forward last year's date.

Describe the blocker concretely: missing year-end payroll adjustment, unreconciled vendor total, unavailable signer or untested data import. Identify the affected population and what output is needed to remove the blocker. Avoid a vague high-risk label that gives the team no information about the next action or the effort remaining.

Work backward from the original deadline to create internal checkpoints for source completion, review, extension eligibility assessment and submission. These are management targets, not additional legal deadlines. Allow time for a paper request when the procedure requires it and for obtaining an authorized signature.

The current Form 8809 instructions require an initial request by the underlying return's filing deadline and no earlier than January 1 of the year the return is due. For a combined request, use the earliest applicable deadline. Schedule the extension decision before the final day so discovering an ineligible route does not consume the remaining preparation window.

For most listed forms, a properly filed timely initial request is automatic. W-2 and 1099-NEC require a nonautomatic paper application, qualifying line 7 facts and an authorized signature. The contingency plan should identify who will verify those facts and who can sign, with a backup contact for absences.

Do not plan on a second extension for W-2 or NEC, because current Form 8809 permits only one possible 30-day extension for those forms. For other forms, an additional request is nonautomatic and must be filed before the initial granted extension expires. Treat that as a separate decision with its own evidence, not an automatic extra month built into every schedule.

Meadow Lock Services, a fictional employer, has one incomplete MISC reconciliation and a W-2 source issue. Its team creates internal gates without assigning invented federal dates. The owner of each gate must produce evidence that the dependency is resolved, not simply report that work is underway.

A provider change is not automatically a working fallback. Confirm access, supported forms, source format and responsibilities before depending on it. Do not send duplicate original returns merely to test whether another route works.

A federal agency filing extension does not change recipient furnishing. Where eligible, Form 15397 provides a separate signed request through the current online or fax route. Verify the exact form's rules, including any shorter period or restriction in its current-year instructions, before moving a furnishing target.

For ACA statements, check the applicable year's direct furnishing rules and any qualifying alternative method under Notice 2025-15. Website publication, availability and request responses remain operational tasks with owners. State reporting and any payments should retain separate deadlines until state-specific authority establishes otherwise.

At the decision gate, record what is known, which route is selected and the application owner. Preserve the final request and submission evidence. Update the schedule only for the obligation actually covered, using the correct request classification and established result. Keep a nonautomatic request's outcome distinct from its sent date.

Reprioritize the remaining work around the critical dependency: source repair, reconciliation, review or transmission. Give each task a next deliverable and escalation owner. Record changes to assumptions and source versions so the plan remains reviewable. Once the returns are filed, reconcile actual agency outcomes and furnishing evidence before closing the contingency register.