Build an operating trail for every in-kind donation

Track an in-kind donation as an open item with a donor, a specific use, a current owner, and a final disposition. Do not close the record when the goods reach your door. Close it when your team can show what arrived, where it went, and whether the donor acknowledgment was completed.

That is the practical center of in-kind donation tracking: the item needs an operating trail, while finance and the donor handle their own valuation and tax questions.

Decide whether the item has a real use

An offer is not yet a received gift. Before accepting donated goods, name the program or event that can use them and the person responsible for the next step.

Record these facts while the offer is still easy to decline or redirect:

• donor or company offering the goods;
• plain description, quantity, and known condition;
• proposed use and the team that requested it;
• delivery method, date, and storage requirement;
• restrictions, expiration dates, or special handling;
• staff owner and acceptance decision.

Accept when the item has a useful destination and your team can receive, store, and use it. If nobody owns the next action, keep the offer open or decline it. Free goods that create an unplanned storage, repair, or disposal job are not operationally free.

Unusual property needs an exception path. Current IRS guidance for charities receiving donated property says reporting requirements can depend on the type of property, the claimed value, and how the charity uses it. Route vehicles, securities, high-value property, and anything with unclear restrictions to a qualified finance or legal adviser before acceptance. This article does not decide those cases.

Create one item record when custody changes

Acceptance says yes to an offer. Receipt proves that the goods arrived. Keep those events separate so a promised pallet does not appear as inventory and an unexpected delivery does not disappear from donor history.

At receipt, add the date and location, the person who accepted custody, the observed quantity and condition, and a stable item or batch ID. Group interchangeable goods at the level your team will actually distribute or report. Twenty unopened winter coats may be one batch. A donated laptop with its own serial number, condition, and assigned user needs its own item record.

The National Forest Foundation's in-kind tracking tool connects internal tracking with donor acknowledgment, project or grant reporting, and planning for resources an organization might otherwise have to purchase. The useful lesson is not a universal spreadsheet layout. It is that someone must compile the records and connect each contribution to the work it supports.

If your team already uses a standard gift intake process, add the item record to that handoff instead of inventing a separate inbox. The gift-processing intake workflow shows how money facts and donor context can travel through separate review lanes without losing one stable identifier.

Keep four facts separate

One in-kind donation can touch several systems, but each system answers a different question:

1. Donor record: Who gave or arranged the goods, and who should receive follow-up?
2. Item record: What arrived, in what quantity and condition, and where is it now?
3. Finance record: What accounting treatment, if any, did the qualified finance owner apply?
4. Acknowledgment record: What message was sent, to whom, and when?

Do not make the acknowledgment carry the inventory record or make a donor-entered estimate become your internal finance decision. For United States federal substantiation, IRS Publication 526 explains that a written acknowledgment for donated property includes a description of the property and does not necessarily include its value. Your organization's adviser should determine the language and process appropriate to the gift.

This separation also keeps corrections small. A quantity correction changes the item record. A new storage location changes custody. A finance adjustment stays with finance. A resent letter changes the acknowledgment history. None of those edits should erase the original offer or receipt event.

Move the item through observable states

Use states that a busy operator can prove from the record:

• Offered: the donor proposed the gift; acceptance is undecided.
• Accepted: a use, owner, and delivery plan are assigned.
• Received: custody, quantity, condition, and location are recorded.
• In use: the item is assigned to a program, event, person, or site.
• Closed: use, distribution, return, sale, transfer, or disposal is recorded, and donor communication is complete.

A state should change only when evidence changes. An email promising delivery can support “accepted,” but not “received.” A storage-room photo can support custody, but not final use. A thank-you message can close acknowledgment while the item itself remains open.

For auction donations, the closeout point is different: the item must become a usable lot before bidding and later pass through checkout. Use the separate auction-item readiness workflow for that path.

Review exceptions instead of recounting everything

Run a short weekly review of open in-kind records. Look only for accepted items not received, received items with no current owner or location, acknowledgment tasks still open, and items whose expected use date has passed.

Take the winter-coat batch as a sample. The record starts with the company's offer, then captures 20 coats received at the program office, a staff owner, and the planned distribution. If 16 are distributed and four move to storage, record both outcomes. The batch stays open until the remaining four have a new use or documented disposition and the donor message is complete.

That sample is the pass condition. Your team should be able to start with the donor, find the item, name its current owner and location, and explain its outcome without reconstructing the story from email.