Skip to content
English
  • There are no suggestions because the search field is empty.

Understanding the Entity, Project and Survey structure

A quick overview of how EngageRocket organises your data before you set up your first survey.

⚠️ Who is this article for? This article is for all EngageRocket users — including Entity Admins and anyone new to the platform — who want to understand how the system is structured before setting up surveys. If you are ready to create your first project, see How to create a survey project.

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 than one.

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 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 between three types: One-off, Frequency, and Milestones. EngageRocket recommends One-off for most use cases — it is the most flexible and still supports the full trend comparison features.

For a full breakdown of each type and how to configure them, see How to create a survey project.

Something Not Working?

  • I created separate projects for each survey round and can't see trend comparisons Likely cause → Trend data is only generated across surveys within the same project. Surveys in different projects cannot be compared or merged retroactively. Action → Contact support@engagerocket.co to discuss your options.

  • I'm not sure which project type I need Likely cause → The differences between project types are not always obvious upfront. Action → Start with One-off. You can always add more surveys to the same project and trends will build automatically over time. For a full comparison of all three types, see How to create a survey project.

  • I accidentally created a new project instead of adding a survey to an existing one Likely cause → It is easy to create a new project when you intended to add a survey inside an existing project. Action → Do not add any surveys to the new project. Delete it, then navigate to your existing project and create a new survey from there. If you have already launched a survey in the wrong project, contact support@engagerocket.co before making any changes.

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.