A pledge moves through four states. The donor sees each one. The system makes the work legible from commitment to delivery.
A donor sees a specific line item — six reams of copy paper for NCPA, three dozen rolls for Saturday's lunch — and commits. The system asks for a name, the quantity, and whether they'll ship or drop off. That's it.
The items arrive at the Flagstaff hub. Either shipped from a retailer with the partner address pre-filled, or carried in by a donor who lives nearby. The card moves to the second column.
For local programs, the items go directly to the Saturday lunch or the Tuesday breakfast. For remote partners, items wait at the hub until the next outbound run — currently a 5-hour drive to Rock Point.
The partner confirms receipt. The donor's card moves to delivered. The loop closes. The donor sees that the thing they did landed where it was supposed to land.
Most charity asks are vague: "donate to our food drive," "help our school." We ask for ten reams of copy paper. We ask for twenty packs of children's underwear, size six. Specificity is what lets a donor say yes to exactly the gap that exists. It's also what prevents the classic charity failure where well-meaning people send the wrong thing and the organization has to figure out what to do with it.
Each line item shows how much is pledged versus needed. A donor looking at 9 cans still needed doesn't have to wonder whether they're duplicating effort. The system self-coordinates because everyone sees the same numbers. No dispatcher, no group thread, no "did you get my email about the chicken?"
Local partners in Flagstaff fill local needs first. Surplus capacity flows outbound to remote partners on scheduled runs. Donors choose whether to give locally or contribute to the outbound queue. Programs in remote places — Rock Point, eventually others — get a structural place in the system without depending on something fragile.
Recipients are 501(c)(3) organizations or programs they operate. No anonymous individual asks, no open marketplace. The platform vouches for the work. Tax receipts work because the recipients are legitimate. Donors trust the platform because we trust the partners — and we know each one personally before they get on the board.
When you commit to a pledge, the system creates a card with your name on it. That card lives on your screen and on the board. Each state transition is real — a person at the partner organization confirms it happened.
Yes. Receipts are issued by the receiving partner organization once delivery is confirmed. The system generates the documentation; the partner countersigns it. Currently in development for the prototype phase — production receipts arrive when the platform is no longer running on in-memory data.
Programs with operational deadlines (Saturday's lunch needs to happen Saturday) have backstop coverage. We see what's not filled by 8pm the night before, and a partner-funded reserve covers the gap. Outbound runs to remote partners are scheduled monthly, so partial fills carry into the next run.
Currently a volunteer driver model. Synod members and donor congregations have offered both vehicles and time. As the network grows, fuel and vehicle costs will move to a partner-shared budget — not per-pledge fees.
No. The Arizona Food Bank Network handles statewide food distribution at a scale this platform doesn't approach. NeighborTable fills a specific gap: durable goods (school supplies, clothing, hygiene) to remote partners that AzFBN's food-focused infrastructure can't carry, plus very local food-rescue micro-coordination between Flagstaff restaurants and individual programs.
Not directly. All needs are posted by verified partner organizations. A partner can post on behalf of an individual or family they're working with — that's how community Christmas drives, school supply lists, and family-adoption programs typically run anyway. The partner is the trust intermediary.
Reach out and we'll talk. The criteria are 501(c)(3) status, a clear program structure, and a real coordinator on the partner side who can post needs and confirm deliveries. More on the partner-with-us page.
We're in early access right now, working with a small set of founding partners. Join the waitlist or reach out directly if you'd like to be one of the first when we open up.