Research note
What share of return-to-work notes name a follow-up owner and date?
A local method for measuring how often return-to-work notes name a follow-up owner and date, with separate checks for the plan, the privacy, and the review.
Published

Table of contents
Question and scope
The question covers employees who returned from an extended leave during the review window. It includes returns after medical, family, and personal leave where a conversation took place. It excludes short absences that needed no plan and cases handled entirely by an outside provider. The review covers one employer, one window, and the roles that use a written return plan.
A case enters the sample when the personnel record shows a leave end date and a return conversation. If the conversation exists only as a message, the case enters as an informal note. Record the source of the note and the date it was written. A note added weeks after the return should be marked as reconstructed.
The stop point is a dated follow-up owned by a named person, not the first day back. A return that was never reviewed can drift from the plan. The follow-up may be a short meeting, a message, or a written check. Report returns with a plan but no follow-up separately.
Definitions and evidence standard
Define a complete note before reviewing any case. It should name the employee, the conversation date, the practical needs, the agreed adjustments, the owner, and the follow-up date. A note that says returned to work does not meet the standard. Record the definition with the case so a later reader applies the same rule.
Use the conversation note, the schedule change, and the follow-up message as the primary evidence. A memory of the meeting can add context but cannot replace a dated entry. If only a verbal report exists, mark the case as unverified rather than assigning a date. Report the share of unverified cases with the result.
Separate the return date from the follow-up date. An employee can return on a Monday while the first review happens two weeks later. Measure both dates so a late follow-up does not look like a late return. The two numbers answer different questions about the process.
Sampling and measurement
Freeze the list of returns before reviewing any of them. Include more than one manager, more than one leave type, and more than one month. Record the export date and the filter used. Do not remove a case because the note is thin, since the gaps are part of the finding.
If the list is large, take a random sample and record the selection method. Keep the full count beside the sample so a reader can see the coverage. A replaced case should be reported as a deviation. The sample should be large enough to compare at least two teams.
Measure the number of returns, the share with a named follow-up owner, the share with a follow-up date, and the share with no note at all. Add the median and longest wait between the return and the follow-up. Report the counts by manager and leave type. A single percentage hides which team drives the gap.
Findings and interpretation
Present the distribution before suggesting a cause. A cluster of missing follow-ups under one manager may mean the note was never added to a task list. A cluster in one leave type may mean the return route is handled by a different team. Read the cases behind the largest cluster before naming a reason.
Compare the result with the note template. A template with a required owner and date may produce a clearer plan than a free-text message. Record the template and the first person who saw the note. The comparison can show whether the gap is in the form or the follow-up.
Check whether late follow-ups still changed the plan and whether the employee was told what changed. A late review that adjusted the hours is different from one that only confirmed attendance. Record the date of the change and the owner. The quality of the follow-up matters alongside its timing.
Limitations
The review measures the presence of an owner and a date, not whether the return was sustainable. A complete note can still describe a plan that did not work. The result describes the documentation trail, not the employee's experience. Report it beside a short employee check so a reader does not overread the number.
The return process may change during the window, and an older case may follow a rule that was appropriate at the time. Record the process version rather than applying the current rule retroactively. A case that missed an old standard may not be a current defect. Keep the version note with the case file.
A return that never had a conversation is invisible to this method. The count may understate the problem if some teams skip the meeting. Pair the review with a count of returns with no note. The answer can reveal a gap the follow-up record cannot show.
Practical next step
Create one return note with required fields for the practical needs, the owner, and the follow-up date. Share it with the manager before the first day back. A single note makes the follow-up measurable. Keep it short enough that a manager will complete it.
Set a follow-up target and name the person who confirms it. A short target such as ten business days gives the manager a clear deadline. Record the date the target was met or missed. Tell the employee who to ask if the follow-up does not happen.
Test the process for one quarter and compare the follow-up rate with the baseline. Keep the change if it improves the rate without pressuring the employee to share private detail. If the note or the reminder causes errors, fix that step. The goal is a supported return, not more paperwork.
Sources
References supplied with this research note.
| Source | Publisher | Context |
|---|---|---|
| Occupational Safety and Health Administration, Safety Management | osha.gov | Primary reference supplied with this article. |
| Centers for Disease Control and Prevention, Total Worker Health | cdc.gov | Primary reference supplied with this article. |
| National Institute of Standards and Technology, Privacy Framework | nist.gov | Primary reference supplied with this article. |