Home · Guides

WISP template for tax preparers (IRS Publication 5708 and Form W-12, line 11)

Paid preparers acknowledge a legal duty to keep a written information security plan when they apply for or renew a PTIN. This guide explains what Form W-12 line 11 is asking, what IRS Publication 5708 actually contains, and how to turn the IRS outline into a plan that fits a real office. It is not legal advice, and it is not an IRS or FTC publication.

What Form W-12 line 11 actually says

On Form W-12 (Rev. October 2026), line 11 is titled “Data Security Responsibilities.” It is a mandatory checkbox. The form states, in substance, that you are aware paid tax return preparers are required by law to create and maintain a written information security plan that provides data and system security protections for all taxpayer information. It tells you to see IRS Publications 5708 and 4557. If the line is left blank, the form says it will not be processed.

You do not attach the plan to the form, and you do not mail a WISP to the IRS with your PTIN renewal. You acknowledge the requirement, keep the plan in a readable format (the IRS suggests Word or PDF), train the people who handle taxpayer data, and review the plan as the practice changes.

The instructions for Form W-12 (Publication, iw12.pdf) point to the same publications. The IRS Security Summit has also issued public reminders that tax professionals need a written information security plan to protect client data.

The legal hook is the FTC Safeguards Rule, not a special IRS “WISP statute”

Publication 5708 is an IRS guide, not itself the regulation. In its implementation of the Gramm-Leach-Bliley Act, the Federal Trade Commission issued the Safeguards Rule (16 CFR part 314). Under that rule, tax return preparers are treated as financial institutions that must develop, implement, and maintain a comprehensive, written information security program appropriate to their size and complexity, the nature of their activities, and the sensitivity of the customer information they handle.

The required elements live in 16 CFR 314.4. They include designating a Qualified Individual, basing the program on a risk assessment, implementing safeguards (including encryption and multi-factor authentication, with limited exceptions), testing, training, service-provider oversight, a written incident-response plan, an annual written report to the board or a senior officer, and—if a “notification event” involves the information of at least 500 consumers—notice to the FTC as soon as possible and no later than 30 days after discovery (ftc.gov hosts the form).

Firms that maintain customer information concerning fewer than 5,000 consumers are exempt from only some of those elements: the written risk-assessment detail in § 314.4(b)(1), the continuous-monitoring or annual penetration-testing/vulnerability-assessment requirement in § 314.4(d)(2), the written incident-response plan in § 314.4(h), and the annual report in § 314.4(i). That is the whole list in 16 CFR 314.6. The written program itself, a Qualified Individual, MFA, encryption, vendor oversight, training, and the FTC 500-consumer notice still apply. “I’m a solo, so I don’t need a WISP” is not what the exception says.

For a checkbox-style walk through 314.4, see our FTC Safeguards Rule checklist for tax professionals.

What IRS Publication 5708 is — and what it is not

Publication 5708, Creating a Written Information Security Plan (WISP) for your Tax & Accounting Practice, is the IRS outline most firms start from. Publication 5709 is the shorter companion on how to keep a plan effective. Publication 4557 covers broader security awareness for tax professionals.

Publication 5708 is candid about its limits. It is not an exhaustive discussion of everything related to WISPs. It is not intended to replace your own research, or to create reliance, or to serve as a substitute for professional advice for your firm. It says there is no one-size-fits-all WISP: a sole practitioner can use a more abbreviated plan than a 10-partner firm. It asks you to cover physical, technical, and administrative safeguards, to keep a record of staff training, and to treat the document as evergreen—reviewed, tested, and updated.

The bare outline in the publication is roughly:

  1. Define the WISP’s objectives, purpose, and scope.
  2. Name the person responsible (the Qualified Individual) and who they report to.
  3. Describe the information you handle and where it lives.
  4. Write a risk assessment of reasonably foreseeable internal and external risks.
  5. Set policies and safeguards (access control, MFA, encryption, physical security, disposal, vendors, incident response, and so on).
  6. State how you will implement, train, monitor, test, and review the plan.
  7. Attach the inventories and acknowledgments that make the plan usable day to day (the publication includes sample attachments such as rules of behavior, authorized users, hardware, and vendors).

A “template” that still says “[Firm Name],” “[list your devices],” and “[describe your risks]” is only a starting point. The work is filling those blanks with your actual office, software, seasonal staff, and gaps—and dating the actions you still have to take.

A practical way to go from the IRS outline to a finished plan

If you want help drafting, not a blank. PreparerGuard asks about your people, systems, and controls and produces a tailored WISP as Word and PDF, following the Publication 5708 structure, with a Safeguards Rule crosswalk and a dated action list. It is a drafting tool. You still review, adapt, and adopt the plan. Solo is $79; Firm (up to 10 staff) is $149; Guided Review is $249.

Build my WISP   Download a sample WISP   Free email check

Questions we hear from preparers

Do I send this to the IRS?

No. Keep it on file and use it.

Can I just download Publication 5708 and type over the sample?

Yes. Many firms do. The sample is public. The hard part is the customization the publication already says you must do. A generator is optional; reading 5708 is not.

Is PreparerGuard IRS-approved?

No, and no commercial WISP kit we know of is. Be wary of anyone who implies otherwise.

Sources (all primary, retrieved November 2026):
  1. IRS, Form W-12, IRS Paid Preparer Tax Identification Number (PTIN) Application and Renewal, Rev. October 2026, line 11 — irs.gov/pub/irs-pdf/fw12.pdf
  2. IRS, Instructions for Form W-12 — irs.gov/pub/irs-pdf/iw12.pdf
  3. IRS, Publication 5708, Creating a Written Information Security Plan (WISP) for your Tax & Accounting Practice — irs.gov/pub/irs-pdf/p5708.pdf
  4. IRS, Publication 5709, How to Create a Written Information Security Plan — irs.gov/pub/irs-pdf/p5709.pdf
  5. IRS, Publication 4557, Safeguarding Taxpayer Data — irs.gov/pub/irs-pdf/p4557.pdf
  6. IRS Security Summit reminder on written information security plans — irs.gov newsroom
  7. 16 CFR 314.4 and 314.6 (FTC Safeguards Rule) — eCFR part 314

Related: FTC Safeguards Rule checklist · Is my tax office email spoofable? · Versión en español · Publication 4557 checklist · Data-breach reporting steps

Disclaimer. PreparerGuard provides document-drafting tools and passive, public-DNS email checks. It is not legal, tax, or professional advice, is not affiliated with or endorsed by the IRS or the FTC, and does not guarantee compliance or security. “WISP” refers to the written information security plan described in IRS Publication 5708. You must review, adapt, and adopt any plan yourself.