Library Overdue Fine Waiver Support Workflow Builder

You are a library patron support lead building a fair and empathetic workflow for overdue fine waiver requests.

Library type: [public library, school library, university library, special library, consortium branch]
Policy context: [fine-free library, partial fines, lost item fees, damaged item fees, hardship waiver, amnesty period]
Patron type: [adult, student, caregiver, teacher, senior, visitor, cardholder from partner branch]
Request channel: [front desk, phone, email, chat, online form]
Situation details: [late return, lost item found, illness, transportation issue, billing confusion, returned to wrong branch, disaster hardship]
Account status: [items returned, still missing, damaged, billed, collections hold, blocked account, unknown]
Staff authority: [can waive up to amount, supervisor approval, circulation manager, no waiver allowed]
Documentation needs: [reason code, notes, receipt, photo, policy citation, privacy limits]
Equity and privacy concerns: [do not ask for sensitive proof, minors, disability, domestic hardship, language access]
Escalation rules: [large balance, repeated requests, damaged materials, aggressive behavior, policy exception]
Tone: [warm, concise, policy-grounded, de-escalating, multilingual plain language]

Create:
1. Intake checklist that gathers only necessary, privacy-respecting information.
2. Decision tree for waive, reduce, payment plan, replacement discussion, supervisor review, or denial.
3. Patron-facing response macros for approved waiver, partial waiver, more information needed, policy-bound denial, and escalation.
4. Staff notes template with neutral language and reason codes.
5. De-escalation script for upset patrons.
6. Accessibility and language-access considerations.
7. Boundaries for minors, sensitive hardship, damaged/lost materials, and inter-branch accounts.
8. Quality review checklist for consistency and equity.
9. Metrics to track: waiver volume, reasons, repeat contacts, blocked accounts resolved, and patron satisfaction.
10. Policy questions to confirm with library leadership before launch.

Do not invent legal requirements or override library policy. Keep recommendations policy-aware and privacy respectful.