You're offline, showing the last version we saved.
Free template

WISP template for tax and accounting firms

Tax preparers count as financial institutions under the Gramm-Leach-Bliley Act, so the FTC Safeguards Rule requires a written information security program, and the IRS expects every professional preparer to have a written information security plan, or WISP. This template follows the structure of IRS Publication 5708 and the elements of the Safeguards Rule, sized for a small firm.

Updated · Editable Word document (.docx) · Free with a firm profile

Free with a firm profile

Get the editable WISP template

The Word document (.docx) is free with a firm profile. Enter your email and we will send a code to unlock it. No password, and one profile unlocks every template.

Have a password? Sign in

By continuing you agree to our terms and privacy policy.

Or build it with AI

Open Claude or ChatGPT with the prompt filled in. It writes the finished document for your firm straight away, then asks a few questions to tailor it. No client data needed.

Open in ClaudeOpen in ChatGPT

Works without client data. Don't paste client names, tax file numbers or ledgers into an AI tool your firm hasn't approved for them. AI data safety playbook.

How to use it

How to use this template

  1. Name your Qualified Individual

    One person who oversees the plan. In a small firm it is usually an owner. They can use an outside IT provider, but the firm stays responsible.

  2. List what you hold and where

    Fill in the inventory first: devices, software, cloud services and paper. You cannot protect information you do not know you have.

  3. Assess the risks honestly

    For each risk, say how likely it is and what you do about it today. The gaps become your action list. For AI note-takers and other vendors, see the client data questions to ask an AI notetaker vendor.

  4. Fix the gaps, then sign it

    Multi-factor authentication and encryption are requirements, not extras. Sign and date the plan, and train the team on it.

  5. Review it every year

    And whenever something changes: a new system, a new office, a new vendor or an incident.

The template

The template in full

[Firm name] written information security plan

Replace everything in [square brackets].

1. Purpose and scope

This plan sets out how [Firm name] protects the confidentiality, integrity and availability of customer information: names, addresses, Social Security numbers, tax returns and return information, bank details, identity documents, and anything else our clients give us. It covers every person who works for or with the firm, every device and system that holds customer information, and paper records.

It is written to meet the FTC Standards for Safeguarding Customer Information (16 CFR Part 314) and follows IRS Publication 5708, Creating a Written Information Security Plan for your Tax and Accounting Practice. Effective date: [date].

2. Qualified Individual and responsibilities

RoleNameResponsibilities
Qualified Individual[Name]Oversees and enforces this plan, runs the yearly risk assessment, and reports to [the owners] at least once a year.
Outside IT provider (if any)[Company, contact][What they manage: devices, backups, monitoring.] The firm stays responsible and the Qualified Individual supervises them.
Every team memberAllFollows this plan, completes security training, and reports anything suspicious to the Qualified Individual at once.

3. Risk assessment

Reviewed [date] by [name]. Rate likelihood and impact as low, medium or high. Every gap goes on the action list in section 9.

RiskLikelihoodImpactWhat we do todayGap
Phishing email steals a loginBlankBlank[e.g. MFA on email and tax software, training]Blank
Lost or stolen laptop or phoneBlankBlank[e.g. full-disk encryption, remote wipe]Blank
RansomwareBlankBlank[e.g. offline backups, patching, endpoint protection]Blank
Client data sent by ordinary emailBlankBlank[e.g. client portal, encrypted file share]Blank
Former staff keep accessBlankBlank[e.g. leaver checklist, access review]Blank
A vendor is breachedBlankBlank[e.g. vendor review, contract terms]Blank
Customer information pasted into an unapproved AI toolBlankBlank[e.g. AI policy, approved tools list]Blank
Paper records left out or thrown away unshreddedBlankBlank[e.g. clean desk, locked storage, shredding]Blank

4. Inventory: what we hold and where

ItemWhat customer information it holdsWho has accessProtection
[Tax software][Returns, SSNs, bank details][Names][MFA, roles]
[Practice management / CRM]BlankBlankBlank
[Client portal / file share]BlankBlankBlank
[Email]BlankBlankBlank
[Laptops and desktops: count]BlankBlank[Encryption, screen lock, updates]
[Phones]BlankBlankBlank
[Backups: where]BlankBlankBlank
[Paper files: where]BlankBlank[Locked cabinet]

5. Safeguards

  • Access: each person has their own login and only the access their work needs. Access is reviewed every [period] and removed the day someone leaves.
  • Multi-factor authentication for anyone who accesses customer information on any system.
  • Encryption of customer information on devices and in transit. No customer information in ordinary email attachments.
  • Updates: operating systems, browsers and software update automatically; devices that no longer get updates are retired.
  • Endpoint protection and a firewall on every device; the office Wi-Fi uses WPA2 or better with a strong password, and guests use a separate network.
  • Backups: [daily] backups, one copy offline or immutable, restore tested every [period].
  • Disposal: customer information is deleted or shredded no later than [period] after it is last needed, unless the law or a business need requires keeping it.
  • Change management: new systems and changes are checked against this plan before they go live.
  • Monitoring: logins and activity on key systems are logged and reviewed for anything unusual.
  • AI tools: customer information goes only into tools on the firm’s approved list, under its AI policy.

6. Service providers

We choose providers that can protect customer information, require it in our contracts, and check them every [period].

ProviderWhat they doCustomer information they holdSecurity terms in contractLast reviewed
[Provider][Service][Data][Yes / No][Date]

7. Incident response plan

Anyone who suspects an incident tells [Qualified Individual] at once, on [phone]. Then:

  • Contain it: disconnect affected devices, reset passwords, revoke access. Do not wipe anything that may be evidence.
  • Report data theft to your IRS Stakeholder Liaison, who alerts IRS Criminal Investigation and the right IRS teams. Find the liaison for your state on irs.gov.
  • If unencrypted information about 500 or more consumers is involved, notify the FTC as soon as possible and no later than 30 days after discovery, through the FTC’s online form.
  • Check your state’s breach notification law, and notify affected clients and the state attorney general where it requires.
  • Call your cyber insurer [policy and phone] and outside IT provider [phone].
  • Write down what happened, what was affected and what was done, and update this plan.

8. Training

Every team member reads this plan and completes security awareness training when they join and at least once a year: [course or provider]. Training records are kept by [name].

9. Action list, review and sign-off

Gap from section 3FixOwnerDue
BlankBlankBlankBlank

This plan is reviewed at least once a year and after any material change or incident. The Qualified Individual reports in writing to [the owners] at least once a year on the state of the program, the risk assessment, and any incidents.

Approved by [name, role] on [date]. Next review due [date].

Firms that hold information on fewer than 5,000 consumers are exempt from some Safeguards Rule requirements, including the written risk assessment, the written incident response plan and the annual written report. This template keeps them in, because the IRS recommends them and they cost little in a small firm.

This template is a starting point, not legal advice. Your obligations depend on where you practise, your professional body and your clients; take advice on anything you are unsure of.

Common questions

Frequently asked questions

Do tax preparers need a WISP?
Yes. The FTC treats professional tax preparers as financial institutions under the Gramm-Leach-Bliley Act, and its Safeguards Rule requires a written information security program. The IRS publishes Publication 5708 to help preparers write one, and has asked preparers to confirm they have a data security plan when they renew their PTIN. AI and the IRS rules for US accounting firms covers how the rules apply to AI tools.
What is IRS Publication 5708?
The IRS guide to creating a written information security plan for a tax and accounting practice, produced with the Security Summit. It explains what a WISP should cover and includes a sample. This template follows its structure.
Who should be the Qualified Individual?
One person who oversees the plan. In a small firm that is usually an owner. You can use an outside IT provider to do much of the work, but the firm stays responsible and must supervise them.
What happens if we have a data breach?
Contain it, then report data theft to your IRS Stakeholder Liaison. If unencrypted information about 500 or more consumers is involved, the FTC must be told within 30 days of discovery. State breach laws may also require notice to clients and the state attorney general.
Does the WISP cover AI tools?
It should. Customer information pasted into an AI tool is information shared with a service provider. Put AI tools on the inventory and vendor list, and only allow customer information into tools your firm has approved. The AI policy template sets the rules, and is AI safe for client data? covers how to check a tool.
More templates

More templates

The thinking behind these: AI for accountants and bookkeepers: what actually works.

Read the notes →

The AI in Practice Summit notes are up: a quick read, the full notes and a transcript for every session, plus the replays and Ask the Summit. Free.