If you have real estate developer clients using the alternative method for common improvements, you will eventually meet this form. Saying yes or no casually can open, close, or precisely fix the IRS’s clock on assessments for that project. You need a clear, practical primer you can share with clients and staff without spinning up a last‑minute research marathon.
The short version: Form 921‑I is a specialized consent tied to Revenue Procedure 92‑29 for real estate projects, and it fixes the IRS assessment period based on when the project is expected to be completed, not a generic audit extension.
Key Takeaways
- Form 921‑I is not a general audit extension. It is a consent form used with Rev. Proc. 92‑29 for real estate projects, typically for investors in S corporations, partnerships, LLCs, trusts, syndicates, or pools that are not under TEFRA.
- The form fixes the assessment period to run until one year after the return is filed for the tax year when the project is expected to be completed.
- The IRS Internal Revenue Manual confirms the 921 series, explains who uses 921‑I, and distinguishes it from 921‑P and 921‑M for TEFRA and BBA partnership regimes. The section was last revised on August 7, 2025.
- A valid consent must be executed by both the taxpayer and the IRS before the normal statute expires. The IRS also recognizes properly documented faxed signatures on consents as “originals.”
- You can obtain the current two‑page April 2015 PDF directly from the IRS. Review both pages, including the on‑form instructions.
What is IRS Form 921‑I?
Form 921‑I is titled “Consent Fixing Period of Limitation on Assessment of Income and Profits Tax.” It lives in a very specific corner of tax practice, where real estate developers elect the alternative method for estimated future common improvement costs under Revenue Procedure 92‑29. In that setting, investors in the electing entity use 921‑I to agree that the IRS can assess any resulting deficiency up to one year after the return is filed for the tax year in which the project is expected to be completed.
The IRS Internal Revenue Manual spells out the 921 series and clarifies when 921‑I is the right choice. It is used by investors in an electing S corporation, partnership, LLC, trust, syndicate, or pool that are not subject to TEFRA. For TEFRA entities the counterpart is 921‑P, and for entities under the centralized partnership audit regime established by the Bipartisan Budget Act of 2015, the counterpart is 921‑M.
If you are thinking, “We usually sign Form 872 for statute extensions,” you are right in general, but 872 is the standard fixed‑date consent for assessments outside of the Rev. Proc. 92‑29 world. The Manual is explicit that waivers like Form 870 are not consents and do not extend the statute, and that any consent must be executed by both parties before the statute expires.
Why this form matters for your clients and your workflow
When a client is using Rev. Proc. 92‑29, 921‑I lets the IRS and the investor agree on a tailored assessment window keyed to project completion. That prevents a last‑minute scramble to issue a notice of deficiency and gives both sides time to reconcile the project’s cost treatment. In practice, it reduces risk for the IRS while giving you, the advisor, breathing room to finalize complex schedules and support files without rushing.
From a delivery standpoint, statute dates are unforgiving. One missed signature or an unsigned IRS line can invalidate the consent. Your team needs a crisp checklist, version‑controlled workpapers, and clear ownership. That is especially true if multiple investors need to sign or a power of attorney is involved.
Scope, not a catch‑all
It bears repeating. Form 921‑I is purpose‑built. It is not a blanket tool for exams, refund claims, or general statute management. If your matter has nothing to do with Rev. Proc. 92‑29 common improvements, you probably need a different consent form, usually Form 872. The Manual’s 2025 update continues to position 921‑I within that narrow lane.
Who should use Form 921‑I, and when?
Use 921‑I when all three are true:
- Your matter involves the alternative method for estimated costs of common improvements under Rev. Proc. 92‑29.
- The taxpayer is an investor in an electing S corporation, partnership, LLC, trust, syndicate, or pool that is not under TEFRA.
- You need to fix the assessment period to one year after the return for the year the project is expected to be completed is filed.
A quick real‑world pattern to recognize
- A client invests in a multi‑phase subdivision through an LLC taxed as a partnership.
- The developer elects the Rev. Proc. 92‑29 alternative method for common improvements like roads and utilities.
- Near statute, the IRS requests a 921‑I to ensure it can assess any deficiency tied to that project once the final numbers settle at project completion.
- You coordinate investor signatures and the IRS signature before the normal statute expires.
When 921‑I is not the right tool
- General audit extensions unrelated to Rev. Proc. 92‑29. Use Form 872 or, in some cases, 872‑A if open‑ended terms apply. Waivers such as Form 870 do not extend statutes.
- TEFRA partnerships. Use 921‑P.
- Entities under the BBA centralized partnership audit regime. Use 921‑M.
Form family overview
Comparison guide you can share with staff
| Form | Who typically uses it | What it does | When the extended period ends |
| 872 | Individuals, corporations, partnerships in general exams | Fixed‑date consent to extend time to assess tax | The specific date stated on the consent |
| 921‑I | Investors in electing S corps, partnerships, LLCs, trusts, syndicates, pools not under TEFRA, within Rev. Proc. 92‑29 | Fixes assessment period for deficiencies attributable to the alternative method on the named project | One year after filing the return for the year the project is expected to be completed |
| 921‑P | TEFRA partnerships using Rev. Proc. 92‑29 | TEFRA counterpart to 921‑I | One year after filing the return for the year of expected project completion |
| 921‑M | BBA centralized partnership audit regime using Rev. Proc. 92‑29 | BBA counterpart to 921‑I | One year after filing the return for the year of expected project completion |
The Internal Revenue Manual lists and defines each 921 variant, including the switch points between non‑TEFRA, TEFRA, and BBA. Keep this table in your binder, because misclassifying the entity’s regime is one of the easiest ways to send the wrong form.
Current form version and where to get it
The current IRS PDF for 921‑I is a two‑page April 2015 revision. Page 1 is the consent, and page 2 holds brief instructions for both IRS employees and taxpayers, including signature authority pointers and references to Delegation Order 25‑2. Download the file directly from the IRS and review both pages before you prep signatures.
Tip you can adopt firm‑wide: save a clean copy using a clear name like 921‑I_ProjectName_TaxpayerName_YYYY.pdf, then generate a separate execution set for signature. Keep the clean copy untouched for version control.
Your rights and the IRS’s policy
The IRS policy is to seek consents only when needed, and never longer than necessary to complete the examination and related actions. Each request to extend the assessment period must come with clear notice of the taxpayer’s rights. That includes the right to refuse, to limit the extension to certain issues, and to limit it to a specific date. Document these notifications in your file.
How to complete Form 921‑I, step by step
- Identify the project and taxpayer details cleanly
- Enter the investor’s name and capacity, the electing entity’s legal name, TIN, and address.
- Describe the real estate project covered by the consent. Keep it specific enough to match the Rev. Proc. 92‑29 election.
- Set the key dates correctly
- The form fixes the assessment period to any time before and up to one year after the return is filed for the tax year the project is expected to be completed.
- If a return is filed before project completion, it is treated as filed on the prescribed day without regard to extensions. Enter the expected completion year carefully.
- Limit the scope appropriately
- The consent is limited to deficiencies attributable to use of the alternative method for the described project. Do not widen it with extra language. The Manual cautions that restricted consents have specific rules, and that consent wording must reflect the parties’ intent.
- Capture all required signatures
- Investor, spouse when relevant for joint filings, authorized representative if acting under a valid power of attorney, and the delegated IRS official.
- If an attorney or agent signs, include Form 2848. Fiduciaries should include Form 56 if not already filed.
- Execute before the statute expires
- A consent must be signed by both the taxpayer and the IRS while the normal assessment period is still open. Track these dates visibly in your workflow so no one is guessing.
Signature authority and dating protocols
- Use legible names, titles, and actual execution dates in month, day, year format.
- Corporate officers, managing members, or other authorized persons can sign for entities.
- The IRS recognizes properly documented faxed signatures on consents as “originals” if contact and case notes meet Manual requirements. This policy has persisted through the 2025 IRM update.
Practical safeguard: keep a duplicate original signed by both the taxpayer and the delegated IRS official. Attach copies behind the relevant returns and store scans in your DMS with immutable audit logs.
Filing mechanics and retention
- The form itself contains brief instructions on page 2. Follow them, then file in duplicate and ensure both sets carry original signatures or properly documented faxed signatures.
- Maintain a clean, fully executed PDF and a control log with who signed, on what date, and which IRS official executed the consent under Delegation Order 25‑2.
Avoid these common errors
- Using 921‑I for a matter that is not a Rev. Proc. 92‑29 project.
- Missing the IRS signature line or getting it after the statute date.
- Mixing regimes and sending 921‑I when the entity is TEFRA or under BBA.
- Altering a consent after a taxpayer signs. If corrections are needed, prepare a fresh consent.
Privacy and secure communications
Keep all sensitive information off public pages. If you discuss specifics with the IRS, use secure channels. When circulating drafts internally, remove SSNs from filenames, restrict access by role, and log every change. The form’s instructions and the Manual emphasize proper authority and documentation, so your internal controls should match that standard.
Delivery checklists your team can use today
921‑I readiness checklist
- Confirm the matter is a Rev. Proc. 92‑29 project.
- Verify the entity’s regime, then pick the correct form in the 921 family.
- Populate project identification and expected completion year.
- Assemble signature authority: officer titles, Form 2848, or Form 56 if applicable.
- Calendar the statute date and set a seven‑day internal deadline buffer.
- Route for quality review, then secure the delegated IRS official signature.
Workpaper standards that speed reviews
- Standardized file names and version control.
- A single cover sheet summarizing project, investor, expected completion year, and statute date.
- A signature matrix that lists every required signer, their capacity, and the date signed.
- An audit log that captures contact attempts, fax logistics when used, and confirmation that rights notices were provided to the taxpayer.
Where Accountably fits, briefly
If you lead a firm that handles real estate investors across busy seasons, the pain is rarely a lack of clients. It is delivery. Forms like 921‑I expose weak SOPs, inconsistent file naming, unclear review roles, and last‑mile signature chaos. Accountably integrates trained offshore teams into your workflow with structured workpapers, layered reviews, and documented SLAs so deadlines stop being coin flips. Use us when you need capacity without chaos, not as a resume farm. We work inside your systems, follow your templates, and keep statute‑critical steps visible and owned. This keeps partners out of review loops and protects client trust when the calendar turns tight.
FAQs
Is 921‑I a general statute extension like Form 872?
No. 921‑I is tied to Rev. Proc. 92‑29 for real estate projects and fixes the assessment period to one year after filing for the year of expected project completion. Form 872 is the general fixed‑date consent most exam teams use outside of this context.
How do I know whether to use 921‑I, 921‑P, or 921‑M?
Use 921‑I for non‑TEFRA investors in an electing entity. Use 921‑P for TEFRA partnerships. Use 921‑M for entities under the BBA centralized partnership audit regime. The IRS Manual lists each form and who uses it.
Can the IRS accept faxed signatures on a 921‑I?
Yes, when the case file documents proper contact and the taxpayer’s preference to fax, a faxed consent is treated as an “original” for this purpose under the Manual’s fax policy. Keep complete case notes.
Where can I get the current 921‑I PDF?
From the IRS. The current two‑page PDF is the April 2015 revision and includes concise instructions on page 2. Verify you have the correct file before routing for signatures.
What must be true for any consent to be valid?
Both the taxpayer and the IRS must execute the consent before the normal statute expires. The consent must clearly reflect the parties’ intent, and alterations after signing are not permitted.
Final notes and compliance
- Information here is current as of January 2, 2026. Always confirm the latest IRS Manual section 25.6.22 and the current 921‑I PDF before you act.
- This article is for educational purposes. For your specific facts, consult a qualified tax professional.
- Keep clean copies, track signatures, and never let statute control live in someone’s head. Put it in your system where everyone can see it.