An Airtable nonprofit supply request workflow can collect what partner organizations need, support staff allocation decisions and track what was actually collected. Use a miniExtensions Form for requests from an approved supply catalog, then review quantities in Airtable before confirming a handoff. A submitted request is demand, not a stock reservation.
Fictional Community Workshop Exchange distributes donated stationery and workshop materials to local partner organizations. Northside Learning Hub asks for twenty sketchpads for an adult learning session. The coordinator needs to confirm the request, allocate a realistic quantity and record collection without asking for personal details about the people attending.
Model requests in units staff can allocate
Create a Supply catalog table with Item name as primary text, Category as single select, Request unit as text, Description as long text and Accepting requests as checkbox. A unit might be one sketchpad, one box of twelve pencils or one sealed art-materials pack. Make the unit explicit so twenty does not mean twenty boxes to one person and twenty individual items to another.
Create Supply requests with Request reference as autonumber, Submitted time, Organization name, Organization contact, Contact email, Supply item as link, Requested quantity as number, Needed by as date and Intended organizational use as long text. Use one item per submission in this baseline so each quantity has a clear unit and separate allocation decision.
Keep Review state, Verified organization, Coordinator, Allocated quantity, Allocation note and Actual collected quantity staff-managed. Suggested states are New, Needs clarification, Allocated, Partially allocated, Not allocated, Withdrawn and Completed. These are proposed process fields. They do not turn Airtable into a real-time warehouse system.
Offer an approved catalog, not a stock promise
Connect a miniExtensions Form to Supply requests. Show organization-level contact information, the supply selector, requested quantity, deadline and a brief explanation of use. Tell requesters that staff will confirm availability and that the form does not reserve goods. Do not collect beneficiary names, health details or other sensitive case information.
Filter the Supply item field to catalog records where Accepting requests is checked. The linked-record filter documentation explains that finder filtering and already-selected values are separate considerations. Review the filter application mode, and disable creation of new catalog items from this form. A requester should select an approved item, not create an unreviewed product.
The catalog should contain only information safe for requesters to see. Do not attach internal donor details, private allocation notes or storage access instructions to an expandable public catalog record. An item marked Accepting requests means staff is willing to review demand; it should not be labeled “in stock” unless a separately maintained system supports that statement.
Keep submission and review distinct
For a standalone intake form without a Login/Lookup page, use Share to allow record creation and disable updates to existing records, following the form creation controls. Keep allocation decisions out of the requester-facing form. A public submission does not establish that the named organization is an approved partner.
The coordinator verifies the organization and contact through the nonprofit’s existing partner process, checks whether a similar request is already pending and clarifies any ambiguous unit. Northside’s twenty sketchpads should remain Requested quantity twenty even if only twelve can be offered. Do not overwrite the request to make the numbers agree.
Staff decides allocation using the organization’s agreed criteria and a current physical or separately managed stock check. Record Allocated quantity twelve and an explanation of the partial decision. If another partner has already been promised the remaining supplies, the coordinator must account for that commitment before confirming this one. The form alone does not prevent over-allocation.
Confirm substitutions instead of silently changing the request
If sketchpads are unavailable but notebooks are available, record the proposed alternative and contact the requester. Do not replace the original linked item and make it appear that the partner requested something else. Keep the original request intact and create a clearly associated replacement request only after staff records the partner’s agreement.
For multiple items, staff can group submissions using a staff-managed Request group reference and plan one collection. Each line still retains its own requested, allocated and collected quantities. This is more transparent than one total count across incompatible units, such as sketchpads plus boxes of pencils.
Allocation communication is manual in this design. The coordinator uses the established contact channel to explain the quantity, any conditions and the next step. An Allocated status does not itself notify the requester, schedule a vehicle or guarantee that a partner can arrive whenever it chooses.
Track arrangements separately from physical collection
Create Collection plans with Plan reference, linked requests, Agreed collection time, Organization contact, Coordinator and Plan state. Use Proposed, Agreed, Completed and Canceled as starting states. Staff records the agreed time only after arranging it with the partner; a requested deadline is not an appointment.
At handoff, staff counts the goods and records Actual collected quantity. If the partner collects ten of the twelve allocated sketchpads, retain Requested twenty, Allocated twelve and Collected ten. Add a factual note about the two remaining items and decide whether they are still held or released for another request.
A cancellation needs the same care. Canceling a collection plan does not automatically release supplies in a separate inventory system. The coordinator must reconcile the actual commitment. Keep any food, medical or otherwise regulated distribution outside this generic materials example unless the organization has an appropriate separate process.
Test the process with fictional partners
Walk through a full allocation, partial allocation, duplicate request, unavailable item, substitution, missed collection and short handoff. Inspect the public form and expanded catalog records for internal information. Check that staff can find allocated requests with no agreed collection and completed plans with missing actual quantities.
These are recommended checks rather than tests performed for this article. This workflow fits organizations that need a clear demand-and-allocation trail while retaining human coordination. Its value is knowing what was requested, what staff promised and what changed hands, without presenting a simple request form as a live inventory guarantee.


