Assessment campaigns
Where campaigns run — often started by a playbook, still privacy-gated.
A campaign is a round of questionnaires — baseline or short pulse. The first launch is carefully human-reviewed; later **recurring pulses can be playbook-scheduled** so you are not rebuilding every wave by hand.
Answers still feed signals, then Decision Packs and risks. You only see response counts, never who said what. Groups below the five-person floor cannot be launched for reporting.
Delivery uses in-app, Slack, Teams, or email fallbacks as configured — without turning campaigns into free-form outreach.
For example
After go-live, the recurring_pulse playbook drafts the next Logistics pulse; the shared service confirms or lets auto-run apply under Tier 2 policy in the mock.
Worth knowing
- Campaign
- One round of a questionnaire sent out to employees, from launch until it closes.
- Playbook
- A versioned rule that can start work from a schedule, threshold, or event without a blank-page rebuild.
What you can do here
- 1Review or launch a campaign from the builder when needed.
- 2Watch response counts (never individuals).
- 3Prefer playbook-driven cadence for recurring pulses.
- 4Pick instruments only from the approved library.