Business Hours vs. Calendar Hours: Why a Friday Ticket Isn’t 67 Hours Old on Monday
A support ticket opened at 4pm on a Friday and closed at 11am on the following Monday has, by the calendar, sat open for 67 hours. Report that number to anyone and it reads as an alarming failure — nearly three days to resolve one ticket. But almost none of those 67 hours were actually worked. The office was closed for roughly 64 of them. The real number, measured in business hours, is 2. Which of those two figures is "correct" depends entirely on what question you're actually trying to answer.
Two different questions wearing the same units
"How long has this been open?" and "how much working time has this consumed?" sound like the same question, but they diverge the moment a night, a weekend, or a holiday sits inside the span. Calendar hours answer the first question; business hours answer the second. Support SLAs, billable-hour windows, and internal "time to resolution" metrics almost always mean to ask the second question, even when they're loosely worded as the first — nobody actually wants a response-time metric that penalizes a team for not working through the weekend.
Why raw elapsed time misleads
The distortion isn't small, and it isn't random — it's concentrated entirely around the edges of the working week. A ticket opened at 9am Monday and closed at 5pm the same day took exactly 8 calendar hours and 8 business hours; the two numbers agree completely, because nothing outside the business day fell inside the span. A ticket opened Friday afternoon and closed Monday morning tells a completely different story: the calendar-hours figure balloons with idle overnight and weekend time, while the business-hours figure stays anchored to what was actually worked. Aggregate calendar-hours metrics across a support queue and the tickets that happen to straddle a weekend will silently drag the average up, making the team look slower than it is on exactly the tickets where nothing was actually wrong.
The working day is a window, not just "not weekend"
Getting business hours right requires more than skipping Saturday and Sunday. A working day has a start time and an end time — commonly 9am to 5pm, but it varies by team and by contract — and often an unpaid break in the middle that shouldn't count either. A ticket opened at 4pm accrues one hour before the day closes, not eight, and a lunch break sitting inside a long ticket's lifespan needs to be subtracted the same way a weekend day would be. Skipping only weekends and holidays while ignoring the shape of the working day itself still overstates every ticket that touches an evening, an early morning, or a midday break.
Holidays compound the same way weekends do
A public holiday sitting inside the span behaves exactly like an extra non-working day: every hour of it is excluded from the business-hours total, the same as a Saturday would be. This matters most for teams operating across countries or regions, where a holiday on one side of a support relationship isn't a holiday on the other — a ticket opened in one country's office and closed in another's needs the calendar of whichever office is actually doing the work, not a shared assumption that both sides observe the same closures.
A worked example
Take a 9am–5pm working day with no lunch deduction. A ticket opens Friday at 4pm and closes the following Monday at 11am. From Friday 4pm to the 5pm close, one hour accrues. The entire weekend contributes nothing. Monday from 9am to 11am adds two more hours. Total: 2 business hours, against 67 calendar hours — a more than 30x difference driven entirely by the fact that the office was closed for most of the elapsed time. Report the 67-hour figure to a manager unfamiliar with the ticket and it reads as a crisis; report 2 business hours and it reads as exactly what happened — a quick fix that happened to straddle a weekend.
Where this number actually gets used
Business-hours measurement is the backbone of any SLA that promises a response or resolution "within N business hours" rather than N calendar hours — which is most of them, once you read the fine print. It's also the right basis for billable-hour reconciliation when work is scoped to business-day availability, for support-team performance metrics that shouldn't be skewed by which tickets happened to land on a Friday afternoon, and for any internal "time to close" dashboard that's meant to reflect effort rather than luck of the calendar.
Measure the time that was actually worked
The Business Hours Between Two Dates calculator takes two timestamps, your working-day window, an optional unpaid break, and the country whose holidays apply, and returns the exact business hours elapsed between them — automatically excluding nights, weekends, holidays, and the break, rather than requiring you to subtract them by hand. Run any metric that's supposed to reflect working time through it before reporting a raw calendar-hours figure that quietly means something else.