The technology spend assessment checklist
This checklist is a self-serve version of a technology spend assessment: gather the documents below, work through the checks category by category, and score what you find by severity and effort. Most businesses can finish a first pass in a few focused hours and leave with a prioritized fix list.
What documents should you gather first?
The audit is only as good as its inputs, so start with collection. You don't need perfect records. Gaps are themselves a finding. Still, aim for all five categories:
- Telecom and connectivity invoices: the last 1–3 bills for every location: internet, phone, mobile, and any circuits. Invoices, not statements; the line-item detail is where errors hide.
- SaaS admin exports: a user or license report from each major application's admin console, ideally including last-login dates, plus a seat report from your identity provider if you have one.
- Cloud bills: the detailed billing or cost-management report from each cloud account, not just the monthly total.
- Contracts, MSAs, and order forms: for your ten largest vendors at minimum. Order forms usually carry the term and renewal dates; the master agreement carries the notice and escalation language.
- Org and site list: current headcount by department and a list of active locations. You can't spot licenses for departed employees or circuits at closed sites without knowing what “current” looks like.
Add one more source that most self-audits skip: an export of technology-related payments from your accounting system and corporate cards. It catches the subscriptions no inventory captures, tools expensed by one department that duplicate what another already pays for.
What should you check in telecom and connectivity?
- Billing errors: reconcile each invoice line against the contracted rate. Look for rates that don't match the agreement, surcharges that were never negotiated, and charges that jumped without a change order.
- Zombie circuits: services still billing for closed offices, disconnected lines, or projects that ended. Match every billed circuit and phone number to a live location and a person who can say what it's for; anything nobody claims is a candidate.
- POTS lines: legacy copper phone lines, often serving old fax machines, alarms, or elevators, at per-line rates that have climbed steeply as carriers retire the technology. Count them, confirm which are still required, and price the modern replacements for the rest.
- Out-of-term services: anything running month-to-month past its original term is usually billing at rack rates. These are the easiest renegotiations on the list because you can act immediately.
What should you check in SaaS and software?
- Last-login utilization: compare paid seats to users active in the last 60–90 days. Departed employees, contractors from finished projects, and never-activated seats all keep billing until someone reclaims them.
- Duplicate and overlapping tools: two project trackers, three e-signature tools, several file-sharing apps. Map each application to the job it does and flag every job with more than one tool attached; this is where the accounting export pays off.
- Tier fit: check which plan features you actually use against the tier you pay for. Enterprise tiers bought for one feature, or for a compliance need that has since been solved elsewhere, are common and rarely revisited.
- Approaching renewals: note every subscription renewing in the next 120 days. Cuts and downgrades usually take effect at renewal, so the calendar determines which findings you can act on this quarter.
What should you check in cloud and infrastructure?
- Unused resources: idle instances, unattached storage volumes, aging snapshots, and dev or test environments that outlived their projects. The detailed bill lists everything you pay for; the question for each item is whether anyone still needs it, and the answer is often no.
- Right-sizing: instances and databases provisioned far above their observed utilization. Your cloud provider's own recommendations console is a reasonable first pass.
- Commitment coverage: steady, predictable workloads running at on-demand rates are the cloud equivalent of month-to-month telecom. Check what share of your stable usage is covered by reserved instances, savings plans, or committed-use discounts.
What should you check across vendor contracts?
- Renewal dates and notice deadlines: for every contract, record the term end, whether it auto-renews, and the deadline for written notice. Log them in a contract renewal calendar so the review you're doing now doesn't have to be reconstructed from scratch next year.
- Pricing versus market: compare your rates to current quotes for equivalent service. This is the hardest check to do alone, because market pricing isn't published; even one competing quote per major contract tells you a lot.
- Escalators and renewal language: flag any contract with an uncapped annual increase or “renewal at then-current list price.” Those clauses, and the notice-window traps that accompany them, are covered in our guide to when to review your technology contracts.
How do you score what you find?
A first pass usually surfaces more findings than anyone can chase at once. Score each one on two axes, severity (annual dollars at stake) and effort (what it takes to act, including contract constraints), and let the grid set the order:
| Severity / Effort | Typical findings | When to act |
|---|---|---|
| High severity, low effort | Billing errors, zombie circuits, unused licenses on monthly plans | Immediately: these need a dispute ticket or an admin console, not a negotiation |
| High severity, high effort | Above-market contracts, tier downgrades, tool consolidation | Schedule around renewal windows; these are negotiations and migrations |
| Low severity, low effort | Small orphaned subscriptions, aging snapshots, single stray seats | Batch into a monthly cleanup pass |
| Low severity, high effort | Marginal replatforming, small vendor switches with migration cost | Usually skip: the disruption outweighs the dollars |
Write each finding as one row in a spreadsheet: finding, category, annual dollars, effort, owner, act-by date, and you have a savings register you can actually work through. The follow-through framework, category by category, is in our guide to reducing technology spend, and if you want the same line items organized into a working budget, our IT budget template uses the same structure.
When does it make sense to bring in an advisor instead?
A self-audit with this checklist reliably finds internal waste: the errors, the unused seats, the forgotten services. Where it hits a wall is the market-facing questions: whether your rates are competitive, what leverage a renewal really carries, and what alternatives would cost. That is because market pricing isn't published anywhere you can look it up. Industry benchmark ranges for professionally-run reviews are typically 20–30% on telecom and 15–25% on software. Ranges reflect industry benchmarks; actual results vary and savings are not guaranteed.
Bring in an advisor when the vendor count outruns the time you have, when a major renewal is inside its 120-day window and you want negotiation support, or when your self-audit surfaced big contracts you can't benchmark. A professional technology spend assessment covers the same ground as this checklist with current market data behind it, and it's free: we're independent. We work across the provider market, not for any single vendor, and typically compensated through standard supplier commissions on the contracts we help you source and manage, usually at no direct cost to you; disclosed per engagement.
By Shane Stewart, Founder · Last updated: July 2026.
Common questions
What is a technology spend assessment checklist?
It is a self-serve version of a professional spend assessment: a document list to gather, category-by-category checks for telecom, SaaS, cloud, and vendor contracts, and a simple severity-and-effort score for prioritizing what you find. It requires no special tools beyond your own invoices, admin consoles, and a spreadsheet.
What documents do I need for an IT cost audit?
The last one to three invoices for every telecom, internet, software, and cloud service; user and license exports from your SaaS admin consoles; detailed cloud billing reports; the contracts and order forms behind your largest vendors; a list of locations and headcount; and an export of technology payments from your accounting system and corporate cards.
How do I prioritize what an IT cost audit finds?
Score each finding on two axes: severity, the annual dollars at stake, and effort, what it takes to act, including any contract constraints. Fix high-severity, low-effort items like billing errors and unused licenses immediately; schedule high-effort items like renegotiations around their renewal windows; batch the small stuff.
When should I bring in an advisor instead of auditing myself?
When you cannot benchmark your rates against current market pricing, when the vendor count is too high for the time you have, or when major renewals are close and you want negotiation support. A self-audit reliably finds internal waste; market-facing questions are where independent benchmark data earns its keep.
See whether you may be overpaying, for free.
A 20-minute call and a free assessment show you the savings in dollars, at no upfront cost.