HRIS data for an employee engagement survey: what to prepare

Why does HRIS data matter for an employee engagement survey?

An engagement survey is only as accurate as the employee list behind it. Questions, timing and communication get most of the planning, but four outcomes are settled by the data before anyone answers a question.

• Who gets the survey

  The employee list is the audience. A leaver still marked active lowers participation; a joiner missing from the file never gets an invitation.

• Who sees what

  Manager dashboards follow the manager field. A wrong or missing manager puts a team's results in front of the wrong leader, or in front of nobody.

• How results cut

  Every report filter is an attribute on the employee record. If plant or company is not in the data, nobody can compare plants or companies later.

• Whether small groups stay protected

  Results only open for groups at or above the anonymity threshold. Over-split or badly coded groups leave more scores hidden than they need to be.

In a large organization the list usually comes from an HR system through an integration, which is why the same questions come up on almost every enterprise evaluation: what fields do you need, how do managers work, and what happens when our data is messy. This guide answers each one.

The HR data questions enterprise buyers ask most

We counted the data questions prospects raised on about 250 enterprise demo calls (organizations of 1,000 or more employees) against about 200 calls with smaller companies. Every one of them comes up far more often at enterprise scale.

How much a group average can hide

On CultureMonkey's benchmark, engagement runs from 7.67 in Europe to 8.22 in LATAM, and from 6.98 in education to 8.29 in hospitality. A group that spans regions or industries can hide gaps that size inside one average, and a report can only split by country, site or business if those fields are in the employee data.

See the full regional and industry benchmarks.

Which employee fields does an engagement survey need?

Seven fields are required for every person in CultureMonkey: external ID, employee ID, first name, last name, email, team and location. The rest depend on the questions you want the results to answer.

Send only what you will use; the fields not to send are listed further down. For mapping each field step by step, see the Help Center guide to HRIS field mapping.

Which employee ID should the survey match people on?

The identifier decides whether a change in your HRIS updates a person or creates a second copy of them. Get it right once and every later sync lines up.

• Use the number HR never reuses

  An employee number or HRIS worker ID stays with a person through name changes, marriages, email changes and transfers. Matching on it means those changes update the record instead of creating a second one.

• Do not use email as the key

  Emails change when people change names, move to another company in the group or switch domains after an acquisition. CultureMonkey falls back to email only when no external ID is present, and that fallback is where duplicates come from.

• Keep the same ID across companies

  In a group with several HR systems, prefix IDs by company if the number ranges overlap, so two people on different systems never collide.

• Do not recycle IDs for rehires

  If your HRIS gives a returning employee their old number, they reactivate with their history. If it gives them a new one, they start a new record. Decide which you want before launch.

Why does manager data have to be right?

The manager field turns a flat list into an organizational hierarchy, and that hierarchy decides which results each leader sees. It is also the field most often wrong in HR data, because nothing in payroll depends on it.

• One manager per person

  CultureMonkey builds the hierarchy from one manager on each employee. Dotted-line and matrix reporting are not modeled, so pick the solid-line manager: the person who does the review and approves leave.

• Managers must exist as employees

  A manager is linked by their own employee ID or email, so every manager must also be in the file. Load managers first, or in the same batch as their reports.

• The top of the tree has no manager

  The CEO or the head of each company has an empty manager field. A blank manager anywhere else puts that person at the top and detaches their team.

• Small teams roll up

  Manager dashboard invitations go to managers with 3 or more reports, and results only open above your anonymity threshold, 5 by default. A manager of two sees their team inside their own manager's results.

How wrong does it get? In one enterprise rollout we supported, about 2,970 of 3,210 employee records, 92.5%, had the right manager at the first upload. The other 240 or so were fixed in the HRIS before launch. Left alone, that would have put roughly one team in thirteen under the wrong leader's results.

CultureMonkey rebuilds the current tree every night from the manager field. See how results by reporting line work once it is in place; the setup steps are in the Help Center under manager relationships and importing managers.

How should teams, sites, business units and companies be coded?

Four layers describe where someone sits. Each person has one of each, and each becomes a filter on every report and a way to scope who sees what.

If your team names carry company or site prefixes to keep them apart, such as "Retail Support" and "Corporate Support", that is the sign a business group or location should carry that part instead. Groups with several companies can read more in multi-entity employee surveys and data segregation for business units.

Which custom attributes are worth adding?

Anything not in the standard fields can travel as a custom attribute. Create it in CultureMonkey first, then map it from the HRIS. Once at least three employees hold a value, it works as a report filter and grouping like any other.

Employee type in CultureMonkey takes fixed values: Regular, Part-time, Shiftworker, Probation or Outworker. Pay type, FLSA status and contract type therefore belong in custom attributes, which take whatever values your HRIS uses. To create them, see custom employee attributes.

How do you include employees without a work email?

Plants, stores, warehouses and hospitals often have many people with no company email. They belong in the data like everyone else, with two adjustments.

The stable employee ID keeps each of them matched without an email address, and a mobile number on the record lets invitations go by SMS or WhatsApp. People can also answer through a QR code or a shared kiosk. See frontline employee surveys for how it works, and the Help Center for setting up SMS, WhatsApp and QR codes.

Should you use an HRIS connector, SFTP, an API or a CSV?

All four routes land the same fields in the same place. Choose by what your HR and IT teams already run.

The connector pages show how each HR system's own structure maps across: Workday, SAP SuccessFactors, Oracle HCM, UKG and ADP. For any other system, use SFTP employee sync or the Employee API, and see SFTP vs API to choose between them. Every route only reads into CultureMonkey; none writes back to the HRIS.

How full and update files behave, how often each route syncs and how to fix a failed sync are covered in the Help Center: connecting an HRIS, importing employees from a file and fixing HRIS sync issues.

How long does HRIS setup take, and who does what?

With CultureMonkey, an enterprise rollout typically takes about five weeks from kickoff to the first survey, including the HRIS integration. Most of the elapsed time is your team's, not the software's: access approvals, fixing data at the source and agreeing who sees what.

Two things shorten it. Start the data work before contracts are signed, since agreeing the fields and the employee ID needs no system access. And give one person on the HRIS side the job of fixing what the first sync finds.

Which HRIS fields should you not send?

Data protection law, GDPR included, expects you to send only what the purpose needs, and security reviews will ask why each field is there. An engagement survey needs far less than your HRIS holds.

For how CultureMonkey stores and protects what you do send, see security and compliance.

What should you check in the employee data before launch?

Run these ten checks on the final employee list a week before launch. Most take minutes in a spreadsheet, and each one prevents a problem that cannot be fixed once responses are coming in.

After the first sync, a quick spot-check of headcounts and a dozen named records catches most of what is left; the Help Center walks through it in checking an HRIS import. For the people side of launch, see the enterprise survey rollout plan.

What happens to survey results when the organization changes?

Reorganizations, transfers and acquisitions do not wait for the survey calendar. Five rules keep results comparable while the structure moves.

Results only open for groups at or above your anonymity threshold, 5 by default and never below 3, so a reorganization that splits teams very finely leaves more scores hidden until those groups grow.

FAQs