What Technical Assistance Is, and When It Works

A foundation funds a year of capacity building for eight small organizations. There are monthly webinars, a shared drive of good templates, and a closing report with strong attendance numbers. Eighteen months later, six of the eight still cannot produce a current balance sheet when a funder asks for one.

Nobody did anything wrong. The sessions happened, the templates were genuinely useful, and the people who showed up learned something. The problem is that almost none of it was technical assistance.

Assistance starts from a constraint, not a topic

Technical assistance is direct help with the specific thing an organization cannot currently do. That sounds obvious until you notice how much capacity building is organized around subjects instead.

• Training transfers knowledge that is the same for everyone in the room. Allowable cost rules are allowable cost rules. A session on them is efficient and worth running.
• Technical assistance works on one organization’s own books, bylaws, and decisions. It cannot be delivered to a room, because no two organizations in that room are stuck in the same place.

A cohort of twelve may genuinely need the same training on allowable cost. They will not need the same help building a chart of accounts, because they are not starting from the same place and several of them do not have one at all. Delivering the second as though it were the first produces attendance and no change.

Why so much of it leaves nothing behind

The failures are consistent enough to list.

• It is aimed at the wrong thing. The program covers what the funder finds interesting rather than what the organization is actually stuck on.
• It stops at handover. A template is delivered, everyone agrees it is excellent, and nobody uses it through a full cycle while help is still available.
• It reaches one person. Everything goes to the executive director, so none of it survives their departure, and in a small organization departures are not rare.
• It produces documents instead of practice. New bylaws exist. The board that was never in the room while they were written has not adopted them and does not refer to them.

The assessment is most of the work

You cannot help with a constraint until you know what it is, and organizations are not always reliable narrators about their own. The thing leadership names first is often the thing that is most irritating rather than the thing that is most binding.

A structured assessment looks across the whole operating picture rather than the presenting complaint.

• Financial management. Chart of accounts, internal controls, who reconciles, and whether a current statement can be produced on request.
• Governance. Board composition, officer roles, bylaws, meeting discipline, and whether the board can read and question a financial statement.
• Organizational infrastructure. Policies, personnel practice, insurance, and record keeping.
• Sustainability. Revenue concentration, funding pipeline, and what happens in the year after a one-time award.
• Strategy. Whether priorities exist in a form the board and staff can hold themselves to.
• Program design and data. Whether the service model is documented and whether outcomes can be evidenced.

An organization is rarely weak across all six. Finding the two or three that actually bind, and spending the engagement there, is what produces change inside a funding period.

Sequence matters more than coverage

Financial management and governance usually come first, because the rest sits on top of them. An organization without internal controls cannot safely receive a disbursement. A board that cannot read a financial statement cannot approve the budget a sustainability plan depends on.

Strategic planning placed before those foundations is the most common sequencing error in capacity work. It feels like progress, it produces a handsome document, and the document describes an organization that does not yet have the systems to execute any of it.

What to ask before you accept it

If someone is about to deliver technical assistance to your organization, these five questions will tell you most of what you need to know.

1. What will you assess before you start, and will we see the findings in writing?
2. Will you do the work with us, or hand us a template and a recording?
3. What will exist at the end of this that does not exist now? Name the artifacts.
4. Will you still be here when we run the new system through a full cycle and it breaks?
5. If the real problem turns out to be governance, are you willing to say so to the board?

The last one matters more than it looks. Consultants are paid by someone, and the finding that a board is not functioning is the one most often softened into something easier to hear.

If you are the one paying for it

Funders get what they measure. Ask for attendance and you will receive attendance.

If you are also moving money to these organizations rather than only helping them, the award process and pass-through administration is a separate discipline carrying its own obligations, and it is worth deciding early who holds them.

• Movement on assessment scores between a baseline and a closing review, per organization rather than as a cohort average.
• Artifacts that now exist and did not before: a chart of accounts, adopted bylaws, a written personnel policy, a board matrix.
• Behavior rather than documents: budgets adopted on time, statements produced monthly, board meetings held with quorum.
• A named account of what did not move, and why.

That last item is the one that makes the rest believable. A cohort report showing every organization improving in every domain is not a result, it is a sales document, and experienced reviewers read it that way.

The limit worth being honest about

Technical assistance cannot fix underfunding. An organization running a real service on a budget that does not cover it has a revenue problem, and no amount of help with its chart of accounts will change that. Capacity building offered in place of operating support is a way of locating the problem inside the organization, where it is cheaper to address.

Offered alongside operating support, it is one of the more useful things a funder can buy. The organizations that most need it are usually the ones with the least room to absorb it, which is an argument for paying for their time during the engagement rather than treating their participation as free.

What good looks like

A year later, the executive director is not the only person who can produce a financial statement. The board asks questions about the budget before approving it. The organization applied for something it would not have been ready to apply for before, and whether or not it won, the application was complete.

None of that shows up in an attendance report. All of it shows up the next time the organization is under pressure, which is the only test that was ever going to matter.