Golden retriever dog in gloves and apron cleaning old electronics near recycling bin indoors

Spring Cleaning Your Technology Without Creating New Risk

May 26, 2026

Spring‑Cleaning Your Technology Without Creating New Risk

Spring cleaning usually starts with closets and storage rooms.

For CPA firms, the real clutter is quieter—and far more consequential.

It's the retired laptops stacked in an office.
The old printer sitting in a back hallway.
The external drive from two upgrades ago that nobody quite remembers.

None of this feels urgent. That's exactly why it becomes risky.

Every piece of retired technology represents a decision your firm already made once—and may be judged on later.

Technology Has a Lifecycle, Not Just a Purchase Date

Most firms plan carefully when they buy technology.
They compare options. Evaluate risk. Approve budgets.

Very few plan with the same care when that technology is retired.

When equipment is replaced, it tends to drift.
Set aside. Forgotten. Dealt with "later."

The problem is that old technology doesn't stop mattering just because it's no longer in use.

Retired devices can still hold client data, credentials, cached email, authentication tokens, or system access paths long after they leave daily operations.

From a compliance standpoint, that matters.

Both the IRS Safeguards Rule, the FTC Safeguards Rule, and widely accepted frameworks like NIST all expect firms to control data through its entire lifecycle—including secure disposal. A missing retirement process is not a gray area. It's a documented control gap.

The External Lens That Actually Matters

If a regulator, insurer, or client ever asks how your firm handles retired devices, they are not asking out of curiosity.

They are asking because retired equipment is a known failure point.

Firms rarely get in trouble because they lacked security tools.
They get in trouble because they lacked a repeatable, documented process with clear accountability.

"We thought it was wiped" is not a defensible answer during an audit, a cyber‑insurance review, or a post‑incident investigation.

Who Owns This Inside the Firm

Every control needs an owner. Technology retirement is no exception.

At a minimum, your firm should be able to state—clearly and consistently—that:

  • One role owns the process (typically the Managing Partner, Operations Lead, or IT owner)
  • IT executes the steps
  • Leadership reviews completion

When no one is explicitly accountable, devices linger.
When devices linger, risk accumulates quietly.

Ownership doesn't require bureaucracy. It requires naming responsibility.

How Often This Should Happen

Technology retirement is not a once‑a‑year cleanup.

At a minimum:

  • Every device refresh or replacement triggers the retirement process immediately
  • Quarterly reviews confirm nothing has been missed
  • Annual documentation review ensures records are complete and defensible

If technology is leaving your control, the process happens then—not at the next spring cleaning.

A Minimum Acceptable Technology Retirement Framework

This is the baseline every CPA firm should be able to explain calmly and confidently.

Step 1: Inventory What's Being Retired

Be explicit.

Laptops, desktops, phones, tablets, printers, copiers, servers, external drives, network equipment, and backup media.

A short walkthrough almost always reveals more than expected.

You cannot secure what you haven't identified.

Step 2: Decide the Destination Intentionally

Every device must be assigned to one of three outcomes:

  • Reuse (internal redeployment or approved donation)
  • Recycle (through a certified business e‑waste provider)
  • Destroy (when data sensitivity requires it)

The mistake isn't choosing the wrong option.
The mistake is letting hardware sit in limbo with no decision at all.

Step 3: Prepare the Device Properly

This is where most firms unknowingly cut corners.

Deleting files or performing a factory reset does not remove data in a defensible way. It simply removes the directory that points to where the data lives.

A common failure example: modern printers and copiers often contain internal hard drives that store images of everything ever scanned or printed. Returning a leased copier without verified drive wiping or removal is a frequent—and costly—oversight.

For any device leaving your control:

  • Remove it from device management systems
  • Revoke associated user access
  • Perform certified data erasure or physical drive destruction
  • Obtain a verification record

Step 4: Document and Close the Loop

For each retired device, you should be able to answer:

  • What it was
  • How data was handled
  • Where it went
  • When it was processed
  • Who handled it

Documentation isn't bureaucracy.
It's what keeps routine questions from becoming formal findings.

The Devices Firms Most Often Overlook

Some equipment almost always gets missed:

  • Phones and tablets with email access or authentication apps
  • Printers and copiers with internal storage
  • External drives and retired servers sitting in closets
  • Rechargeable batteries, which are regulated business waste in many states

None of these are automatically dangerous.
They become dangerous when they're ignored.

The One‑Page Technology Retirement Checklist

This is the artifact your firm should keep on hand.

Technology Retirement Checklist

  • Inventory completed
  • Destination assigned (reuse, recycle, destroy)
  • Device removed from management systems
  • User access revoked
  • Certified data wipe or destruction completed
  • Verification record obtained
  • Disposal partner verified
  • Documentation stored centrally

If you can't check every box, the process isn't finished.

Your Next‑Week Action

Within the next seven days, assign one accountable owner and inventory every retired or idle device in your firm—including storage rooms and closets—using the checklist above.

That single step closes more gaps than most firms realize.

What To Do Next

Reach out to 911 IT right now to have your technology retirement process reviewed against IRS, FTC Safeguards Rule, and NIST expectations and get clear, documented next steps before this turns into a compliance issue.