Nonprofits

How small nonprofits build a temp talent pool without a staffing agency

Standard temp-pool advice assumes a staffing agency and a temp-to-permanent pipeline. Most small nonprofits have neither. The realistic model is a self-built pool of recurring temps who come back project after project.

How small nonprofits build a temp talent pool without a staffing agency

Most temp-talent-pool advice is written for organizations big enough to partner with a staffing agency and stable enough to convert temp workers into permanent hires. Neither matches the reality for most small nonprofits. Agency fees and minimum contract sizes are often out of reach when your annual people budget is tight. And the temp-to-permanent pipeline assumes you have full-time positions opening up at a useful cadence, when in fact most small nonprofits open one new permanent role every year or two.

In Canada, a registered charity (CRA) is not the same as a nonprofit without charitable status. Only registered charities and other qualified donees can issue official donation receipts. That distinction doesn’t change how you coordinate paid temps, but it does change what you can offer volunteers versus paid workers, and how you report pay. Employees get a T4 (income tax, CPP, and EI deducted at source). Fees for services outside an employment relationship are reported on a T4A. The slip does not decide status — CRA’s employee-versus-contractor tests in RC4110 do. At-will employment is not a Canadian doctrine.

The realistic version is different. Your temp pool comes from people who already know your work, and the goal isn’t conversion to permanent staff. It’s making sure good temps come back the next time you need them.

Where your real temp pool lives

Skip the agency mental model entirely. Your temp talent pool is sitting in five places, and you almost certainly already know most of the people in it.

Past volunteers who’d happily do paid work. A volunteer who has shown up reliably for three Saturdays at your fundraiser is your fastest possible temp. They know how you work, they like the cause, and they’re a known quantity. Many will say yes to paid temp work for the same organization because it pays them for time they were going to give anyway. When the role is paid, classify it: T4 if they’re an employee, T4A if they’re genuinely a contractor. Don’t treat a paid gig as “still volunteering.”

Returning seasonal workers. Whoever staffed your last summer program, year-end push, or annual fundraiser is probably willing to come back if asked early enough. Most won’t proactively contact you, but they’ll say yes if you reach out. For seasonal youth hiring, Canada Summer Jobs is a federal wage subsidy (2026 jobs between 20 April and 29 August) — not a staffing agency.

Contractors you’ve used before. The graphic designer you hired for one project, the photographer from the last gala, the bookkeeper who helped during audit season. Each of them is, functionally, a one-person temp pool already. They’ve been vetted by your past hire decision.

The friend-and-staff network. Your current staff have friends, partners, kids, and neighbours who freelance or do casual work. Asking is free. Most small nonprofits underuse this aggressively because it feels like nepotism. It isn’t, as long as you’re paying market rate and the role is real.

Adjacent organizations’ alumni. People who’ve worked at other nonprofits in your space, especially recent past-staff who left for school, family reasons, or a different city. They’re often genuinely happy to do flexible temp work for a sister organization, particularly if they liked their previous role. To expand beyond the networks you already have, Volunteer Canada and CharityVillage are the usual Canadian boards — not a US skills-based marketplace.

These people share a quality no agency temp has: they already know your work. Onboarding takes a quarter of the time. The mission resonates from minute one. And when you need them again next quarter, they remember where the supplies are kept.

Forget temp-to-permanent. Aim for recurring temping.

Most “engagement pipeline” advice tells you to design touchpoints that move temp workers toward permanent roles. For small nonprofits, that goal is mostly aspirational. You don’t open enough permanent positions to absorb your strongest temps, and the temps worth keeping usually aren’t trying to become full-time staff anyway. They have day jobs. They have school. They have other commitments. Temp suits them.

The honest goal isn’t conversion. It’s recurring engagement. A temp who’s done two gigs for you is more valuable than a new applicant in almost every measurable way: they know your systems, they’ve been vetted by performance, they have context, and they don’t need re-onboarding for the basics. The metric to actually track isn’t “what percentage of temps became staff.” It’s “what percentage of last year’s temps are working with us again this year?”

That second metric is achievable. The first is mostly a fantasy, and chasing it generates pipeline activity that doesn’t pay off.

How to build a pool that comes back

Recurring temping isn’t automatic. People come back when the previous gig was good, the relationship felt genuine, and you made it easy to say yes again. A few specifics that work:

Pay on time, every time. This is the foundation. A single late payment, even by a week, costs you more goodwill than a month of relationship-building can rebuild. Set up payments to be reliable before you do anything else. If they’re employees, that includes T4 payroll (CPP and EI deducted at source). If they’re contractors, T4A reporting where CRA’s policy applies.

Make re-onboarding genuinely easy. A returning temp shouldn’t have to redo a full orientation. A short “what’s changed since you were here” briefing, a fresh login if needed, and confirmation of pay rate is enough. If the comeback feels like a fresh hire, fewer people will come back.

Keep useful records. Not a hiring funnel. A relationship CRM. For each past temp: contact details, the gigs they’ve worked, what they were good at, what to be aware of, and what they’re available for now. Honest internal notes (“Sarah is excellent at front-of-house, less comfortable handling cash, available weekends only”) save the next manager hours of guessing. A dedicated hiring platform can do this if you have the budget; a shared spreadsheet works if you don’t. Data quality matters more than the tool.

Light-touch check-ins between gigs. Not spam. Once or twice a year, a personal email asking if they’re available for upcoming work. That’s it. The point is to stay top-of-mind without becoming an obligation.

First call on new gigs. When a new temp opportunity comes up, work through your existing pool before posting a public ad. This is faster, cheaper, and produces better hires. It also signals to past temps that you genuinely value them, which makes them more likely to say yes.

Specific recognition after each gig. Not “thanks for helping out.” “The way you handled the donor question at the gala saved Marcus’s evening, and we noticed.” Specifics make recognition feel real and give the person a story to tell about working with you, which is what employer brand actually is.

The diversity problem with network-built pools

The honest weakness of building a temp pool from past volunteers, friends-of-staff, and adjacent organizations is that those networks are usually not diverse. Your network looks like you. So does your past hires’ network. The temp pool you build out of those networks will keep reinforcing the demographic patterns of who already works in your space.

Fixing this matters and isn’t done by accident. Concrete moves that work:

  • Ask staff to suggest people from networks they’re not already in. The colleague who’s involved in a different community group, the volunteer who knows people through their religious community or affinity group.
  • Build relationships with organizations whose networks complement yours: inclusion-focused groups in your sector, university programs serving underrepresented students, and professional networks supporting women, racial and ethnic minorities, disabled professionals, or other groups underrepresented in your field. Volunteer Canada and CharityVillage are the public boards; they are not a substitute for those relationships.
  • When evaluating past temps for return engagements, use structured criteria rather than gut feel. Whose work was strong? Who showed up reliably? Who solved problems without escalating? These are answerable from your records, not from impressions.
  • Track your re-engagement patterns. If you’re rehiring the same five people every season and they’re all from one demographic slice, that’s the signal to expand the pool, not a sign that those five are uniquely good.

This isn’t checkbox diversity. It’s a real source of strength: a temp pool that draws from multiple networks is genuinely more resilient than one drawn from a single network. When one set of people gets busy, you have others to call.

Tools that fit small-nonprofit reality

For the actual work of managing a recurring-temp pool, the tooling needs are lighter than the corporate-recruiting playbook suggests. You need three things: a way to keep records, a way to coordinate gigs, and a way to communicate with the pool when needs come up.

For the records, a Canadian fundraising CRM can handle this if you’ve got broader needs around donor data and volunteer tracking too — CanadaHelps for giving, or the CRM you already run. For just the temp side, a simple spreadsheet is fine until you outgrow it. A few basic metrics are worth tracking: re-engagement rate, time-to-respond when you reach out, and average gigs per person per year. These tell you whether the pool is actually working.

For coordinating actual gigs, shift signup tools where temps can see what’s available and claim what fits work better than back-and-forth email. Zelos is a task and shift signup app with built-in messaging. It handles this at small-nonprofit scale, and the free plan covers unlimited team members, which matters when your “team” is fifty past temps you want to keep in your roster year-round without paying for inactive seats. People choose; software doesn’t assign. Never per seat. 25 concurrent active tasks on the free plan.

For communication, one channel that the pool actually checks. Group chat, email list, whatever your people use. Consistency matters more than the platform.

Employer brand for the people you want back

The employer brand that matters for repeat temps is different from the one that matters for new applicants. New applicants are persuaded by your website, your reviews, and your mission. Repeat temps are persuaded by what their last gig actually felt like.

For repeat temps, the “brand” they’re judging is the lived experience of working with you, not anything you’ve said about yourself. Did the manager respect their time? Was the role what was promised? Did the pay arrive on schedule? Did anyone follow up?

Improving this isn’t recruitment-marketing work. It’s operational. Pay on time. Communicate clearly. Treat temps as colleagues during the gig and as people you’d like to work with again afterwards. Word-of-mouth in the temp world is faster and more honest than any review platform; the temps who had a good experience tell their networks, and the ones who didn’t tell theirs.

If your employer brand for temps is rough right now, the fix is the next gig, not the next ad campaign.

The pool you’ve built beats the pool you rent

Working through a staffing agency makes sense for organizations with predictable, ongoing temp needs and the budget to absorb agency fees. For most small nonprofits, the realistic temp pool is one you build and own. People who already know your mission, who’ve worked with you before, who come back when asked.

The way to build that pool is straightforward and slow. Pay on time. Keep useful records. Stay in touch lightly between gigs. Call your past people first when new opportunities open. Treat each gig as an audition for the next one, not a feeder for a permanent role that probably isn’t coming.

For onboarding logistics on the gig itself, the standard temp-onboarding fundamentals still apply. The difference is that with a returning pool, you do that work once per person, not once per gig.

Ready to simplify your team coordination?

Try Zelos free