Library Material Reconsideration (Book Challenge) Form

This form is used when a patron formally requests that a library review a book, film, audiobook, or other item in the collection. It captures the item details, the specific concern, and the action the patron is requesting so staff can route the challenge consistently. It is not meant for general feedback or informal complaints.

It works for print books, e-books, audiobooks, DVDs, and other library-owned materials as long as the item can be identified in the catalog. The Material Details section includes format, publication year, and library location so staff can find the exact item. If your library only reviews certain formats, you can narrow the field options with validation or conditional logic.

A patron, parent, guardian, or authorized representative typically completes the submission, depending on your library policy. The form should then be reviewed by the designated collection manager, branch manager, or reconsideration committee. If your process includes an intake coordinator, this form gives them the fields needed to log the request and preserve an audit trail.

Use it whenever someone wants a formal review of library material, not just when a complaint escalates. A single form should represent one challenged item or one clearly related set of items, depending on your policy. If a patron has multiple unrelated concerns, separate submissions are usually easier to track and review.

Collect only the PII you need to contact the requester and document the review. Avoid asking for unnecessary identifiers, sensitive personal history, or extra narrative that does not affect the reconsideration process. If your library allows anonymous submission for initial feedback, keep that separate from the formal challenge workflow and make the distinction clear.

It prompts for the specific passages or content at issue, the concern category, and the requested resolution, which keeps the review focused on the material rather than the person submitting it. That structure helps staff compare requests consistently and reduces vague or incomplete complaints. It also supports a written record of what was asked and what happens next.

Yes. Most libraries tailor the concern_category and requested_action fields to match local policy, such as age appropriateness, language, accuracy, or religious viewpoint. Using controlled options improves data quality, while an 'other' field preserves flexibility for unusual cases.

This form pairs well with ticketing, case management, and document storage tools so the submission, supporting documents, and final decision stay together. If your library uses a help desk or records system, map the fields to a case ID and add an audit trail for each status change. You can also route submissions by branch or collection type using conditional logic.

Common mistakes include making every field required, failing to explain what happens after submission, and collecting too much personal information. Another issue is using a free-text field where a date picker, multi-select, or dropdown would be more accurate and easier to review. A short staff workflow and a clear patron notice help avoid confusion during rollout.