Trigger a Manual Lifecycle Survey

There are two ways to send out Lifecycle Surveys in 15Five: automatically, based on a specific event like an employee’s hire date, and manually, which gives you control to launch a survey at the time that makes the most sense for your organization. This article walks you through how to manually trigger a Lifecycle Survey—ideal for collecting feedback at key milestones such as promotions, project completions, or unscheduled departures.

Access and availability

⛔️ Required access to the Lifecycle Surveys Dashboard.
👥 This article is relevant to Account admins.
📦 This feature is available in the Total Platform, Legacy Perform, and Engage pricing packages.


How to Manually Trigger a Lifecycle Survey

  1. Click Surveys in 15Five's main, left-hand navigation, then select Lifecycle.
    Engagement.png
  2. Scroll down to the "Surveys" section and locate the survey you’d like to send manually. Then, click the ellipsis (•••) next to the survey name and select "Send manually."
    ManualTriggerSurvey.png
  3. Choose the employee(s) you want to include in the survey, then click Send.
    SendManualWorkflow.png
  4. After clicking Send, a notification will be sent to participants and/or their managers via email, based on the questions configured in the survey. All participants have 14 days to complete the survey before it expires.


Manage Surveys at a Glance

  • Filter by type: Instantly switch between Triggered and Manual surveys.

  • Quick context: See schedule details, next send date, upcoming audience, and response rate (including recent responses) right in the list.

  • Clearer controls: A new Pause/Resume option replaces the old on/off toggle.

When viewing survey participants, you can now quickly see:

  • Next send date

  • Participant’s status

  • Response rate

  • Quick actions like Re-open, Nudge, and View results—all available from a drawer view.

Preview Survey Templates

On the survey overview page, you can now preview both employee and manager questions before sending.

 

Was this article helpful?

We're sorry to hear that.

Please tell us why →