Outsourced EmploymentPowered by StealthAgents

Research note

How often do remote separations lack a confirmed notice delivery?

A local method for measuring whether remote separation notices have a recorded send, delivery, and acknowledgment before the last working day.

Published

Research note illustration for How often do remote separations lack a confirmed notice delivery?
Table of contents

Question and scope

The question covers notices about the end of an assignment, a resignation acceptance, a temporary layoff, or another separation event. It includes the message that states the last working day and the return of company property. It excludes general announcements that do not name an individual. The review covers one employer and one role family.

A separation enters the sample when the employee record shows a final date. If the date was later changed, use the date in effect at the time of the review and record the change. A case that is still open at the end of the window is counted separately. Keep completed and pending cases apart.

The delivery standard should be written before the review. It may require a sent copy, a delivery confirmation, and an acknowledgment from the employee. Define what counts for each channel, such as an email delivery receipt or a signed courier record. Record the standard version used for each case.

Definitions and evidence standard

Define a confirmed delivery as evidence that the message reached the employee's controlled address or device. A message marked sent but not delivered does not qualify. A read receipt is stronger than a delivery receipt but is not always available. Record the level of evidence rather than treating all confirmations as equal.

Record the address or number used and the date it was verified. A notice sent to an old personal address may never reach the employee, even when the system says it was sent. If the employee had a company device, record whether it was still active on the send date. The channel matters as much as the message.

Separate a delivery failure from an employee who chose not to respond. A message delivered to the correct address and left unanswered is different from a message that bounced. Record the bounce, the retry, and the alternate channel used. The two cases need different follow-up.

Sampling and measurement

Freeze the list of separations before reviewing any of them. Include more than one manager and more than one separation reason. Record the export date and the filter used. Do not remove a case because the file is thin. A thin file is 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. 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 separations, the number with a sent notice, the number with a delivery confirmation, the number with an acknowledgment, and the number with all three. Add the number with a verified address and the number with a failed first attempt. Report the counts by manager and channel. A single rate hides where the failure occurs.

Findings and interpretation

Present the distribution before suggesting a cause. A cluster of missing confirmations under one manager may mean the manager sends notices from a personal inbox. A cluster on one channel may mean the company address list is out of date. Read the cases behind the largest cluster before naming a reason.

Compare the confirmation rate with the notice method. A hand-delivered notice with a signature may produce stronger evidence than an email, but it may not be possible for a remote employee. Record the method and the evidence it produces. The comparison should inform the process, not rank the people.

Check whether the employee acknowledged the last working day and the property return step. An acknowledgment that only confirms receipt of the message may not show that the employee understood the date. Record what was confirmed. The content of the acknowledgment matters.

Limitations

The review measures notice evidence, not whether the separation was fair or lawful. A well-documented notice can still support a poor decision. The result describes the delivery record, not the reason for the separation. A reviewer should read the notice and the decision as separate records.

A remote employee may have multiple addresses and devices, and the record may not show which one was active. Note the channels the company can verify. The count may understate delivery when the employee received the message through a channel the system does not track. Report the channels that were checked.

The written standard may change during the window. Record the version that applied to each case. A notice that met the old standard may not meet the current one. The reviewer should not apply a new rule retroactively.

Practical next step

Verify the employee's contact details at the start of the separation process and record the date. Send the notice to the verified address and a second company-approved channel. Record both sends and both results. A single channel is a single point of failure.

Add a delivery confirmation step to the separation checklist and name the person who checks it. If the first attempt fails, use the alternate channel the same day. Record the retry and the time. The checklist should not close on a sent status alone.

Test the revised process for one month and compare the confirmation rate with the baseline. Keep the change if it improves delivery without delaying the last working day. If the second channel adds confusion, choose a better primary channel. The goal is a notice the employee actually receives.

Sources

References supplied with this research note.

Article source directory
SourcePublisherContext
U.S. Department of Labor, Terminationdol.govPrimary reference supplied with this article.
U.S. Department of Labor, Recordkeepingdol.govPrimary reference supplied with this article.
National Institute of Standards and Technology, Privacy Frameworknist.govPrimary reference supplied with this article.