Batch 5 hygiene note, 2026-05-17: Complete historical bereavement correction. The live Knowledge Center article was verified with bereavement carved out from PTO. Optional future work is a standalone bereavement policy only if firm terms are later defined. Indexed in the SAIL Knowledge Base Hygiene Hub - 2026-05-12.
Correct the live Litify Knowledge Center Attendance, PTO, and Scheduling Policy after Sam clarified that bereavement pay is separate from PTO and does not reduce PTO.
I re-read the live policy article from LITIFY_ORG, then searched the live Knowledge Center for bereavement references. Salesforce does not allow filtering Body__c directly in SOQL, so I pulled the relevant policy set and then a broader Knowledge Center export locally. The full retrieved set found bereavement references only in Attendance, PTO, and Scheduling Policy and Guide - PTO Requests, OOO Calendar, and Unscheduled PTO; I did not find a standalone bereavement-day policy.
I updated the live policy so the PTO-first rule now explicitly covers medical leave, maternity or parental leave, other paid leave, unpaid leave, extended leave, approved leave programs, personal leave, and other non-working time away arrangements. Bereavement leave and workers' compensation remain carved out.
I added clear bereavement language: bereavement pay is separate from PTO and does not reduce the employee's PTO balance. Unless management approves a specific number of paid bereavement days in writing, the amount of paid bereavement time is situation-specific and determined by firm management.
I also revised the six-week example so it now refers to approved paid medical leave, maternity or parental leave, or other paid leave, avoiding any accidental implication that bereavement is part of the PTO-first example.
REST PATCH returned HTTP/1.1 204. A post-update SOQL read confirmed the article remains Published, LastModifiedDate = 2026-05-12T22:12:04.000+0000, LastModifiedBy = Sam Aguiar, and the body contains maternity or parental leave, Bereavement pay is separate from PTO, situation-specific, and the revised six-week paid medical or parental leave example. A local HTML balance check confirmed matching p, ul, li, and ol tag counts in the updated body.
Rollback package: /Users/samaguiar/Documents/Projects/admin/backups/litify-knowledge-pto-policy-bereavement-correction-20260512T181148/
Key files are current-record.json, old-body.html, new-body.html, update-payload.json, rollback-payload.json, and post-update-record.json. The rollback path is a Salesforce REST PATCH using rollback-payload.json against /services/data/v66.0/sobjects/Knowledge__c/a5mUV0000004ly1YAA.
Session log: /Users/samaguiar/Documents/Projects/admin/session_logs/litify-pto-policy-bereavement-correction-2026-05-12.md
QA queue mirror: /Users/samaguiar/Documents/Codex/_qa-queue/2026-05-12.md
The clarification has been applied live and verified. No Litify blocker remains for this correction.
If Sam wants HR policy cleanup to continue, a future agent can decide whether the PTO request guide should be lightly clarified so it still says calendar entries should show OOO, while bereavement pay itself does not reduce PTO. A future agent could also draft a standalone bereavement policy if Sam later wants fixed paid-day numbers.