Public libraries · Staff readiness · Patron privacy

Libraries help people navigate change. The systems around them should too.

We support library systems on staff readiness, digital access and literacy, patron support and privacy, community workforce pathways, and program readiness. Delivery covers staff training and train-the-trainer sessions, responsible AI and public AI programming where it applies, consistent workflows across branches, and clear escalation so every shift and every location answers the same way.

Discuss library staff training 678.397.8411

Four people, including a woman in a plum hijab and a wheelchair user, reviewing an open book and tablet at a library table.

Staff readiness

Practical training for the work librarians already do.

Patron-facing boundaries

What staff can say, and where to escalate.

Digital access

Support that does not assume prior technology comfort.

Community pathways

Workforce and program support with measures.

What should library staff know before offering public AI programs?

Library staff need three things before a public AI program: a written boundary for what staff will and will not do with AI on a patron's behalf, a patron privacy rule that covers uploaded documents and personal details, and a response for inaccurate output. Staff readiness comes first. Public programming comes after.

Staff training is not public AI literacy programming

A patron class explains what the tools do. Staff training decides what a person at the desk is authorized to do when a patron asks for help with a résumé, a benefits form, an immigration document, or a medical question. Those are different sessions.

What library staff practice in session

Desk script, including the refusal case
Patron privacy
Verifying output
Referral and escalation
Documenting a decision
Branch consistency

Delivery, accessibility, and language

Content is educational and operational. It is not legal, clinical, or financial advice.

Delivery for a single branch
Single staff-day session for one branch or system, with a sponsor debrief for directors and branch-services leaders.
Delivery across a system
Multi-branch delivery with a shared boundary document, or train-the-trainer so internal staff repeat the program without ongoing external cost.
Accessibility and language
Materials are built with accessibility in mind, and bilingual English/Spanish delivery is available when included in scope.

Questions buyers ask

Direct answers

How can libraries protect patron privacy during AI assistance?

Keep patron documents and identifying details out of staff accounts and shared tools, help at the patron's own device where possible, and record nothing beyond what circulation policy already allows.

What should librarians tell patrons before they upload documents to an AI tool?

That anything uploaded may be retained by the vendor, that identifying details should be removed first, and that the library cannot guarantee the accuracy of the result.

How should libraries respond when AI produces inaccurate information?

Treat it as an unverified source. Say plainly that it may be wrong, verify against a known reference, and document the correction so other branches respond the same way.

What does responsible AI training for librarians include?

Approved tools, a desk script, patron privacy rules, verification practice, escalation paths, and one documented change per branch with an owner and a date.

Next step

Discuss staff-facing library support.

Bring the number of branches, the staff count, and the programming date you are working toward. We confirm format and fit in twenty minutes.

Discuss library staff training 678.397.8411 Contact page