Skip to main content

When patrons misbehave: 10 guidelines

One of the surprisingly popular talks I've been giving (most recently, this morning in Rapid City SD) is about public library policies. I don't focus on particular wording, or even a checklist (although such checklists do exist, like this excellent one from the Colorado State Library). Instead, I focus on the general orientation that boards and staff should take when confronted with the inevitable issue of patrons behaving badly.

Although it will come as a surprise to some, the best response to trouble isn't always to create a new policy so that stern librarians can ensure it never happens again. I propose a set of guidelines, instead. They are:
  1. Begin with general policy guidelines. Start with ALA's Library Bill of Rights, one of our clearest statements of professional purpose.
  2. Use your best judgment. No matter how thorough your policies may be, there will be surprises. Remember the mission and values of the institution, and do your best.
  3. Presume innocence and good intentions. Most people are wonderful.
  4. Treat everyone with respect: eye contact, smile, handshake - but don't touch when they are upset.
  5. Model appropriate behavior: speak quietly and courteously.
  6. Set sensible boundaries and state them clearly when necessary. When wild things happen, sometimes it just never occurs to people that they're out of line. So tell them: "Sir, you are speaking very loudly, and other people are having trouble working."
  7. Know when to make an exception. Most of the time, the rules are reasonable, and people follow them. But sometimes, people are in various kinds of trouble, and holding to the rules is actually bad service. That's why libraries hire smart people: to discern the difference between usual and unusual, and make a good call.
  8. Look out for each other. Buddy up, whether it's to extricate one another from awkward situations (someone monopolyzing or creeping out a librarian) or perilous ones (walking out into dark parking lots).
  9. Holler for help when you need it. When you feel that your safety, or public safety, is threatened, you're not a SWAT team officer or superhero. Call 911. That's just knowing your own boundaries.
  10. Review policies after an incident. Was it a one-off event, or a trend? Every problem doesn't need a policy. Most situations don't. But reviewing an incident while it's fresh helps to clarify what steps might have been taken to make things better.
What policy guidelines would YOU add to the list?

Comments

Belly said…
The link to the checklist is forbidden. Any way to get it another way?
Jamie LaRue said…
Sorry about that. I think I fixed it. Should be here:

http://www.cde.state.co.us/sites/default/files/documents/cdelib/librarydevelopment/publiclibraries/download/pdf/policieschecklist_2012.pdf
Unknown said…
This list is very succinct and well worded. Thank you, C

Popular posts from this blog

Uncle Bobby's Wedding

Recently, a library patron challenged (urged a reconsideration of the ownership or placement of) a book called "Uncle Bobby's Wedding." Honestly, I hadn't even heard of it until that complaint. But I did read the book, and responded to the patron, who challenged the item through email and requested that I respond online (not via snail-mail) about her concerns. I suspect the book will get a lot of challenges in 2008-2009. So I offer my response, purging the patron's name, for other librarians. Uncle Bobby's wedding June 27, 2008 Dear Ms. Patron: Thank you for working with my assistant to allow me to fit your concerns about “Uncle Bobby's Wedding,” by Sarah S. Brannen, into our “reconsideration” process. I have been assured that you have received and viewed our relevant policies: the Library Bill of Rights, the Freedom to Read, Free Access to Libraries for Minors, the Freedom to View, and our Reconsideration Policy. The intent of providing all tha

Installing Linux on a 2011 Macbook Pro

I had two MacBook Pros, both 13" models from late 2011. One had 4 gigs of RAM, and the other 8. Both of them were intolerably slow. In the first case, I wound up installing CleanMyMac , which did arcane things to various files, and put up alerts to warn me about disappearing memory. But it made the machine useable again, albeit not exactly speedy. I changed some habits: Safari as browser rather than Firefox or Chrome. I tried to keep tabs down to four or five. The second Mac had bigger problems. Its charger was shot, but even with that replaced, the battery tapped out at 75%. More importantly, the whole disk had been wiped, which meant that it wouldn't boot. Recently, I had downloaded a couple of Linux distributions ("distros") on USB drives. Elementary OS 5.1 (Hera) was reputed to be a lightweight, beautiful distro that shared some aesthetics with the Mac OS. So I thought I'd give it a try. Ahead of time, I tried to read up on how difficult it might be to

The enemies of literature

Every year, apologists for the restriction of reading stumble over themselves to "mock" Banned Books Week. Walther (Oct 1, 2023's " The Enemies of Literature ") upholds the grand tradition. Complaints about banning, the argument goes, are simply false. Walther writes, "In zero cases since the advent of Banned Books Week has a local or state ordinance been passed in this country that forbids the sale or general possession of any of the books in question." Yet Texas HB 900 was passed on June 13 of this year. It requires book vendors to assign ratings to books based only on the presence of depictions or references to sex. If a book is "sexually explicit" and has no direct connection to required curriculum, it must be pulled from the school. (One wonders what happens to the Bible, and its story of Lot's daughters, first offered by their father for gang rape, and whom he later sleeps with.) In Arkansas, legislation stated that school and pu