Understanding the Entity, Project and Survey structure
A quick overview of how EngageRocket organises your data before you set up your first survey.
Before creating your first survey in EngageRocket, it helps to understand how the platform organises everything. EngageRocket uses a simple three-level structure, Entity, Project, and Survey, and knowing how these relate to each other will save you time and help you get cleaner data.
The three levels explained
1. Entity
Your Entity is your organisation's account in EngageRocket. Think of it as the main container that holds everything, all your projects, surveys, employee data, and permission settings. You will typically only have one entity, though some organisations with multiple subsidiaries may have more.
2. Project
A Project is a folder that holds multiple related surveys. For example, you might create a project called 'Pulse Check 2025' to house all your quarterly surveys for that year. Grouping surveys inside one project is what enables automatic trend comparisons, so your dashboard can show you how scores have shifted over time.
3. Survey
A Survey is a single round of data collection within a project. For example, inside 'Pulse Check 2025' you might run 'Q1 Pulse Survey', 'Q2 Pulse Survey', and so on. Each survey collects responses and feeds results into the shared project dashboard.
💡 Important for trend tracking: Always keep related surveys inside the same project. The platform can only compare results across surveys that share the same project. Creating a new project for each survey round will break your trend data.
The three project types
When you create a project, you will need to choose one of three types. Here is a quick guide to help you decide:
1. One-off
A single-instance survey conducted once. This is the recommended option for most organisations, it gives you the most flexibility with timing while still supporting trend comparisons within the project.
2. Frequency
A recurring survey that runs automatically at a set schedule, for example, every two weeks or every month. Useful if you want fully automated recurring surveys on a fixed cadence.
3. Milestones
Automated surveys triggered by key dates in an employee's lifecycle, such as 30, 60, or 90 days after their start date. Ideal for onboarding and probation feedback.
💡 Not sure which to choose? EngageRocket recommends One-off for most use cases. It is more flexible and still supports the full trend comparison features.
Confidentiality Threshold
To maintain trust and protect anonymity, you can define a minimum number of responses required before results are shown. EngageRocket recommends a threshold of at least 3 responses to uphold data privacy and foster honest feedback.

Something not working?
- I created separate projects for each survey round and can't see trend comparisons — Trend data is only generated across surveys within the same project. Surveys in different projects cannot be merged retroactively. Contact our support team to discuss your options.
- I'm not sure which project type I need — Start with One-off. You can always add more surveys to the same project and trends will build automatically over time.
Still Need Help?
If you have questions about how to structure your projects and surveys, Reach out to us at support@engagerocket.co and we'll be happy to assist!