Employee Training Feedback Survey Template
Use this employee training feedback survey to capture what happened right after training and what changed on the job later. Start with the immediate post-session instrument, then schedule the 7-14 day and 30/60-day follow-ups so you cover Kirkpatrick Levels 1-4 in one plan. If you want a shorter, single-moment version, adapt the <a href="/LPA-post-training-feedback">post-training feedback survey template</a> as your core.
Trusted by 5000+ Brands
Copy-ready questions mapped to Kirkpatrick Levels 1-4
Use this section to copy the right questions for each Kirkpatrick moment (Level 1 right after, Level 2 within 7-14 days, Level 3 at 30-60 days, Level 4 only if you have a real metric to tie in).
If you want a shorter, single-moment version, start with the post-training feedback survey template as your immediate post-session core, then add the follow-ups below when you are ready.
Quick setup:
- Immediate post-session (Level 1): Select an internal starter set of 6-8 rating questions plus 1 focused open-text prompt (adjust after you see completion rates and comment quality).
- 7-14 day check (Level 2): Add an internal starter set of 2-4 questions (confidence + 1-3 light knowledge checks aligned to objectives).
- 30/60-day follow-up (Level 3): Schedule an internal starter set of 4-6 questions (application + barriers + support needed).
- Demographics: Keep only what you will actually use to segment results safely.
If there is no instructor, cut the facilitator block. For self-paced eLearning, replace room/logistics items with platform/access/navigation items. For virtual sessions, keep one tech stability item and one engagement item. Delete any module you cannot act on before you send.
Level 1 (Reaction): immediate post-session
"Overall, this training was a good use of my time."
Why it matters: This is your Level 1 headline outcome. Track it over time and use it to spot sessions that need immediate fixes.
When to use: Immediate post-session for ILT, virtual, and eLearning.
"The training objectives were clear."
Why it matters: Low clarity scores usually predict messy comments about pacing and relevance. Fixing objectives often fixes half your Level 1 issues.
When to use: Immediate post-session; keep for ILT, virtual, and eLearning.
"The content was relevant to my day-to-day work."
Why it matters: Relevance is a fast proxy for whether learners will try the behaviors later (your bridge from Level 1 to Level 3).
When to use: Immediate post-session; especially useful when multiple roles attend the same course.
Level 1 (Reaction): delivery and practice
"The pace was right (not too fast, not too slow)."
Why it matters: Pace is one of the most actionable delivery levers. Use it to decide whether to cut content or add practice time before the next run.
When to use: Immediate post-session for ILT/virtual. Optional for eLearning (replace with "The module length was manageable").
"I had enough opportunities to practice (examples, exercises, scenarios)."
Why it matters: Practice time is a common driver of both perceived learning (Level 2) and later use on the job (Level 3).
When to use: Immediate post-session for ILT/virtual; adapt for eLearning as "The activities helped me apply the concepts."
Optional Level 1 module: facilitator/instructor (remove if no instructor)
Keep this block anonymous if you want candid feedback, and avoid asking for sensitive personal comments.
"The facilitator explained concepts clearly."
Why it matters: Clarity is the #1 coaching lever for many instructors and can be fixed before the next session.
When to use: Immediate post-session for ILT/virtual; remove for eLearning with no facilitator.
"The facilitator encouraged participation and handled questions effectively."
Why it matters: Engagement problems often show up as low practice scores and weak Level 2 confidence.
When to use: Immediate post-session for ILT/virtual. Remove if the session was self-paced only.
Optional Level 1 module: logistics/tech (keep this short)
Fix these first because they can block everything else.
"The training environment/technology worked well (room, audio, video, platform)."
Why it matters: Tech friction drives drop-offs and low satisfaction even when content is strong.
When to use: Immediate post-session for ILT/virtual/eLearning (edit the examples to match your setup).
"What is the one thing we should change before the next run?"
Why it matters: This forces prioritization. You will get fewer "everything" comments and more usable fixes.
When to use: Immediate post-session. Keep it focused (one change) to improve text quality. Use these prompts with how to write better open-ended questions so comments stay specific and actionable.
Level 2 (Learning): 7-14 day check
Use a light touch and align to your stated objectives. This is where many teams connect their evaluation plan back to Kirkpatrick (reaction, learning, behavior, results) as described in the CIPD evaluating learning and development factsheet.
"I feel confident using the key skill(s) from this training."
Why it matters: Confidence is not proof of learning, but it is a fast signal for where you need more examples, practice, or job aids.
When to use: 7-14 day check for ILT/virtual/eLearning (after learners have had a chance to try something).
"Which course objective(s) do you feel least confident about right now?"
Why it matters: This points you to the exact module that needs re-teaching, better practice, or clearer examples.
When to use: 7-14 day check. Use a checkbox list of your actual objectives (not generic topics).
"Quick check: Which option is the correct next step in [process/skill]?"
Why it matters: One or two objective checks can catch misunderstandings without turning your survey into a full test.
When to use: 7-14 day check. Keep it to an internal starter maximum of 1-3 items; link to a separate assessment if you need more.
Level 3 (Behavior/transfer): 30/60-day follow-up
Ask about specific behaviors and barriers. Transfer depends on the work context (tools, time, manager support) - a practical point emphasized in Baldwin and Ford's transfer of training review.
"In the past 30 days, how often have you used [specific behavior from the training]?"
Why it matters: Frequency beats vague intent. You will see whether the behavior is sticking or dying after the first week.
When to use: 30/60-day follow-up. Use a clear scale (Never, Once, Monthly, Weekly, Daily) and name the behavior.
"What is the biggest barrier to using what you learned?"
Why it matters: Barriers tell you what reinforcement to build (job aids, workflow changes, manager prompts) instead of just tweaking slides.
When to use: 30/60-day follow-up. Offer a checkbox list (time, tools, permissions, unclear expectations, manager support) plus an Other option.
"What support would help you apply this more consistently?"
Why it matters: This converts complaints into an input list for reinforcements you can actually ship (templates, office hours, manager talking points).
When to use: 30/60-day follow-up. Keep responses safe by asking about support, not personal performance.
Level 4 (Results): only if you can tie to a metric
Ask for directional signal in the survey, then validate with your operational metrics where possible.
"Since the training, I have seen improvement in [quality/speed/safety/customer outcome] in my work."
Why it matters: This gives you an early read on perceived impact while you wait for harder measures (tickets, quality audits, sales, incident rates).
When to use: 30/60-day follow-up or 60-90 days if results lag. Only include if learners can reasonably observe the outcome.
Keep demographics minimal (privacy + trust)
Ask only what you will actually use in reporting. Good defaults are role/track and location; avoid unique combinations in small cohorts (for example: role + location + shift) if it makes people identifiable. Next step: delete any demographic you cannot safely report back in groups.
When to run a training feedback survey (3 best moments)
1) Immediate post-session (Level 1 reaction + logistics)
Internal starter cadence (adjust after your baseline): Send within 1-2 hours of completion (or the next morning for late sessions). Close after about 3-5 days, and send 1 reminder at about 24 hours plus a final reminder about 24 hours before close.
Use this moment to catch fixable issues (pacing, clarity, tech, materials) before the next cohort.
2) 7-14 day check (Level 2 learning recall + reinforcement needs)
Internal starter cadence (adjust after your baseline): Send on day 7 for high-frequency skills (daily/weekly behaviors) and day 14 for lower-frequency skills. Close after about 4-7 days, with 1-2 reminders spaced about 2-3 days apart.
Use this moment for confidence + 1-3 objective checks and to collect what support people need next (job aids, practice, office hours).
3) 30-60 day follow-up (Level 3 application + barriers; Level 4 if metrics exist)
Internal starter cadence (adjust after your baseline): Send at day 30 when you expect quick application; use day 60 when behavior change needs time, approvals, or tooling. Close after about 7-10 days, with 2 reminders (around day 3-4 and day 7-8).
Use this moment to ask about frequency of use, barriers, and manager/support needs; add a results check only if you can connect it to a real KPI or operational metric. If you want a research-backed reminder approach, keep your cadence consistent and short as described in the BMC review on follow-up strategies that improve survey participation.
Anonymous vs identified (and how to protect trust in small cohorts)
Use this section to pick the response identity option that matches your goal (candid feedback vs follow-up vs manager validation).
- Default to anonymous for facilitator/delivery feedback and small-group psychological safety.
- Switch to confidential identified only when you need targeted follow-up or to match to completion/assessment data.
- Add a manager mini-survey only when managers can observe specific behaviors 30-60 days later.
Default setup: anonymous link + a clear promise about how you will report results (minimum group size). If you need a checklist for controls, review your platform's privacy, confidentiality, and anonymity settings before you send. Next step: choose one approach and paste the matching intro copy into your survey.
| Option | Pros | Cons / risks | Best use cases | What to say in the survey intro (copy-ready) |
|---|---|---|---|---|
| Anonymous link | Candid facilitator and logistics feedback; lower fear of consequences; easier to field fast. | You cannot follow up 1:1; small cohorts can still feel identifiable through details in comments. | Most post-session Level 1 surveys; pilots; any course where instructor coaching is the goal. | "This survey is anonymous. We will report results only in groups of at least 5 (internal starter threshold; adjust based on cohort size and sensitivity) and will summarize comments when needed." |
| Confidential identified (HR/L&D can see names; managers do not) | Enables targeted follow-up; supports longitudinal tracking (same person at 7-14 and 30-60 days); can match to completion/assessment data. | Lower candor if trust is weak; higher burden to explain handling; higher risk in small cohorts if reporting is sloppy. | Programs that include coaching, remediation, or required follow-ups; Level 2/3 tracking where you must link responses over time. | "Your responses are confidential. Only the L&D team will see individual responses. We will report results in groups of at least 5 (internal starter threshold; adjust as needed) and will not share individual answers with your manager." |
| Manager check-in mini-survey (separate instrument) | Adds an outside view of observable behaviors; surfaces environmental barriers (workload, priorities, tools). | Managers may not observe the behavior; risk of turning feedback into performance judgment if phrased poorly. | 30/60-day validation for behavior change; reinforcement planning; removing blockers at the team level. | "This short check-in asks about observable behaviors after training. Do not use it for performance ratings; we will summarize results at the team level." |
Small-cohort safeguards (use at least two):
- Minimum reporting threshold: Internal starter threshold: report only when n >= 5 (or n >= 10 for sensitive topics). Adjust after you understand your baseline participation and identifiability risk.
- Roll up segments: Combine to department/program level if team-level cuts are too small.
- Harden your open text: Replace "Tell us what happened" with focused prompts (one change, one barrier) to reduce identifying detail.
- Do not over-promise: Say "confidential" only if you can keep managers and instructors out of raw responses.
Next step: decide your minimum n and state it in the intro so learners know what to expect.
How to customize and deploy (fast) without losing signal
Use this section to ship a clean survey fast without losing the signal you need to improve the next run.
- Length: Use an internal starter target of about 8-12 core questions for the immediate post-session survey; cut optional modules first.
- Wording: Swap in your real objectives and behaviors (avoid generic wording).
- Trust: Decide anonymity up front and copy/paste the intro that matches it.
Default setup: one 5-point agreement scale for ratings, plus 1-2 focused open-text prompts (internal starter targets; adjust after you review completion and comment quality). If your training is ILT/virtual/eLearning, tweak it like this: If no instructor, remove facilitator items; if virtual, add one tech item; if eLearning, add one platform/access item. Next step: edit the objectives/behaviors, then set your send and close dates.
- Swap in your objectives and key skills: Replace placeholders ("[behavior]") with 3-6 concrete skills learners can actually do on the job. Use the same language your course uses so people do not have to translate.
- Pick the right modules by format: ILT/virtual: keep facilitator + pacing + participation. eLearning: cut facilitator items and add platform/access + navigation clarity. If the course was hybrid, keep both but cap each module to an internal starter target of 2-3 items.
- Add branching by role/track (only if needed): If you trained multiple roles, route 1-2 role-specific behavior questions by track so people only answer what applies. Keep shared core questions identical so you can compare cohorts.
- Standardize your rating scale: Use one agreement scale throughout and label endpoints. If you are deciding between 5 and 7 points, follow the practical guidance in Likert scale question design (5-point vs 7-point) and do not mix scale lengths in the same survey.
- Cap length with a priority order: Must-ask: overall value, objectives clear, relevance, practice, confidence, intent-to-apply, one barrier, one open-text "one change". Optional: detailed logistics, extra facilitator items, extra demographics.
- Set your sender and reminders: Send from a recognizable person (training lead) and a consistent mailbox. Internal starter target: 1 reminder for a 3-5 day window and 2 reminders for a 7-10 day window (adjust after you see baseline response rates and time zones). Basic questionnaire hygiene like clear purpose and low burden improves completion, as summarized in Imperial College London's best practice in questionnaire design guidance.
- Paste a trust-building intro (copy-ready): "Help us improve the next run. This typically takes about 3 minutes (internal estimate; confirm after you preview). We will summarize results and share changes we make; we will report results only in groups of at least 5 (internal starter threshold; adjust as needed) and will not share individual responses with your manager."
Next step: schedule your 7-14 day and 30/60-day follow-ups now so you do not lose the Level 2/3 signal.
Results and action guide: score, segment, and turn feedback into the next-run change log
Use this section to turn ratings and comments into specific changes you can ship before the next cohort - and to set up the 30/60-day follow-up so you can see behavior transfer.
- Build a one-page scorecard (percent favorable + median) for each module.
- Segment only by fields you can safely report (course, cohort, role/track).
- Log the top 3 changes with an owner and due date.
Default setup: report percent favorable (top-2 box) and the median for Likert items; do not over-read averages on ordinal scales. If your training is ILT/virtual/eLearning, tweak it like this: ILT/virtual - split "delivery" from "content"; eLearning - split "platform" from "content." Next step: create your change log while the session is still fresh.
- Step 1: Build a simple scorecard (one row per theme)
Start with 6 buckets: Overall value, Instructor/Facilitator (if applicable), Content relevance/clarity, Practice, Logistics/Tech, Learning confidence + Intent-to-apply. Use 2-4 items per bucket max and keep the item wording stable so you can trend over time.
Output: a table or slide with percent favorable + median for each bucket, plus the top 3 comment themes.
- Step 2: Read Likert ratings as distributions (not just an average)
Calculate percent favorable (for example: Agree + Strongly agree) and compare it across cohorts and formats. Then check the median to avoid a few extreme ratings distorting your story.
Internal starter action triggers (calibrate after your baseline):
- If percent favorable is below 70% on clarity or relevance, prioritize revising content/examples before the next run.
- If percent favorable is below 60% on logistics/tech, prioritize fixing the environment/platform before touching slides.
- Step 3: Use a Kirkpatrick workflow to prioritize fixes
Fix Level 1 blockers first (logistics, pacing, clarity) because you can ship them before the next session. Next, address Level 2 gaps by adding practice, better examples, and a quick knowledge check aligned to objectives.
Then protect Level 3 transfer: schedule the 30/60-day follow-up and include barriers and support needs. Teams that follow the full chain (reaction to learning to behavior to results) get more usable signals than smile sheets alone; the relationships between training criteria are summarized in Alliger et al.'s meta-analysis of training evaluation criteria.
- Step 4: Code open-ended comments into themes you can count
Tag each comment to 1-2 themes (content, pacing, examples, practice time, tools/access, manager support). Count theme frequency and pull 2-3 representative quotes only when they cannot identify a person.
Use focused prompts to improve text quality, and follow the techniques in how to write better open-ended questions to reduce vague or overly sensitive comments.
- Step 5: Convert insights into a next-run change log (owner + due date)
Create a simple log with: Finding, Evidence (score/theme count), Decision, Owner, Due date, and "Shipped?". Sort by impact and speed: ship quick fixes (materials, instructions, tech checks) within 7 days; ship content/practice changes before the next cohort.
Internal starter triggers that force a decision (calibrate after your baseline):
- If "time" shows up as a top barrier in more than 25% of Level 3 responses, draft a manager reinforcement message and ship a 10-minute workflow job aid.
- If more than 20% select "tools/access" as a barrier, assign an IT/process owner and set a resolution date.
Next step: publish a short "You said / We changed" note to learners after you ship the first three fixes.
Frequently Asked Questions
How long should a post-training feedback survey be?
As an internal starter range, keep the immediate post-training survey to about 8-12 questions so you protect completion rates while still getting a clear Level 1 read. Make the 30/60-day follow-up shorter (about 6-10 questions) and focus it on specific behaviors and barriers. Use optional modules and branching so people only see what applies (eLearning vs instructor-led).
When should I send the survey after training to get the best responses?
As an internal starter cadence, send within 1-2 hours of completion (or the next morning) while details are fresh. Keep it open about 3-5 days and send 1-2 reminders depending on your close window, then adjust after you see baseline response rates and time zones. Schedule a 30-60 day follow-up to capture behavior transfer, and extend the window if you also need manager input or KPI data.
Should training feedback surveys be anonymous?
Default to anonymous when you want candid facilitator and logistics feedback and you do not need individual follow-up. Switch to confidential identified when you need to coach specific learners, link to completion/assessment data, or track the same person over time. In small cohorts, protect trust with minimum reporting thresholds (for example, an internal starter threshold like n >= 5) and aggregation.
How do I measure Kirkpatrick Levels 2 and 3 without turning this into a test?
Use a light Level 2 check: self-reported confidence plus 1-3 objective questions aligned to your course objectives, or link to a separate assessment when you need more depth. For Level 3, send a 30/60-day follow-up that asks about specific behaviors, frequency of use, and barriers/support needed. Keep the wording about training improvement, not employee performance evaluation.
What should I do with open-ended comments so they lead to changes?
Tag comments into a small set of themes (content, pacing, examples, practice, tools, manager support) and count how often each theme appears. Convert the top themes into a change log with an owner and deadline, then close the loop with learners using a short "You said / We changed" summary. This keeps comments from becoming a one-time venting channel.
Can I send a manager survey to validate on-the-job behavior change?
Yes - use a short manager check-in 30-60 days later that asks about observable behaviors and barriers, not opinions about the person. Keep it brief (for example, an internal starter range like 3-6 items) and state confidentiality expectations up front. Avoid using manager responses as an individual performance rating tool.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED