CAB Workbench

[Alan_Mou]

In the CAB workbench - I click on refresh agenda to get the list of changes and start the meeting.   But if someone submits a change late.  The agenda is been automatically updated when during the approval ( there must be some sort of refresh happending in the back ground)  .    but this means the agenda is been updated and with tickets that are late.    

why is this and how to prevent it as it quite disruptive 

[pavani_paluri]

Hi @Alan_Mou ,

What you’re seeing in CAB Workbench is expected behavior: the agenda isn’t “frozen” once you hit *Refresh Agenda*. The system keeps listening for changes in the background, so if someone submits a new change request that meets the agenda criteria, it gets pulled in automatically. That’s why late tickets suddenly appear mid‑meeting — the agenda is being refreshed behind the scenes.

CAB Workbench is designed to keep the agenda current with the latest change data.
The “refresh agenda” button gives you a snapshot, but the underlying logic still updates when new qualifying changes are submitted.
This is disruptive if you want a fixed agenda once the meeting starts.

How to prevent it
Lock the agenda before the meeting: Instead of relying on the live agenda, generate the agenda report and save it as a static snapshot. Use that snapshot during the meeting.
Use filters with date/time cut‑off: Add a condition so only changes submitted before a certain time are included. That way, late changes won’t appear.
Governance process: Communicate to change managers that submissions after the agenda refresh deadline will roll to the next CAB.
Customization option: Some organizations customize CAB Workbench so the agenda refresh only happens manually, not automatically, once the meeting is in progress.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P