[object Object]

A Change Advisory Board is supposed to lower risk, not lower velocity. Freshservice gives you the primitives. Whether your CAB becomes a bottleneck or a control comes down to how you model approvals.

Three change categories, three workflows

  • Standard: pre-approved templates, no CAB needed
  • Normal: CAB approval, asynchronous via the agent portal
  • Emergency: post-implementation review, fast-track approver

Most teams skip Standard because nobody curates the catalog. Standard changes should cover 60%+ of volume. Identify your top 20 recurring changes and template them this quarter.

Approval graphs, not chains

Freshservice supports parallel approvals. Use them. Security and Application Owner can approve in parallel; you do not need them sequential. Set the rule:

Approval policy: "Normal-Production"
Approvers: [Security Lead, Application Owner, Infra Lead]
Mode: parallel
Required: 2 of 3

SLA the approval, not just the change

Set an SLA on time-to-first-approval. If a change request sits unapproved for 48 hours, escalate to the approver’s manager automatically.

Bypass rules that hold up under audit

Emergency changes bypass CAB but require post-implementation review within 5 business days. Use a workflow that auto-creates the PIR ticket on emergency change closure and assigns to the change manager.

// Workflow Automator action
{
  "trigger": "change_closed AND type == emergency",
  "action": "create_ticket",
  "template": "post_implementation_review",
  "due_in_days": 5
}

CAB meeting hygiene

Drive CAB meetings off a saved view filtered by status: awaiting_approval AND scheduled_window: this_week. Anything older than the meeting prior gets escalation flag.

What to do this week

Move your top 20 recurring changes to Standard templates, switch sequential approvals to parallel where allowed, set the 48-hour approval SLA, and wire the auto-PIR for emergencies.

[object Object]
Share