DOCUMENTATION & PROOF
How to Save, Organize, and Protect Important Work Records
This page explains simple, practical ways to save work-related records in case you need them later.
Documentation is not about escalation.
It is about accuracy, memory, and protection.
You do not need permission to document.
WHAT IS WORTH SAVING
It is generally helpful to save:
- Emails related to attendance, leave, discipline, or policy changes
- Instructions that conflict or change
- Denials or approvals
- Meeting notices or summaries
- Screenshots of systems or errors
- Medical or leave-related communications
If it affects your job, your pay, or your rights, it is worth saving.
HOW TO SAVE EMAILS (OUTLOOK)
If you receive an important email, do not rely on it staying in your inbox.
Emails can be deleted, altered, or become inaccessible.
- Recommended options include:
- Saving the email as a PDF
- Printing to PDF and naming the file clearly
- Saving entire email threads when possible
Screenshots are acceptable for short messages, but long threads are easier to review as PDFs.
NAMING FILES SO THEY MAKE SENSE LATER
Use clear, neutral file names.
A simple format works best:
Date – Topic – From/To
Example:
2026-01-15 Attendance Follow-Up Email – Supervisor Name.pdf
Avoid emotional language in file names.
KEEPING THINGS ORGANIZED
Use one folder for work-related records.
- Inside it, consider subfolders such as:
- Attendance
- Leave / FML / Disability
- Work Comp
- Discipline or Meetings
- General Communications
Consistency matters more than perfection.
WHAT NOT TO DO
- Do not edit or alter documents.
- Do not add commentary inside saved files.
- Do not store records on shared work devices if possible.
Documentation should preserve what happened, not reinterpret it.
SIMPLE LOG TEMPLATE (OPTIONAL)
Keeping a basic log can help when events blur together.
- A log can include:
- Date
- What happened
- Who was involved
- How it was communicated
Short, factual entries are best.
WHY THIS MATTERS
Most disputes are not about one event — they are about patterns.
- Documentation helps show:
- Timing
- Consistency (or lack of it)
- Changes in expectations
- System issues
You do not need to know whether you will ever need it.
Saving it early is easier than trying to recreate it later.
FINAL REMINDER
Documentation is not retaliation.
It is not insubordination.
It is not overreacting.
It is a reasonable step to protect yourself.
EVS LIVES MATTER 