Research / Schedule continuity

What share of schedule preference notes survive a supervisor change?

A bounded review of scheduling handovers, with a protocol for measuring how many employee schedule preferences remain visible and correctly classified after a supervisor change.

Published: · Sources: 12 · 10 minute read

One employer
One supervisor change
Bounded review
Research summary for What share of schedule preference notes survive a supervisor change?
In this article

Published November 20, 2026.

Schedule preferences are often held in one supervisor's memory and informal notes. A supervisor change can erase months of small arrangements in a single week. Employees then repeat the same request and conclude that nobody recorded it. This review sets out a bounded way to measure how many preference notes survive such a change. It does not estimate a national share and does not claim that a ledger prevents every scheduling dispute.

Question and scope

This review asks what share of schedule preference notes survive a supervisor change. The unit is one documented preference at one team during one supervisor transition. A preference counts as surviving when the incoming supervisor can find the note, reads it, and states whether it is a commitment or an open request. The measure is about continuity of the record, not about whether the preference was granted.

Set the scope to one employer, one team, and one transition window of at least four weeks. Record the outgoing supervisor's last date, the incoming supervisor's first date, and the rule for calling a preference in scope. If a note was created after the transition, record it separately rather than counting it as surviving. A stable list is what makes the share comparable across teams.

Exclude preferences about matters outside scheduling, such as pay or leave entitlements, unless the scheduling consequence is recorded separately. State the exclusion and report the number of excluded notes. Include preferences that are still open if they were active at the transition. Test the definition on a few notes before reviewing the full team.

Definitions that make the measure reproducible

Define a preference note as a written entry that names the employee, the scheduling request, and the date it was raised. The note may sit in a roster system, a shared document, or a supervisor handover file. The format is less important than the presence of the three fields. A verbal arrangement is not a note for this measure.

Define a commitment as a scheduling decision that the employee has been told to rely on. It may be a fixed day off, a standing start time, or an agreed limit on a particular shift. Define an open request as a preference that has not been promised. The two labels must be distinguishable in the note, because an incoming supervisor treats them differently.

Define survival as the incoming supervisor locating the note and correctly restating its status within the first two schedule cycles. The restatement may be written or spoken, but it must be recorded by the reviewer. Finding the note without understanding its status is not enough. Keep the same test for every team in the sample.

Evidence standard and data dictionary

For each team, capture the team name, the shift pattern, the number of employees, and the transition dates. Add the outgoing and incoming supervisor names and the handover method used. These fields help a reader see whether survival depends on a meeting, a file, or a single person. If the handover method is unknown, record that rather than guessing.

For each preference, capture the employee reference, the request type, the date raised, and the last review date. Record whether the note is marked as a commitment or an open request. Note where the note is stored and whether the incoming supervisor has access. Record whether the status was restated correctly.

Record the request type in a short list such as fixed day, start time, shift length, weekend rotation, or transport constraint. Type shows whether one kind of request survives while another is lost. Keep the list short and apply it consistently. A commitment about a fixed day with no record deserves more attention than a soft preference.

Sampling and collection

Draw the sample from the team's preference ledger or scheduling file, not from the notes the incoming supervisor happens to mention. The full list shows every preference that was active at the transition. If a note is missing from the file, that is a finding. A sample built from remembered notes will overstate survival.

Collect one full transition window so the sample includes the first two published schedules. A single week may not show whether the new supervisor actually used the notes. If the team publishes schedules far in advance, extend the window to cover both cycles. Note any schedule that was published late.

Record the review date separately from the transition date. Note any preference that was restated verbally but not used in a schedule. A verbal restatement shows awareness, while use in a schedule shows continuity. Report both counts so the reader understands what the sample covers.

Analysis and reporting

Report the number of active preferences, the number the incoming supervisor located, and the number restated with the correct status. Use the same denominator for every share and list the notes with missing fields. A share without a denominator invites a misleading comparison. Show the count beside the share so a small team is not overinterpreted.

Split the results by team and by preference type. A site average can hide one team whose commitments were carried in a single supervisor's memory. It can also hide a type of request that is never marked as a commitment. Present both splits even when the sample is small, and label small counts clearly.

Separate a note that was found from a note that was used in a schedule. The first is a record measure, while the second is a practice measure. Each points to a different fix. A single combined category would suggest one remedy for two problems.

Limits of the evidence

The record cannot show whether the employee was satisfied with the outcome. A surviving commitment may still be inconvenient, and a lost note may concern a request that was no longer needed. The protocol measures continuity, not satisfaction. Report any employee feedback beside the share when it is available.

A team with few preferences may produce too few observations to support a stable share. Describe the cases instead of ranking teams when the count is low. If one supervisor created most of the notes, report that concentration. A general share would hide the dependence on one person.

The definition of a commitment varies by employer. A formal roster entry suits some sites, while a signed handover note suits another. State the rule and apply it consistently across teams. A change in the rule should be noted so a later comparison remains honest.

Applying the result

Give the finding to the person who owns the scheduling handover and ask for one observable change. The change might be a required status field, a handover meeting before the last day, or a two-week review of the new schedule. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions in the next transition.

If most notes are lost, start with a single shared ledger rather than a new policy. A file that both supervisors can open is easier to adopt than a formal process. Ask the outgoing supervisor to mark each row as a commitment or an open request. Measure the share again after the next transition.

If notes are found but not used, the problem may be the handover conversation rather than the file. Look at whether the incoming supervisor reviewed the ledger before publishing the first schedule. A record that is read too late cannot shape the roster. Measure the timing of the review beside the survival share before changing the form again.

Data Sources and Methodology

The review uses public labor-market, employment-law, records-management, and human-capital guidance to bound the definitions and keep the recommended fields within common practice. The sources below are context for the process, not evidence that any employer follows them in the same way. Each measure is defined from the employer's own scheduling records, then compared with these public references where a reference is relevant. The citations are listed with the topic they support so a reader can check the boundary without searching an entire site.

The method is deliberately descriptive. It does not pool employers or estimate a national share. 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

  1. U.S. Bureau of Labor Statistics, Job Openings and Labor Turnover Survey - accessed November 20, 2026.
  2. CIPD, Turnover and Retention Factsheet - accessed November 20, 2026.
  3. U.S. Equal Employment Opportunity Commission, Recordkeeping Guidance - accessed November 20, 2026.
  4. International Organization for Standardization, Quality Management Principles - accessed November 20, 2026.