The Power of Consistent Documentation and Equitable Application of Policies and Procedures
Consistent, Equitable Accountability (and Great Documentation) Is Your Best Lawsuit Insurance
How clear standards, uniform enforcement, and contemporaneous records help reduce risk in employment disputes—including FMLA claims
When an employment claim shows up—whether it’s about leave, performance, discipline, accommodation, or termination—the outcome often turns on two questions: Were expectations clear and applied consistently? and Can the organization prove it? That’s why consistent, equitable accountability paired with strong documentation is more than good management—it’s a practical form of legal risk control.
Why Consistent Accountability and Documentation Matter in Employment Disputes.
Consistency reduces “pretext” arguments. Many claims hinge on whether the stated reason for an action (discipline, layoff selection, termination) was the real reason. When the same standards are applied the same way, it’s harder to argue the decision was a cover for unlawful motives.
Equity makes comparators less compelling. Plaintiffs often point to “similarly situated” employees who were treated better. Documented, objective differences—role requirements, prior discipline, attendance patterns, business needs—help explain why situations were not actually comparable.
Contemporaneous records beat reconstructed memories. A timeline, emails, attendance logs, and signed acknowledgements created at the time of events generally carry more weight than after-the-fact explanations.
Clear processes prevent technical violations. With leave laws like the FMLA, disputes often arise from notice, certification, and call-in procedures. A documented process (and proof it was followed) helps avoid “we didn’t know” and “you didn’t tell me” stalemates.
Five Recent FMLA Case Lessons: Documentation and Uniform Enforcement Win
The cases below illustrate a repeating pattern: employers have a far stronger defense when they can show (1) a legitimate business reason, (2) a consistently applied policy, and (3) records that back up both.
1. Lutz v. Mario Sinacola & Sons Excavating, Inc. The employer did not violate the FMLA by laying off an employee who was out on FMLA at the time, because she would have been laid off even if she was not out on FMLA. Also, an employer does not "replace" a laid off employer by distributing her former responsibilities among her colleagues. Thus, she has no comparators among the employees who were not laid off, who had never taken FMLA leave and who absorbed her former responsibilities.
2. Cerda v. Blue Cube Operations, LLC. The employer did not violate the FMLA by not offering it to an employee because she never sufficiently notified the company of her need for FMLA leave. She had only told a supervisor she planned to visit her father during lunch breaks, and casually mentioned to an HR employee she might explore "possibly getting FMLA," but never followed through.
3. Acker v. General Motors, LLC. The employer did not violate the FMLA by terminating an employee for failing to comply with its policy requiring notice of absences, even if the absences that the employee failed to report were protected by the FMLA. The FMLA allows employers to require employees to comply with the employer's usual and customary notice and procedural requirements for requesting leave, absent unusual circumstances.
4. Turner v. University of Louisiana. The employer did not violate the FMLA by requiring an employee to submit medical documentation to support each absence under its paid sick leave policy. The employee argued that this requirement was a veiled attempt to unlawfully require her to recertify her medical condition before taking each absence for purposes of the FMLA.
5. Caldwell v. KHOU-TV. The Fifth Circuit articulated the five-element prima facie burden employees must satisfy for FMLA interference claims, requiring her to demonstrate that (1) she was an eligible employee; (2) her employer was subject to FMLA requirements; (3) she was entitled to leave; (4) she gave proper notice of her intention to take FMLA leave; and (5) her employer denied her the benefits to which she was entitled. In this case, the employer did not violate the FMLA because the employee could not demonstrate all five elements. This framework has repeatedly been used to secure employer summary judgment when employees cannot satisfy all elements.
What These Cases Mean for Managers and HR: Practical Habits That Create Legal “Security”
1) Document the business reason—especially for layoffs and role changes
In Lutz, the employer prevailed because it could show the employee would have been laid off regardless of FMLA leave—and that distributing duties among remaining staff is not the same as “replacing” a laid-off worker. The litigation lesson: when decisions impact someone on protected leave (or in another protected status), you want a clean, well-supported record of the objective criteria and business drivers.
Selection criteria and scoring (if used), kept consistent across the affected group
Org charts before/after and a brief rationale for restructuring
Budget/workload data supporting the reduction
A short memo capturing who made the decision, when, and what information was reviewed
2) Set clear notice requirements—and document the notice you received (or didn’t)
Cerda highlights a common failure point: informal, vague conversations that never become a formal request. Employers can’t respond to what they don’t know, and employees can’t later claim they “clearly asked” when the record shows otherwise. Your safest approach is to make the pathway to request leave obvious—and to memorialize what was said, by whom, and when.
Train supervisors to route any “I need time off for a medical/family issue” comment to HR the same day
Use a simple intake template: date, who reported, what was requested, expected dates, and next steps provided
Confirm in writing what the employee is (and is not yet) requesting, along with how to complete the request
3) Enforce “usual and customary” procedures uniformly—even when leave may be protected
In Acker, the employer’s defense succeeded because it consistently required employees to follow its call-in/absence reporting procedures. The takeaway is not “be rigid”; it’s “be predictable.” When procedures exist, apply them consistently and document exceptions as true exceptions (e.g., “unusual circumstances”), not as ad hoc favors that later look like unequal treatment.
Keep the same standard for everyone: who to notify, by when, and what information is required
Log absences and call-ins consistently (a simple spreadsheet or HRIS notes can be enough)
If you grant an exception, document the reason and the specific dates it applied
4) Keep medical documentation requests tied to policy—and apply them consistently
Turner is a reminder that documentation requests can be lawful and still become a flashpoint if they look targeted. The safer practice is to have a clear policy (e.g., what documentation is required for paid sick leave, what the timelines are, and who reviews it) and to apply that policy the same way across employees and departments.
Centralize sensitive documentation handling (limit access; keep medical info separate from personnel files)
Use standard forms and standard timelines
Document what you requested, when you requested it, what you received, and what decision was made
5) Build the record to defeat the claim elements—not just to “have notes”
Caldwell lays out what an employee must prove in an FMLA interference claim, including eligibility, entitlement, proper notice, and denial of benefits. A strong documentation culture helps you address each point directly: eligibility records, leave policies, notice intake notes, approvals/denials with reasons, and communications showing the employee was offered the process.
A Simple Accountability + Documentation Checklist (Use This Before Problems Escalate)
Standards: Are expectations written, role-specific, and communicated (policies, job descriptions, performance standards)?
Consistency: Are similar issues handled in similar ways across teams? If not, is the difference documented and legitimate?
Timeliness: Are coaching conversations and corrective actions documented close to when they occurred?
Specifics: Do notes capture dates, examples, impacts, and the expectation going forward (not labels like “bad attitude”)?
Follow-through: Is there a documented improvement plan or next checkpoint?
Leave/attendance process: Do employees know how to report absences and request leave, and do managers route potential leave triggers to HR?
Confidentiality: Is medical information handled separately and only by those who need to know?
Bottom Line
Consistent, equitable accountability creates a workplace where expectations are clear and decisions are predictable. Documentation turns that consistency into proof. Together, they don’t just improve performance management—they provide real security when an employment dispute arises, because you can show what happened, why it happened, and that you treated people fairly along the way.
For more information you can reach out to Tanzi Cannon at General Counsel by Cannon, PLLC. at t.cannon@gcbycannon.com, 413-369-9220 or go to www.GCbyCannon.com.
This material is provided for informational purposes only. It is not intended to constitute legal advice, nor does it create a client-lawyer relationship between General Counsel by Cannon and any recipient. Recipients should consult with counsel before taking any actions based on the information contained within this material.
This material may be considered attorney advertising in some jurisdictions.