How to Keep a Pump-at-Work Documentation Log
August 21, 2026
If pumping at work is repeatedly delayed, interrupted or pushed into an unsuitable space, memory quickly turns into “it happened a lot.” A useful record needs dates, times and patterns.
The free PUMP Act Break & Space Evidence Log is a local-first shift ledger for exactly that purpose.
One row per pumping event
For each event, capture:
- date;
- shift;
- time you needed to pump;
- time the break actually started;
- waiting minutes;
- break duration;
- location;
- whether the location was a bathroom;
- whether it was shielded from view;
- whether it was free from intrusion;
- whether the space was available when needed;
- whether anyone interrupted the break;
- whether you had to continue working;
- who you notified afterward.
This creates objective patterns such as average wait time, number of interrupted breaks, or how often the designated room was unavailable.
Distinguish availability from privacy
These are different failures.
A room may be private but unavailable because another employee or meeting occupies it. Another room may be immediately available but subject to people entering without notice.
Do not collapse both into “room problem.” Separate fields make the record much more useful.
Record exact responses
When you report an issue, note:
- who received the report;
- method: in person, message, email, HR ticket;
- what you said;
- what response you received;
- promised fix;
- follow-up date;
- whether the problem repeated afterward.
This builds a second timeline: not only what happened, but what happened after the employer knew about it.
Keep supporting evidence carefully
Depending on what you lawfully possess, useful evidence may include:
- written schedules;
- emails or messages;
- written room policies;
- photos of a space when appropriate and lawful;
- HR responses;
- your own contemporaneous notes.
Avoid collecting private information about coworkers or recording conversations unlawfully. The goal is a clean personal work record, not surveillance.
Review the pattern weekly
A weekly summary can answer:
| Metric | Why useful |
|---|---|
| Events logged | Scale of record |
| Average waiting time | Access delays |
| Breaks interrupted | Continuity problem |
| Bathroom events | Space issue |
| Privacy failures | Intrusion pattern |
| Worked during break | Compensation/work-time context |
| Open follow-ups | Employer response gap |
The PUMP Act Evidence Log calculates these patterns so the user does not have to count them manually.
FAQ
Should I log normal successful pump breaks too?
Yes. A complete record is more informative than a file containing only bad events. It shows the denominator and can reveal whether a problem is isolated or systematic.
Can the log replace a complaint or legal filing?
No. It is evidence organization. Use the process and agency guidance that applies to your situation.
Where does the data go?
It stays on your device unless you choose to export it.
Use the PUMP Act Break & Space Evidence Log to turn “this keeps happening” into a dated, measurable record.