Diagnosing FIRE Access Problems Before Contacting Support

Record the official site address and the task you were attempting. Were you opening the FIRE production site, the FIRE test site, the IR Application for TCC, or IRIS? Similar terminology can send a user to a working login for the wrong system.

Record the step at which progress stops: site does not load, sign-in fails, organization is not visible, a code is not recognized, upload is blocked, or a submitted file has a Bad result. These are different categories, and a password reset will not solve all of them.

Keep a concise timeline with date, time zone, browser, and the exact message. Capture a redacted screenshot only when it adds useful context. Do not put passwords, PINs, or live recipient details into a general troubleshooting ticket.

Use the IRS FIRE page for current maintenance and access guidance. Compare the observation time with the announced maintenance windows and retirement milestones. A closed test or production service cannot be restored by creating another account.

The dated transition notice gives November 1, 2026 as the last FIRE test date, November 9 for IR application changes, and November 19 at 3 p.m. Eastern for final production filing. Read the current notice before relying on an older saved procedure. IRS transition dates.

If the public site fails to load outside known windows, document the behavior and have your technical team check the ordinary browser/network path. Avoid weakening security settings or disabling company protections as an improvised fix. The objective is to identify the actual failure, not to force access through an unsupported setup.

The table classifies work; it does not claim that a particular error always has one cause. Verify the observed facts before selecting a fix.

Fictional example. An operator can sign in, view the correct company, and find a recently submitted file. Its status is Bad. A colleague opens an internal ticket titled “FIRE account broken” and suggests resetting the password.

The operator records the actual sequence: access succeeded, the file is visible, and the processed file has error details. The investigation moves to the file-processing workflow. The assigned filename and error listing are sent to the person responsible for preparing that export.

Another fictional case stops before the organization application is visible. Here, the team checks application type, organization selection, and the user's authorized role instead of editing the return file. The same broad complaint leads to a different next action because the evidence identifies a different layer.

For a genuine personal FIRE lockout, follow current official recovery guidance or contact the IRS Technical Services Operation using the route on the FIRE page. Publication 1220 describes account-reset support, but current availability and retirement instructions must also be checked. Publication 1220, common problems.

For application access, confirm the person's actual role with an authorized administrator. An operational Contact's duties and application-maintenance permissions are different. Use the current IRM role definitions to understand that boundary.

Do not use another person's account to bypass a missing authorization. Likewise, do not start an obsolete new-TCC application workflow simply because a code cannot be found in an old spreadsheet. Recover the organization's context and ask the appropriate official question.

State one specific unresolved question, followed by the exact system, legal organization reference, time of failure, observed message, and actions already tried. Include the application or assigned file reference only through an appropriate controlled channel.

Have the authorized person make account-specific inquiries. Record the official response, reference number if supplied, next action, and who will perform it. Do not treat a general suggestion as confirmation that an account has been reset or a file accepted.

After the action, repeat only the necessary check and record what changed. If the issue is a retirement limitation, move the task to the current transition route while preserving historical records. Keep any unresolved filing outcome open independently of whether access has been restored.