Written and maintained by DeadlineDaysReviewed on August 1, 2026
A 4-business-hour SLA that starts Friday at 15:30 reaches Monday at 11:30 with 09:00-17:00 weekday hours and no holiday.
Run an SLA clock through defined service windows.
Direct answer
Example with business hours 09:00-17:00, Monday-Friday, no holiday, and an America/New_York wall-clock label. It does not convert to UTC or resolve DST gaps and overlaps.
Example assumptions: weekends excluded, no public holiday, start inside business hours. Verify transition cases in the source system.
Plan zone-labelled wall-clock SLA deadlines with business hours, business days, holidays, and closures. No UTC conversion or DST resolution is performed.
No login. No database. Calculator inputs are not stored on a server.
Use this SLA deadline calculator for wall-clock planning of support response targets, incident commitments, and operations handoffs. Choose a local start time, zone label, duration, business window, non-working days, public holidays, and company closures. The browser calculation keeps that zone as context; it does not convert an instant or resolve DST gaps and overlaps.
How counting works
Enter the recorded local trigger, retain its zone label, and select the service window, pause periods, and holiday calendar before planning an SLA response deadline.
Business Days Calculation RulesPublic holiday data
Data status: Source review record (US 2026)
Add regional, employer, company, bank, carrier, or contract closures as custom holidays when they govern this calculation.
Planning reference only. This result does not decide legal SLA compliance or breach. Confirm the contract wording, day 0/day 1 rules, time zone and DST handling, business hours, holidays, policies, and the production service desk clock.
Follow the entered trigger through opening windows, paused periods, and counted intervals to the displayed wall-clock deadline.
Fixed example: Fri Jul 10, 2026 at 15:30, four business hours, 09:00-17:00 Monday-Friday, with no holiday in the interval.
| Start | End | Decision | Minutes |
|---|---|---|---|
| Fri, Jul 10, 2026 15:30 | Fri, Jul 10, 2026 17:00 | Counted | 90 |
| Fri, Jul 10, 2026 17:00 | Fri, Jul 10, 2026 24:00 | Paused: outside opening window | 0 |
| Sat, Jul 11, 2026 00:00 | Sat, Jul 11, 2026 24:00 | Paused: non-working day | 0 |
| Sun, Jul 12, 2026 00:00 | Sun, Jul 12, 2026 24:00 | Paused: non-working day | 0 |
| Mon, Jul 13, 2026 00:00 | Mon, Jul 13, 2026 09:00 | Paused: outside opening window | 0 |
| Mon, Jul 13, 2026 09:00 | Mon, Jul 13, 2026 11:30 | Counted | 150 |
Follow the entered trigger through opening windows, paused periods, and counted intervals to the displayed wall-clock deadline.
The selected zone is a wall-clock label. This calculator does not convert the entry to a UTC instant or resolve daylight-saving gaps and overlaps; verify transition cases in the source system.
DeadlineDays applies the chosen zone as a label to entered wall-clock fields, then counts the SLA duration without converting to an offset or UTC instant.
SLA timing depends on the service definition, so the displayed timestamp must be reviewed against the agreement that creates the obligation.
These cases follow counted wall-clock fields across closing hours and holidays within one selected zone label; they do not perform cross-zone instant conversion.
Useful for first-response support targets that pause outside working hours.
Operations teams can compare internal handoff windows without counting nights.
Near a DST transition, verify the actual elapsed instant in the source system.
Useful when customer support or contract obligations pause on non-working days.
Use this calculator for support and operations wall-clock plans where counting pauses outside working hours.
Estimate when a response is due for P1, P2, or standard queues.
Count only configured working hours and skip holidays when needed.
Document the selected wall-clock zone label without claiming UTC conversion or DST resolution.
Confirm receipt time, contractual time zone, calendar versus business hours, operating window, breaks, holidays, severity, and day-zero wording.
An SLA deadline is the date and time by which a response, resolution, handoff, or other service commitment should be completed.
Business hours count only configured working time. Calendar hours add time continuously without skipping nights, weekends, or holidays.
In business-hour and business-day modes, it skips the days selected as non-working days.
They are excluded in business-time modes when the option is enabled and holiday data can be loaded for the selected country.
The calculator can move the start to the next available business time before counting the SLA duration.
Yes. Add one custom holiday per line using YYYY-MM-DD and an optional holiday name.
The selected date and time are treated as wall-clock fields and shown with the chosen zone label. The calculator does not convert to UTC or resolve daylight-saving gaps and duplicate local times.
No. It is a general planning tool. Confirm official SLA, contract, payroll, tax, and legal deadlines with the relevant source.
This calculator is a general date and time planning tool. It is not legal, contract, accounting, payroll, tax, employment, or customer-support policy advice. Confirm real SLA obligations, contracts, support policies, statutory deadlines, and DST/time-zone boundary cases with your operating system, contract, official source, or qualified professional.