Often, yes. IT support is grant-eligible for a nonprofit when the cost is necessary to the funded work, reasonably priced, tied to that work in a way you can show, and documented. The grant’s own budget terms make the final call, so the agreement in your file outranks anything we say here, including this article.
We’ve spent thirty years keeping Metro Atlanta nonprofits, churches, law firms and clinics online, and the same pattern repeats. Nobody forbids the IT spend. The money gets stuck because nobody wrote down how the IT bill relates to the program. This piece walks through which grants tend to cover IT support, what survives review, what paperwork to keep, and how to build IT into a proposal before you submit it. It isn’t legal or accounting advice, so run the final numbers past your auditor.
Which grant categories cover IT support for nonprofits
Think of grants on a sliding scale. General operating support sits at the flexible end, restricted and technology grants sit in the middle, and government pass-through money sits at the strict end.
General operating support is the easy case. The funder trusts you to run the place, so a managed IT contract, a help desk, backup and security tooling all fit as ordinary overhead. You still keep invoices, but you rarely need to prove which program benefited.
Nonprofit technology grants and restricted project money
Nonprofit technology grants and restricted project money pay most easily for things you can point at: program software, hosting, new equipment, one-time setup and migration work. A grant that funds a client case-management system, for example, will usually accept the licenses, the hosting and the technician time to get it running.
Ongoing support is where it gets narrower. A restricted grant will often accept support for the systems it paid for, but not the whole office’s help desk. Read the budget template. If it has lines for “contracted services” or “technology,” those are your homes. If it caps indirect costs at a low percentage, assume anything shared will have to fit under that cap.
The most dependable way to see how a given funder will react is to check the budget narrative guidance before you write a word of the proposal.
Government pass-through money and the federal cost rules
Federal money that reaches you through a state or county agency follows the federal cost rules in 2 CFR Part 200, usually called the Uniform Guidance. Those rules are the strictest you will meet, and they are also the best yardstick for any restricted grant, federal or not.
The core tests in 2 CFR 200.403 are simple to say and tedious to prove. A cost must be necessary and reasonable, allocable to the award, treated consistently with how you treat other costs, and adequately documented. Pass the four and IT support is allowable. Miss one and you will be repaying money after an audit finding.
Your agency may add its own limits on top, so read the subaward terms, not just the federal rules.
IT support costs that count as grant-eligible spending
Grant funding for IT services usually stalls on allocation. A managed IT contract covers the whole office, but a grant can pay only the share that serves the funded work, and under 2 CFR 200.405 allocability follows the benefit actually received. If you remember one sentence from this article, make it that one.
Direct costs tied to the funded program
Some costs are easy. Software used only by program staff, hosting for the program’s database, backup of the program’s data, security tooling on the program’s devices, and one-time setup all tend to survive review, because the benefit is obvious and the invoice can say so.
These costs are easy to defend because you can draw a straight line from the invoice to the program. If the grant bought a tablet fleet for field workers, the mobile device management and the setup labor go with it.
Shared managed-service fees and the allocation problem
Here is the part that gets disputed. A shared managed IT contract usually counts toward a grant only when you can show, through a written allocation method, the share that serves the funded program, and that method has to be applied the same way every month, not reinvented whenever somebody asks.
You have two honest routes. The first is a direct charge using a reasonable basis, such as the program’s share of users, devices or supported systems. The second is recovering the cost through an indirect rate. On federal awards, a nonprofit that has never negotiated an indirect rate can elect a de minimis rate of up to 15 percent of modified total direct costs, which recovers shared overhead like help desk coverage without preparing an indirect cost proposal. Confirm the current rate in 2 CFR 200.414 before you budget around it.
Pick one route per cost. Charging the help desk directly to a grant and also counting it in an indirect pool is double dipping, and auditors look for it.
Three other things get challenged again and again:
- A general office help desk charged straight to one grant, with no allocation.
- Subscriptions that run past the end of the award period.
- Costs incurred before the award starts, unless the funder approved them in writing.
None of this means shared IT can’t be funded. It means the paperwork has to exist before somebody asks.
Compliance documentation funders expect for IT spending
Funders don’t reject IT costs because they dislike technology. They reject them because the file can’t answer a basic question. You can head that off by building the file as you go, not in a panic during a site visit.
The invoice and allocation file auditors read first
Auditors start with paper, and the paper is boring on purpose. Your file should hold a signed contract, itemized invoices that name the systems and services, the allocation worksheet, quotes or a short reasonableness note showing you compared prices, and time records if any staff hours are charged to the grant.
The invoice itself does more work than most people expect. A line that says only “monthly IT support” invites questions. One that names the systems, the users and the program’s share of them, with the allocation worksheet attached, is far easier to defend.
That’s why we itemize. When a funder asks why a line item exists, the technician who set it up is usually still on your account and can explain it in plain English. It’s one of the few real advantages of a provider that doesn’t rotate its people every year.
Security evidence: MFA, backups, and staff training
Many funders, insurers and agencies now ask whether you run basic controls. Expect questions about multi-factor authentication, backups that have actually been restore-tested, who has admin access, and whether staff get security awareness training.
The division of labor matters here. We supply the technical proof: MFA enrollment reports, backup and restore logs, patch status, and a record of the training your staff completed. You own the grant narrative, meaning the explanation of why those controls protect the funded program and its participants’ data.
If your program touches health information, the compliance file gets heavier, and what HIPAA-compliant IT support really involves is worth reading before you promise anything in a proposal. Backup is also a common grant line, and what a disaster recovery plan actually costs will help you price it honestly.
We can hand you evidence. We can’t write your narrative, and a funder will notice if nobody on your side understands it.
Case study: documenting a shared IT contract before the funder asks
This is a typical case, not a testimonial. The point is the question and the paper that answered it.
The setup, the audit question, and the fix
A mid-sized nonprofit holds a multi-year program grant passed through a state agency. Its managed IT contract covers every desk in the office, but only the program team and the program’s case-management database serve the grant. In year one, the bookkeeper charged the full monthly IT invoice to the grant because the invoice said “IT support” and the grant had a technology line.
Then the program officer asked a plain question: why does a whole-office bill appear in a single program’s budget?
The nonprofit had no answer ready, and that is the part that hurts. The costs were legitimate, but nothing in the file said so, and the officer was entitled to doubt them.
The fix took an afternoon. The provider reissued itemized invoices naming each system and user group. The nonprofit wrote a short allocation worksheet based on the program’s share of supported users and systems, signed it, and applied it to every month going forward, including the months already billed. The charge dropped to the program’s share, the remainder moved to general funds, and the officer closed the question in one email.
The lesson isn’t that the nonprofit did something wrong. It’s that a written method, applied consistently, is what separates an allocated cost from a guess.
Nonprofit tech budget planning before you apply for a grant
Put IT in the proposal before you submit it. Asking for permission after the award is slower, and some funders won’t allow it at all. Good nonprofit tech budget planning is mostly a spreadsheet exercise, and you can finish it in an evening.
Build IT line items from a full year of invoices
Pull twelve months of IT invoices, not a few recent ones. A full year catches the annual renewals, the surprise hardware failure and the seasonal projects that a quick estimate misses.
Then sort every line into the categories the funder’s budget template uses. Most templates have the same buckets: equipment, software, contracted services and indirect. A laptop goes in equipment, a database license in software, the managed support contract in contracted services, and anything you can’t tie to a program goes into the indirect pool.
Next, decide which lines belong to the funded program and write down why. Use the same logic you would use in the allocation worksheet, because the proposal and the later documentation should match.
Finally, carry recurring costs forward only as far as the award period allows. A twelve-month grant gets twelve months of support fees, not the three-year contract you happen to have signed. For a recurring fee you need to spread across programs, 2026 managed IT pricing in Atlanta gives you a baseline to sanity-check against.
If you are also weighing plans for a tight budget, IT support built for churches and nonprofits goes deeper on what fits.
TechSoup alternatives for discounted software and hardware
Discount marketplaces such as TechSoup cut software and some hardware prices for verified nonprofits, and for plenty of organizations that’s real money. We have no quarrel with them.
But a discount is not a grant. A discounted license is a lower price on a product and nothing more; it does not come with a person who answers when the server goes down. A marketplace is a price list, not a “trusted digital transformation partner,” whatever the brochure language says.
If you want TechSoup alternatives, there are two. Several major software vendors run their own nonprofit programs directly, and local providers can often source equipment and licensing as part of a support relationship. Vendor terms change often, including who qualifies and what’s discounted, so check the current terms the week you buy, not the week you budget.
Discounts also shrink the line item you put in a grant budget, which helps. They don’t tell you who configures the software, secures it or fixes it. For that, how a local provider differs from a national MSP is a fair way to judge your options.
What to do before the next grant deadline
With the 2027 budget coming together, a few moves will save you grief later.
Confirm the award period and the cost rules first, because everything else depends on them. Find the dates the funder will pay for, whether pre-award costs need written approval, and whether the budget allows direct charges, an indirect rate or both.
Ask your IT provider for an allocation note, along with itemized invoices that name systems and users. If your provider can’t produce those, that’s worth knowing before an auditor finds out for you.
Then get a quote that matches your budget lines, so the numbers in the proposal come from a document and not from memory.
If you’d like to check which of your current IT invoices fit the grant you’re pursuing, request a quote and we’ll go through them with you. A real technician will pick up the phone.
Frequently asked questions
Can a grant pay for a monthly managed IT contract?
Sometimes. It works when the grant’s budget allows contracted services and you can show the share of the contract that serves the funded program. A signed contract, itemized invoices and a written allocation method make that case. Check the grant’s budget terms first, since they decide.
What is the de minimis indirect rate, and does it cover IT?
On federal awards, a nonprofit that has never negotiated an indirect cost rate can elect a de minimis rate of up to 15 percent of modified total direct costs. It can recover shared overhead such as help desk coverage. Confirm the current rate in 2 CFR 200.414, and don’t charge the same cost both directly and through the indirect pool.
Can we charge IT costs we incurred before the grant started?
Usually not, unless the funder approved them in writing. Costs before the award start date are one of the most common disputes. Ask your program officer before you spend, and keep the approval in your file.
Does a TechSoup discount replace paying for IT support?
No. A discount lowers what you pay for licenses and some hardware. It doesn’t install, secure or fix anything, and it doesn’t give you someone to call when something breaks.
Will our IT provider write the grant application?
No. Your IT provider supplies technical proof such as MFA reports, backup logs, itemized invoices and an allocation note. Your organization writes the narrative and owns the budget decisions, and the funder makes the final call.
