Defend the Technology Number at Your Next Board Meeting

The board is voting on your technology number

You are a nonprofit Executive Director, finance director, or operations director. A board member says every technology dollar is a dollar unavailable to the mission. The meeting date is set, and you have to defend the number.

Do not bring one lump sum. Put a mission reason, funding reason, or control reason beside every line. Show the board what you will remove and reduce before asking it to approve an increase.

Work the workbook first. Build the eight-section board pack second. You can do both without hiring anyone.

---

Your defense is credible only if some lines can be cut

A technology budget defense is only credible if it also cuts.

If you present a board pack in which every existing line is necessary and the total goes up, the board learns that your analysis always produces the same answer. After that, the analysis carries no information and they will discount it. The next time you bring a genuinely urgent item, you will have spent the credit already.

So run the workbook honestly. Most organizations that do this find seats they stopped using, two products doing one job, a subscription attached to a staff member who left in 2024, and at least one renewal nobody remembered agreeing to. Take those to the board alongside the increases. A pack that says “we are removing four lines, reducing two, and asking for one increase, and here is why each” is believed. A pack that only asks is not.

That is the whole mechanism. The cutting is what makes the defending work.

---

Use the award terms and line evidence instead of a generic percentage

It will not tell you what percentage of your budget should go to technology.

You have probably been asked for that number. You may have been shown one. Be careful with it. There is no neutral, current, sourced benchmark for nonprofit technology spend as a share of budget that survives examination, and the broader “overhead ratio” framing it belongs to is contested in the sector for reasons worth knowing: it treats infrastructure as waste by definition, it varies enormously by program model, and it can be gamed by reclassifying costs rather than reducing them.

If your board wants a percentage, give them this instead: a line-level table where every line has a reason, an owner, an evidence state, and a decision. That answers the actual question underneath the percentage question, which is whether the money is doing anything.

If a funder requires a specific ratio or cost category treatment, that requirement comes from your award or your funder’s policy, and it governs. Read it. Do not substitute a sector rule of thumb for the terms you actually signed.

---

Part 1: Build the eight sections for the board vote

Eight sections, in this order. The order is doing work: the board sees the decision and the cuts before it sees any request.

Section 1: Put the amount and requested vote first

One sentence at the top of page one. What you are asking the board to approve, decline, or choose between. Not context. Not a summary of the year. The ask.

If there are multiple decisions, list them as a numbered set of no more than three, each in one sentence. A board pack requesting seven decisions gets none of them.

Section 2: Show every line and annual amount you will remove or reduce

Put this second, ahead of any request. List the lines you are cutting, the annual amount recovered, and when the recovery lands. This section establishes that the analysis is real.

Line	Function	Current annual cost	Decision	Recovery starts	Why
			Remove / Reduce		(unused seats, duplicate function, program ended, no owner)

Total recovered, annualized: $______

Section 3: Tie each remaining line to a program outcome

Every remaining technology line, grouped by the program or function it serves. Not by vendor. Not by category. By what it is for.

A board that sees “case management system, serves the housing program, 340 clients tracked, required by the county contract” understands the line. A board that sees “software subscriptions, $61,400” does not, and will treat the whole block as discretionary.

Section 4: Quote the funding source and restriction

Which lines are charged where, and what limits apply. Three columns matter here: the funding source, whether the funds are restricted, and whether the cost is currently charged as direct, charged as indirect, or paid from unrestricted funds.

State plainly which lines you are unsure about, because the unsure ones are the ones your auditor will find. See Part 3 on allowability before you fill this in.

Section 5: Cite the control requirement and current evidence

The lines that exist because a control requirement, a contract, an insurance condition, or a regulator requires them. This section is where technology spend stops being discretionary in the board’s mind, so be strict about what you put in it. A line belongs here when you can name the requirement, not when the vendor said it was a best practice.

For federal awards, 2 CFR 200.303 requires recipients and subrecipients to establish, document, and maintain effective internal control over the federal award, and to take reasonable cybersecurity and other measures to safeguard information.

That regulation states a duty. It does not name a product. Nothing in it tells you which tool to buy, and any vendor claiming that their product satisfies 200.303 is selling you a conclusion that only your own documentation and your auditor can reach.

Section 6: State what the program loses if the line is declined

Two or three sentences per item, stated as what would happen to the mission and the organization, in units the board already uses. Days of service interruption. Client records exposed. A grant report you could not produce. A contract obligation you would fail.

Do not lead with fear. You can frighten a board once, and after that everything you bring is discounted, including the item that genuinely warrants alarm.

Section 7: Give the board a smaller credible option

Two or three real options for each decision. Real means each could actually be chosen. Include the smaller option whenever a smaller option is credible, and include a defer option with a written trigger attached: what would have to happen, by when, and who watches for it.

	Option	Year-one cost	What it addresses	What it leaves open
A
B
C	Defer	$0 now		Trigger:

Section 8: Record the vote, owner, due date, and completion evidence

Field	Entry
Decision owner
Approval date
Implementation owner
Due date
Evidence of completion	(the specific artifact that will prove it happened)
Reported back to board on

The evidence-of-completion field is the one people skip. It is also the reason the same item reappears three board meetings running with a larger number attached.

---

Part 2: Put every technology line in the budget workbook

Two sheets. Sheet one is the line inventory. Sheet two is the exposure sheet, and it is the one that finds money.

Sheet 1: Record the amount, funding source, owner, and renewal date

One row per technology line. Not one row per vendor. If a vendor sells you three separate things that serve three separate programs, that is three rows.

#	Line	Program served	Grant or contract	Restriction	Control requirement	Current annual cost	Renewal date	Evidence	Owner	Decision
1
2

Column definitions, because the definitions are where the value is:

• Program served. The program, department, or organization-wide function this line supports. If you cannot name one, write “none identified” and stop being polite about it. That is a finding.
• Grant or contract. The specific award, contract, or funding source the cost is charged to. Write the award identifier, not the funder’s name alone.
• Restriction. Restricted, unrestricted, or mixed, plus a note on what the restriction says. If a cost is split across sources, record the split and the basis for it.
• Control requirement. The named requirement this line satisfies, if any. Cite the source: the award term, the contract clause, the insurance condition, the regulation. “Security” is not a control requirement. “2 CFR 200.303 internal control documentation for Award #_____” is.
• Current annual cost. Total annual cost including per-seat charges, support fees, implementation amortization, and any charge that arrives on a different invoice from the main one.
• Renewal date. The date, plus the notice period required to cancel. The notice period is the field that matters and the field most often unknown. Find it now, before it costs you a year.
• Evidence. What proves this line is doing its job: a usage report, a seat count against staff count, a test result, a report produced from the system, a control artifact. See the evidence states below.
• Owner. A named person. Not a department, not “IT”, not the vendor. If no name fits, that is a finding too.
• Decision. One of the six states below.

Give every line one of six board decisions

State	Use it when
keep	The line has a named mission, funding, control, or operating reason, an owner, and evidence that it is used
reduce	The function is needed at a smaller size: fewer seats, a lower tier, a shorter retention, a narrower scope
remove	No current reason, no owner, no use, or a second product already does the job
defer	A decision is genuinely better made later, and a written trigger says when it returns and who watches for it
fund through an eligible source	The cost is justified and is currently charged to the wrong place, subject to your cost policy and award terms
needs evidence	You cannot yet defend it either way, and you have named who will produce what, by when

needs evidence is a legitimate state and you should expect several. What is not legitimate is carrying it for two budget cycles. Put a date on every one.

defer without a trigger is not a decision. It is a way of avoiding one, and it is how a line survives four years unexamined.

Mark the dated artifact confirmed, stale, missing, or pending

State	Meaning
used and verified	A usage or activity report from the system itself, dated within the last 90 days
assumed used	Somebody believes it is used and no report has been pulled
unused	The report shows no meaningful use, or seats materially exceed the people who need them
no evidence available	The system cannot produce a usage report, which is itself worth recording

Move assumed used to a real state before the board pack goes out. Most of your recoverable money is sitting in that row.

Sheet 2: State what the program loses under each cut

This is the sheet that pays for the exercise. Five tests, run against sheet one.

Test 1: Seats against people. For every per-seat line, put licensed seats next to the number of staff and volunteers who actually need it, then next to the number who logged in during the last 90 days.

Line	Seats licensed	Staff who need it	Active in last 90 days	Seats recoverable	Annual value

Departed staff are the usual finding. So are seats bought for a grant-funded position that ended, seats bought in a bundle nobody unbundled, and seats for a program that moved to a different tool two years ago.

Test 2: Duplicate function. Group every line by the job it does. File storage. Video meetings. Email. Donor records. Case notes. Scheduling. E-signature. Forms. Backup. Password storage. Any job with two or more products under it is a candidate.

Function	Products doing it	Combined annual cost	Why both exist	Decision

Duplicates usually arrive one of three ways. A department bought its own thing. A grant paid for a tool that stayed after the grant ended. Or a suite you already pay for includes the function and nobody turned it on. That third one is common and it is free money.

Test 3: Owner gaps. Every line where the owner column is blank, or where the named owner has left, or where the only person who understands it is a contractor.

Test 4: Renewal exposure. Every line whose renewal date falls in the next twelve months, sorted by date, with the cancellation notice deadline computed backward from it. This column is the one that turns an intention into a decision, because a notice period that passed last month means the decision is already made for another year.

Line	Renewal date	Notice required	Cancel-by date	Auto-renew	Decision due

Test 5: Exit cost. For every remove and reduce candidate: what does it cost to leave. Data export, format, staff hours, a migration, a period of running both, retraining. A line that costs $9,000 a year and $14,000 to leave is a different decision from one that costs $9,000 and exports cleanly to a spreadsheet.

Run the five tests before you write a single word of the board pack. The order matters, because Section 2 of the pack is built from these results.

---

Part 3: Check each award before charging the cost

This is the highest-risk section in this document, so it is written carefully.

Which of your technology costs may be charged to a federal award, and whether they are treated as direct or indirect, is determined by your award terms, the notice of funding opportunity, the federal cost principles applicable to your award, and your organization’s own written cost policy. It is not determined by this document, by a consultant, or by a vendor.

Anyone who tells you a specific technology cost is allowable without having read your award is guessing, and the guess is being made with your money and your audit exposure.

What this pack does is make the question askable. Fill in these fields for each line you charge or intend to charge to an award, then take the completed rows to your finance staff, your auditor, and where necessary your counsel.

Field	What to record
Award identifier	The specific award, not the funder name
Award terms reviewed	Yes or no, with the date and who read them
Cost treatment	Currently direct, currently indirect, or unrestricted funds
Basis for the treatment	The written policy or award provision that supports it
Allocation method	If shared across programs or awards, how the split is computed
Documentation held	Where the support for this allocation lives
Open question	The specific thing you need your auditor to confirm
Confirmed by	Name and date, once answered

Two facts you can rely on, both from named federal sources:

Internal control. 2 CFR 200.303 requires federal award recipients and subrecipients to establish, document, and maintain effective internal control over the federal award, and to take reasonable cybersecurity and other measures to safeguard information.

Single audit. Under 2 CFR 200.501, the general single-audit threshold is $1 million in annual federal award expenditures.

Whether your organization crosses that threshold in a given year, and how expenditures are counted for that purpose, is a determination for your auditor. Do not decide it from a summary. Both provisions are stated here because they come up constantly in technology conversations and are constantly misquoted by people selling something.

If you are also subject to HIPAA as a covered entity or business associate, separate obligations apply, including individual breach notice without unreasonable delay and no later than 60 calendar days after discovery under 45 CFR 164.404, with notification timing to HHS differing by breach size under 45 CFR 164.408. Whether HIPAA applies to your organization is a legal determination.

---

Part 4: Put operating and exit cost beside the $0 license

Nonprofit pricing is real and worth using. It also produces a specific failure that shows up in almost every workbook we have seen filled in.

A free or discounted tool is not a free tool. The license is one cost among several, and it is frequently the smallest one.

Cost that survives the discount	What it looks like
Administration	Somebody has to configure it, manage accounts, remove departed users, and answer questions about it
Integration	Getting data in and out of your other systems, and keeping that working when either end changes
Training	Every new staff member and volunteer, forever
Support	Donated tiers often carry reduced or community-only support, which converts vendor time into your staff’s time
Data and exit	What happens to your records if the donation program changes, the eligibility rules change, or you outgrow the tier
Control burden	A tool holding client data carries the same safeguarding expectations whether you paid for it or not

Three specific traps, in the order they occur.

The unadministered tool. A donated platform arrives, gets set up by a volunteer or a departing staff member, and then nobody owns it. Accounts accumulate. Departed staff keep access. Nobody knows what data is in it. This tool now costs you nothing in cash and quite a lot in exposure, and it will not appear in any budget review because its line is $0. Put every donated tool in sheet one with a cost of zero and an owner field that must be filled.

The tier that becomes a purchase. The donated tier covers ten users and you now have twenty-six. The donated tier excludes the module your program actually needs. The eligibility rules change. Record the tier limits and the point at which you would cross them, in the renewal exposure test.

The migration you cannot afford. You built three years of program records inside a donated system. Check the export path now, while you have no urgency, and record what you find in the exit cost column. Ask two questions of the vendor in writing: what format does a full export produce, and how long does the data remain available after an account closes.

None of this argues against donated licenses. Use them. Record them properly, give each one an owner, and count the administration in your real cost of the line.

---

Part 5: Check seats, overlap, owner gaps, renewals, and exit cost

Not a benchmark. A list of the recurring findings, in rough order of frequency, so you know where to look first.

1. Seats for people who left. Almost universal. Check every per-seat line against your current roster, then against actual logins.
2. Two products doing one job. Usually file storage, video meetings, or e-signature. Frequently the suite you already pay for includes one of them.
3. A tool from a grant that ended. The program closed. The subscription did not.
4. A tier bought for a peak that passed. Storage, sending volume, or user count sized for a campaign three years ago.
5. Support or maintenance on hardware you replaced. It keeps billing.
6. A renewal nobody agreed to. Auto-renewal with a notice period that quietly passed.
7. Paid features already included elsewhere. Backup, password storage, and forms are the common three.
8. A device fleet decision hiding in a subscription. Windows 10 standard support ended October 14, 2025, and commercial Extended Security Updates start at US$61 per device for year one and double in each consecutive year. If you have Windows 10 devices, that is a growing line with a known escalation, and it belongs on the board pack with a device count and a replacement date rather than arriving as a surprise in year three.

---

Part 6: Prepare the figures and documents the board will request

“Why is this more than last year?” Answer with the line-level table, and lead with what you removed. If the increase is a price change rather than a scope change, say which vendor and by how much.

“Can we cut it in half?” Show them the exposure sheet. Some of it can be cut and you have already cut it. For the rest, name what each cut would stop the organization from doing, in program terms. A board that sees which program loses what will make a real choice.

“What do similar organizations spend?” Be careful here. If you use a figure, give the publisher, the date, the peer set, and the denominator. If you do not have one that meets that bar, say the comparison is not available at a quality you would defend and answer on your own facts.

“Didn’t we already buy something for this?” Frequently yes, and the honest answer helps you. A capability that was licensed and never deployed reframes the request from new money to finishing something.

“Can a volunteer do this?” Sometimes, and a real answer includes the continuity question. A volunteer-administered system with client data in it needs a named backup person and a documented handoff, or you have created a single point of failure with a mission attached to it.

“Does this come out of program or admin?” That is the allowability and cost policy question in Part 3. Give them the recorded treatment and the basis, and flag the lines your auditor has not yet confirmed.

---

Part 7: Four mistakes that weaken your board number

Nothing gets cut. Covered at the top, and it is the failure that matters most. If the workbook produced no removals, either the exercise was not run honestly or you are the rare organization with a perfectly sized stack. Assume the first.

The vendor fills in the workbook. Your IT provider is answering questions about the necessity of services they sell you. They may answer honestly. They are also the wrong party to decide which of their lines get removed. Ask them for usage reports, seat counts, and renewal terms, and make the decisions yourself.

A control requirement gets asserted without a source. Someone writes “required for compliance” in the control column with nothing behind it. That line is now protected forever and nobody will ever question it again. Require a citation in that column: the award term, the contract clause, the policy, the regulation.

The pack becomes a defense of everything. The moment a board recognizes the format as an annual argument for the status quo, the format stops working. Its power comes from the fact that it produces different answers in different years.

---

Keep the approved pack with the vote and completion record

This is general guidance for budget preparation and board reporting. It is not legal advice, accounting advice, or grant compliance advice. It does not determine what is allowable under any award, what your cost policy should say, or what your funders require. Allowability, cost treatment, indirect cost rates, single audit applicability, and reporting obligations depend on your specific awards, your written policies, and your facts. Have your finance staff, your auditor, and where the question is legal your counsel review anything in this workbook before it reaches a funder.

Every regulatory item here is sourced to a named authority through SBK’s source register. Where a rule depends on your award or entity type, this document says so rather than giving you a single number that would be wrong for most readers.

Once the budget is decided, the reporting problem starts, and it is a different problem with a different audience. The companion document, The Nonprofit Grant and Board Technology Report, covers the reporting side: connecting a technology line to a program, a funding source, a control requirement, current evidence, and a named decision, for a board or for a funder.

SBK Consulting is a family-run, vendor-neutral IT advisory firm serving the New York, Connecticut, and New Jersey metro area since 2010. Zero vendor partnerships, zero reselling, zero commissions or referral fees, which means we have no financial interest in which lines you keep and none in the ones you cut. 125+ years of combined experience, 100% US-based. We will sit with one budget cycle or one grant report if that is useful. If you run the workbook, cut four lines, and never call us, that is the outcome this was built for.

(718) 407-4169