Research question and scope
This protocol asks how much effective coverage a Philippine holiday week removes from a support lane. Effective coverage is the number of staffed hours that can actually handle the queue, after local holidays, approved leave, and reduced transport are counted. The unit is one coverage day for one queue. The study measures lost capacity and reassigned work, not attendance or individual reliability.
Set the scope to one queue, one holiday calendar, and an observation window that includes a normal week for comparison. Record the holiday proclamations, the provider's leave policy, and the shift schedule at the start. If the schedule changes during the window, keep the earlier definition or analyze the change separately. The comparison week should be close enough that demand is similar.
Population and unit of analysis
Define the population as every coverage day in the selected queue during the window. The unit is the day, not the employee, because coverage is a property of the queue. A day with three people available and two queues is not the same as a day with three people and one queue. Record the queue count and the priority rules for each day.
Exclude days when the client's business was closed and record the exclusion count. Include days when the team was open but reduced, because that is where the coverage loss usually appears. Test the day definition on one holiday week and one normal week before collection begins. Keep the excluded days with the sample so the denominator is auditable.
Definitions that make the measure reproducible
Define nominal coverage as the hours on the published schedule. Define effective coverage as nominal hours minus holiday hours, approved leave, and any period when the team could not access the systems. Define a coverage gap as a period when the queue had arrivals but no available owner. Define reassigned work as a task moved to another day or person with a recorded owner.
Do not count a day as covered because one person was on call but unavailable for the queue. Do not count scheduled catch-up work as live coverage. Each definition should include one positive and one boundary example. Publish the definitions so two reviewers can classify the same day the same way.
Evidence standard and data dictionary
For each day, capture the schedule, the holiday status, the leave records, the queue arrivals, the first-response times, and the tasks reassigned. Add the person who approved the reduced schedule and the client notification. Record whether the client changed its expectations for the week. Keep the packet with the queue record.
Also capture the transport or utility disruption if it affected the team, because a holiday can reduce attendance beyond the official calendar. If the provider uses a different holiday list, record which list applied. A reviewer should be able to rebuild the day from the packet without asking the team lead. Record who reported the disruption and when the team regained access.
Sampling and collection
Draw the sample from the schedule and the queue system rather than from a list of problem days. Record the export date, the filters, the row count, and the selection rule. Include every queue in the lane so a gap in one queue is not hidden by coverage in another. If the window is short, include the full population rather than a sample.
Collect the schedule as it was published, not as it was edited afterward. If a swap happened, record the original and the change. Do not infer coverage from the final attendance record alone, because a person can be present and still unavailable for the queue. Note the collection date separately from the coverage date.
Analysis and reporting
Report nominal hours, effective hours, and the share lost for each day. Show the arrivals and the first-response times for the same days. Break the result down by queue and by holiday. Use the normal week as a comparison, not as a target, because demand may differ.
Compare the lost hours with the work that was reassigned or deferred. A holiday week can look well covered if the queue was quiet, even when the team had no capacity for a surge. Report the deferred work separately. If the sample is small, show the daily counts rather than an average.
Limitations and sources of error
The record cannot show work that was never requested because the client knew the team was away. It also cannot capture informal coverage from a manager who answered messages on a holiday. A reduced schedule may be a deliberate service decision rather than a failure. The study measures capacity, not the fairness of the arrangement.
Holiday calendars can change, and local observances may differ by province. Leave records may be incomplete or recorded after the fact. Note these gaps and their treatment. Do not use the result to compare individual attendance without accounting for approved leave.
Review cadence and next action
Give the result to the service owner and the client contact and ask for one change. The change might be a pre-approved holiday rota, a reduced queue, or a clearer client note. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the schedule and the client promise at the same time.
Repeat the protocol for the next holiday week and compare the same fields. If effective coverage improved but response time did not, the queue may be constrained by decisions rather than hours. If the client deferred less work, the note may be working. Close the review when the owner accepts the finding and the next window is scheduled.
Demand adjustment and seasonality
Holiday weeks often coincide with seasonal demand, which makes a simple before-and-after comparison misleading. Compare the holiday week with the same week in a prior period when possible. If that is not available, adjust for the queue's normal weekday pattern. Report the adjustment so the reader can see how much of the change is demand.
Separate customer-driven demand from work the team generates internally. A holiday can reduce customer requests while increasing catch-up tasks. Both affect coverage but in different ways. Show them separately so the owner does not credit the rota for a quiet market.
Client notification quality
A holiday plan is only as good as the client's understanding of it. Check whether the client received the dates, the reduced hours, the paused work, and the escalation contact before the week began. Record whether the client acknowledged the note. A note that was sent but never read is not a notification.
Compare client messages during the holiday with the note that was sent. If the client asked about work that the note said would pause, the note was unclear or the client did not accept it. Use that evidence to improve the next note rather than blaming the client. Keep the client's original message so the review can quote it.
Cost of deferred work
Deferred work is not free even when it is completed later. It can delay a customer promise, increase the next week's load, or create a second review. Estimate the cost using the same time rate as the original task. Show the deferred items with their new dates and owners.
Separate work that was safely deferred from work that should have been covered. A task with no customer promise and a clear next date is usually safe. A task that affects a payment or a customer commitment is not. The distinction should drive the next holiday rota.
Replication and version control
Keep the holiday calendar, the schedule version, and the queue export with the report. Repeat the measurement for the next holiday using the same definitions. If the provider changes its leave policy, publish a new baseline. The comparison should be reproducible without asking the original analyst.
Schedule the next measurement before the holiday season ends. Assign the owner and the queues to include. A coverage review that happens once a year cannot guide the next rota. The value comes from the comparison over several cycles.
Keep the rota and the measurement notes together so the next planner can see the reasoning. A number without the schedule and the client note is hard to interpret. If the next holiday changes the queue, update the scope before comparing. The record should explain the decision, not only the result.
