Research note
How often do remote equipment returns lack a dated confirmation?
A local method for measuring how often remote equipment returns close without a dated receiving confirmation, with a clear definition of the start and stop points.
Published

Table of contents
Question and scope
The question covers devices and accessories issued to a remote employee and expected back at separation. It includes laptops, tokens, phones, monitors, and any item listed in the written equipment policy. It excludes items the employee bought personally or was allowed to keep. The review covers one employer, one review window, and the roles that commonly receive equipment.
An item enters the sample when it appears on an issued asset list and the employee has left or moved to a role that does not need it. A verbal promise to return the item is not enough to place it in the sample. If the item is later found to be owned by the employee, record the correction. The sample should follow the written asset list rather than a memory of the desk.
The stop point is a dated confirmation from a named person at the destination, not a carrier scan. A carrier scan shows that a package moved, not that the right device arrived. A confirmation may include the serial number, the condition, and the accessories present. Report carrier-only records separately so they are not mistaken for a completed return.
Definitions and evidence standard
Define a dated confirmation before reviewing any case. The confirmation must name the item, the date, and the person who checked it. A message that only says a box arrived does not meet the standard. Record the definition with the case so a later reader can apply the same rule.
Use the asset system, the shipping record, and the receiving log as the primary evidence. A remembered conversation can support context but cannot replace a dated entry. If the only evidence is a verbal report, mark the case as unverified rather than assigning a date. Report the share of unverified cases with the result.
Separate the physical return from the access removal. A device can arrive after the account is closed, and an account can stay open after the device returns. Measure both dates so one control does not hide the other. The two numbers answer different questions about the separation.
Sampling and measurement
Freeze the list of assigned items before reviewing any of them. Include more than one manager, more than one device type, and more than one carrier. Record the export date and the filter used. Do not remove a case because the record is incomplete; incomplete cases 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 items, the median and longest wait to confirmation, and the share with no dated confirmation. Add the number with no recorded shipment and the number with an unclear asset record. Report the counts by device type and returning manager. A single percentage hides which item or team drives the gap.
Findings and interpretation
Present the distribution before suggesting a cause. A cluster of missing confirmations under one manager may mean the receiving site never told the manager. A cluster on one device type may mean the carrier label is wrong. Read the cases behind the largest cluster before naming a reason.
Compare the confirmation rate with the return method. A prepaid label may produce a faster return than a reimbursement process. Record the method and the first person who saw the package. The comparison can show whether the problem is shipping or tracking.
Check whether late items were eventually confirmed and whether the employee was told what was still open. A late confirmation with an explanation is different from an item that disappeared. Record the date of any update and the reason given. The quality of the delay matters alongside its length.
Limitations
The review measures confirmation, not whether the device was wiped or reused correctly. A fast confirmation can still hide a data risk. The result describes the return clock, not the security outcome. Report it beside the wipe evidence so a reader does not overread the number.
The written 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.
An item that was never recorded as issued is invisible to this method. The count may understate the problem if equipment moved without an asset entry. Pair the review with a physical count of devices held by current staff. The answer can reveal a gap the return record cannot show.
Practical next step
Create one asset list per employee and send it before the last workday. Include the serial numbers, the accessories, and the return date. Ask the employee to confirm the list. A single list makes the return measurable.
Set a receiving step with a named person and a same-day confirmation. Record the serial number and the condition at arrival. Tell the employee when the item is confirmed. The step should close the loop rather than only log a shipment.
Test the process for one month and compare the confirmation rate with the baseline. Keep the change if it shortens the wait without creating a new delay. If the label or the receiving address causes errors, fix that step. The goal is a confirmed return, not more paperwork.
Sources
References supplied with this research note.
| Source | Publisher | Context |
|---|---|---|
| U.S. Department of Labor, Recordkeeping | dol.gov | Primary reference supplied with this article. |
| National Institute of Standards and Technology, Privacy Framework | nist.gov | Primary reference supplied with this article. |
| Cybersecurity and Infrastructure Security Agency, Secure Our World | cisa.gov | Primary reference supplied with this article. |