Research question and scope
This protocol measures the share of scheduled shifts that miss at least one required system check at the start. The unit is one scheduled shift for one specialist. A miss means a blocking check failed or was not completed before the first task. The measure describes readiness, not attendance.
Set the scope to one team, one published check list, and a fixed period. Record the systems on the list, the roles covered, and the grace period allowed before the first task. If the list changes during the period, split the sample at the effective date. A new check item changes the denominator.
Keep the measure separate from a performance rating. A blocked start may come from a permission delay, a tool outage, or a missed step. The purpose is to find where readiness breaks. A neutral framing makes the team more willing to report the real cause.
Population and unit of analysis
Define the population as every scheduled shift in the period, including shifts with no assigned work. The unit is the shift, not the specialist or the check item. One shift may miss three checks, and it should count once as a blocked start while the three items are reported separately. Use the shift identifier to group them.
Exclude shifts cancelled by approved leave or a client closure. Report them separately as not scheduled. The check cannot fail on a shift that did not happen. Keep the two groups distinct in the analysis.
Include shifts where the specialist started late but completed the check before the first task. A late start is a different measure from a missed check. Record both times. Combining them would hide the difference between punctuality and readiness.
Definitions that make the measure reproducible
Define a required check as an item marked blocking in the published list. Define completion as a recorded result with a timestamp before the first task. Define a miss as a failed item or a missing record at the grace cutoff. Publish one example of a pass and one example of a miss.
Define the recovery time as the period from the failed check to the first successful retest. Define a workaround as a temporary path the owner accepts without a full repair. Record both states. A workaround that is never retested should not be counted as recovered.
Decide how to treat a check that was done but not logged. Record it as unverified rather than passing. The record is part of the control and the measure. A verbal confirmation cannot be compared across shifts.
Sampling and data collection
Draw the sample from the check form and the time system for the full period. Record the export date, the filters, and the row count. Include every scheduled shift and every check item on the list. A sample of blocked shifts alone cannot produce a readiness rate.
Capture the shift identifier, the scheduled start, the check timestamps, the failed items, the first task time, and the owner. Add the recovery time and the workaround status. Store the export with the report. The timestamps are the core evidence.
Check a small overlap sample against the queue record. If the check form says ready but the first task started before the check, the definition or the clock is wrong. Record the discrepancy and correct the method before the full sample. A measure that trusts one system can overstate readiness.
Record the time zone and the daylight rule used for the scheduled start. A shift that crosses a clock change can look late when it was on time. Keep the conversion rule in the method. The result should not depend on the reviewer's location.
Measuring blocked shift starts
Report the share of shifts fully ready, the share ready with exceptions, and the share blocked. Show the counts behind each share. The three groups describe different levels of readiness and should not be collapsed into one rate. A single rate hides whether the problem is access or discipline.
Break the result down by system, day of week, and shift group. A system with many failures may need a permanent fix rather than a better reminder. A cluster on one day may point to a maintenance window. Compare only groups with similar volume and complexity.
Report the median and longest recovery time for blocked shifts. A recovery of ten minutes is different from a shift lost to a missing role. Show the recovery beside the share. The pair tells the reader whether the load is a nuisance or a service risk.
Limitations and next action
The measure cannot show a check that was done correctly but never logged or a tool that failed after the first task. It also cannot show the quality of the work that followed. Treat the result as a measure of recorded readiness. Note the systems and shift types that were not included.
Give the result to the team lead and the system owner with one change to test. The change might be a pre-shift permission check, a shorter form, or a maintenance window outside the shift. Record the effective date and repeat the measure with the same definitions. A controlled change is easier to judge.
Review the blocking items before changing the whole check. One missing role may explain a large share of the blocked starts. Fix the permission path first if that is the pattern. The goal is a shift that can begin, not a longer checklist.
