Skip to main content

Distributions

A distribution is the campaign that pushes a published policy to a defined set of employees. Distributions are how a policy moves from "exists in the library" to "needs to be acknowledged by Friday."

/policies/distributions is the standalone hub; the same view appears embedded in a policy's detail page scoped to that one policy.

What the campaign list shows​

Per row: policy title, recipient count, acknowledgement progress bar (% acknowledged of total), deadline, and contextual actions.

Filters:

  • Status — active, paused, completed, cancelled
  • Policy — narrow to one policy

Creating a campaign​

The create sheet captures:

  • Policy — pick from published policies
  • Recipient targeting — by department, site, client account, LOB, role, or custom employee attributes (mix-and-match, AND-combined)
  • Quiz requirement — whether recipients must pass the policy's quiz before they can acknowledge
  • Acknowledgement deadline — when the campaign expects sign-off
  • Language preference — for bilingual policies, which version each recipient gets (typically derived from the employee's preferred locale)

Per-recipient view​

The campaign detail sheet lists every targeted employee with their current status (pending / read / acknowledged / quiz_failed / overdue) and controls for:

  • Sending a reminder
  • Extending the deadline
  • Closing or cancelling the campaign

Auto re-acknowledgement on major versions​

When a policy publishes a major new version, the distribution engine automatically creates re-acknowledgement campaigns for every employee in active distributions of that policy. Minor / editorial changes do not trigger re-acknowledgement — the existing acknowledgement carries over.

This is the bridge that keeps published material and recorded acknowledgements aligned without manual intervention.