There are two ways to run a listening event in the Perceptyx platform.
Both use the same platform, the same reporting, and the same action planning. What changes is who does the work. This article lists the practical differences so you can tell which model a given survey needs.
The two delivery models
Perceptyx-led Also referred to as managed or classic. Perceptyx designs the survey with you, builds and launches the event, configures reporting, and delivers an analysis of the results. | Self-led Also referred to as self-service or on demand. You design, build, and launch the event in the Listening Event Builder, configure reporting, and analyze the results in the platform. |
Responsibility by stage
| Stage | Perceptyx-led | Self-led |
|---|---|---|
| Design | Perceptyx | Customer |
| Build | Perceptyx | Customer |
| Launch | Perceptyx | Customer |
| In field | Perceptyx | Customer |
| Report | Perceptyx | Customer |
| Act | Customer | Customer |
Action planning is customer-owned in both models.
Feature availability
Available means generally available in that model. Conditions apply means available with a prerequisite, listed under the table. Not available means not available today.
| Feature | Perceptyx-led | Self-led |
|---|---|---|
| Event types | ||
| Point-In-Time events | Available | Available |
| Lifecycle events | Available | Conditions apply |
| Crowdsource events | Available | Available |
| 360 feedback events | Available | Conditions apply |
| Survey design | ||
| Question library, logic, and branding | Available | Available |
| Translations | Available | Available |
| Attributed and anonymous in one event | Available | Not available |
| Manager name in question text | Available | Not available |
| Launch and fielding | ||
| Email invitations and reminders | Available | Available |
| Microsoft Teams and Slack invitations | Conditions apply | Conditions apply |
| Survey Launch tool | Conditions apply | Not available |
| Lifecycle invitations to a third party | Available | Not available |
| Custom Lifecycle Sensor Logic | Available | Not available |
| Reporting | ||
| Advanced Reporting and Dashboard Builder | Available | Available |
| Cross-Survey Dashboards | Available | Available |
| Standard Point-In-Time benchmarks | Available | Available |
| Industry and regional benchmarks | Available | Not available |
| Automatic manager report accounts | Available | Conditions apply |
| Matrixed manager hierarchy | Available | Not available |
| Demographic added after the event closes | Available | Not available |
| Combined 360 and engagement reporting | Available | Not available |
| Analysis and action | ||
| Comment Copilot and Narrative Analysis Agent | Conditions apply | Conditions apply |
| Action planning | Available | Available |
| Consultant analysis and readout | Available | Not available |
Where conditions apply
- Microsoft Teams and Slack delivery is enabled by Perceptyx on request.
- The Survey Launch tool is available on request for Perceptyx-led events.
- Comment Copilot and Narrative Analysis Agent require a subscription and cover Point-In-Time events.
- Self-led Lifecycle events use the standard sensors available in the Listening Event Builder. Custom Lifecycle Sensor Logic means trigger rules beyond those standard sensors, such as conditional launch timing, custom data fields, and rehire rules.
- Self-led 360 feedback events use an initial setup completed by Perceptyx.
- Automatic manager report accounts require manager hierarchy to be enabled before the survey is built.
Design, build, and launch
| Perceptyx-led | Self-led | |
|---|---|---|
| Survey design | Perceptyx designs the item set with the customer. | The customer designs the event in the Listening Event Builder. |
| Survey build | Perceptyx builds the event. The customer reviews and approves. | The customer builds the event. |
| Pre-launch testing | A pilot test and formal approval are part of the plan. | The customer previews and tests the event. |
| Launch | Perceptyx launches on the agreed date. | The customer launches. An optional internal approval step is available. |
| Typical time from kickoff to launch | About 10 to 12 weeks for a full Point-In-Time program. | Days to a few weeks. |
| Translations | Perceptyx manages translation and provides a review window. | The customer manages translations in the builder. |
| Attributed and anonymous respondents | Can be combined in a single event. | An event is either all attributed or all anonymous. |
| Manager name in question text | Supported. | Not supported. |
Fielding and reporting access
| Perceptyx-led | Self-led | |
|---|---|---|
| Invitations and reminders | Built and scheduled by Perceptyx. | Built and scheduled by the customer. |
| Microsoft Teams and Slack invitations | Available. Perceptyx enables delivery on request. | Available. Perceptyx enables delivery on the account on request. |
| Survey Launch tool | Available on request. | Not available. |
| Lifecycle survey recipients | Any contact in the record, including a hiring manager or human resources contact. | The main person in the record row. |
| How Lifecycle surveys are triggered | Custom logic built and run by Perceptyx, covering conditional launch timing, custom data fields, and rehire rules. | Standard sensors in the Listening Event Builder. Sensors are rules based on attributed demographics that add people to an open survey automatically. |
| Data cleanup before reporting | Perceptyx removes leavers and partial responses. | Responses are reported as collected. |
| Manager report accounts | Created automatically from the hierarchy when the event closes. | Created by the customer, unless manager hierarchy is enabled before the build. |
| Manager hierarchy | Built and maintained by Perceptyx, including matrixed structures. | Enabled by Perceptyx before the build. Designed for non-matrixed structures. |
| Adding a demographic after close | Supported. Allow about three business days. | Not supported. |
Reporting, analysis, and support
| Perceptyx-led | Self-led | |
|---|---|---|
| Where results are viewed | Advanced Reporting. Cross-survey work is done in Cross-Survey Projects. | Advanced Reporting. Cross-survey work is done in Cross-Survey Projects. |
| Reporting site setup | Built and translated by Perceptyx, with training for the reporting audience. | The customer builds dashboards with the Dashboard Builder in Advanced Reporting. |
| Results analysis | Perceptyx consultants analyze results and present them to leadership. | The customer analyzes results in the platform. |
| Trending and cross-survey work | Perceptyx maps questions between surveys. | Configure Trend and Cross-Survey Dashboards, across closed events of either type. |
| Benchmarks | Loaded by Perceptyx, including industry, regional, and healthcare cuts. | A standard set is applied: Perceptyx overall average and 75th percentile, S&P 500 average and 75th percentile. |
| Combined 360 feedback and engagement reporting | Supported. | Not supported. |
| Action planning | Available. | Available, and enabled by default on new events. |
| Comment Copilot and Narrative Analysis Agent | Enabled per event after the survey closes. Subscription required. | Runs when a Point-In-Time event closes. Subscription required. |
| Support contacts | Program manager, consultant, platform services, and Customer Care. | Knowledge base and Customer Care. |
Common questions
Can we use both?
Yes. A Perceptyx-led annual survey alongside self-led pulses through the year is a common pattern.
Can we trend a self-led survey back to a Perceptyx-led one?
Yes. You can trend back to any closed event of either type.
Do results live in different places?
No. Both models report inside the same platform.
Can a survey switch models once it is underway?
No. Several settings, including manager hierarchy and demographics, cannot be changed once an event has been built.
Current as of August 2026.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article