Book requests arrive in the corridor and at the desk, and the same title is asked for again and again. I would rather give readers a link. Anyone can suggest a title, say who it is for and explain why. The librarian counts the repeats in one sheet.
The three parts of the form
About the book: title, author, series, format and a link to its page. This lets you find the exact edition.
About the reader: who it is for and what kind of book it is. This shows gaps in the shelves.
About the request: why the library should have it, whether a class needs it and whether the requester wants the first loan.
Who fills it and who reads it
Students, teachers and parents fill it from a link on the library page. The librarian reads the rows as JSON or CSV. A visitor's AI might ask: "What is the title and author?" Then "Who is it for?" Then "Why should the library have it?" It shows the answers and sends only after a yes. See agent-fillable forms and forms for schools.
A tip
Count repeats, and keep class requests in a separate pass because they have a deadline. Recruit shelf helpers with a volunteer application form, and run a reading trivia quiz when the new books arrive.
Questions
How do I spot a title that many people asked for?
Download the CSV and sort by book_title. Repeated titles sit together, so you can count them quickly and buy the most requested ones first.
Can a requester say the book is for class?
Yes. The needed_for_class box names the class or project, so you can handle urgent requests before general wish-list titles.
Does the requester hear when the book arrives?
No. The form sends nothing to them. If they left an email, use your usual library notice. The first-loan tick box shows who to tell first.