Outsourced EmploymentPowered by StealthAgents

Research note

How often do return-to-work plans name a review date?

A local method for measuring how often return-to-work plans name a review date, with separate checks for the date, the owner, and the recorded outcome.

Published

Research note illustration for How often do return-to-work plans name a review date?
Table of contents

Question and scope

The question covers employees who return from an extended leave with a written plan. It includes returns that start full time, part time, or with a restriction. It excludes short absences that never required a plan. The review covers one employer, one window, and the roles that use extended leave.

A case enters the sample when the leave record shows a return date and a plan file exists. If the plan lives only in a message thread, the case enters as an informal plan. Record the source of the return date, such as the leave system or the approved request. A date added after the return should be marked as reconstructed.

The stop point is a named review date in the plan, whether or not the review has happened yet. A plan that says review later has no date and does not meet the standard. A plan with a date but no owner is a separate failure. Report the two conditions separately so the result shows which part is missing.

Definitions and evidence standard

Define a review date before reading any plan. The date must be a calendar day, not a week number or a vague period. It should sit close enough to the return to allow a change in the workload. Record the definition with the case so a later reader applies the same rule.

Use the plan file, the leave record, and the calendar entry as the primary evidence. A manager's memory can add context but cannot replace a dated entry. If the only evidence is a verbal agreement, mark the case as unverified. Report the share of unverified cases with the result.

Separate the presence of a date from the occurrence of the review. A plan can name a date that was never used. Measure both so an on-paper date does not look like a completed check. The two numbers answer different questions about the plan.

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 work pattern. Record the export date and the filter used. Do not remove a case because the plan 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 plans, the share with a dated review, the share with a named owner, and the share with a recorded outcome. Add the median gap between the return and the review. Report the counts by manager and leave type. A single percentage hides which part of the plan is weakest.

Findings and interpretation

Present the distribution before suggesting a cause. A cluster of plans with no date under one manager may mean the template has no field for it. A cluster in one leave type may mean the plan is written by a different team. Read the cases behind the largest cluster before naming a reason.

Compare the result with the plan template. A template with a required date field will produce more dates than a blank page. Record the template version and the person who owns it. The comparison can show whether the gap is a form problem or a habit.

Check whether plans with a date also recorded what changed at the review. A date that passed with no note may mean the review never happened. Record the outcome where one exists. The quality of the review matters alongside the presence of the date.

Limitations

The review measures the plan document, not the employee's recovery or the fit of the work. A complete plan can still be a poor plan. The result describes the paperwork, not the return experience. Report it beside the employee's check-in notes so a reader does not overread the number.

The leave policy may change during the window, and an older case may follow a rule that was appropriate at the time. Record the policy 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 with no written plan is invisible to this method. The count may understate the problem if some employees return without any plan at all. Pair the review with a count of returns that had no plan file. The answer can reveal a gap the plan record cannot show.

Practical next step

Add three required fields to the plan: the review date, the review owner, and the place where the outcome is recorded. Send the plan to the employee before the first day. A short form makes the check measurable. Keep the fields visible at the top of the page.

Set the first review within the first two weeks and name the person who will hold it. Record the date the review happened and what changed. Tell the employee who to contact if the load is wrong before the review. The date should be a commitment, not a suggestion.

Test the process for one month and compare the share of plans with a review date against the baseline. Keep the change if it increases the share without adding a new delay. If the form or the owner causes errors, fix that step. The goal is a usable plan, not more fields.

Sources

References supplied with this research note.

Article source directory
SourcePublisherContext
U.S. Department of Labor, Family and Medical Leave Actdol.govPrimary reference supplied with this article.
U.S. Equal Employment Opportunity Commission, Disability Discriminationeeoc.govPrimary reference supplied with this article.
Occupational Safety and Health Administration, Safety Managementosha.govPrimary reference supplied with this article.