Scaling partner operations with Airtable
At America's Thrift Stores I ran the Bags for Bucks program: schools, churches, nonprofits and businesses collected donated goods, ATS weighed them and paid the partner by the pound. The role was new and had no system, so I built one in Airtable and used it to run 50+ partners across multiple states.
A database of transactions, not relationships
One flat table
247 rows, one per drive. First Baptist Church appeared three times and nothing said it was the same organization.
Four questions nobody could answer
Who is our contact? Do they have a W-9, the tax form we needed before paying them? How many pounds have they raised with us? When did we last talk to them?
Everything by hand
Onboarding checklists were copied from scratch for each partner. Emails went out by hand, or not at all. Leadership could not see where any partner stood.
| Drive | Organization | Dates | Status | Lbs |
|---|---|---|---|---|
| Spring Drive 2024 | First Baptist Church | Mar 4 to 18 | Complete | 1,240 |
| Earth Day Collection | Northstar LLC | Apr 15 to 29 | Active | — |
| Fall Drive 2023 | First Baptist Church | Oct 2 to 16 | Complete | 980 |
| Holiday Give-Back | Lincoln Elementary | Dec 1 to 15 | Complete | 670 |
| Back to School 2023 | First Baptist Church | Aug 7 to 21 | Complete | 1,100 |
| Community Clean-Up | Meridian Co. | May 6 to 20 | Scheduled | — |
| Spring Drive 2024 | Hope Church | Mar 11 to 25 | Active | — |
Contact & status
Drive history
Communication log
Tasks & Outbox
Left: the drives table I inherited. Right: the same church as one partner record after the rebuild. Sample data.
One record per partner
Four tables
Organizations, Drives, Partner Tasks and a Communication Log. A partner could have many drives, many tasks and a full history, and every one of them linked back to the organization.
One clear status list
I replaced vague, overlapping statuses with a pipeline from Discovery to Closed Paid, plus a Priority tag (Upcoming, Support, Discovery, Pending) so leadership could read the whole program at a glance.
16 interface pages
One page per job. A daily cockpit for me, a dashboard for leadership, a hub for the ADLMs (the area logistics managers who placed bins and ran pickups), and reference pages for files, templates and procedures.
The status list. Deferred, Cancelled and Lost sat beside the pipeline. A drive could only be entered into Vonigo, the pickup and routing tool, once its dates and location were confirmed, so incomplete drives never reached the drivers.
| Page | What it was for |
|---|---|
| Dashboard | Pounds, funds, families served, status charts, top partners |
| Organizations Command Center | Priority Base, the daily cockpit in Part 5: active and at-risk partners, tasks, email buttons |
| Priority: Schools | Schools had their own W-9 steps and calendar |
| Most Recently Contacted | Who had gone longest without a call or email |
| Drive Calendar & Dates | Scheduling conflicts across every active drive |
| Organization Record Review | Everything about one partner on one page |
| Onboarding Steps | Checklists with a progress bar per partner |
| Master Partner Checklist | The template that copied itself into each new partner |
| Page | What it was for |
|---|---|
| All Partners & Drives | The phone book, and where data got cleaned up |
| Files & Templates | PDFs, flyers and promo materials in one place |
| SOPs, read-only and editing | A locked copy for daily use and a working copy |
| Email Editing | Where the email templates were written and fixed |
| ADLM Hub | Who covered where: bins, pickups, drivers, weight tickets |
| Kanban by Category | The pipeline as a board |
| Table of Contents | Every page listed with what it was for |
| Page Descriptions | How to use each page, so the team could run it without me |
System prepares. Human decides.
Pre-written for every stage
20+ emails, from the intro and follow-ups through the welcome kit, W-9 request, pickup reminder, check-ins, thank-you and results.
Filled in, then checked
Partner name, organization, dates and payout came from the record. Highlighted blanks showed what to check before sending. Nothing sent on its own.
Stage-locked and logged
Only the emails for the partner's current status showed. Every send wrote a timestamped entry in the Communication Log.
Communication log
Pick an email, then press Send. Locked emails belong to a later stage. Sample wording, not the real templates.
21 automations that responded to reality
State, not time
Each one fired on something real: a status change, a missing document, a logged pickup. Never "day 3" or "day 7".
A checkbox, not a timer
Each email was a task on the partner's checklist. Ticking it Done moved that email into the Outbox, ready to personalize and send in one click. I chose the moment. The system did the setup.
Exceptions first
The Uh-Oh Board listed every partner with a problem, the reason and a countdown, so I found them before the deadline did.
One status change could set off work in all three layers: partner operations, logistics, and reporting. Sample partner.
| 15 email automations | Fired when |
|---|---|
| Intro email | A new partner record was created |
| Follow-up: no response | No reply after the intro |
| Follow-up: confirm dates | Interested, dates still open |
| Date confirmation request | Dates missing on an interested partner |
| Date confirmation | Dates and logistics locked |
| Welcome kit | After confirmation, before the drive |
| W-9 request | Drive confirmed, no W-9 on file |
| W-9 reminder | Still missing close to the drive start |
| Weekly pre-drive check-in | Each week before the drive, with a manual override |
| Support check-in | 7 days before the start |
| Schools check-in, W-9 on file | School partner, paperwork done |
| Schools check-in, W-9 missing | School partner, paperwork still owed |
| Pickup reminder | Pickup scheduled: access, bins, contact |
| Post-drive thank you | Drive marked complete |
| Results and payout | Pound totals entered |
| 6 workflow automations | What it did |
|---|---|
| Priority → task list | Copied the Master Partner Checklist into the partner, set due dates, turned on the Outbox |
| New drive → task scaffold | Created the baseline tasks for a new drive |
| Sync new drives | A new drive inherited its organization's fields, status and logistics manager |
| ADLM notification | Told the right logistics manager when a drive landed in their area |
| Status-driven buttons | Only the actions for the current stage were available |
| Pickup logged → closeout | Locked the drive, staged the thank-you, set the renewal target |
Open it, work the list, go home
Only who needed me
Priority Base showed active and at-risk partners: status, onboarding progress, days in the system and any flag. Nothing else.
Five panels per partner
Details, overview cards (W-9, days since sign-up, task %), the communication log, the task list and the Outbox.
Rules written into the system
No reply after two follow-ups meant mark cold. A missing W-9 blocked payment and was flagged 14 days out. A confirmed drive with no logistics manager could not move forward.
Partner info
Outbox and tasks
Partner info
Status
Partner info
Action needed
Partner info
Exception
Status
Flag
Partner info
Tasks
Partner info
Next
Click a partner to open its panel. Sample partners, fictional names.
Eight weeks, the same every time
Week by week
From the welcome packet four weeks out to the renewal offer four weeks after, every email and asset was tied to a week and staged in the Outbox. Nothing was ad hoc.
Built to come back
Closing a drive set a renewal target six months out and created an outreach task 30 days before it. Returning partners kept their whole history.
What else shipped
Documentation for a role that had none
A full standard operating procedure, a six-step onboarding checklist, a day-to-day guide, and the logic for assigning logistics managers by zip code.
A partner toolkit
Editable flyers, logos, newsletter copy, social posts with captions and photo guidance, built with the marketing and social teams after partners asked for materials that did not exist.
Targets for the program
1.5M additional pounds a year, 85%+ partner retention and 5 to 10 new partnerships a month, with a priorities report to the team every Monday.
Results
How I think about systems
State > Time
Automations respond to what is happening, not what the calendar says.
Human > Auto
System prepares. Human decides. One click executes.
Context > Speed
Every email reviewed. Partners are people, not funnel entries.
Focus > Volume
Show what needs attention now. Hide the noise, surface the exceptions.