How to map a food bank operation

How to map a food bank operation: draw the stock check, the no-show branch and the restock loop first, then the roles. Live example from visit list to closed session.

A food bank session looks like a line from booking to parcel, but it has branches that decide whether a household leaves with food. Draw the diet check, the stock check and the no-show first, and the roles follow.

The short version

  • Map the decisions and label every branch before you assign roles.
  • Show the no-show as its own branch: hold, contact, return to stock.
  • Draw the check and repack loop so a mismatch has somewhere to go.
  • End every session with a record and a restock request.
  • Put the roles in lanes last and read the handoffs.

Branches first, roles second

Most charts of a food bank start with the people: clients, coordinators, packing volunteers and a shift lead. That gives a tidy set of lanes and little insight. The questions that matter on the day are about what can go wrong. Does this household have a dietary need? Is everything on the pick list in stock? Does the packed parcel match the list? Did the client arrive before the session ended? Each is a decision with more than one exit, and the operation is the sum of those exits.

Two parts are easy to leave out. The first is the no-show. A parcel that is packed and never collected is neither finished nor wasted yet: it is held for a short time, the client is contacted, and the items return to stock with a note of the missed visit. The second is the restock loop. Every session ends by recording what went out and sending a request for the items that ran low, and that request feeds the next donation intake. A chart that stops at the hand-over hides the work that keeps the next session possible.

So map in this order. List the decisions and label every branch. Draw the check-and-repack loop before the parcel leaves the packing table. Add the no-show path and the return to stock. Then close the session with the record and the restock request. Only then put the steps into lanes, so each handoff between client, coordinator, volunteer and shift lead shows as a lane crossing you can look at.

The example below is a parcel packing and distribution process in QueryChart, built in five stages. It is an illustration of structure. Your own food safety rules, safeguarding duties and eligibility criteria come from your organisation and the law where you operate, so put them in the labels and comments yourself.

From visit list to a closed session

A food bank parcel process with a diet check, a stock check, a no-show branch and a restock request.

  1. The visit list and the diet check

    The session starts from the printed visit list. Each booking is checked for household size and dietary needs, and the first decision asks whether a special diet or allergy is noted. The two answers lead to different picking steps, which is why the decision comes before any packing.

  2. Picking and the stock check

    A flagged parcel is picked with suitable items and a standard parcel is picked for the household size. Both paths meet at a second decision that asks whether everything on the pick list is in stock. If not, an equal item is substituted or the shortfall is noted, and the chart rejoins the main path.

  3. Pack, check and repack

    The parcel is packed and labelled, then a second volunteer checks it against the list and the dates. A mismatch sends the parcel to be corrected and repacked, and the line returns to the same check. That loop is what keeps an error from reaching the client, and the passing branch stages the parcel for hand-over.

  4. The no-show branch

    A decision asks whether the client arrived before the session ended. Yes leads to the hand-over and a chance to ask for more help. No leads to a short hold, a contact attempt and the return of unclaimed items to stock with the no-show noted. Both paths then meet again at the record.

  5. Restock and the roles

    The visit and parcel number are recorded and a restock request goes out for low items, which ends the session. With the branches fixed, the lanes for client, booking coordinator, packing volunteer and shift lead show where each handoff happens and where parcels wait.

How it works

  1. List every decision

    Write down each point where the outcome can differ: special diet or not, everything in stock or not, parcel checked or not, client arrived or not. Add each as a decision in QueryChart with labelled branches, before any lanes exist.

  2. Draw the main path to a hand-over

    Connect the steps from visit list to hand-over using the yes branches. Keep it short and plain so you can read the spine in one pass, with the exceptions hanging off it.

  3. Draw the check and repack loop

    Add the second volunteer check as a decision and send the no branch to a correction step that returns to the same check.

  4. Add the no-show branch

    From the arrival decision, draw the hold, the contact attempt and the return to stock. Put your own hold period in a comment, taken from your session rules.

  5. Close with a record and a restock request

    Join the hand-over path and the no-show path at one record step, then add the restock request as the last action before the end.

  6. Assign lanes and read the handoffs

    Move the steps into lanes for the client, the coordinator, the packers and the shift lead. Each lane crossing is a place where a parcel can wait, so look at those first.

Mistakes to avoid

  • Stopping at the hand-over

    The session is not over until the visit is recorded and low stock is requested. Draw the close.

  • Leaving out the no-show

    Uncollected parcels are routine. Show where they are held and where the items go afterwards.

  • A check with no way back

    A second check that can only pass is decoration. Give the failing branch a correction step and a return.

  • Starting with the lanes

    Lanes first gives a picture of who is in the room. Decisions first gives a picture of what happens to a parcel.

Map your own food bank session

Open the parcel packing example as your own chart, change the checks and the hold step to match your session rules, and then assign the lanes.

Map your own food bank session

Related guides

Frequently asked questions

What is the first thing to draw when mapping a food bank?

The decisions. List the points where a parcel can take a different route and draw each with labelled branches. Roles can be added as lanes afterwards without changing the logic.

How do I show a client who does not arrive?

As a branch from the arrival decision. The no leads to a short hold, a contact attempt and the return of the items to stock, and then joins the same record step as the hand-over.

Where do I go next after the parcel process?

Follow the stock upstream and the client before. Read /templates/food-bank-donation-intake-process for how items arrive, /templates/food-bank-client-registration-and-referral-process for how a household joins, and /templates/food-bank-stock-rotation-and-expiry-process for how stock is kept in date. For the people who run the sessions read /guides/how-to-map-a-volunteer-journey.

Is this chart food safety or safeguarding guidance?

No. It shows the structure of a session. Food safety rules, eligibility criteria and safeguarding duties are set by your organisation and the law where you operate, and belong in your labels and comments.

The template behind this guide

Food bank parcel packing and distribution process flowchart — Food bank parcel packing and distribution process flowchart: pick against dietary needs, pack and double-check, hand over, handle no-shows and send restock requests.