Pick a start date, a start time, an SLA in hours, and a time zone, and the calculator adds those hours to the start instant and returns the wall-clock deadline in the same zone. This is continuous clock-hour math: every hour counts the same, including nights, weekends, and public holidays. The calc does not skip non-working time. If your SLA contract pauses on weekends or honors a 9-to-5 working day, this tool will quote a deadline that is too early; use the add business days calculator to land on a working day, or the business days between calculator to count working hours separately.
Common use cases
- Confirming an incident response deadline. A P1 ticket opens at 14:00 UTC with a 4-hour response SLA. Enter the start, set hours to 4, keep the zone at UTC, and read 18:00 UTC as the moment the response is due. Quote that exact wall-clock time in the ticket so on-call and the customer agree.
- Translating a vendor SLA into your local zone. A vendor commits to a 24-hour resolution starting from when the case is filed. Enter the file time in their zone, set 24 hours, and switch the result zone to your own. The calculator returns the deadline in your wall clock so you can plan the follow-up call without doing the offset math by hand.
- Setting a follow-up reminder for a 72-hour callback. A renewal lead asks for a 72-hour callback. Enter the call end time, set 72 hours, and pin the result in your calendar. The deadline is a single instant, so a recurring reminder is unnecessary.
- Sanity-checking a deadline that crosses a DST boundary. When the start is the day before clocks spring forward, the local hour digits will skip from 02:00 to 03:00. Run the calc to see how many wall-clock hours actually elapse between start and deadline, then explain it to anyone surprised by the local clock face.
How it works
The calc combines your start date and start time into an instant in the chosen zone, converts that to UTC, adds the SLA hours as fixed UTC hours, and converts the resulting instant back to the same zone for display. The math is identical to subtracting two timestamps: one hour means 3,600 seconds of real time, regardless of weekend, holiday, or DST. The output reads YYYY-MM-DD and HH:mm in the entered zone.
- Enter the start date and time. Pick a calendar date and a 24-hour clock time. The two together pin the SLA clock to a single moment, not a range.
- Choose the zone the start belongs to. Pick UTC for server logs and machine timestamps, or an IANA zone such as America/New_York for a wall-clock contract. The deadline is rendered in this same zone.
- Set the SLA hours. Enter a non-negative number such as 4, 24, 72, or 720 (30 days). Negative hours are rejected; zero hours returns the start instant unchanged.
- Read the deadline. The calc returns the deadline date and the deadline time in your entered zone. Quote both in the ticket so anyone reading the SLA without the start time still knows when the clock runs out.
- Cross-check against your contract clause. If the contract pauses on weekends, holidays, or off-hours, this tool quotes the wrong deadline. Switch to a business-day calculator for a working-day result instead.
Worked examples
Standard same-day 4-hour SLA
Enter start date 2026-04-27, start time 14:00, hours 4, zone UTC.
Result: The calc returns deadline date 2026-04-27 and deadline time 18:00 in UTC. The clock runs continuously from 14:00 to 18:00 with no gaps.
For a same-day, weekday, in-hours scenario the answer matches what most contracts intend. The behavior diverges from intent the moment a weekend, holiday, or off-hours boundary lies inside the SLA window.
Crossing into the weekend
Enter start date 2026-04-25 (Saturday), start time 22:00, hours 4, zone UTC.
Result: The calc returns deadline date 2026-04-26 and deadline time 02:00 in UTC. Sunday counts the same as any other hour.
The calc does not pause for the weekend. If the SLA only runs during the working week, the deadline you actually need lands on Monday morning, not 02:00 Sunday. A business-day calculator handles that case instead.
DST spring-forward in New York
Enter start date 2026-03-07, start time 23:00, hours 6, zone America/New_York. Clocks spring forward on March 8 at 02:00 EST, jumping straight to 03:00 EDT.
Result: The calc returns deadline date 2026-03-08 and deadline time 06:00 in America/New_York. Six UTC hours elapse, but the local clock face advances seven positions because the 02:00 hour does not exist that day.
The calc adds hours in UTC, so the elapsed real time is exactly 6 hours. If your contract reads "6 hours by the local clock," the wall-clock answer you want is 05:00 instead of 06:00. Choose the zone deliberately when DST sits inside the window.
Multi-day 720-hour (30-day) SLA
Enter start date 2026-04-27, start time 09:00, hours 720, zone UTC.
Result: The calc returns deadline date 2026-05-27 and deadline time 09:00 in UTC. Thirty 24-hour days advance the calendar by 30 days exactly.
For long SLAs (resolution windows, refund eligibility windows) the lack of calendar awareness rarely matters: the deadline lands on a specific instant, and downstream review still happens during business hours. For short SLAs the gap between clock-hour math and contract intent is much larger.
Edge cases & gotchas
- Weekends and public holidays do not pause the clock. A Saturday hour, a Sunday hour, and a public-holiday hour all count toward the SLA. If the contract specifies "business hours" or "working days," the deadline this tool returns is earlier than the contract intends. Reach for a business-day calculator when the SLA is denominated in working days, or split the calc: use this tool for "wall-clock guaranteed by," and a business-day calc for "follow-up scheduled by."
- DST transitions shift the local-clock face. On the day clocks spring forward, the local hour digits skip an hour; on fall-back, they repeat one. The calc still adds the SLA in UTC, so a 6-hour SLA always elapses 6 hours of real time. The local clock face on the deadline can read one hour later or earlier than naive subtraction would suggest. Confirm by reading the deadline aloud against the start.
- Negative SLA hours are rejected. The calc throws when given a negative number. To compute when an SLA started given the deadline, run the math by hand or invert the inputs: enter the deadline as the start and read the prior moment from your own subtraction. Zero hours is allowed and returns the start instant unchanged, which is occasionally useful as a no-op.
- Very large SLAs (720h, 8760h) work but the framing is suspect. A 30-day or 365-day SLA evaluates correctly: 720 hours from any start instant lands exactly 30 days later in UTC. For human-scale review windows that long, contracts almost always specify business days; double-check that "30 days" in your clause is calendar days before reading off this calc.
Frequently asked questions about SLA Deadline Calculator
Does this calculator pause on the weekend?
No. Every hour counts the same, including Saturday and Sunday. A 4-hour SLA starting at 22:00 Saturday lands at 02:00 Sunday, not Monday morning. For weekend-aware deadlines, switch to a business-day calculator.
Does it skip public holidays?
No. The calc has no holiday calendar. A 24-hour SLA starting on December 24 lands on December 25 with no exceptions. If your contract pauses on holidays, compute the working-day portion separately.
Does it know about business hours like 9-to-5?
No. The clock runs continuously from the start instant for the full SLA. To bake in a working day, denominate the SLA in business days and use a business-day calculator, or compute the working-hour portion separately.
How does it handle daylight saving time?
The hours are added in UTC, so the elapsed real time is always exact. The local clock face on the deadline can shift by an hour relative to the start because of a DST jump. The example for March 7 to March 8 in New York shows this: 6 UTC hours, but the local clock advances from 23:00 to 06:00.
What time zone should I pick for the result?
The result is rendered in the same zone you used for the start. Pick UTC when the start is a server timestamp, an IANA zone such as Europe/London when the contract is written in local terms, and convert with the timezone converter if you need the deadline in a third zone.
Can I enter a negative number of hours?
No. The calc rejects negative input with an error. To find the start moment given a deadline and an SLA length, subtract the hours yourself, or feed the deadline as the start and a related calc as a check.
Why does my contract deadline disagree with the result?
Most contract SLAs assume working days, business hours, or a holiday-aware calendar. This calc assumes none of those. If your clause reads "within 4 business hours during a 9-to-5 weekday," translate it to calendar hours before entering, or use the business-day tools for the working-time portion.
Glossary
- Service-level agreement (SLA)
- A contractual commitment to respond, restore, or resolve within a stated time window. SLAs typically distinguish response time (first acknowledgement) from resolution time (full fix).
- Clock-hour SLA
- An SLA denominated in continuous wall-clock hours, where every hour counts. This calculator implements clock-hour SLAs.
- Business-hour SLA
- An SLA denominated in working hours, typically 9-to-5 on weekdays with public holidays removed. The clock pauses outside business hours. Not implemented by this calc.
- Response time
- The interval between an incident being raised and the first human acknowledgement. Often the tightest SLA tier (15 minutes, 1 hour, 4 hours).
- Resolution time
- The interval between an incident being raised and the issue being fully restored. Usually a longer window (24h, 72h) and often denominated in business days for non-critical severities.