Temperature Check Survey Template (Employee Pulse)
Run a 3-5 minute employee temperature check you can repeat weekly or biweekly. Keep a stable core for clean trends, rotate one optional module when you need a deeper read, and close the loop with clear owners and dates.
Trusted by 5000+ Brands
Temperature Check Question Library (Core + Swap-In Modules)
"I understand what is expected of me this week."
Why it matters: Clarity moves quickly and is a common root cause of missed deadlines and stress.
When to use: Core question. Keep it unchanged so you can trend week to week.
"I know the top priorities for my team this week."
Why it matters: Priorities shift; this catches misalignment early before it becomes rework.
When to use: Core question. Pair with an open-text prompt on blockers.
"My workload is manageable for the next 1-2 weeks."
Why it matters: Workload is a leading indicator for burnout and quality issues.
When to use: Core question. Trend it; react to sustained declines, not one-off dips.
"I can complete my work within reasonable working hours."
Why it matters: This separates "busy" from "unsustainable" and is easier to act on.
When to use: Core question. Use with a workload module if scores drop.
"I feel supported by my manager to do my job well."
Why it matters: Manager support often predicts whether issues get solved locally or escalate.
When to use: Core question. Use carefully for small teams to protect anonymity.
"In the last week, I received recognition that felt meaningful."
Why it matters: Recognition is a fast-moving signal for morale and retention risk.
When to use: Core question if recognition is part of your culture goals; otherwise rotate quarterly.
"I have the tools and access I need to do my work."
Why it matters: Tools and access are fixable. This question points you to process and systems work.
When to use: Core question. Track trends and pair with an open-text blocker prompt.
"I can raise a concern or risk without negative consequences."
Why it matters: Psychological safety affects reporting of quality issues, safety risks, and ethical concerns.
When to use: Core question if you want early-warning on risk; otherwise run as a monthly module.
"Overall, I feel positive about work right now."
Why it matters: A simple "overall" sentiment item helps you spot broad swings fast.
When to use: Core question if you keep the same wording and response scale each wave. If you prefer a 0-10 wellbeing item instead, swap this question (and keep it 0-10 every wave); subjective self-report trends work best with consistent response scales (see the OECD's Guidelines on Measuring Subjective Well-being).
Use one rating scale across your core questions and do not change it between waves. If you use a 0-10 overall sentiment item, keep it 0-10 every wave and avoid adding multiple different scales in the same short pulse.
"What is the #1 thing making it harder to do great work this week?"
Why it matters: This turns scores into something you can fix (process, staffing, tooling, decisions).
When to use: Include in every wave if you have capacity to review and summarize themes.
"Start / Stop / Continue: What should we start doing, stop doing, and continue doing?"
Why it matters: This produces actionable suggestions without forcing a long narrative.
When to use: Rotate monthly (not weekly) if comments volume gets too high.
"In the last week, I have had to work at an unsustainable pace."
Why it matters: This is a sharper "workload spike" signal than a general workload item.
When to use: Swap-in module (Workload spike). Run for 2-4 waves during peak periods.
"I have enough time for focused work (not meetings/messages)."
Why it matters: If focus time collapses, quality drops and cycle time increases.
When to use: Swap-in module (Workload spike). Use to justify meeting cuts or WIP limits.
"I understand why the recent change was made."
Why it matters: People accept change faster when the "why" is clear and consistent.
When to use: Swap-in module (Post-change). Run for 3-6 waves after an announcement.
"I know what I need to do differently because of the change."
Why it matters: This separates understanding from execution readiness.
When to use: Swap-in module (Post-change). Pair with a blocker prompt: "What is unclear?"
"My 1:1s (or check-ins) help me remove blockers and stay on track."
Why it matters: This points to a specific manager habit you can coach.
When to use: Swap-in module (Manager-only readout). Report only at safe rollups.
"I get timely feedback that helps me improve."
Why it matters: Timely feedback predicts performance improvement and reduces rework.
When to use: Swap-in module (Manager-only readout). Use for coaching and enablement, not "gotcha" ranking.
"I can get help quickly when I am stuck."
Why it matters: Distributed work fails when help is slow or hard to access.
When to use: Swap-in module (Distributed/frontline). Use with questions about handoffs and coverage.
"I have the information I need to serve customers/patients safely and well."
Why it matters: For frontline roles, missing information creates immediate service and safety risk.
When to use: Swap-in module (Distributed/frontline). Pair with a prompt: "What info is missing?"
Keep stable: 8-10 core questions (clarity, workload, support, resources, wellbeing) plus 1-2 open-text prompts.
Rotate: Only one module at a time (2-4 questions) and keep it for a few waves.
Lock wording: Do not tweak phrasing between waves. If you must change wording, treat it as a new trend line.
Do next: Pick your core questions and choose one module you will rotate in for the next 2-4 waves.
How to Customize and Launch Your Temperature Check (Cadence, Scale, Comms)
-
Starter setup (good default): Run weekly or biweekly, keep it under 5 minutes, and use the same response scale every wave. Adjust after 2-3 waves once you see completion time and data stability.
-
Cadence: Starter target is a schedule you can keep for 8-12 weeks. Example: Tuesday-Thursday morning, with the same close time each wave.
-
Scale: Choose one rating scale and do not change it. If you use agreement, decide between Likert scale options (5-point vs 7-point) for pulse surveys and stick with it for clean trends.
-
Length: Starter target is 8-12 questions total (including 1-2 open-text prompts). If you need more detail, rotate a module instead of adding permanent questions.
-
Invite (copy-paste):
Subject: 3-minute temperature check (closes Friday)
Body: "Please take 3 minutes to answer this week's pulse. We will share back the top themes and 1-2 actions by [date]." -
Reminder timing: Send 1 reminder at the halfway point and 1 on the close day (not more). Evidence-backed tip: follow basic fieldwork hygiene from AAPOR's Best Practices for Survey Research and treat response dips as a signal to improve comms, not to pressure people.
-
Reminder (copy-paste): "Quick reminder: this week's pulse closes at [time]. If you have not responded, your input helps us pick one improvement to act on."
-
Response-rate safeguards: Pre-notice the day before, keep the window short (3-5 days), and send from a trusted leader. If a subgroup stops responding, assume how response bias and nonresponse can skew results before you assume sentiment improved; nonresponse can be systematic (see Rogelberg and Stanton's research on organizational survey nonresponse).
-
Share-back promise (copy-paste): "We will share 3 takeaways and 1-2 actions with owners and dates. If we cannot act on something yet, we will explain why."
Do next: Lock your cadence and scale, then paste the invite and put reminder times on your calendar.
Sampling and Anonymity Rules (Minimum Group Sizes and Safe Cut Breaks)
Pick who gets the pulse
Default: Send to everyone every wave so your trends stay comparable. If you must sample, keep the same sampling rules each wave (same sites, roles, and shifts).
Set your reporting threshold (minimum group size)
Choose a minimum group size for reporting (your "reporting threshold"). Report results only in groups at/above that threshold and avoid slicing results into smaller cuts.
Use sample size and minimum reporting threshold guidance to pick a practical rule and apply it consistently.
Suppress small subgroups and risky intersections
Rule: If a cut falls under your threshold (or gets close), suppress it. If a safe group becomes unsafe after a second filter (example: Location A + Night shift), suppress the intersection.
Handle comments so people stay safe
Do not share raw verbatims with leaders. Summarize themes, redact names, and avoid quoting text that includes identifying details (project names, incidents, unique role details).
Use employee-facing confidentiality language you can keep
Say what you will do: "We report results in aggregated groups and do not share raw comments." Avoid promises you cannot prove. Imperial College London's guidance on staff survey confidentiality is a good model for clear, practical wording.
Reporting: Only publish results for groups at/above your reporting threshold.
Segmentation: Start with one safe cut (team or location). Add more only if cells stay safely above threshold.
Comments: Share themes and counts, not raw quotes.
Do next: Write your reporting threshold into the invite and build your first report views around it.
Results to Action: Trend Rules, Safe Segmentation, and a Lightweight Action Plan
-
Set your baseline and label Wave 1 as your starting pointExport Wave 1 results and keep them unchanged. Your goal is not a perfect benchmark; it is a repeatable starting line for your own trends.
-
Use trend rules so you do not overreactStarter rule: Look for movement sustained across multiple waves (for example, 3 waves in a row) before you call it a real shift. Treat one-wave spikes as "investigate" signals, not automatic action.
-
Look at three views: overall, by safe rollups, and by question areaBuild a simple dashboard: (1) overall trend line, (2) team/location rollups that meet your threshold, (3) a heatmap by driver area (clarity, workload, support, resources, wellbeing) to spot hotspots.
-
Triangulate with open-text themes before you pick actionsTag comments into 5-10 themes and count them. Use the top two themes to explain the "why" behind score movement, then validate with a quick manager check-in.
-
Pick 1-2 focus areas and write a lightweight action planFor each focus area, define: Action (what changes), Owner (one name), Due date, and How you will know (which pulse item should move). The U.S. OPM's FEVS results guidance is a practical reference for turning survey results into priorities and action planning.
-
Close the loop, then re-pulse to confirm improvementStarter target: share back within about 7 days (or before the next wave closes), then track whether the next wave moves in the right direction. Re-run the same core questions next wave to see if the change is big enough to notice. If you need a broader listening system beyond this early-warning pulse, map your plan to a Voice of Employee (VOE) survey template for a broader listening program.
Do next: Create a one-page action tracker (focus area, owner, due date) and commit to a share-back date.
Frequently Asked Questions
How often should we run an employee temperature check survey?
Default: Run it weekly or biweekly if work and priorities change fast; run monthly if things are stable. Keep the same day/time when you can, and keep your core questions unchanged so the trend line stays clean.
How many questions should a temperature check pulse include?
Aim for 8-12 questions total, including 1-2 open-text prompts, so most people finish in under 5 minutes. If you want more detail, rotate a 2-4 question module for a few waves instead of making the pulse longer.
Should the survey be anonymous or confidential?
Use anonymous collection when you want maximum candor and you can report only in safe aggregates. Use confidential collection when you need follow-up (for example, safety concerns) and you can clearly explain who can see what. Either way, protect people by reporting only in groups above your threshold and summarizing comments instead of sharing raw verbatims.
What is a safe minimum group size for reporting results by team or location?
Set a minimum reporting threshold in your policy and do not publish results below it. Suppress small subgroups and risky intersections (example: team + shift) that drop under the threshold. For comments, redact identifiers and share themes and counts rather than quotes that could identify someone.
How do we interpret results without an industry benchmark?
Start with your own baseline, then compare each wave to your prior waves. Prioritize sustained movement over one-wave swings, and use open-text themes to understand the "why". Choose actions where scores are low or dropping and the themes point to fixable system issues.
What should we do after we share results with employees?
Close the loop with a tight sequence: share 2-3 findings, name 1-2 actions, assign owners and dates, then confirm progress in the next pulse. Do not launch another wave if leaders will not act or communicate. Repeated "ask with no change" trains people to ignore the survey.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED