Review PII Before OSHA 300/301 Submission
Find possible SSNs, email addresses, and phone numbers in narrative fields before uploading case data.
Why this happens
Free-text narratives can accidentally contain personal identifiers copied from incident reports, emails, or claim notes.
What you must verify yourself
These are workflow and human-review steps, not automatic RuleTally checks.
- Read incident_description and all four nar_ fields; pattern matching does not reliably detect names or addresses.
- A clean pattern scan is not proof that a narrative is free of personal identifiers.
- Preserve required template fields. Narrative cleanup does not mean deleting structured date_of_birth or date_of_hire fields.
How to fix it
- 01
Review every warning in context and manually read each narrative.
- 02
Remove unnecessary identifying details from narratives without changing the incident facts.
- 03
Keep your internal source record separately and do not email employee files to RuleTally.
- 04
Use OSHA’s current PII guidance and CSV template before submission.
Check the whole file locally.
RuleTally shows the row, field, expected format, and official source without uploading the employee file.
Open local preflight