Resources
/
Tickets
/
Alerts and Escalations
Tickets
Alerts and Escalations
Make sure the right people hear about issues fast, and that urgent work moves up the chain.
Still stuck?
Our support team can walk you through it
Alerts and Escalations
Learn how Chekhub flags work that needs attention: SLA timers on tickets, and multi-stage approval chains and change control that route work to the right person when the first one can't act.
The moment something's at risk of slipping, whether it's a ticket nearing its SLA target or an approval stuck at a stage, Chekhub raises a flag, so it never sits unnoticed until it's too late.
Timers: a ticket's SLA tab tracks live countdowns against each of its five statuses: Pending, Assigned, In Progress, Completed, and Closed.
Escalation: approval chains and change control route work through ordered stages. Each stage can require multiple approvers at once (joined by And) or offer backup alternatives (joined by Chain, an OR).
Delivery: exception alerts (overdue, missed, rejected) go out immediately by email. Configure this in your notification preferences.
Reading a Ticket's SLA Tab
Every SLA policy that applies to a ticket lives in one place: the ticket's own SLA tab.
Open the ticket, then click the SLA tab: a small count badge on the tab itself shows how many policies apply — no need to open the tab just to check.
Read the table: one row per policy that applies to this ticket, one column per ticket status — Pending, Assigned, In Progress, Completed, and Closed.
Read each cell: a green ✓ Done means that status's target was met, No SLA means this policy doesn't set a target for that status, and an orange countdown chip (e.g. "8m left") is a live clock still running, with a progress bar underneath showing percent of target used. Once a target is missed, that cell turns into a red ⚠ Breached by <1m chip with a filled red progress bar past 100%.

The SLA tab on a ticket with two applicable policies — one from the project, one from the org — each tracked against the same five ticket statuses. 
The same ticket a few minutes later: Pending's clock is still running, while Assigned, In Progress, Completed, and Closed have all breached their targets. Check the Source column to see where a policy comes from — a project-level policy and an org-level default can both apply to the same ticket at once.
Pause SLA when work is legitimately blocked: the button in the top right stops this ticket's running clocks until it's resumed.
Use the ⋮ menu for a one-off exception: each status's countdown chip carries its own overflow menu with a single action, Override SLA — a way to adjust that target for this specific ticket without editing the policy itself.

The ⋮ menu next to a live countdown chip, showing its one action: Override SLA.
A ticket can carry more than one policy — nothing forces a single ruleset, so a stricter project policy and a looser org default can both be tracked side by side. All five status clocks start counting down together from when the ticket is created, rather than waiting for the ticket to actually reach each status — that's why a ticket can show Assigned, In Progress, Completed, and Closed as already breached while it's still sitting in Pending.
Building an Approval Chain
Approval chains are the reusable building block behind change control sign-off — routing work through the right people, in order, before it can proceed.
Open Approvals: from the Admin Panel, click Approvals in the top navigation bar (alongside SLA Policies, Change Control, and the other admin sections).

Approvals sits in the Admin Panel’s top navigation, alongside SLA Policies and Change Control. Find the Chains panel and click + ADD to start a new chain.

The Chains panel on the Approvals tab — every chain the organization has built lives here. Name it, describe it, and set its Locations: a clear name (e.g. "Capital Project Approval"), a Description of when to use it, and which locations it applies to.

A new chain starts with a name, description, and the locations it applies to—stages come next. Add a stage: in the Stages section, select a pre-existing chain to prepopulate the stages, or add a new stage to build the chain from scratch.
Add approvers to the stage: pick members from the dropdown. Add a second approver alongside the first and Chekhub joins them with And — both must approve for that path to clear.
Add a Chain for backup coverage: click + CHAIN to add a second, alternate set of approvers to the same stage — now either the original approver(s) or the new chain can clear it. ✕ CHAIN removes one.
Repeat for additional stages, then save: reorder stages with the up/down arrows if needed, then click the checkmark. The chain is now available on tickets and change control templates.

Stage 1 requires Don Smith and Diego Ramirez; Stage 2 needs only Grace Kim. Either stage could add a “+ CHAIN” backup path.
A ticket sits in Pending until every stage in its chain clears; an Assigned-approval chain moves it to Assigned, a Closed-approval chain moves it from Completed to Closed. Existing chains live in the Chains panel once they've been created.
Change Control
Change control routes electrical, mechanical, and other higher-risk work through its own tab on the ticket that kicks off once the ticket's Approvals finish.
Open a ticket's Change Control tab: it sits alongside the ticket's Approvals and SLA tabs.

The Change Control tab on a saved ticket — same And/Chain-OR mechanic as Approval Chains: Stage 1 (Manager Or Admin), Stage 2 (Management Group And Electrical Operations). Each stage also carries its own Instruction field — custom text the approver sees, like "Please approve the following risk level 1 electrical maintenance." Set the Risk Level: five levels, color-coded from Risk Level 1 (highest, dark red) down to Risk Level 5 (lowest, green). It's a classification field on the ticket — changing it doesn't swap in a different set of approval stages; the stages below stay the same regardless of which level is picked.

The Risk Level dropdown—five levels, dark red (highest) to green (lowest). Build the approval stages — for Assigned Approval and Closed Approval separately: the same And/Chain-OR mechanic as Approval Chains, and each track can reuse a pre-existing chain or be built stage-by-stage from scratch with +STAGE. Multiple approvers in a stage are joined by And, alternates by Chain (Or).
Choose what ticket information travels with the change: checkboxes for Message, Locations/Assets, Participants, and more, alongside Internal/Customer/Vendor Team fields.

Assigned Approval and Closed Approval are two separate tracks — this one's still empty, offering the same choice as Approval Chains: "Use a pre-existing chain or add a new stage."
Note: Change Control shares its whole approval mechanic with Approval Chains — same And/Chain-OR logic, same reuse-or-build-from-scratch choice, and the same Assigned/Closed split described in the Approval Chain section above. It's independent of Risk Level, though: Risk Level is just a label on the ticket, not a switch that pulls in a different pre-built chain.


