Outsourced EmploymentPowered by StealthAgents

Research note

What share of probation reviews happen on or before the scheduled date?

A local method for measuring whether probation reviews happen on or before the date set at hire, with separate checks for the conversation and the written summary.

Published

Research note illustration for What share of probation reviews happen on or before the scheduled date?
Table of contents

Question and scope

The question covers employees with a written probation period and a scheduled review date. It includes reviews held in person, by call, or in writing. It excludes reviews that happen after probation has already ended without a recorded date. The review covers one employer, one review window, and the roles that use probation.

A case enters the sample when the employee has a start date, a probation end date, and a named reviewer. If the dates were never written down, the case enters as an undated record. Record the source of the date, such as the offer letter or the human resources system. A date that was set after the fact should be marked as reconstructed.

The stop point is the date the review conversation happened and the date the written summary was sent. A scheduled meeting that was cancelled does not count as a review. A summary without a conversation may count only if the written policy allows it. Report the two dates separately so a late summary does not look like a late conversation.

Definitions and evidence standard

Define on time before reviewing any case. A review is on time when the conversation happens on or before the scheduled date and the summary is sent within the written window. Record the window with the case. A definition that changes during the review makes the result impossible to compare.

Use the calendar, the review note, and the message system as the primary evidence. A manager's memory can support context but cannot replace a dated entry. Mark a case as unverified when the only evidence is a verbal report. Report the share of unverified cases with the result.

Separate the conversation from the decision. A case can hold the meeting on time and still decide late. Measure both steps so a fast meeting does not hide a slow decision. The two numbers answer different questions about the process.

Sampling and measurement

Freeze the list of probation cases before reviewing any of them. Include more than one manager, more than one role, and more than one start month. 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 method. Keep the full count beside the sample so a reader can see 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 cases, the share reviewed on or before the date, the median days early or late, and the share with no recorded date. Add the number with no written summary. Report the counts by manager and role. A single percentage hides which team drives the result.

Findings and interpretation

Present the distribution before suggesting a cause. A cluster of late reviews under one manager may mean the manager never received the date. A cluster in one role may mean the standard probation period is too short for the work. Read the cases behind the largest cluster before naming a reason.

Compare the result with the review method. A shared calendar may produce a different pattern than a personal reminder. Record the method and the person who set the date. The comparison can show whether the problem is scheduling or capacity.

Check whether late cases were still reviewed and whether the employee was told about the delay. A late review with an explanation is different from a case that was forgotten. Record the date of any update and the reason given. The quality of the delay matters alongside its length.

Limitations

The review measures timing, not whether the comments were useful or fair. A timely review can still be poorly prepared. The result describes the calendar, not the quality of the conversation. Report it beside a sample review so a reader does not overread the number.

The written probation 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 case with no written date is invisible to a calendar method. The count may understate lateness if managers hold reviews without recording them. Pair the review with an anonymous question about whether employees received a review. The answer can reveal a gap the record cannot show.

Practical next step

Set the review dates at hire and send them to the employee and the manager. Put the dates in the same calendar the team already uses. Record the reviewer and a backup. A visible date is easier to keep than a remembered one.

Prepare the examples before the meeting and write the summary within one business day. Record the conversation date and the summary date. Tell the employee what happens next. The record should show a real exchange rather than a single form.

Test the calendar for one quarter and compare the on-time share with the baseline. Keep the change if it improves timing without turning the review into a paperwork race. If a role needs a longer period, change the schedule rather than the standard. The goal is a useful review, not a perfect date.

Sources

References supplied with this research note.

Article source directory
SourcePublisherContext
U.S. Equal Employment Opportunity Commission, Prohibited Employment Policies and Practiceseeoc.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.