Research question and scope
This protocol asks whether the client and the provider hold the same holiday calendar before a quarter begins, including the dates, the coverage decisions, and the payroll cutoffs. The unit is one client-provider calendar handoff for one quarter. The study compares the provider's calendar, the client's calendar, and the decisions recorded for each overlap. It does not evaluate whether either calendar is legally correct, because that depends on the applicable proclamation and contract.
Set the scope to one client, one provider team, and one quarter, and record the calendar systems and the people who maintain them. If the team changes its calendar process during the window, keep the earlier definition for the full comparison or analyze the change separately. A new calendar tool can look like a new process when it is only a new format. Record the tool version and the handoff date.
Population and unit of analysis
Define the population as all dates in the quarter that either side treats as a non-working day or as a deadline. The unit is the date, identified by the calendar date and the jurisdiction. A date that appears on both calendars with different treatment remains one unit with a conflict flag. A date that appears on only one calendar is a separate unit with a source flag.
Record the national holiday layer, the local observance layer, and the client's own calendar layer separately. These strata matter because a national holiday and a local fiesta carry different coverage implications. Include dates that are not holidays but carry a payroll or reporting cutoff, because those are where calendar gaps become operational failures. Test the unit definition on two ordinary dates before collection begins.
Definitions that make the measure reproducible
Define a shared date as one that appears on both calendars with the same working status. Define a conflict as a date that appears on both calendars with different status, such as a provider holiday and a client working day. Define an unrecorded date as one that appears on one calendar but not the other. Define a coverage decision as a written choice about who works, who is off, or which deadline moves.
Do not treat an oral assurance that the teams are aligned as a shared date. Do not treat a calendar invite as a coverage decision unless it names the person and the work. A date with no coverage decision is not resolved even when both calendars agree that it is a holiday. Each definition should include one positive example and one boundary example so a second coder can apply it consistently.
A date can also be a conflict when both sides agree it is a holiday but disagree about who covers an essential service. Record the service expectation separately from the working status, because a closed office and a stopped service are not the same thing. The coverage decision should name the service that continues and the person who performs it. That distinction prevents a calendar that looks complete but leaves a critical queue unattended.
Evidence standard and data dictionary
For each date, capture the date, the jurisdiction, the source document, the provider status, the client status, and the coverage decision. Add the decision owner, the approval date, and the affected deliverable or payroll cutoff. Record whether the date was confirmed in writing and whether the client acknowledged it. Code each field as present, missing, or not applicable.
Also record the last time each calendar was updated and the person who updated it. A calendar that is correct but stale is a different risk from one that is current but incomplete. If a date is based on a commercial calendar rather than an official source, mark the source type. A second coder should be able to reproduce the classification from the packet without asking either team what it meant.
Sampling and collection
Collect the provider calendar, the client calendar, and the official source list for the same quarter. Record the export date, the filters, and the row count for each. Compare the calendars date by date rather than by asking each team whether it agrees. If the quarter is long, review every date that either side marks as non-working or as a cutoff, plus a sample of ordinary dates.
Collect the evidence from the systems that existed at the time of the handoff. Do not rebuild a missing decision from memory, because reconstruction measures the investigator rather than the process. If a calendar was shared as a screenshot, record that format and its limitations. Note the collection date separately from the handoff date so the reader can see how much of the record has aged.
Analysis and reporting
Report the number of dates reviewed, the share that were shared, the share with a conflict, and the share with no coverage decision. Present the counts by layer and by whether the date affected a payroll or reporting cutoff. Include the number of dates with a missing source so the reader can see the size of the gap. Use the same denominator for every rate.
Inspect the conflicts that affected a hard deadline and describe the pattern without naming individuals. A cluster of conflicts around payroll cutoffs may point to a process gap, while a cluster around local fiestas may point to a missing local layer. Compare the decision date with the handoff date, because a decision made after the quarter began is late even if it is correct. Report the client acknowledgement rate separately.
A simple matrix of provider status against client status makes the pattern easy to see. The four cells are both working, both closed, provider closed with client working, and provider working with client closed. Report the count in each cell and the share with a written coverage decision. The matrix is more useful than a single alignment percentage because it shows where the risk sits.
Limitations and sources of error
The record cannot show whether a holiday was legally observed or whether a premium was owed. It can show only whether the two calendars agreed and whether a decision was recorded. A complete calendar is not proof of a lawful or fair schedule, and an incomplete one is not proof of a violation. Local rules and contracts may impose requirements this protocol does not interpret.
Calendars can omit verbal agreements, local observances that were never entered, and cutoffs that live in a separate payroll system. A date that was resolved informally may not appear in the sample. Record those cases and their treatment instead of dropping them silently. If the same person maintains both calendars, note the independence limitation and analyze that subgroup separately.
The calendar can also change after the quarter begins, especially when a special non-working day is declared late. Record the date of the last update and whether the change was communicated to the client. A calendar that was correct at the handoff but never updated is a different failure from one that was wrong from the start. The report should separate those two cases.
Review cadence and next action
Give the result to the client owner and the provider operations lead and ask them to choose one observable change. The change might be a single calendar source, a mandatory coverage-decision field, or a handoff deadline before the quarter begins. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the source and the decision process at the same time.
Repeat the protocol with the same definitions after the change and compare the same fields. If conflicts fell but late decisions did not, inspect whether the handoff date is early enough. If acknowledgement improved but coverage did not, the decision may still be too vague to act on. Close the review when the owner accepts the finding and the next quarter is scheduled.
Ask both sides to name the person who will maintain the calendar between handoffs. A shared document without an owner tends to drift after the first update. Record the owner, the backup, and the channel used for changes. That small ownership step is often more valuable than another field in the template.
