What share of first-month check-ins produce a recorded action?

Published November 10, 2026.

Many employers can say that a new hire had a first-month check-in, and far fewer can say what changed because of it. The conversation may be warm, the notes may be thoughtful, and the same small problem may still be waiting in week six. This review sets out a bounded way to measure what share of first-month check-ins produce a recorded action. It does not estimate a national completion rate or claim that a recorded action always solves the problem. The protocol is designed so a small employer can test its own process without a large survey program.

Question and scope

This review asks what share of first-month check-ins produce a recorded action with a named owner and a due date. The unit is one check-in conversation with one new hire during the first thirty-one days of employment. The study records whether the check-in occurred, whether an action was written down, who owned it, and whether it closed. It does not judge whether the manager was caring or whether the new hire was satisfied.

Set the scope to one employer, one new-hire group, and one check-in process. Record the timing, the format, and the person who conducts the check-in at the start. If the process changes during the window, keep the original definition for new hires already in progress and analyze later cohorts separately. A new form can look like an improvement when it is only a change in who writes the notes.

Exclude informal conversations that were never intended as a check-in, and state the exclusion. Include check-ins where the new hire declined or did not attend, because the decline is part of the result. Test the definition on two recent new hires before collecting the full sample. A clear definition is what separates a real measure from an anecdote.

Definitions that make the measure reproducible

Define a check-in as a scheduled conversation between a new hire and a manager, peer, or onboarding owner that covers how the first weeks are going. Define a recorded action as a written item that names what will change, who owns the change, and when it is due. A general note such as "check in again" is not an action unless it names a specific step. Keep the action text short enough that two reviewers would classify it the same way.

Define a closed action as one where the owner reports completion and the new hire confirms the result. A task marked done in a tracker without confirmation is pending, not closed. Define a declined check-in as an offer the new hire chose not to accept. Keep the routes separate in every table so the reader can see which denominator is in use.

Record the date of the check-in, the participants, the role, and the site or team. Add the action text, the owner, and the due date. State the timing rule for the first month, especially whether the count includes the first day. A check-in on day thirty-one should not be counted as a first-month check-in if the scope ends on day thirty.

Evidence standard and data dictionary

For each check-in, capture the invitation date, the conversation date, and the record date. Add the action text, the owner, the due date, and the closure date where one exists. Record whether the new hire was told how the notes would be used. Keep the raw notes in the approved file rather than a personal folder.

Record whether the action concerned access, training, schedule, equipment, or a social concern. A simple category helps a later reviewer see whether the same gap recurs across hires. Add whether the action required another department, because a cross-team dependency often explains a delay. Do not record sensitive personal detail that is not needed for the work.

A useful field is whether the new hire was asked to confirm the action in their own words. Confirmation reduces the chance that the manager heard a different problem than the one described. Record the confirmation and any correction. A second reviewer should be able to understand the action from the record without asking either person.

Sampling and collection

Draw the sample from the new-hire roster, not from the check-in calendar. The calendar hides the new hires who were never invited. Record the export date, the filters, and the number of new hires excluded. If the employer has only a few new hires, describe each case instead of computing a rate.

Collect the check-in record as it existed at the time, not as it was rewritten after the new hire raised a concern. If the action was added later, record the addition date. Do not infer an action from a later email. Note the collection date separately from the check-in date.

Record whether the check-in was in person, by phone, or by video. Add whether a written summary was sent to the new hire. A summary gives the new hire a chance to correct the record before it becomes the official version. A check-in that exists only in the manager's memory is difficult to audit.

Analysis and reporting

Report the number of new hires, the share offered a check-in, the share who attended, and the share with a recorded action. Show the counts by action category, owner, and team. Present the action rate and the closure rate separately. Use the same denominator for every rate and show the records that are incomplete.

Inspect the actions without scoring the managers. A high action rate with a low closure rate may show a process that generates tasks faster than the team can finish them. A low action rate with a high closure rate may show a narrow but effective process. Describe both movements before drawing a conclusion.

A useful additional view is the share of actions that were closed before the next check-in. That share shows whether the first month is a sequence of fixes or a list of open items. Report it separately and avoid combining it into a single score. A new hire can have a good conversation and still leave because the action never closed.

Limits of the evidence

The record cannot show whether the new hire told the whole truth or whether the manager heard it accurately. It can show only what was discussed, written, and closed. A high action rate is not proof of a healthy onboarding program. The protocol also cannot capture an issue that the new hire raised to a peer outside the formal check-in.

A small employer may have too few new hires to support a stable share. Describe the cases and the actions instead of ranking teams. If one manager conducts most of the check-ins, report that concentration. A general rate would hide a single habit.

A new hire may decline a check-in because of time pressure or distrust. The decline is a finding, not a missing data point to be ignored. Record the offered route and whether an alternative was available. Report the decline rate beside the attendance rate.

Applying the result

Give the result to the onboarding owner and the leadership team and ask for one observable change. The change might be a standard action template, a weekly closure review, or a rule that every check-in ends with one named fix. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions for the next cohort.

If the action rate rises but closure does not, the process may be collecting requests without capacity to finish them. If closure rises while the number of actions stays flat, the team may be choosing better fixes. Report the two movements together before drawing a conclusion. Close the review when the owner accepts the finding and the next cohort is scheduled.

Ask the last five new hires whether they saw a change after their first-month check-in. A direct answer is more useful than a general satisfaction score. Fix the step that made the action invisible. The next measurement should show whether the same gap recurred.

Record whether the action was visible to the new hire after the check-in. An action that lives only in a manager's tracker gives the new hire no evidence that the conversation mattered. Report the visibility and the closure together. The two details answer different questions about trust.

Ask the manager whether the check-in template made the action easier to write. A template that is too long will be skipped during a busy month. Record the time required and the completion rate. A short form that people actually use is better than a perfect form that stays blank.

Data Sources and Methodology

The review uses public employment and workplace guidance to bound the definitions and to keep the recommended record fields within common practice. The sources below are used as context, not as a claim that any one employer follows them in the same way. Each measure in this protocol is defined from the employer's own records, then compared with these public references where the reference is relevant. The citations are listed with the specific topic they support so a reader can check the boundary without searching the whole site.

The method is deliberately descriptive. It does not pool employers or estimate a national rate. A reader who repeats the protocol should use the same definitions, the same observation window, and the same sampling rule, then report the counts beside the shares. Keep that report with the study record so a later reviewer can repeat the comparison.

Sources

Society for Human Resource Management, employee handbooks and policies - accessed November 10, 2026.
U.S. Department of Labor, workplace safety and health - accessed November 10, 2026.
Centers for Disease Control and Prevention, workplace health promotion - accessed November 10, 2026.
Project Management Institute, risk management resources - accessed November 10, 2026.

Question and scope

Definitions that make the measure reproducible

Evidence standard and data dictionary

Sampling and collection

Analysis and reporting

Limits of the evidence

Applying the result

Data Sources and Methodology

Sources

Related Research