Interpret the timestamp in the SLA time zone
The received date is treated as local wall time in the selected IANA zone. The browser time zone does not override the policy.
A ticket arrives late on Friday. The SLA clock follows London business hours, Monday is a holiday, and an approved customer wait pauses the timer. Adding the target to the received timestamp produces the wrong deadline.
Calculate first-response and resolution deadlines against the hours that actually count. The result shows when the clock starts, which windows contribute time, and what was skipped.
A four-hour target does not mean four elapsed hours when the clock pauses after 5 pm, skips a holiday, or excludes an approved wait.
These are the service windows that contributed time to the resolution deadline.
This result is a planning check, not a legal interpretation of an SLA. Confirm pause rules, holiday calendars, response definitions, and escalation terms against the governing policy.
The calculator uses one deterministic sequence. It does not infer a policy from the priority label.
The received date is treated as local wall time in the selected IANA zone. The browser time zone does not override the policy.
Closed hours, unselected weekdays, and listed holidays add calendar time without consuming the target.
The output shows the counted target, approved pause, closed time, clock start, and the service windows used for resolution.
The output is only as accurate as the policy entered. This tool does not decide whether a response qualifies, whether a pause was permitted, which holiday calendar governs a customer, or whether an existing deadline may be changed.
Those decisions belong in the operating policy and the ticket record. The calculator makes the time arithmetic visible so an operator can compare the system deadline with the stated rules.
A correct timestamp does not repair an SLA that applies one commitment to every class of work or a dashboard that cannot explain why a clock paused.
See why time zone, weekly schedule, and fixed historical deadlines belong in the policy.
Keep distinct response and resolution commitments inside one triage queue.
Connect deadline status with ageing, backlog, classification, and the work still blocked.
Follow work from intake and triage through ownership, plugin execution, and the audit trail.
Business hours are arithmetic. Policy definitions decide whether that arithmetic belongs on the ticket.
No. The calculation runs locally in the browser. Ticket dates, schedules, holidays, priority targets, and pause durations are not submitted to Latch.
The calculator counts time only inside the selected daily window on the selected business days. Dates listed as holidays contribute no service time. The clock resumes at the next available business window.
Yes. It uses the selected IANA time zone and the time-zone data available in the browser. A local time that does not exist because the clocks move forward is rejected instead of silently shifted.
The entered pause duration is excluded from both SLA clocks. It extends each deadline by that many counted service minutes. The calculator does not model separate pause and resume events.
No. It is a planning and verification tool. Confirm the governing policy definitions, holiday calendar, pause eligibility, escalation rules, and any existing ticket deadline before relying on the result.
See how Latch keeps triage, operator decisions, plugin actions, approvals, execution results, and the audit trail on one ticket.