Firebird Community Cycle: Board Service for a Two-Location Bike Co-op

community6 min read
← Back to Projects

Volunteer board member and digital strategy lead for a Barrie not-for-profit (September 2022 to March 2026). Grant writing, POS procurement, and a city-partnered bike diversion program that keeps hundreds of bikes a year out of the landfill.

WordPressGrant WritingOntario Trillium FoundationCanada Summer JobsPOS ProcurementMoneris GoLightspeedKPI TrackingVolunteer Management

Firebird Community Cycle is a registered not-for-profit (Incorporation No. 1852268) that has run a community bike workshop in Barrie, Ontario since 2011. The organization received the City of Barrie's Active Transportation Award the year it was founded. It now operates two locations: 134 Anne Street South and 132 Penetang Street, with a small core of staff and a larger pool of volunteers.

I served as a volunteer, board member, and digital strategy lead at Firebird from September 2022 until I stepped down in March 2026. Roughly 8 to 10 hours a week, most weeks. The board meetings were the small part. The interesting part was what got written between meetings: grant applications, vendor comparisons, program retros, and the program data that makes the next grant application possible. I came on because I wanted my hands on a derailleur and ended up keeping the spreadsheet that determined whether we could afford new ones.

This case study is about three pieces of that work, because trying to describe everything a volunteer board does over three and a half years produces a list nobody wants to read.

Grant writing as data discipline

The single most useful thing a small not-for-profit can do is keep a clean book of program metrics, because grant applications eat metrics for breakfast. Every funder asks the same five questions in slightly different language: who did you serve, how many of them, what changed for them, who else paid for it, and what would happen without you.

I have led or co-authored three grant applications since 2023:

  • City of Barrie Recreation and Sport Community Grant (2023). Operating support for the workshop and youth programs.
  • Canada Summer Jobs (2025 to 2026). Wage subsidies for two summer staff positions running the Bike ReCycle Program and accessible repair clinics.
  • Ontario Trillium Foundation Capital Grant (2026). A $45,000 request for capital improvements across the two-location footprint, including tooling and accessibility upgrades. In review at time of writing.

The OTF application was the one that taught me the most. Capital grants are not narrative grants. The reviewer is looking for a defensible per-line cost basis, a maintenance plan, and a realistic answer to "what happens to this asset in five years if your funding picture changes." We rewrote the budget twice. The first version had the right total and the wrong shape (too much equipment, not enough installation labour). The second version got the shape right and the narrative wrong (the maintenance plan read like a wish list). The third version was the one we filed.

What I underestimated, the first time through, was how much of a capital grant is asset-stewardship language rather than program impact language. A youth program grant rewards counting how many kids walked through the door. A capital grant rewards convincing the reviewer that the workshop bench you are buying will still be useful in 2031, that the volunteer mechanic who will be inspecting it has a name, and that there is a written replacement plan for when it eventually fails. The rhetoric is closer to facilities management than fundraising. I had to rewrite to that voice instead of the one that had worked for the youth-program submission.

The discipline that fed all three applications is mundane. We track volunteer hours. We track bikes received, refurbished, and redistributed. We track participants per program by demographic where they choose to share it. None of it is glamorous, and all of it is what makes the difference between a grant narrative that sounds plausible and one a reviewer can verify in the appendix.

POS procurement: a comparative analysis nobody asked me to write

Firebird operates two locations. For most of its history, point-of-sale was a single station per location, on different platforms, with no shared inventory. When we started looking at growing the retail side of the workshop (used parts, refurbished bikes, basic accessories), the board asked whether a unified POS made sense.

I wrote a comparison. The two finalists were Moneris Go and Lightspeed Retail. The summary, abbreviated:

CriterionMoneris GoLightspeed Retail
Monthly base cost (two locations)LowerHigher
Two-location inventory syncLimitedNative
Reporting depthBasicStrong
Hardware costBundledAdd-on
Integration with our bookkeeping (QuickBooks Online)IndirectNative
Learning curve for volunteer staffLowModerate

The recommendation went to the board with a clear tradeoff: Moneris Go is cheaper and easier for a rotating volunteer pool to learn; Lightspeed is the right answer if and only if we expect retail volume to keep growing past the point where unified inventory matters. The board voted on the cheaper option for now, with a written trigger to revisit the decision once monthly retail revenue crossed a defined threshold. That trigger is in the meeting minutes; it is not aspirational.

What I want to say about that document is not that it was a great document. It was a fine document. The thing worth saying is that small not-for-profits rarely write comparison memos at all. They pick the option whoever volunteered to research it likes best. Forcing the comparison onto paper changed the shape of the conversation in the room.

Two specific things came out of writing it down rather than discussing it verbally. First, the trigger condition (revisit when monthly retail revenue crosses a defined threshold) only made it into the minutes because the memo had a row that demanded a number. A verbal discussion would have ended at "we will check in next year." Second, the volunteer-learning-curve row turned out to weigh more than the inventory row in the eventual decision, and that ranking only became visible once the criteria sat side by side. In a board with rotating mechanic-volunteers, the cost of retraining is not a footnote.

The Bike ReCycle Program

Firebird runs the Barrie Bike ReCycle Program in partnership with the City of Barrie. The model is simple: the city diverts bikes from landfill at the dump and through bylaw seizures, those bikes come to Firebird, our volunteers and mechanics refurbish what is salvageable, and the refurbished bikes go back into the community through giveaway days, low-cost sales, and partner referrals. What is not salvageable is stripped for parts, and the parts feed the workshop's used-parts inventory.

The program diverts hundreds of bikes a year. The exact number is in our annual report and varies by season; the operational reality is that we triage what comes in, fix what can be fixed in a reasonable number of volunteer-hours, and pass on what cannot.

The interesting structural feature of the program is the partner network. Refurbished bikes are not redistributed by Firebird alone; they are routed through partner organizations who can reach populations we cannot. The list, which you can find on the website, includes CMHA, Barrie Public Library (with whom we run the Shifting Gears youth cycle club for ages 10 to 12), Living Green Barrie, Barrie Police Service, Georgian College, TNO Toronto, Uplift Black, Youth Haven, the David Busby Centre, the John Howard Society, and College Boréal.

That partner list is also what makes the data work. Every bike that goes out the door has a destination category. Every category corresponds to a relationship someone has built and is maintaining. The database is small. The relationship work behind it is not.

Programs I help with but did not design

Two programs I want to name even though I am not their architect:

Shifting Gears Cycle Club. A youth cycle club for ages 10 to 12, run in partnership with Barrie Public Library. Mechanics fundamentals, road safety, and a lot of riding. The library connection is what gets families through the door who would not otherwise know the workshop exists.

Accessible repair workshops for women and gender-diverse individuals. Drop-in repair clinics structured to be lower-pressure than the general drop-in floor. The "accessible" framing is doing real work: a repair workshop full of guys with tools is not psychologically the same room as one designed around a different default.

I support these programs by helping with the digital and grant infrastructure that lets them keep running. The pedagogy is run by people who have been doing it longer than I have.

What this work taught me

The thing I did not fully understand before joining the board is how much of small-not-for-profit operations is simply keeping clean records. A bike that arrives with no paperwork and goes out the door with no paperwork is, for the purposes of next year's grant application, a bike that did not exist. The discipline of writing things down, the same week they happen, in a format the next volunteer can find, is what separates an organization that can grow from an organization that survives on the goodwill of whoever currently has the most context in their head.

The corollary, which took me longer to accept, is that the right level of record-keeping for a volunteer organization is one notch below what a paid organization would do. A perfect database that nobody updates is worse than a passable spreadsheet that gets touched every Saturday. I have made the mistake of designing the better system. The better system rotted within a quarter because no volunteer wanted to learn it. The passable spreadsheet is still in use.

That is the part that connects most directly to my day job at metricHEALTH. The KPI dashboards I help build for healthcare clients exist because clinical work, like volunteer work, is invisible unless someone counts it. Counting it well, in a way that the front-line people doing the work can actually feed and trust, is the same problem in both places. Different domain, same instinct.

I stepped down from the Firebird board in March 2026, after three and a half years. The OTF application I led is still in review at time of writing. The Bike ReCycle Program continues to run, now under the next round of board members.