Resources
/
Getting started
/
Approver's Guide
Getting started
Approver's Guide
Review, approve, or reject the requests that need your sign-off.
Still stuck?
Our support team can walk you through it
Approver’s Guide
When a ticket needs your sign-off, Chekhub routes it to you as part of an approval chain and waits for your decision before the work moves forward. Some tickets carry their own Assigned and Closed Approval chains; others also have a separate Change Control with its own approval chain on top. This guide walks through both.
Before you start: you’ll only see a ticket here if you’ve been added as an approver on a chain attached to it — the ticket’s own Assigned or Closed Approval chain, or a Change Control’s Assigned or Closed Approval chain — individually, by role, or as part of a team. If a ticket you were expecting never shows up, check with your Chekhub administrator that you’re on the right chain and that your role has permission to view it.
Part 1: Approving a Ticket
A ticket’s Assigned Approval chain lives on the ticket itself — a stage in it routes to you before the ticket can move forward, and a separate Closed Approval chain can do the same before it’s closed out.
Find your pending approvals
1. Watch for the notification. When a ticket reaches a stage you’re part of, Chekhub notifies you that your sign-off is needed. Open the notification to jump straight to the ticket.


2. Or check your My Tasks list. Tickets waiting on you show up there, grouped under an Approve heading, so you don’t have to rely on notifications alone if you’re working through a backlog.


3. Confirm why it’s waiting on you. Open the ticket’s Approvals tab to see which stage is active and which approver group it’s waiting on — you alone, or you alongside others. The same tab shows the ticket’s Closed Approval chain, if it has one, sitting below — a second gate that clears separately, before the ticket can be closed.

Review the ticket information
You’ll see the ticket’s message, location, checklists, and other details as long as you have access to the ticket itself. If something you’d expect to see is missing, check with your Chekhub administrator that you have the right access, rather than assuming it doesn’t exist.

Complete anything required before you approve
1. Look for properties flagged as required. A template can require a property before your stage is able to clear. If one hasn’t been filled in yet, Chekhub flags it and won’t let the ticket move forward until it is.


2. Fill in what’s asked and move on. Optional properties can be left blank; required ones can’t. If you’re not the one with the answer, check who it’s required from before assuming it’s blocking you.
Approve, reject, or comment
The decision itself, and what happens to the ticket right after.
1. Approve. Approving clears your part of the current stage. If your stage combines approvers with And logic, the ticket still waits on the others; with Or logic, your approval alone clears the stage and moves the ticket forward.

2. Reject. Rejecting sends the ticket back to the requester rather than advancing it. Leave a comment explaining what needs to change — a rejection with no explanation just bounces back and forth.
3. Comment. Make a note on the ticket and tag any internal members needed to help inform your approval decision.

Part 2: Approving a Change Control
Some tickets — a Preventative Maintenance inspection with elevated risk, for example — carry a Change Control on top of the ticket itself. It has its own risk level and description, and its own Assigned Approval chain, separate from the ticket’s.
Spot the Change Control and what it’s asking
1. Look for the CC-CM card. A ticket that carries a Change Control shows it as its own card, sitting just above the ticket in your board — distinguished by its CC-CM number, a light highlight, and a badge showing how many approvers are on its chain.


2. Start with the risk level and description. What you can see here depends on the Change Control template — every Change Control carries a risk level and a description set by the template, and that’s your first read on what you’re being asked to approve. Its Assigned Approval stages sit alongside it, on the ticket’s Change Control tab, where the configuration can also be reviewed, and edited, right up until the first approval is submitted.

Work through a multi-stage chain
1. Stages run in sequence. A Change Control’s chain can have several stages, and each one only goes active once the stage before it clears. Approving doesn’t mean the Change Control is done — it means it moved to the next stage, which may wait on a different group entirely.
2. Clearing a stage hands off to the next one. Once your stage is approved, it’s marked cleared and the chain moves to the next stage below it, waiting on its own approvers.

Related reading: Navigating the Admin Panel — for how chains, templates, and roles get configured in the first place.
