A training needs analysis template records, on one page, the business goal, current versus desired performance, the root cause of the gap, who needs training, the recommended solution and how success will be measured. Fill it at three levels — organisational, task and individual — using at least two data sources, and only design training for gaps caused by missing skills or knowledge.
What is a training needs analysis?
A training needs analysis (TNA) is the process of identifying the gap between current and required performance, finding out why it exists, and deciding whether training will close it. It is the "A" in the ADDIE model and the step that most often gets skipped.
Most training requests arrive as solutions: "Our team leads need communication training." A TNA turns that request back into a problem statement — what is going wrong, for whom, how often, and at what cost — and then tests whether a classroom program is really the answer. Sometimes it is. Often part of the gap is caused by an unclear process, a missing tool or conflicting incentives, and no amount of training will fix those.
A good TNA gives you three things: a clear target for the program, the evidence to justify the investment to management, and a baseline to evaluate against later with Kirkpatrick's four levels.
The three levels of TNA
A complete training needs analysis works at three levels: organisational, task and individual. Each answers a different question, and skipping one usually means training the wrong people or the wrong skills.
| Level | Key question | Typical inputs | Output |
|---|---|---|---|
| Organisational | Where does the business need performance to change, and is there support for training? | Business plan, unit KPIs, leadership interviews, audit findings, expansion or restructuring plans | Priority areas, business case, constraints (budget, time, locations) |
| Task / operational | What does good performance in this job look like? | Job descriptions, SOPs, competency frameworks, observation of top performers, quality standards | List of critical tasks with the skills, knowledge and standards each requires |
| Individual / person | Who is not meeting the standard, and by how much? | Performance reviews, skills assessments, manager ratings, self-assessments, quality and error data | Named groups or individuals with specific gaps and priority |
Think of it as a funnel: the organisational level tells you where to look, the task level tells you what good looks like, and the individual level tells you who needs what.
Which data collection methods work best?
Use at least two methods so that one source checks the other. Interviews tell you what people believe; performance data and observation tell you what actually happens.
| Method | Best for | Watch out for |
|---|---|---|
| Stakeholder interviews | Business goals, context, what "good" means to leaders | Leaders often describe solutions, not problems — keep asking "what would you see?" |
| Focus groups | Frontline view of obstacles, process issues, morale | Senior people in the room silence others; group by level |
| Surveys / questionnaires | Reaching large or dispersed teams quickly | Self-ratings are inflated; ask about specific tasks and frequency |
| Job observation | Seeing the real workflow and the gap between SOP and practice | People behave differently when watched; observe more than once |
| Performance and operational data | Objective baselines: errors, turnaround time, complaints, rework | Data may reflect process or system issues, not skill |
| Skills tests and simulations | Measuring actual capability against a standard | Test must mirror real tasks, not trivia |
| Document review | Audit reports, customer feedback, exit interviews, past training evaluations | Old documents may describe problems already fixed |
Training needs analysis template (copy this)
Here is a one-page training needs analysis template you can paste into a spreadsheet or document. Complete one row per performance gap; most TNAs end up with three to six rows.
| Field | What to write |
|---|---|
| 1. Business goal | The result the organisation needs, in measurable terms (e.g. "reduce repeat complaints") |
| 2. Target role / group | Job role, number of people, locations, shifts, languages, experience levels |
| 3. Desired performance | What people should do on the job, to what standard (from task analysis) |
| 4. Current performance | What they do now, with evidence and the data source |
| 5. Gap | The difference between 3 and 4, stated as behaviour, not as a topic |
| 6. Root cause | Tick one or more: skill · knowledge · process · tools/systems · incentives · environment · selection |
| 7. Training need? (Y/N) | Yes only if the cause is skill or knowledge |
| 8. Priority | High / Medium / Low, based on business impact and urgency |
| 9. Recommended solution | Training format and duration, plus any non-training actions (job aid, process fix, coaching) |
| 10. Success measures | Baseline figure, target and measurement method at each Kirkpatrick level you will use |
| 11. Owner and timeline | Who is accountable for the solution and the review date |
| 12. Stakeholder sign-off | Name, role and date of approval |
Field 6 is the most important line in the template. It forces the conversation that separates a useful TNA from a wish list.
How to run a TNA step by step
A practical training needs analysis follows six steps, from business goal to signed-off recommendation.
- Clarify the business goal. Meet the stakeholder who raised the request. Ask what result must change and how they will know it has. Write it down before discussing training.
- Define the standard. Through task analysis, describe what competent performance looks like. Watching or interviewing your best performers is the fastest route.
- Collect current-performance data. Pick two or three methods from the table above, proportionate to the size of the problem.
- Diagnose the root cause. For each gap ask: if their life depended on it, could they do it? If yes, it is not a skill problem.
- Prioritise and recommend. Rank gaps by impact and urgency. Recommend training for skill and knowledge gaps and other actions for the rest.
- Agree success measures and sign off. Record baselines now — you cannot evaluate later without them.
Worked example: a customer support team in a Bengaluru GCC
Here is an illustrative, fictional example of the template applied in an Indian workplace. Names and figures are deliberately left out; the point is the reasoning.
Scenario: A global capability centre (GCC) in Bengaluru runs a technical support desk for an international software product. The support head asks L&D for "communication skills training" because customer satisfaction scores have dropped and escalations to senior engineers have risen.
Organisational level
Leadership interviews confirm the business goal: protect customer satisfaction and reduce escalations, because senior engineers are being pulled away from product work. The centre has also recently added a new product module and hired a sizeable batch of freshers to cover it.
Task level
The L&D lead observes three strong support engineers and reviews the support SOP. Good performance means: diagnosing the issue within the first interaction, writing a clear resolution note, and setting expectations when an issue must be escalated.
Individual level
Ticket data, a review of a sample of closed tickets and two focus groups (freshers and experienced engineers separately) reveal three distinct gaps:
| Gap | Who | Root cause | Training need? | Recommended solution |
|---|---|---|---|---|
| Cannot troubleshoot the new module, so they escalate early | Recent fresher batch | Knowledge and skill | Yes — High | Hands-on technical workshop on the new module, delivered by internal SMEs, with practice on real (anonymised) tickets |
| Resolution notes are unclear to customers | Mixed; across experience levels | Skill, plus no standard note format | Partly — Medium | A note template (process fix) plus a short written-communication session with practice and peer review |
| Escalation hand-offs lose information | All engineers | Tool: the ticketing form lacks mandatory fields | No | Change the ticketing form; brief the team in a team meeting |
Notice what happened to the original request. "Communication skills training" became one targeted technical workshop, one short writing session paired with a template, and one tool change. The success measures agreed were escalation rate, customer satisfaction on tickets handled by the target group, and a quality score on a sample of resolution notes, each tracked against the pre-training baseline.
Because the technical workshop is delivered by engineers rather than professional trainers, the TNA also flags a supporting need: those SMEs need help to teach well. Our guide to moving from subject matter expert to trainer covers exactly that.
Common TNA mistakes to avoid
- Accepting the request as the diagnosis. "We need a leadership program" is a solution. Ask what leaders are doing, or not doing, that hurts results.
- Relying on one data source. A survey alone mostly measures opinion. Pair it with observation or performance data.
- Listing topics instead of behaviours. "Excel" is a topic; "builds a monthly variance report without errors" is a performance gap you can train and measure.
- Training for non-training problems. If the cause is a broken process, a missing tool or a conflicting incentive, training will waste money and frustrate participants.
- Forgetting the baseline. Without "before" data captured during the TNA, Level 3 and Level 4 evaluation is guesswork.
- Making it too big. An annual company-wide TNA that takes months is often out of date by the time it is approved. Keep each analysis proportionate.
- No stakeholder sign-off. If the business owner has not agreed the gap and the measures, they will judge the training on something else.
Learning TNA in the Bodhih Certified TTT
Training Needs Analysis is taught on Day 2 (Instructional Design Mastery) of the Bodhih Certified Train The Trainer (TTT) Program, together with the ADDIE model, experiential activity design and storytelling for training. Participants work on their own training content, use Bodhih's training design templates (including TNA and session-plan templates), and carry the analysis through to evaluation on Day 4. If your role leans heavily towards design, Bodhih also runs a dedicated instructional design course for trainers. For definitions of terms used here, see the trainer's glossary.
Frequently asked questions
What is a training needs analysis (TNA)?
A training needs analysis is a structured process for finding the gap between how people currently perform and how they need to perform, working out why that gap exists, and deciding whether training is the right fix. It is the first phase (Analysis) of the ADDIE model and produces a short report that guides objectives, content, format and evaluation.
What are the three levels of training needs analysis?
The three levels are organisational (which business goals and units need attention), task or operational (what a job requires in terms of skills, knowledge and standards) and individual or person (which people fall short of those standards and by how much). A complete TNA connects all three so training targets the right people for the right business reason.
What should a training needs analysis template include?
At minimum: the business goal, current and desired performance, the size of the gap, root cause (skill or knowledge versus process, tools or motivation), the target audience, priority, recommended solution, success measures with a baseline, and an owner and timeline. Our copyable template above includes all of these in one table you can paste into a spreadsheet.
How long does a training needs analysis take?
It scales with the problem. A focused TNA for one team and one skill can be done in a few days using interviews, a short survey and existing performance data. A company-wide annual TNA across many roles can take several weeks. Keep it proportionate: the aim is enough evidence to make a sound decision, not a perfect research study.
What is the difference between TNA and training needs assessment?
In everyday L&D practice in India the two terms are used interchangeably. Some practitioners use 'assessment' for gathering data on the gap and 'analysis' for interpreting causes and choosing solutions. What matters is doing both: measuring the gap and diagnosing why it exists before you design anything.
Where can I learn to run a TNA hands-on?
Training Needs Analysis is taught on Day 2 (Instructional Design Mastery) of the Bodhih Certified Train The Trainer (TTT) Program, alongside the ADDIE model. Participants receive Bodhih's TNA and session-plan templates and apply them to their own training topic during the four days.