ADA Medical Confidentiality in Return-to-Work: What Supervisors Can and Cannot See

The Moment the Line Gets Crossed

A warehouse supervisor walks into the RTW coordinator's office to ask about a worker coming back on light duty. "So what exactly is wrong with her?" It is a reasonable-sounding question from someone who is trying to run a shift. The coordinator, trying to be helpful, hands over the physician's progress note. In thirty seconds, a well-intentioned conversation has crossed a line the ADA draws explicitly — and the employer is now exposed.

This scenario plays out in facilities of every size, in every sector. It is not usually malicious. Supervisors want context. They want to understand why a task is restricted, whether the assignment is permanent, whether they need to plan for a replacement. Those are legitimate operational concerns. The problem is that the ADA gives supervisors access to a specific category of information — functional work restrictions and accommodations — and not to the underlying medical record that generated those restrictions.

Getting that distinction right is not a paperwork formality. It is a legal requirement with real exposure if it fails. This article explains exactly where the line sits, why it exists, how to structure your records and your conversations to stay on the right side of it, and what your supervisors actually need in order to manage a transitional duty assignment effectively.

---

What the ADA Actually Requires

Title I of the ADA governs employment-related medical information. When an employer collects medical information in connection with a reasonable-accommodation request or a return-to-work evaluation, the regulation is specific about how that information must be stored and who may access it.

Under 29 CFR 1630.14(c)(1), medical information must be collected on separate forms, maintained in a separate medical file, and kept apart from the standard personnel file. Access is restricted to personnel with a legitimate business need. (JAN, 2025)

That "legitimate business need" standard matters because it is not open-ended. The EEOC's guidance — confirmed in published informal discussion letters — draws a clear operational line: supervisors and managers may be told about an employee's work restrictions and necessary accommodations. They may not be told the diagnosis, the treatment plan, the prognosis, or the contents of the treating physician's notes. (EEOC via Gordon Feinblatt, 2024)

The regulation also applies to electronic records, not only paper files. A shared drive folder, a case-management system, or an email thread containing a physician's progress note carries the same confidentiality obligation as a locked file cabinet. (EEOC Informal Discussion Letter, 2011)

The practical implication: your RTW records need to be structured so that access to medical source documents is genuinely separate from access to the restriction summary a supervisor needs to make a duty assignment.

The line the ADA draws is functional, not diagnostic. Supervisors receive the what — "no lifting above shoulder height, maximum four hours on feet per shift" — not the why.

---

The Two Layers of Information in Every RTW Case

Every return-to-work case generates at least two distinct categories of information. Understanding the distinction is the first step toward maintaining it.

Layer 1 — Medical source documents. This includes the attending physician's progress notes, the medical-status report (the APF, work status report, or equivalent state form), any specialist consultation notes, imaging or diagnostic results, and any communications from the insurer's nurse case manager that reference clinical findings. This layer belongs in the separate medical file. Access is limited to the RTW coordinator, HR personnel with a specific program role, and — with appropriate authorization — the insurer and any designated medical reviewer.

Layer 2 — Functional restriction summary. This is the operational translation of Layer 1: a plain-English or plain-task description of what the worker may and may not do during the transitional period. It includes the restriction start date, the expected review date, and any conditions on hours or equipment. This layer is what reaches the supervisor.

The risk in most organizations is not that supervisors are intentionally raiding the medical file. It is that the two layers were never separated in the first place. If your RTW coordinator maintains a single binder or a single shared folder containing both the physician's note and the restriction summary, a supervisor asking an innocent question can end up looking at protected information before anyone realizes what happened.

Separation has to be structural, not just aspirational.

---

What a Supervisor Does and Does Not Need

One of the most effective ways to maintain the confidentiality line is to define, in advance, exactly what information a supervisor needs to manage a transitional duty assignment — and to issue only that information, in a standardized format, from the first day of the assignment.

Information category	Supervisor receives	Stays in medical file
Diagnosis or medical condition	✗ No	✓ Yes
Treatment plan or medications	✗ No	✓ Yes
Physician's progress notes	✗ No	✓ Yes
Functional restrictions (tasks, positions, weights)	✓ Yes	—
Hour or schedule limitations	✓ Yes	—
Equipment or environment restrictions	✓ Yes	—
Restriction start and review dates	✓ Yes	—
Approved transitional duty assignment	✓ Yes	—

The restriction summary the supervisor receives should come from the RTW coordinator, not directly from the physician's note. The coordinator reads the clinical document, extracts the operational parameters, and produces a standardized restriction summary — a one-page document that describes what the worker can do, what the worker cannot do, and when the restrictions are next scheduled for review. That is what the supervisor signs, keeps, and acts on.

This design accomplishes two things simultaneously. It gives the supervisor every piece of information needed to manage the assignment safely and legally. And it keeps clinical detail — which the supervisor has no need to see and no authority to interpret — inside the medical file where it belongs.

For a deeper look at how the supervisor's role fits into the broader transitional duty structure, see The Supervisor's Role in Transitional Duty.

---

Structuring Your Records for ADA Medical Confidentiality

Record separation is not optional, and it is not self-executing. It requires a deliberate file architecture and a clear access policy. Here is how to build both.

Separate file locations, not just separate folders. The medical file should not live inside the personnel file or inside the general RTW case folder that supervisors or payroll staff might access. If your files are physical, that means a locked cabinet accessible only to designated HR personnel. If your records are electronic, that means a directory or system with access controls that genuinely restrict who can open which documents — not just a naming convention that depends on everyone following the rules.

A defined access list. Put in writing which roles may access Layer 1 (medical source documents). Typically: the RTW coordinator, the HR director or designated HR manager, and any third-party administrator or insurer contact with a documented program relationship. The supervisor is not on this list. A payroll clerk is not on this list. The safety manager is on this list only if the role requires it for the specific case (e.g., evaluating environmental restrictions for a hazmat exposure injury).

A standardized restriction-summary document. The RTW coordinator should use a consistent, templated format to extract and communicate restrictions to the supervisor. The template should have fields for: worker name, assignment start date, restriction review date, approved tasks, restricted tasks, hour limitations, and supervisor acknowledgment signature. It should have no field for diagnosis, injury code, or medical provider name. The absence of those fields is a design feature.

Training for supervisors. Supervisors should be told — explicitly, in writing, as part of their RTW orientation — that they will receive a restriction summary, that the restriction summary is all they are authorized to receive, and that if a worker, physician, or insurer contact shares additional medical information with them verbally, they should route it to the RTW coordinator and not retain it. The training should also cover what to do if a worker volunteers their own diagnosis: acknowledge it neutrally, do not record it in any supervisor-held document, and log the conversation for the coordinator.

The return-to-work case management guide covers the full documentation lifecycle for a workers' comp RTW case, including how restriction documents flow between the medical file and the operational record.

---

Common Failure Points — and How to Close Them

Even organizations with a clear policy run into specific moments where the confidentiality boundary breaks down. Knowing where the failures concentrate makes them easier to prevent.

The physician's note goes directly to the supervisor. In some operations, especially smaller ones, the worker brings the physician's return-to-work note directly to their supervisor rather than to HR. The supervisor reads it, makes a duty decision, and files it in a desk drawer. The note contains diagnosis codes, clinical observations, and prescription information — none of which belongs outside the medical file. Fix: establish a written policy that all medical documentation from a treating provider goes to the RTW coordinator or HR, not to the supervisor, before any duty decision is made.

The restriction summary includes clinical language. A coordinator who pulls restriction language verbatim from a physician's note may inadvertently include diagnostic context. "Patient presents with L4-L5 herniation; restrict lifting to 10 lbs." The restriction (10 lbs) is appropriate for the supervisor. The clinical finding (L4-L5 herniation) is not. The summary should be rewritten in functional terms only.

Group communication exposes the record. A supervisor mentions an injured worker's restrictions in a team meeting to explain a staffing change. This is not necessarily an ADA violation by itself, but it becomes one if the supervisor discloses the underlying condition. Brief supervisors specifically: you may tell the team that a colleague has a temporary work restriction and is on modified duty. You may not name or describe the condition.

Electronic records without access controls. An RTW coordinator who manages cases in a shared spreadsheet or a shared drive folder accessible by all HR and supervisory staff has not separated the medical file — regardless of what the written policy says. The access control has to match the policy.

---

What This Means for Your RTW Documentation System

The ADA's medical confidentiality requirements are not uniquely burdensome — they map directly onto good case-management practice. A well-structured RTW system separates medical documents from operational documents by design, routes information to the people who need it and only to those people, and maintains an audit trail of who accessed what and when.

For organizations managing five or more active workers' comp cases at a time, informal processes — a shared binder, a coordinator who holds everything in their head, a supervisor who handles their own documentation — tend to break down. The access boundary gets blurry. A document lands in the wrong place. An accommodation conversation happens without a record. Any of those moments becomes an exposure when a claim or an EEOC complaint triggers a records review.

If you are evaluating your current documentation structure against these requirements, the ADA and workers' comp interactive process article walks through how the reasonable-accommodation obligation interacts with the workers' comp RTW timeline — including where the records from each process need to be kept.

For healthcare sector operations, where workers frequently manage their own medical contacts and clinical language is common in the workplace, the healthcare transitional duty playbook addresses how to maintain the confidentiality boundary in environments where clinical vocabulary is part of everyday conversation.

The documentation side of this — templated restriction summaries, separate file structures, supervisor acknowledgment forms, and access logs — is exactly what a purpose-built RTW workflow tool is designed to support. Transitional Duty Manager separates medical and operational records structurally, so the access boundary is built into the system rather than depending on everyone remembering the policy on a busy shift.

---

What Supervisors Need — Delivered in Writing

The most practical thing an RTW coordinator can do, today, is make sure every supervisor managing a transitional duty assignment has one document: a written restriction summary, issued by the coordinator, that tells the supervisor everything they are authorized to know and nothing they are not.

That document should be standardized, templated, and consistent — so the supervisor knows exactly what to expect and so the organization can demonstrate, if asked, that it has a process for maintaining the confidentiality line.

The Supervisor's Transitional Duty Toolkit at /store/supervisor-transitional-duty-toolkit includes a restriction-summary template, a supervisor acknowledgment form, and a one-page briefing on what supervisors may and may not ask during a transitional duty assignment — drafted for the people who actually manage the work, not for the attorneys.

This article describes general documentation and administrative practices related to ADA medical confidentiality requirements. It is not legal advice. Confirm your organization's specific obligations and current regulatory requirements with qualified employment counsel and, as applicable, with the EEOC or your state's equivalent enforcement agency.