Plan and prepare
Before asking for donated goods, identify who will use them, where they will be stored, and who can receive them. A request should solve a confirmed need rather than fill an empty room. Name a receiving coordinator and set a maximum quantity that the project can handle.
Publish a short list with item descriptions, acceptable condition, needed quantities, and delivery arrangements. Include a date and a way to check whether the request is still open. If the program cannot safely handle food, chemicals, damaged electronics, or other specialized goods, say so at the point of donation rather than after arrival.
Use a clear process
Ask donors to confirm large deliveries first. Record an expected arrival window and the space or equipment required. Do not publish a private volunteer's home address as a drop-off point without explicit agreement. Offer directions to an established organization when its program is better suited to the donation.
At receipt, count and inspect goods within the team's competence, then record accepted quantities and their storage location. Keep uncertain items separate pending a decision. A donation should not move directly into distribution simply because refusing it feels awkward. Use the program's established disposal or return arrangements when acceptance criteria are not met.
Worked example
Suppose a school-supply project needs one hundred unused notebooks but can store only that amount. The public list can show the required size, current quantity committed, delivery window, and remaining need. If a donor offers two hundred notebooks, the receiving coordinator should confirm what can be accepted and, if appropriate, suggest another organization that has agreed to receive the surplus. Accepting everything first and searching for a destination later transfers the burden of the donation to volunteers, storage space, and future recipients.
Decisions and exceptions
Use a simple commitment log before goods arrive. An entry might include the donor's chosen contact, item description, quantity offered, acceptance confirmation, expected arrival, and actual receipt. Keep donor details private while publishing only the remaining need. A pledged quantity should reduce the request temporarily only if the program is confident enough in the arrangement to rely on it. Establish a way to reopen the request if a delivery is canceled or missed, and tell the donor how to report that change without embarrassment.
Check and improve
At the end of the campaign, compare requested, received, usable, distributed, and remaining quantities. These numbers explain why a collection succeeded or created extra work. Ask whether the original request was precise enough and whether recipients could use the items as supplied. A notebook collection might also need accessible writing materials or different formats that the first request overlooked. Record those lessons before the next appeal. Thank donors accurately, describing what the program accomplished without implying that every received item was distributed or that a large donated volume necessarily met the most important need.
Solo and community application
Alone, use a needs list before collecting items for someone else and confirm they actually want the goods. In a community project, compare the receiving log with distributions each day the program operates. Assign someone to reduce or close public requests as soon as sufficient stock is committed.
Reference guidance
FEMA's donations training stresses planning solicitation, collection, prioritization, and distribution. The item-level workflow here applies those principles to a small project. After each campaign, review unused stock and volunteer time, then make the next request more precise. A smaller useful donation can contribute more than a large load that nobody can use.