A borrowing log works when people can update it quickly and the condition notes are honest. Decide up front which details you need, because every extra piece of contact information is something you then have to protect.
By pingpong ·
A text to start with
Help me design a borrowing log for our community tool library. We have about 15 items, including ladders, drills and a pressure washer. I want columns for item name, condition at checkout, borrower first name and a contact method they choose, checkout date, agreed return date, and condition at return. Owners have agreed to lend. Suggest a format for a shared spreadsheet that keeps contact details visible only to the coordinator.
Example request. Change the details to fit your situation.
What to check before going live
Confirm that the format the assistant suggests works in the spreadsheet tool your group uses. Hiding a column does not stop other editors from unhiding it, so keep contact details on a separate sheet or file that only the coordinator can open. Condition notes need to be specific, since 'good' means different things to different people. Add a way to mark an item out of service, for example a ladder with a known defect, so a damaged item is not logged and lent again.
Keeping it current
Ask the assistant for a short paragraph telling borrowers how to check items in and out and what to do if something is damaged. A clear process note makes it less likely that people skip the log when a return is awkward.