The Nonprofit Grant and Board Technology Report
Make the Technology Number Match in Your Grant Report and Board Packet
Use one three-sheet record to produce the six-section report each audience needs.
Unlock the full document
This document is free. Leave a work email so we can send corrections and updated versions, and the full sheet unlocks below.
Your board and funder are reading the same cost differently
The board asks what the technology money does and who watches it. The funder asks whether the cost was allowable under the award, allocated correctly, and supported by records.
If you write two reports from two spreadsheets, the numbers can disagree. The error may surface during a board meeting, grant review, or audit.
Keep one 10-field record beneath both reports. Use the same cost, award term, program, evidence, owner, and date. Change only the emphasis for the reader.
You can build it without hiring anyone.
Put the dated artifact in the evidence column, never the invoice
A purchase does not satisfy a requirement. Evidence does.
This deserves stating plainly because the opposite claim is a standard nonprofit sales technique. A vendor tells an executive director that their platform “meets 2 CFR 200 requirements” or “makes you grant compliant” or “satisfies your funder’s security requirement.” Sometimes the words are softer than that. The implication is the same, and it is wrong in a way that costs money twice: once at purchase, and again when a monitor or auditor asks for documentation the purchase never produced.
The federal requirement is on you. 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.
Read what that asks for: establish, document, and maintain. Those are activities performed by your organization. A tool can support them. A tool cannot perform them, and no invoice is evidence that they happened.
So this report never records a purchase in the evidence column. It records an artifact: an access review with a date and a reviewer, a restore test result, a policy with a version date and an approval, a training completion record with a denominator, a configuration export. If the only thing you can put in the evidence column is a receipt, the honest entry is no evidence.
Use one record for two reporting decisions
Same underlying facts. Different question, different tolerance, different failure mode.
| Reporting to your board | Reporting to a funder | |
|---|---|---|
| The question underneath | Is this money doing something, and does someone own it | Was this cost allowable, allocable, properly documented, and consistent with what we approved |
| What they want first | The decision and the consequence | The award, the period, the amount, and the basis |
| Tolerance for an open item | High, if it has an owner and a date | Low, and it should be raised before they find it |
| Level of detail | Summary with the ability to go deeper on request | Line level, with documentation available |
| Worst failure | A pattern of items that never resolve | A number in a report that your general ledger does not support |
| Language | Program consequence in plain terms | The award’s own terms and defined categories |
| What “unknown” costs you | Credibility, slowly | A finding, quickly |
Two practical rules follow.
For the board, lead with the decision. They are there to decide things. If the first line of your report is not a decision or a status against a prior decision, you have written a briefing and they will treat it as reading material.
For the funder, lead with the award and the period, and use their vocabulary. Do not invent category names. If the award terms call something a defined cost category, use that exact phrase. Where your treatment of a cost rests on an interpretation, say so in the report rather than waiting to be asked, and name who made the interpretation.
And one rule that covers both: never send a funder a number you have not reconciled to your accounting records. A technology report that disagrees with the general ledger creates a problem larger than whatever the report was trying to explain.
Part 1: Give each reader a six-section report from the same record
Six sections. Ten fields distributed across them. The order is fixed because the order is what makes it readable to a board.
Section 1: State the board decision or funder status first
The decision requested, or the status of a decision previously made. One or two sentences. If reporting status against a prior decision, name the meeting date it was approved and the evidence of completion that was promised.
Section 2: Name the program, award, restriction, and period
| Field | Entry |
|---|---|
| Program served | The program, department, or organization-wide function |
| Funding source | The specific award, contract, fee income, or unrestricted funds |
| Restriction | Restricted, unrestricted, or mixed, with a note on what the restriction says |
If a line is split across sources, record the split and the basis for the split, and say where the allocation methodology is documented.
Section 3: Quote the requirement and link the dated artifact
| Field | Entry |
|---|---|
| Control requirement | The named requirement, with its source. Award term, contract clause, insurance condition, regulation, or internal policy. If none, write operating need and explain the need |
| Current evidence | The artifact that demonstrates the control operates, with its date and who produced it. Or no evidence, which is a valid and useful entry |
Evidence states, used consistently across every sheet:
| State | Meaning |
|---|---|
current | Artifact exists, is dated within your stated review period, and names a person |
stale | Artifact exists and predates your review period |
in progress | Named owner, named artifact, and a due date |
no evidence | Nothing exists yet, and you are saying so |
no evidence reads better to a monitor than a vague assertion does. It reads better to a board too. Write it.
Section 4: Reconcile the amount to the ledger
| Field | Entry |
|---|---|
| Cost status | Current annual or period cost, whether it is charged direct, charged indirect, or paid from unrestricted funds, and whether the amount changed since the last report |
State increases and decreases explicitly with the reason. A price increase and a scope increase are different events and boards ask which one it was.
Section 5: Name the owner and next reporting date
| Field | Entry |
|---|---|
| Owner | A named person accountable for the line and its evidence. Not a department. Not a vendor |
| Reporting date | The date of this report, and the period it covers |
A vendor cannot be the owner of a control. They can operate part of it. Somebody in your organization owns whether it works and whether the evidence exists.
Section 6: Record the next action, due date, and approver
| Field | Entry |
|---|---|
| Next action | The specific next step, the person who owns it, the due date, and the artifact that will show it was done |
Every open item leaves this report with a name and a date attached. Items without one return unchanged for years, and a board that watches that happen three times stops reading the report.
Part 2: Keep the award, technology line, and decision in three sheets
Sheet 1: Quote the award term, period, restriction, and report date
One row per award, contract, or restricted funding source. Build this once and maintain it, because everything else references it.
| # | Award or contract | Funder | Period | Amount | Restriction summary | Technology costs permitted | Cost treatment basis | Reporting dates | Terms reviewed by | Date reviewed |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 |
Notes on three columns that get filled in badly:
- Technology costs permitted. Quote or cite the award language rather than paraphrasing it. A paraphrase written in a hurry two years ago is how an unallowable cost becomes a habit.
- Cost treatment basis. Whether a technology cost is charged as direct or as indirect, and whether it may be charged to a federal award at all, is determined by your award terms, the notice of funding opportunity, the federal cost principles applicable to that award, and your organization’s own written cost policy. It is not determined by this workbook. Record what your policy and your award say, and record your open questions in the next column.
- Terms reviewed by. A name and a date. If nobody has read the current award terms since the application was submitted, that itself belongs in your next board report.
Where an award is federal, note whether the organization’s federal award expenditures approach the single audit threshold. Under 2 CFR 200.501, the general single-audit threshold is $1 million in annual federal award expenditures. How expenditures are counted for that purpose in your case is a determination for your auditor.
Sheet 2: Tie each technology amount to its program and evidence
One row per technology line, cross-referenced to sheet one. This is the working sheet.
| # | Technology line | Program served | Award ref | Restriction | Reason type | Control requirement | Evidence artifact | Evidence date | Evidence state | Annual cost | Cost treatment | Owner | Decision |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 |
Reason type takes exactly one of five values, and every line must carry one:
| Reason type | Meaning |
|---|---|
mission | Directly enables program delivery to the people you serve |
grant | Required or explicitly permitted by an award, with the award term cited |
contract | Required by a contract with a funder, a payer, a partner, or a client |
control | Exists to satisfy a named control, safeguarding, or compliance requirement |
operating | Runs the organization: payroll, accounting, email, telephony |
A line with no reason type is a finding, and it goes in the report as a finding.
The five values are also where the crosswalk earns its name. Reading down the control rows tells you which requirements you believe you are meeting. Reading across to the evidence columns tells you which of those beliefs are supported. The gap between the two is the entire point of the sheet.
Sheet 3: Track each report, board vote, owner, and due date
One row per decision or reported item. This is the sheet that ends the reappearing-item problem.
| # | Date | Audience | Item | Decision | Decided by | Owner | Due date | Evidence of completion | Status | Closed date |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Board / Funder / Both | Open / Closed / Deferred |
Decision values match the companion budget workbook so the two documents stay in step: keep, reduce, remove, defer, fund through an eligible source, needs evidence.
A defer row without a written trigger in the due date column is incomplete. Write the condition that brings it back and the person who watches for it.
Before each board meeting, filter this sheet to open rows past their due date. That list is your first agenda item, and it should be short. When it stops being short, the report has told you something more useful than any of its other contents.
Part 3: One fictional board and grant report with matching figures
The organization below is fictional. All numbers are illustrative and are not benchmarks for any real organization. Award identifiers are invented.
TECHNOLOGY AND GRANT REPORT
To: Board of Directors, Harbor Reach Community Services From: M. Okafor, Executive Director Reporting date: June 9, 2026, covering January 1 through May 31, 2026 Prepared with: Internal finance and program staff. No preparer holds a commercial interest in any item below.
SECTION 1: DECISION
Three decisions are requested. First, approve removal of two duplicate technology lines recovering $7,140 annually. Second, approve $3,400 to complete an access review and restore test required to close an open internal control item on Award HHS-FICT-2026-0417. Third, note that the video platform line is deferred to the FY27 budget cycle with the trigger stated below.
Status against a prior decision: at the February 10, 2026 meeting the board approved documenting the case management system access review. That item is now in progress with a July 15, 2026 due date, described in Section 6.
SECTION 2: PROGRAM AND FUNDING
| Line | Program served | Funding source | Restriction |
|---|---|---|---|
| Case management system | Housing stability program, 340 households | Award HHS-FICT-2026-0417 (fictional) | Restricted. Award permits direct charge of program data systems. Terms reviewed March 3, 2026 |
| Client scheduling tool | Housing stability program | Same award | Restricted, same terms |
| Video meeting platform, standalone | Organization-wide | Unrestricted | None |
| Donated productivity suite | Organization-wide | Donated license, $0 | None. Administration time is real and is charged to management and general |
| File storage, second product | Finance and development | Unrestricted | None |
SECTION 3: CONTROL REQUIREMENT AND CURRENT EVIDENCE
| Line | Control requirement | Current evidence | Evidence state |
|---|---|---|---|
| Case management system | Internal control over the federal award, 2 CFR 200.303, applied to access to client program data | Quarterly access review. Last completed October 2025 | stale |
| Case management system | Recoverability of program records | No restore has been tested or timed | no evidence |
| Client scheduling tool | operating need. No named control requirement | Usage report pulled May 12, 2026 shows 4 active users of 22 licensed seats | current |
| Video meeting platform | operating need | Usage report May 12, 2026 shows 11 meetings in 90 days; the donated suite hosted 412 | current |
| Donated productivity suite | Account administration and removal of departed staff | No documented removal process. Three departed staff accounts remained active as of May 12, 2026 | no evidence |
| File storage, second product | None. Function duplicated by the donated suite | Usage report May 12, 2026 shows 2 active users | current |
The access review and the restore test are the two items driving the second decision request. Neither is satisfied by any purchase. Both are satisfied by performing the work and retaining the record.
SECTION 4: COST STATUS
| Line | Annual cost | Cost treatment | Change since last report |
|---|---|---|---|
| Case management system | $18,600 | Direct to award, per cost policy dated June 2025 | Unchanged |
| Client scheduling tool | $2,640 | Direct to award | Unchanged. 18 of 22 seats unused |
| Video meeting platform, standalone | $1,908 | Management and general | Unchanged. Function duplicated |
| Donated productivity suite | $0 license | Administration time charged to management and general | Unchanged in cash. Administration burden is unmeasured |
| File storage, second product | $4,500 | Management and general | Increased $600 at March 2026 renewal, a price change rather than a scope change |
| Removals proposed | -$7,140 | Client scheduling tool and second file storage product |
One open allowability question is flagged for the auditor: whether a portion of the donated suite’s administration time is appropriately allocated across awards under the organization’s cost policy. Finance has raised this with the auditor and it is scheduled for the August 2026 planning meeting. No allocation change has been made pending that answer.
SECTION 5: OWNER AND REPORTING DATE
| Line | Owner |
|---|---|
| Case management system and its access review | D. Reyes, Program Director |
| Restore test and recovery documentation | M. Okafor, Executive Director, with outside adviser on a flat fee |
| Donated suite administration and account removal | Vacant. This vacancy is the finding |
| All cost treatment and allocation questions | L. Tran, Finance Director |
Reporting date: June 9, 2026. Period covered: January 1 through May 31, 2026. Next report: October 2026 board meeting.
SECTION 6: NEXT ACTION
| Item | Owner | Due | Evidence of completion |
|---|---|---|---|
| Complete quarterly access review for case management system | D. Reyes | July 15, 2026 | Signed review record listing each account, its role, the reviewer, and the date |
| Run and time a restore test of program records | M. Okafor | September 1, 2026 | Written test result: date, records restored, elapsed time, verifier |
| Assign an owner for the donated suite and remove the three departed accounts | M. Okafor | June 30, 2026 | Named owner in the crosswalk, plus a directory export showing the accounts removed |
| Cancel client scheduling tool and second file storage product | L. Tran | Before September 14, 2026 cancellation deadline | Written cancellation confirmations from both vendors |
| Confirm donated suite administration allocation | L. Tran | After August 2026 auditor planning meeting | Written auditor confirmation, filed with the cost policy |
| Video meeting platform decision | M. Okafor | Deferred. Trigger: return to the board at the FY27 budget cycle, or immediately if the donated suite’s meeting function stops covering the need. D. Reyes watches for the second condition | Decision recorded in the decision log |
End of fictional example.
Part 4: Five record gaps that can produce a finding
The number that does not tie to the ledger. A report assembled from vendor invoices and a report assembled from the accounting system will disagree, because one of them counts a prepaid annual charge in a different period. Reconcile before you send. This is the single most common cause of an avoidable funder question.
The paraphrased award term. Somebody summarized the terms in 2024 and the summary has been governing decisions ever since. The summary was slightly wrong. Cite and quote, and record who read the actual document and when.
The control that is a product name. The evidence column says the name of a platform. That is a purchase, not evidence. What is the artifact, what date does it carry, and who produced it.
The item that has been open for four reports. Open items are fine. Open items with no owner and no date are how a board learns that the report is decorative. Filter sheet three by overdue rows before every meeting.
The vendor-written report. If your IT provider writes the section that argues their services are necessary, the report has a conflict inside it that a funder is entitled to know about. Ask them for usage reports, seat counts, configuration exports, and renewal terms. Write the reasoning yourself, and if an outside party did contribute, disclose whether they earn anything on the outcome.
Part 5: Ask which requirement and artifact the quote addresses
“Which specific requirement does this satisfy, and what artifact does it produce that I could hand to an auditor?” A good answer names an artifact: an exportable access log, a configuration report, a retention setting record. A weak answer names the requirement back at you.
“What is the total annual cost including administration, and what does exiting cost?” Ask this about donated and discounted offers especially. A license at $0 with eight staff hours a month of administration attached to it is a real cost that appears in no budget line.
Neither question is hostile. Both are the questions a funder will eventually ask you, and it is better to ask them at the point of sale than at the point of monitoring.
Keep both reports tied to the same source rows
This is general guidance for board and funder reporting. It is not legal advice, accounting advice, or grant compliance advice. It does not determine allowability, cost treatment, indirect cost rates, single audit applicability, or reporting deadlines for any award. Those are set by your award terms, your notice of funding opportunity, the applicable cost principles, your written policies, and your funder, and they are interpreted by your finance staff, your auditor, and where the question is legal by counsel. Where this document names a federal provision, it names only the provision, its text, and its source.
Every regulatory item here is sourced to a named authority through SBK’s source register. Where a rule varies by award, entity type, or funder, this document says so rather than flattening it into a single number.
If the problem you have is upstream of reporting, meaning the budget itself has never been examined line by line, start with the companion document, The Nonprofit Technology Budget Defense Pack, and bring its results into sheet two here.
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, so we have no interest in what appears on your technology lines. 125+ years of combined experience, 100% US-based. We will review one board cycle or one covered federal award with you if that is useful. If you use the template, close three open items, and never call, the document did what it was built to do.
(718) 407-4169