Success by JazE Edutech / Case Study
Case Study
Follow one fictional bank's twelve-month technical assistance engagement with a nonprofit — three deliverables, 410 donated hours, and every CRA log entry.
Banks give nonprofits technical assistance: skilled staff services delivered free, such as building a financial education curriculum, standing up data and reporting systems, or training staff on grant compliance — often because qualifying work can be documented as a community development service under the Community Reinvestment Act. A typical engagement runs from a needs-assessment call through a scoped package of deliverables to documented staff hours in the bank's CRA exam file.
Explore the behavior-change comparison lab and transfer checkpoints below.
Full written guide, sources, and FAQs
How one regional bank scoped, delivered, and documented a twelve-month technical assistance engagement with a community nonprofit — three deliverables, 410 donated staff hours, and every CRA ledger entry along the way. A model replay for bank CRA teams and nonprofit administrators.
This resource helps readers connect what technical assistance do banks provide to nonprofits to classroom practice, standards-aware implementation, and responsible next steps for schools and sponsors.
Technical assistance — often shortened to TA — is skilled help a bank gives a nonprofit at no charge: designing a financial education curriculum, building data and reporting systems, training staff on grant compliance, or advising on budgets, marketing, and technology. Banks do this for many reasons, and one is structural: staff time spent delivering qualifying community development services is a category federal examiners review under the Community Reinvestment Act, alongside loans and investments.
In practice, technical assistance is scoped like a small consulting project: a needs-assessment call, a written agreement, named bank employees, deliverables with deadlines, and a paper trail. The replay on this page follows one fictional regional bank and one community nonprofit through a full twelve-month engagement — three deliverables, 410 donated staff hours valued at $34,850 under the model's stated assumptions, and the exact ledger entries each deliverable produced for the bank's CRA exam file.
Everything on this page is a model scenario. Harborlight Savings Bank and the Juniper Street Learning Center are fictional, constructed from public CRA guidance to show what a complete technical assistance engagement looks like from both sides of the table. No real bank, nonprofit, deployment, or outcome is described, and nothing here promises or predicts CRA credit — examiners alone make that determination for each bank's actual file.
Read it two ways. If you work at a bank, treat it as a documentation blueprint to hold against your own files — especially the ledger discipline in the exam-file section. If you run a school or community nonprofit, treat it as a preview of what to ask for, what a well-run partner will expect from you, and what a realistic twelve-month rhythm feels like.
The Community Reinvestment Act encourages banks to help meet the credit needs of the low- and moderate-income neighborhoods where they take deposits. Alongside loans and investments, federal examiners consider community development services — activities a bank performs itself, such as teaching financial education classes, serving on a nonprofit board, or providing technical assistance to organizations serving those neighborhoods. The banking agencies' CRA rules and the interagency questions and answers describe services like these and the records banks keep to support them.
For nonprofits, the appeal is practical. A community organization often needs a skill more than it needs another small grant: someone who builds reconciliation spreadsheets for a living, a trainer who can make a compliance workshop digestible, a lending officer who knows exactly what funders ask for. Technical assistance transfers those skills from the bank to the nonprofit, then leaves them behind when the engagement ends.
The engagement opens with a needs-assessment call: the bank's community development officer, one compliance trainer, and the learning center's executive director spend an hour separating nice-to-have from genuine capacity gaps. Three survive the filter. The center's adult workforce program needs a financial education curriculum it cannot afford to build. Its outcome reporting is a tangle of spreadsheets that its next grant renewal depends on. Its two-person staff has never prepared for a funder audit. Each surviving gap becomes a scoped deliverable with named staff and dates.
The signed one-page agreement commits six bank employees — two from community development, two analysts, two compliance trainers — to 410 hours across twelve months. Under the model's assumptions, a blended rate of $85 per fully loaded professional hour values the package at $34,850 in donated expertise. The nonprofit's obligations are just as concrete: a meeting room, participant lists gathered with consent, staff time for co-planning, and candid feedback at each quarterly checkpoint.
The replay deliberately keeps the awkward middle months. Curriculum sessions are rescheduled when the center's boiler fails in February. The dashboard's first draft tracks inputs nobody will ever act on, so the analysts rebuild it around five decisions the director actually makes. The second compliance workshop draws two attendees, and the trainers rework the format into shorter hands-on sessions. The project lead logs every setback the same way she logs the wins, because a file that shows only victories reads as marketing rather than evidence.
This is the section to slow down on: a ledger that starts empty in January and fills, entry by entry, as the year progresses. For each deliverable the bank writes one community development service entry — the activity, its community development purpose, who primarily benefits, where it happens, dates, hours, and staff roles — and files the supporting evidence behind it. Step through the exam binder below: each entry card slots into the file, closes a deliverable tab, and pushes the hour meter toward 410 — then imagine your own file.
By month twelve, the model nonprofit's outcomes look like this: all 60 adult learners completed the eight-week financial education course with pre- and post-assessments on file; the dashboard produced twelve monthly outcome reports that anchored the center's grant renewal narrative; and the staff passed a mock funder audit with no material findings. Each is a model result, not a real one — the point is what measured looks like: a before-and-after number, an artifact, and a date attached to every claim.
The bank's trail mirrors the nonprofit's. The exam binder holds the signed engagement agreement, quarterly time logs totaling 410 hours, the finished curriculum with its standards mapping, dashboard screenshots, workshop materials, and a closing memo that ties each deliverable to its ledger entry. When an examiner asks how staff time served the community, the bank hands over a story with dates and receipts instead of a warm anecdote.
The ledger also records what honesty costs: two rescheduled cohorts and one full dashboard redesign are noted inside the entries, with the hour overage absorbed within the 410-hour cap. Entries stay credible because the file, not anyone's memory, carries the details — and because the bank can show its work, including the parts that went sideways before they went well.
Deliverable 1 is where a platform earns its keep. In the model, the bank adapts Success's scenario-based financial literacy curriculum — lessons built around the money decisions students and adults actually face — to the learning center's workforce schedule rather than writing a course from scratch. Schools and community organizations can explore the classroom kits and readiness resources on this site to see what a sponsor-supported deployment looks like in practice.
For banks, the pattern generalizes: pair donated staff expertise with a curriculum partner, and the deliverable survives staff turnover on either side. For administrators, the ask gets easier when you can point to standards alignment, device coverage, and evidence-based instruction. This replay owns the end-to-end question — what a full technical assistance engagement looks like from needs assessment to exam file — while the narrower question of whether the CRA requires or subsidizes financial literacy training is dissected in the companion training piece linked below. The other tools and case studies linked there walk the neighboring questions — what a qualified activity looks like test by test, and how community development work shapes a bank's overall CRA rating.
The caveat bears repeating: Harborlight Savings Bank and the Juniper Street Learning Center do not exist; the hours, dollar values, and outcomes are stated assumptions and illustrations, not measurements; and nothing here is legal, tax, or compliance advice or a promise of CRA credit, regulatory treatment, or a rating outcome. Which activities qualify, and how examiners weigh them, depends on each bank's facts, its regulator, and the CRA rules and guidance in force — banks should confirm specifics with their compliance teams and regulators.
The public sources below are the authority layer for the framework: how the banking agencies describe community development services, the records banks keep, and the education standards the model curriculum maps to. Start with the FFIEC's CRA materials and your own regulator's pages, then bring questions to your compliance team.
It is skilled, unpaid help a bank's employees give a community organization — such as building a financial education curriculum, setting up data and reporting systems, or training staff on grant compliance. Under the CRA, this kind of staff-delivered help can be documented as a community development service when it meets the qualifying criteria.
Hours employees spend delivering qualifying community development services as part of their job can be documented and reviewed by examiners. Purely personal, off-hours volunteering is generally not treated as a service the bank itself performed. What matters is that the bank structured, staffed, and documented the activity.
A grant is money the bank gives, generally reviewed as a qualified investment. A community development service is work the bank's own people perform, such as technical assistance. Many engagements combine both — for example, a grant funds materials while staff hours build the program.
Identify banks with branches near the people you serve, then contact their community development or community relations officers with a short proposal: your mission, the low- or moderate-income population you serve, the specific capacity gap, and the scoped help you need. The needs-assessment call in this replay shows what a good first conversation covers.
Typical files include the engagement agreement, activity descriptions with community development purpose, beneficiary and location notes, dates and staff hours, and the deliverables themselves — curricula, dashboards, training materials. Records created at the time of the work are stronger than a year-end reconstruction.
No. Activities are evaluated against criteria such as community development purpose, who primarily benefits, and the bank's assessment area, and examiners make the final determination. That is why careful scoping and documentation — the backbone of this replay — matter as much as the work itself.
Federal Financial Institutions Examination Council
Board of Governors of the Federal Reserve System
Office of the Comptroller of the Currency
Federal Deposit Insurance Corporation
National Community Reinvestment Coalition
Jump$tart Coalition for Personal Financial Literacy