Collection Weeding (Deselection) Record

This template records why a library item was selected for weeding, what evidence supported the decision, and what happened to the item afterward. It is designed for collection development records, not for patron-facing notices or inventory tracking. Use it to create a clear audit trail for deselection decisions.

Typically, a collection development librarian, branch manager, or designated selector completes the form, with review by an approver if your policy requires it. The person filling it out should know the item’s usage history, condition, and collection fit. If multiple staff contribute, one person should own the final submission to avoid conflicting entries.

Use it whenever an item is removed from the collection, whether the review happens on a rolling basis, during a scheduled weeding cycle, or as part of a subject-area review. Many libraries use one record per item or per small batch, depending on local policy. The key is consistency so decisions can be compared over time.

It works for print books, media, reference materials, and other circulating or noncirculating collection items if your policy allows deselection. The item_identifier and format fields help distinguish between editions, copies, and media types. If you manage special collections, you may need a separate workflow with stricter review steps.

List the specific criteria used, such as low circulation, outdated information, poor physical condition, duplication, or lack of relevance to the current collection profile. Avoid vague phrases like "old" or "unused" without supporting detail. The goal is to show that the decision followed policy, not preference.

The approval and attestation section creates a documented review trail that supports internal governance and collection policy enforcement. It also helps demonstrate that deselection decisions were based on stated criteria rather than arbitrary removal. If your institution has retention or public-record obligations, keep the completed records according to your records schedule.

Yes. You can add branch-specific fields, subject headings, or local policy references, but keep the core fields intact so records stay comparable. If one branch uses different disposition options or approval paths, use conditional logic rather than overloading the form with every possible field.

If possible, yes, because item identifiers and circulation data are easier to verify when the form is linked to your catalog or ILS. Integration can reduce manual entry and lower the risk of mismatched identifiers. Even without integration, the template should capture enough detail to reconcile the record later.

A common mistake is recording only the final disposition and skipping the reason for deselection. Another is using free-text notes for fields that should be structured, such as format or approval date. The form works best when it captures the decision path, not just the outcome.