Culture Index Survey Template
Measure day-to-day culture behaviors (trust, speaking up, clarity, follow-through) with a stable set of core questions you can trend over time. Set up: keep a consistent core, add a few demographics for safe team cuts, and choose a simple scoring rule you will repeat each wave. Privacy/quality guardrail: report only groups with n >= 10 and suppress smaller cuts so results never become individual diagnostics.
Trusted by 5000+ Brands
Who Should Take Your Culture Index Survey (and How to Segment Safely)
Use this section to set your respondent list and reporting cuts so you can share team-level results without exposing individuals.
- Default respondent set: Send to all employees by default; include contractors only if they work day-to-day inside your teams.
- Privacy and data-quality rule (starter default): Set a minimum group size for reporting (for example, minimum n >= 10) and suppress or roll up any cut below it.
Default respondent set
- Start with all employees (full-time and part-time). Keep the trend line clean across locations.
- Add contractors/temps only when relevant: include them if they attend team meetings, use the same tools, and experience the same managers.
- Exclude groups you cannot act on: if you cannot change their experience, do not measure it.
Safe segmentation (reporting cuts you can actually use)
- Role level: manager vs individual contributor.
- Tenure band: 0-6 months, 6-24 months, 2+ years.
- Org unit: department, then team (only if team n meets your minimum).
- Location: office site, country/region.
- Work arrangement: remote, hybrid, on-site.
Privacy rule: set a minimum group size (starter default: minimum n >= 10) and suppress any cut below it. Pair that with clear platform settings from your privacy, confidentiality, and reporting controls so your promise matches your configuration.
Invite wording that builds trust: say who can access raw results, when reporting happens, and how small groups get rolled up. Imperial College London uses the same practical approach in its staff survey confidentiality FAQs.
Transparency rule: disclose field dates, who ran the survey, and how you calculated response rate. AAPOR recommends this kind of disclosure to help people judge survey quality and trust the results in its Disclosure Standards.
Next: add your demographics, set your minimum n, and remove any segment you will not report.
Culture Index Questions by Dimension (Core + Optional Modules)
Use this section to lock a stable core question set so you can trend results and avoid rewriting your index every cycle.
- Core length (typical range): Keep about 20-35 Likert items as your always-on core, then rotate 5-10 optional items by quarter.
- Comment safety: Tell people not to name individuals in open-text answers, and follow open-ended question best practices when you set expectations and report themes.
"I understand our top priorities for the next 90 days."
Why it matters: Culture shows up in what people do every day. Priority clarity reduces churn, rework, and conflict.
When to use: Include in every run. If a team reorganized, add an N/A option for people between roles.
- "I can explain how my work connects to our strategy."
- "Leaders make decisions that match our values."
- "We say no to work that does not fit our priorities."
"I feel safe speaking up with concerns or mistakes."
Why it matters: If people do not speak up, you only see problems after they become incidents. Psychological safety predicts learning behavior in teams.
When to use: Always include. If you run this on small teams, report only when n meets your minimum.
- "People here listen without blaming when something goes wrong."
- "I can disagree with my manager without negative consequences."
- "When I raise a concern, I believe it will be handled fairly."
Edmondson's psychological safety research is a good reference point when you write and interpret speaking-up items.
"People treat each other with respect on my team."
Why it matters: Respect and fairness drive belonging and retention. They also change how people interpret tough feedback.
When to use: Include in every run. Add N/A for teams with limited interaction (for example, fully independent field roles).
- "I am treated fairly regardless of background."
- "I trust leaders to do what they say they will do."
- "Rules and policies are applied consistently."
"I get the information I need to do my job, on time."
Why it matters: Communication quality shows up as delays, duplicated work, and avoidable escalations.
When to use: Include in every run. If you support customers, add N/A for people without cross-team dependencies.
- "Decisions that affect my work are communicated clearly."
- "I know where to find the latest process or policy."
- "Meetings start with clear agendas and end with owners."
"My manager sets clear expectations and follows through."
Why it matters: Leadership behaviors shape norms. Follow-through is where values turn into day-to-day trust.
When to use: Include in every run. Report by manager level (not by named managers).
- "Leaders explain the reasons behind decisions."
- "My manager gives useful feedback that helps me improve."
- "Leaders hold themselves to the same standards as others."
"My team works well with other teams to get work done."
Why it matters: Collaboration problems hide inside handoffs. A culture index should surface friction across teams.
When to use: Include in every run. Add N/A for roles with minimal cross-team contact.
- "Other teams respond to us in a reasonable time."
- "We resolve conflicts directly, not through escalation."
- "Ownership is clear when work crosses teams."
"I have the tools and time I need to do quality work."
Why it matters: Enablement is a culture driver you can fix quickly. Low scores usually point to process, staffing, or tool issues.
When to use: Include in every run. Add N/A for new hires in their first two weeks.
- "Processes help me get work done (not slow me down)."
- "Workload is manageable most weeks."
- "When priorities change, we adjust timelines."
"I feel like I belong on my team."
Why it matters: Belonging changes how people participate. You will see it in meeting dynamics and willingness to ask for help.
When to use: Include in every run. Only report demographic cuts that meet your minimum n rule.
- "Different viewpoints are valued here."
- "I can be myself at work."
- "I have equal access to growth opportunities."
"I would recommend this organization as a great place to work."
Why it matters: Outcome items help you summarize culture in one line. They also anchor your index trend.
When to use: Include in every run. Keep wording unchanged so trends mean something.
- "I see myself working here in a year."
- "I feel motivated to do my best work."
- "Overall, I am satisfied with my job."
"What is one thing we should keep doing because it strengthens our culture?"
Why it matters: Strengths comments tell teams what to protect while they fix weak spots.
When to use: Include every time. Add a note: do not name individuals; describe behaviors and practices.
"What is one change we could make in the next 30 days to improve your experience at work?"
Why it matters: A 30-day frame pushes practical fixes (meeting norms, handoffs, tooling) instead of vague requests.
When to use: Include every time. Follow open-ended question best practices and block reporting for small groups.
Scale tip: keep your agreement labels consistent each wave (for example, Strongly disagree to Strongly agree). Likert-type items work best when options stay stable and easy to scan, as summarized in Koo and Yang's overview of Likert-type scales.
Next: pick your core questions, add N/A where needed, and freeze the core wording for your next 2-3 waves.
Setup Choices That Change Your Index (Pick One Approach)
| Decision | Option A | Option B | Default + when to switch |
|---|---|---|---|
| Agreement scale | 5-point Faster to answer; easier on mobile. |
7-point More nuance; better for deeper reads. |
Default: 5-point for monthly/quarterly pulses. Switch to 7-point when you need more spread and you run fewer waves. Use Likert scale options for employee surveys to pick labels you will keep stable. |
| Identity handling | Anonymous You do not collect direct identifiers. |
Confidential You can link responses to people, but restrict access. |
Default: Anonymous + minimum-n suppression (for example, minimum n >= 10) for any team cut. Switch to confidential only if you have a clear use case (for example, closed-loop support) and a written access rule. |
| Index weighting | Equal-weight Each dimension counts the same. |
Weighted Some dimensions count more. |
Default: equal-weight for a simple, repeatable index. Switch to weighted only if leaders agree to act differently on the weighted dimension this cycle. |
| Question strategy | Always-on core + rotating modules Short survey; steady trends. |
All questions every time More detail; longer survey. |
Default: always-on core + 1 rotating module per wave (5-10 items). Switch to all questions only for an annual deep-dive. |
Next: choose one option per row and document it so the next wave matches.
Launch Plan and Messaging (Cadence, Invites, Reminders, Length)
-
Set your cadence and field window
- Cadence (starter default): run a baseline now, then pulse quarterly. Use monthly pulses only when work is changing fast.
- Field window (starter target): keep the survey open about 5-10 business days and publish results as soon as practical (many teams aim for ~2 weeks). Pick a window you can repeat each wave.
-
Lock privacy rules before you write the invite
- Set minimum n (starter default): use minimum n >= 10 for team/location cuts; roll up anything smaller. Adjust up or down based on team size distribution and privacy risk.
- Remove risky cuts: do not report any demographic slice that will fall below your minimum n.
-
Choose demographics you will report (and nothing else)
- Start with: department, team, location, role level, tenure band, work arrangement.
- Stop at action: if a demographic will not change a decision, remove it from the survey.
-
Pilot for timing and confusion
- Send a pilot: use a small cross-section (often 10-20 people across roles). Ask them what felt unclear.
- Time target: aim for about 5-7 minutes. Measure actual completion time and cut items until you hit it.
-
Send a named-sponsor invite (copy/paste)
- Sender: use a senior leader employees recognize. Add HR/People Ops as the reply-to.
- Invite text: "We are running a Culture Index survey to measure what helps or blocks great work across teams. It takes about 5 minutes. We will report results only for groups that meet our minimum n (for example, n >= 10); smaller groups roll up. We will share results by [date] and each team will pick 2-3 actions."
- Bias guardrail: keep language neutral and avoid leading phrases that push a "good" answer. If you want a quick checklist, review common sources of response bias before you send.
-
Schedule reminders and close the loop
- Reminders (starter default): send 1-2 reminders. For a 7-day field window, a common schedule is day 3 and day 6.
- Keep it short: keep each reminder brief (often ~50-75 words) and consistent with the privacy promise.
- Reminder text: "Quick reminder: the Culture Index survey closes [date]. It takes about 5 minutes. We will share results by team where groups meet our minimum n (for example, n >= 10) and use them to choose actions in the next 30 days."
Response-rate hygiene: keep administration consistent across waves and define response rate the same way each time. Use AAPOR's Standard Definitions for response rates so your trend comparisons stay honest.
Evidence note: well-timed reminders can lift web survey participation; a randomized experiment shows measurable gains from reminder strategies in Cook et al. (JMIR) on internet survey reminders and incentives.
Next: paste the invite into your email tool, schedule reminders, and set your survey close date.
Scoring, Reporting, and Action Planning (Measure - Discuss - Act - Re-measure)
Use this section to calculate a culture index you can explain in one minute and turn into team actions in 30 days.
- Scoring approach: score by dimension first, then roll up to one overall index.
- Privacy guardrail: publish only minimum-n results and do not use scores for performance evaluation.
-
Define your index formula: score each dimension as a mean (1-5) or top-2 box (percent Agree/Strongly agree). Top-2 box = the share choosing the top two positive options.
-
Convert to a simple headline number: map your overall result to 0-100 for easy sharing (example: on a 1-5 scale, ((mean - 1) / 4) * 100). Start with equal-weight dimensions.
-
Handle N/A and missing data: exclude N/A from the denominator for that item, then compute the dimension from remaining items. If you need a completeness rule, use a starter threshold (for example, require ~50% of items answered to score a dimension for a person) and keep it consistent across waves.
-
Set reporting rules: publish any team/location/role cut only when groups meet your minimum n (starter default: minimum n >= 10); suppress smaller cuts and roll up. Do not share any individual-level scores or lists of respondents.
-
Add disclosure notes to every report: show field dates, who was invited, how you calculated response rate, and what changed since last wave (question changes, org changes, segment definitions). Government survey programs document methods the same way in reports like the FEVS technical and methods documentation.
-
Run the action loop: pick 1-2 lowest dimensions plus 1 recurring comment theme. Choose 2-3 team actions, assign an owner, set a due date, and re-pulse on a practical timeline (often ~4-8 weeks) using the same core items.
Next: create a one-page results view (overall + dimension scores + top themes) and schedule team action discussions within 2 weeks.
Frequently Asked Questions
How many questions should a culture index survey have?
Many teams use a short core of about 20-35 Likert items across key dimensions, plus 2 open-text prompts. Keep the core unchanged so your trend line stays meaningful, then rotate optional modules quarterly.
How do I calculate a culture index score from Likert questions?
Score each dimension first using either a mean (average 1-5 or 1-7) or a top-2 box (percent in the top two positive responses). Then average the dimension scores into one overall index; start with equal weights and only add weights if you will act differently on the weighted dimension.
What minimum group size should I use for team-level reporting?
Set a minimum group size and suppress anything smaller; a common starter default is minimum n >= 10 for team cuts, but you should adjust based on team sizes and privacy risk. If teams are smaller, combine teams, roll up to department, or report only the overall organization score.
Should the culture index survey be anonymous or confidential?
Anonymous means you do not collect direct identifiers; confidential means you can link responses to people but limit access. Use anonymous collection plus minimum-n suppression for reporting, and never use comments to try to identify individuals.
How often should we run a culture index pulse survey?
Run a baseline now, then pulse quarterly as a common starting cadence. Switch to monthly pulses only during rapid change, and use an annual deep-dive when you need a longer module set; keep timing consistent and adjust reporting groups if your org structure changes.
Can we include contractors or temporary workers in the culture index?
Include contractors or temps if they work inside your day-to-day teams and experience the same managers and norms. Segment them separately when possible, and do not report their results if the group falls below your minimum n rule.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED