Campaigns for Employee Events
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2026 07:00 AM
Hi everyone! Does anyone use campaigns (Content Experiences) for mass employee events like yearly policy/handbook signatures? We’d like to use a campaign for this but were recently told by a SN rep that any content in a campaign schedule with a “to-do” trigger/stage type cannot be sent more than once to an employee, even if we were to clone and resend the campaign.
We’d really like to use the “to-do” trigger/stage type so employees could view instructions or receive an email first before getting their assigned campaign tasks (looking at 1-3 bundles of content in a single campaign).
We anticipate that some employees will not complete the campaign on time and if we cannot clone and resend the campaign or task, we will need to manually keep recreating and resending the campaign content to employees until they have completed them.
Has anyone has success using campaigns for something similar and can share their work around?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago - last edited 4 weeks ago
Hi @KennaK ,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
You can use Content Experiences for policy acknowledgements and employee campaigns. However, the key consideration here is the difference between recurring campaign stages and to-do completion triggers.
ServiceNow documentation identifies Recurring as the trigger for date-based repeatable content, including yearly campaigns. A To-do Completion trigger makes the next stage available when an employee completes a specific to-do item.
I would recommend evaluating the following approach:
Use a Recurring trigger with Yearly frequency for the annual policy acknowledgement campaign.
Keep the initial instructions or announcement in an Immediate stage.
Configure the acknowledgement tasks as To-do content in the relevant campaign stage.
Use separate stages for different groups of tasks if employees must complete them in sequence.
Track employee completion through the campaign targets and to-do status.
For employees who miss the deadline, evaluate a separate recurring campaign cycle rather than assuming that cloning the campaign will reset previously delivered to-dos.
One important point: ServiceNow documentation confirms that Dynamic stages trigger content only once and recommends Recurring triggers for annual repetition. However, it does not explicitly establish that cloning a campaign resets the one-time delivery restriction for an employee. I would validate this behavior with ServiceNow Support before designing a manual resend process around cloning.
References:
Hope you find this helpful!