Research note
What share of exit interviews produce a dated theme summary?
A local method for measuring how often exit interviews produce a dated theme summary, with a clear start point and a single evidence standard.
Published

Table of contents
Question and scope
The question covers departures where the employee took part in an exit conversation and the company kept a record of it. It includes conversations held by call, in writing, or in person. It excludes departures with no recorded conversation and cases handled only by an external adviser. The review covers one employer, one window, and the roles that use exit interviews.
A case enters the sample when the departure date is known and the exit record exists in the system of record. If the only evidence is a calendar invite, the case enters as an unverified conversation. Record the source of the departure date, such as the resignation letter or the human resources system. A date reconstructed after the fact should be marked as such.
The stop point is a dated theme summary filed by a named owner, not a promise to write one. A draft in a personal folder does not count. A summary must name at least one theme and the evidence behind it. Report cases with a raw note but no summary separately.
Definitions and evidence standard
Define a theme summary before reviewing any case. The summary should group comments into a small set of neutral categories and state the source of each theme. It should not repeat names or unique stories. Record the definition with the case so a later reader applies the same rule.
Use the exit note, the summary file, and the case log as the primary evidence. A memory of the conversation can add context but cannot replace a dated entry. If only a verbal report exists, mark the case as unverified rather than assigning a date. Report the share of unverified cases with the result.
Separate the conversation date from the summary date. A conversation can happen on the last day while the summary is written weeks later. Measure both dates so a late summary does not look like a late conversation. The two numbers answer different questions about the process.
Sampling and measurement
Freeze the list of departures before reviewing any of them. Include more than one manager, more than one role, and more than one exit method. Record the export date and the filter used. Do not remove a case because the record is incomplete, 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 cases, the share with a dated summary, the median and longest wait, and the share with no summary at all. Add the number with no recorded conversation. Report the counts by manager and role. A single percentage hides which team drives the gap.
Findings and interpretation
Present the distribution before suggesting a cause. A cluster of missing summaries under one manager may mean the exit note never reached the owner. A cluster in one role may mean the conversation happens in a tool that is not searched. Read the cases behind the largest cluster before naming a reason.
Compare the result with the exit method. A written form may produce a faster summary than a live call because the text is already in the system. Record the method and the first person who saw the note. The comparison can show whether the delay is in the conversation or the write-up.
Check whether late summaries still contained useful themes and whether the employee was told what would happen next. A late summary with a clear action is different from a summary that was never used. Record the date of any follow-up and the owner. The quality of the delay matters alongside its length.
Limitations
The review measures the presence of a summary, not whether the themes led to a change. A summary can be filed on time and still be ignored. The result describes the documentation clock, not the outcome. Report it beside the follow-up record so a reader does not overread the number.
The exit process 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 departure with no exit conversation is invisible to this method. The count may understate the problem if people leave without any recorded discussion. Pair the review with a count of departures that had no conversation at all. The answer can reveal a gap the summary record cannot show.
Practical next step
Create one exit template with a fixed place for the conversation date, the themes, and the summary owner. Send the template to the interviewer before the last day. A single form makes the summary measurable. Keep the form short enough that an interviewer will actually complete it.
Set a target for the summary and name the person who checks it. A short target such as five business days gives the owner a clear deadline. Record the date the target was met or missed. Tell the employee what will happen with the themes.
Test the process for one month and compare the summary rate with the baseline. Keep the change if it shortens the wait without losing the evidence. If the form or the owner causes errors, fix that step. The goal is a usable summary, not more paperwork.
Sources
References supplied with this research note.
| Source | Publisher | Context |
|---|---|---|
| U.S. Equal Employment Opportunity Commission, Prohibited Employment Policies and Practices | eeoc.gov | Primary reference supplied with this article. |
| U.S. Department of Labor, FLSA Recordkeeping Fact Sheet | dol.gov | Primary reference supplied with this article. |
| National Institute of Standards and Technology, Privacy Framework | nist.gov | Primary reference supplied with this article. |