Patron Code of Conduct Incident Report (Library)

Use it for conduct issues that affect safety, access, or service delivery, such as disruptive behavior, harassment, refusal to follow rules, property damage, or threats. It is also useful when staff need to document a warning, escort, or temporary restriction of privileges. If the event is only a routine service complaint, a lighter intake form may be enough.

The staff member who observed the incident or the supervisor who handled the response should complete it as soon as practical. If multiple staff were involved, one person should consolidate the facts and attach witness details. The goal is a consistent record with clear fields, not a narrative written from memory days later.

Use it every time a patron conduct issue requires staff intervention, a witness statement, evidence capture, or a restriction decision. Consistent use matters because repeated low-level incidents can show a pattern that single notes miss. If your library has a separate security log, this form can complement it rather than replace it.

This template includes an anonymous submission option for cases where the reporter is a patron or community member and wants to avoid identifying themselves. For staff-created records, anonymous submission is usually not appropriate because the library needs an audit trail and follow-up contact. If anonymity is enabled, make sure the form explains what information will still be collected and how it will be used.

Collect only what you need to identify the person and document the event, using the minimum-necessary principle. If the patron is known, a library card number or internal identifier is usually better than asking for extra PII. If the patron is unknown, use a description field and avoid collecting sensitive details that do not help staff follow up.

The form should use clear labels, required-versus-optional markers, and field types that match the data, such as date pickers and multi-selects. If the incident involves a patron requesting an accommodation or a disability-related interaction, staff should document only the relevant facts and avoid assumptions. Progressive disclosure helps keep the form usable for staff under pressure.

The submission notice should tell the user whether the report goes to a supervisor, security lead, or branch manager, and whether a follow-up review will occur. That confirmation line reduces uncertainty and helps staff know when to escalate. If the report triggers a restriction, the follow-up section should capture who reviews it and what next step is required.

You can adjust the incident categories, restriction types, and follow-up fields to match your code of conduct and local procedures. Some libraries add fields for youth patrons, after-hours incidents, or banned-item rules, while others keep the form shorter for front-desk use. Keep the core structure intact so staff can still document date, location, response, witnesses, and outcome consistently.

Ad-hoc notes often miss key facts like time, location, witness names, or whether de-escalation was attempted. A structured template creates a cleaner audit trail, makes review easier, and supports more consistent privilege decisions. It also reduces the chance that staff collect unnecessary PII or skip important follow-up details.