Goals & alignment
SMART goals examples for employees: 45 examples by role, with a goal-writing template
Forty-five SMART goals for HR, sales, engineering, customer support and healthcare roles, each broken down letter by letter, with a reusable goal-writing template and a guide to cascading SMART goals into OKRs.
By the CLEAR Talent team22 min read
Key takeaways
- SMART is a test for how a goal is worded: specific, measurable, achievable, relevant and time-bound.
- Record a baseline before you set a target. Without one, a number is a guess.
- Measure the outcome you want, not the activity that might produce it.
- Keep the list short — three to five goals for a review period is a common range — and weight them.
- Link every individual goal to a team or organisation objective; that is what makes the relevant test real.
Most goals fail long before anyone works on them. ‘Improve customer satisfaction’, ‘grow the pipeline’ and ‘be more proactive’ sound reasonable in a planning meeting, but at review time nobody can say whether they were met, because nobody agreed what meeting them would look like.
SMART goals fix the wording. This guide explains what each letter asks for, gives you a sentence formula and a reusable template, then sets out 45 example goals for employees in HR, sales, engineering, customer support and healthcare, each broken down against the five criteria. It finishes with how SMART goals relate to OKRs and KPIs, and how to cascade them so individual goals still connect to what the organisation is trying to achieve. The numbers in the examples are illustrative placeholders, not benchmarks: replace each one with your own baseline and a target your team has agreed.
What a SMART goal is, letter by letter
A SMART goal passes five tests. Each one is a question you can ask of a draft goal before it is agreed.
- Specific: what exactly will change?
- Name the result, the area it applies to and, where it helps, the approach. ‘Improve onboarding’ is a theme; ‘reduce leavers in the first 90 days in the warehouse team’ is a goal.
- Measurable: how will anyone know?
- Choose the measure, where the number comes from and today’s baseline. If the only evidence will be the employee’s own impression, the goal is not yet measurable.
- Achievable: is it realistic with the time and resources available?
- A good target needs effort but not luck. Check what the person controls, what support they need and what else they are carrying this period.
- Relevant: which objective does it serve?
- Name the team or organisation objective the goal contributes to. A well-specified goal that serves nothing is busywork, however neatly it is written.
- Time-bound: by when, and when will we check?
- Set a deadline and at least one checkpoint before it, so a goal that is drifting becomes a conversation while there is still time to act.
Some versions of the acronym swap in attainable, realistic or timely. The questions are the same, and so is the purpose: a goal that the employee, their manager and anyone reviewing it later would all read the same way.
How to write a SMART goal in five steps
Work through the criteria in this order. It is quicker than drafting a sentence and then trying to make it fit all five.
Start from the objective above you
Before writing anything, look at the team or organisation objective the goal should support. It stops you writing a goal that is perfectly specified and irrelevant.
Describe the outcome, not the task
Ask what should be different at the end of the period. ‘Launch the new induction’ is a task; ‘cut first-90-day leavers from 12 to 6 a quarter through a new induction’ is an outcome with the task inside it.
Pick the measure and record the baseline
Decide which number will show progress, where it comes from and what it is today. If there is no data yet, the first goal may be to establish the baseline.
Test the target against the resources
Agree what the person controls, what help they need and what they will stop doing to make room. A stretching target with no capacity behind it is a wish.
Set the deadline and the checkpoints
Put a date on the goal and one or two check-ins before it. Agree in advance what would justify revising the goal, so a change mid-period is a decision rather than a quiet rewrite.
A sentence formula helps: by [date], I will [achieve a specific result] from [baseline] to [target], measured by [source], so that [the objective it serves]. Not every good goal fits the formula word for word, but every good goal answers each of its blanks.
Here is the difference in practice. ‘Improve response times’ becomes ‘By 30 September, bring first-response time on priority tickets under one hour for 95% of cases during business hours, up from 80% today, measured in the helpdesk report, so the support team meets the service commitment in this year’s customer objective.’
A reusable SMART goal template
Copy the template below for each goal, or download it as a CSV to use in a spreadsheet. The right-hand column shows one goal filled in, for a hypothetical support team lead.
Template
SMART goal-writing template
Fill in every row before the goal is agreed. The last five rows are what keep a goal alive after the setting meeting.
| Field | What to write | Worked example |
|---|---|---|
| The goal | ||
| Goal statement | One sentence naming the result, the measure, the target and the date | Reduce the backlog of tickets older than seven days from 140 to below 30 by 30 June |
| Specific | What will change, where, and the main way you will do it | Tickets older than seven days in the billing queue, cleared through a daily triage slot |
| Measurable | The measure, its source, the baseline today and the target | Count of open tickets older than seven days in the helpdesk report: 140 today, below 30 by the deadline |
| Achievable | What the person controls, the support they need and what they will stop doing | Two agents get a protected hour a day; the weekly queue review moves to fortnightly for the quarter |
| Relevant | The team or organisation objective the goal contributes to | The support team goal of resolving customer issues within agreed service levels |
| Time-bound | The deadline and at least one checkpoint before it | Deadline 30 June; checkpoints at the end of April and the end of May |
| Keeping it live | ||
| Owner | The one person accountable for the result | Support team lead |
| Weight | Its share of the person’s goals for the period, so priorities are stated rather than implied | 30% of this period’s goals |
| Evidence | What will be attached or referenced when progress is reported | Weekly backlog export from the helpdesk report |
| Support needed | What the manager or another team has agreed to provide | Manager to agree the rota change with the operations lead |
| Revision rule | What would justify changing the goal mid-period, and who agrees the change | A major product incident; any change agreed with the manager and recorded at a check-in |
The worked example is illustrative. Replace the numbers with your own baseline and an agreed target.
SMART goals examples for HR and people teams
Nine examples across three HR roles. HR goals often slide into activity (‘run the engagement survey’), so each of these names the result the activity is meant to produce.
Examples
SMART goals for HR roles
| SMART goal | Specific | Measurable | Achievable | Relevant | Time-bound |
|---|---|---|---|---|---|
| Recruiter | |||||
| Cut average time to fill for engineering roles from 60 to 45 days by 30 June by agreeing a five-day CV turnaround with hiring managers. | Engineering vacancies; CV turnaround agreement | Days from approved requisition to accepted offer | Turnaround is within recruiter and manager control | Open roles are delaying the product roadmap | 30 June |
| Use a structured interview scorecard for every customer-facing vacancy by the end of Q3, up from about half today. | Customer-facing vacancies; structured scorecards | Share of vacancies with completed scorecards | Scorecard template already exists | Supports consistent, defensible hiring decisions | End of Q3 |
| Raise the offer acceptance rate for graduate roles from 70% to 80% for the September intake by adding a pre-offer call with the hiring manager. | Graduate offers; pre-offer call | Offers accepted as a share of offers made | One extra call per candidate | The graduate programme needs a full intake | September intake |
| HR business partner | |||||
| Make sure every manager in the operations division records a mid-year check-in with each direct report by 31 July. | Operations managers; mid-year check-ins | Check-ins recorded against headcount | Six weeks for about 40 managers | Mid-year evidence feeds fair year-end appraisals | 31 July |
| Reduce leavers in the first 90 days in the warehouse team from 12 to 6 a quarter by Q4 through a revised induction and a 30-day check-in. | Warehouse new starters; induction and check-in | Leavers within 90 days of start, per quarter | Induction owned jointly with the site manager | Early attrition drives hiring cost and overtime | By Q4 |
| Hold a calibration session for each of four departments before ratings are released on 15 December, with every changed rating recorded with a reason. | Four departments; calibration with recorded reasons | Sessions held and changes documented | Sessions fit the existing review timetable | Consistent ratings across departments | Before 15 December |
| Learning and development specialist | |||||
| Launch a six-module programme for new managers and have all 18 managers promoted this year complete it by 30 November. | Newly promoted managers; six modules | Completions out of 18 | Modules delivered in working hours over five months | Stronger first-line management | 30 November |
| Agree an individual development plan with at least one dated action for 90% of employees in the finance function by the end of February. | Finance function; development plans | Share of employees with a dated action | Plans drafted in existing one-to-ones | Closes skills gaps found in last year’s reviews | End of February |
| Cut the average time to complete mandatory compliance training from 45 to 20 days after assignment by the end of Q3, using shorter modules and reminders. | Mandatory compliance training | Days from assignment to completion | Content changes are within L&D’s remit | Reduces compliance exposure | End of Q3 |
SMART goals examples for sales roles
Sales goals are the easiest to measure and the easiest to get wrong. Revenue targets belong here, but so do the conversion and retention goals that make revenue repeatable.
Examples
SMART goals for sales roles
| SMART goal | Specific | Measurable | Achievable | Relevant | Time-bound |
|---|---|---|---|---|---|
| Account executive | |||||
| Close €240,000 of new annual recurring revenue from mid-market accounts in Q3. | New revenue from the mid-market segment | Closed-won value in the CRM | Pipeline covers about three times the target | Mid-market is this year’s growth segment | End of Q3 |
| Raise my conversion rate from qualified opportunity to closed deal from 20% to 25% by year end by using a mutual action plan on every deal over €20,000. | Qualified opportunities; mutual action plans | Win rate on qualified opportunities | Plan template provided by sales enablement | Better forecast accuracy and revenue | Year end |
| Book 12 discovery meetings a month with named target accounts in the healthcare sector from April to June. | Named healthcare target accounts | Discovery meetings held per month | Supported by a sector campaign from marketing | Healthcare is a new target market | April to June |
| Sales development representative | |||||
| Generate 40 sales-qualified opportunities in Q2, with at least 60% accepted by account executives within two working days. | Qualified opportunities handed to account executives | Opportunities created and acceptance rate | In line with last quarter plus one new sequence | Feeds the account executives’ pipeline | End of Q2 |
| Reach a 15% reply rate on outbound sequences to the retail segment by 30 September by rewriting the three lowest-performing sequences. | Retail outbound sequences | Replies as a share of prospects contacted | Three rewrites over a quarter | Retail pipeline is below plan | 30 September |
| Complete certification on the new product line and run five qualified demos of it independently by 31 May. | New product line; certification and demos | Certification passed; five demos logged | Training time agreed with the manager | The new product launches this year | 31 May |
| Account manager | |||||
| Keep gross revenue retention across my book of 45 accounts at or above 92% for the financial year. | Existing book of 45 accounts | Gross revenue retention from finance reports | In line with last year’s result | Retention protects recurring revenue | Financial year end |
| Hold a documented business review with each of my top 15 accounts by the end of Q2, each ending in an agreed success plan. | Top 15 accounts; business reviews | Reviews held with a success plan attached | About one review a week | Reviews surface risk and expansion early | End of Q2 |
| Grow expansion revenue from existing accounts by €80,000 in the second half by introducing the analytics add-on to accounts with more than 200 users. | Accounts with more than 200 users; analytics add-on | Expansion revenue booked | A defined list of eligible accounts | Expansion is part of this year’s revenue plan | Second half of the year |
SMART goals examples for engineering roles
Engineering goals work best when they describe a change a user or colleague would notice — faster, more reliable, easier to work on — rather than a count of tickets closed.
Examples
SMART goals for engineering roles
| SMART goal | Specific | Measurable | Achievable | Relevant | Time-bound |
|---|---|---|---|---|---|
| Software engineer | |||||
| Reduce the 95th-percentile response time of the search API from 900 ms to under 400 ms by the end of Q3 without increasing infrastructure cost. | Search API latency | 95th-percentile response time from monitoring | Profiling has already identified the slow queries | Search speed affects customer conversion | End of Q3 |
| Raise automated test coverage on the billing service from 55% to 75% by 30 September, starting with the invoicing and refund paths. | Billing service; invoicing and refund paths first | Line coverage in the CI report | About a day a week over the quarter | Fewer billing defects reaching customers | 30 September |
| Cut the median time to first review on the payments team’s pull requests from two days to one by the end of Q2 by setting up a review rota. | Payments team pull requests; review rota | Median hours from opening to first review | Rota agreed with the team lead | Faster delivery on the payments roadmap | End of Q2 |
| Engineering team lead | |||||
| Reduce production incidents caused by deployments from six a quarter to two by Q4 by introducing automated rollback on the three highest-traffic services. | Deployment-related incidents; automated rollback | Incidents tagged as deployment-caused | Rollback tooling already used on one service | Reliability is a company objective this year | By Q4 |
| Hold a fortnightly one-to-one with each of my seven reports and agree a development goal with each by 31 March. | Seven direct reports; one-to-ones and development goals | One-to-ones held; seven goals agreed | About two hours of one-to-ones a week | Supports retention and growth in the team | 31 March, then ongoing |
| Onboard two new engineers so each ships a change to production within two weeks and works independently on a ticket by the end of their second month. | Two new starters; first change and independence | Dates of first production change and first solo ticket | A buddy assigned to each new starter | Team capacity for the second-half roadmap | Two weeks and two months from start |
| Platform engineer | |||||
| Cut the average build time for the main application from 18 minutes to 8 by the end of Q2. | Main application build pipeline | Average build time from CI metrics | Caching and parallelisation options identified | Every engineer waits on the build | End of Q2 |
| Achieve 99.9% monthly availability for the customer API in each month of Q3, measured by the external uptime monitor. | Customer API availability | Monthly availability from the uptime monitor | Recent months have been close to the target | Availability is a commitment to customers | Each month of Q3 |
| Document and test a recovery runbook for each of the five critical services, including a timed restore drill, by 30 November. | Five critical services; runbooks and drills | Runbooks published; drill times recorded | One service a month | Business continuity planning | 30 November |
SMART goals examples for customer support roles
Support teams usually have plenty of KPIs already. A SMART goal is the right tool when one of them needs to move this period, or when the work behind the numbers needs to change.
Examples
SMART goals for customer support roles
| SMART goal | Specific | Measurable | Achievable | Relevant | Time-bound |
|---|---|---|---|---|---|
| Support agent | |||||
| Keep my customer satisfaction score at 90% or above each month in Q3 while handling my share of the queue. | Personal satisfaction score | Monthly score from post-ticket surveys | In line with the last two quarters | Customer satisfaction is a team KPI | Each month of Q3 |
| Resolve 75% of my tickets on first contact by the end of Q2, up from 65%, after completing the advanced troubleshooting module in April. | First-contact resolution; troubleshooting training | Share of tickets resolved without a follow-up | Training booked; ten-point gain over a quarter | Fewer repeat contacts for customers | End of Q2 |
| Write or update eight help-centre articles on the most frequent billing questions by 31 August. | Billing help-centre articles | Eight articles published | About two hours a week | Self-service reduces billing contacts | 31 August |
| Support team lead | |||||
| Bring first-response time on priority tickets under one hour for 95% of cases during business hours by the end of Q3, up from 80%. | Priority tickets in business hours | Share answered within one hour | Rota changes are within the lead’s control | Meets this year’s service commitment | End of Q3 |
| Reduce the backlog of tickets older than seven days from 140 to below 30 by 30 June. | Tickets older than seven days | Count from the helpdesk report | Daily triage slot for two agents | Resolving issues within service levels | 30 June |
| Review five tickets per agent each month and give each agent written feedback within a week, from April to September. | Monthly quality reviews for every agent | Reviews completed and feedback dates | About half a day a month | Consistent quality across the team | April to September |
| Support operations specialist | |||||
| Halve repeat contacts about password resets by the end of Q4 by publishing a guided self-service flow. | Password-reset contacts; self-service flow | Repeat contacts tagged as password resets | Flow built with the product team’s agreement | Frees agent time for complex issues | End of Q4 |
| Introduce a ticket-tagging scheme and tag every new ticket consistently from 1 September, so product teams receive a monthly top-ten issues report. | Ticket tagging and a monthly report | Share of new tickets tagged; report delivered | Scheme agreed with team leads in August | Product teams fix the causes of contacts | From 1 September |
| Reduce average handle time on refund requests from 14 to 9 minutes by 31 October with macros for the five most common cases. | Refund requests; five macros | Average handle time from the helpdesk | Macros take about two weeks to build and test | Faster refunds for customers | 31 October |
SMART goals examples for healthcare roles
In healthcare, many of the most important goals are about competence, documentation and access rather than volume. These examples are about how work is organised and evidenced; they are not clinical guidance, and any target should follow your organisation’s policies and clinical governance.
Examples
SMART goals for healthcare roles
| SMART goal | Specific | Measurable | Achievable | Relevant | Time-bound |
|---|---|---|---|---|---|
| Registered nurse | |||||
| Complete supervised practice and sign-off on the ward’s competency for central venous catheter care by 31 March. | One named clinical competency | Signed-off competency on the record | Supervision sessions agreed with the practice educator | The ward needs more staff signed off | 31 March |
| Use the ward’s structured handover checklist for every handover I lead in Q2, confirmed in the monthly audit of ten handovers. | Handovers I lead; structured checklist | Monthly handover audit results | Checklist already in use on the ward | Supports safe continuity of care | Throughout Q2 |
| Mentor one newly qualified nurse through their preceptorship, meeting fortnightly and completing every review point on schedule by 30 September. | One preceptee; fortnightly meetings | Review points completed on time | Protected time agreed with the ward manager | Retention of newly qualified staff | 30 September |
| Ward manager | |||||
| Bring the ward’s monthly hand hygiene audit result to at least 95% for three consecutive months by the end of Q3. | Ward hand hygiene audit | Monthly audit result | Recent results are close to the target | Infection prevention objective | End of Q3 |
| Make sure every member of staff on the ward has an in-date annual appraisal and competency record by 31 January. | All ward staff; appraisals and competency records | Share of staff with both in date | Appraisals scheduled across four months | Evidence of competence for inspection and assurance | 31 January |
| Reduce agency shifts from 60 to 35 a month by the end of Q4 by filling rota gaps from the internal staff bank first. | Agency shifts; internal bank | Agency shifts booked per month | Bank staff already registered for the ward | Staffing cost and continuity of care | End of Q4 |
| Allied health and clinic administration | |||||
| Reduce the wait for a first outpatient physiotherapy appointment from eight weeks to five by 31 December by adding two group sessions a week. | Physiotherapy outpatient waiting time | Weeks from referral to first appointment | Group sessions fit existing clinic capacity | Access targets for outpatient services | 31 December |
| Send the discharge letter to the patient’s GP within 48 hours of discharge for 95% of patients by the end of Q2. | Discharge letters to GPs | Share sent within 48 hours | Template and workflow already agreed | Continuity of care after discharge | End of Q2 |
| Cut missed outpatient appointments from 10% to 7% by 30 September by sending reminders 48 hours before each appointment. | Missed outpatient appointments; reminders | Missed appointments as a share of those booked | Reminder system already available to the clinic | Better use of clinic capacity | 30 September |
All figures are illustrative. Clinical targets, audit standards and competency requirements come from your organisation, its regulators and its clinical governance, not from this list.
SMART goals, OKRs and KPIs: how they fit together
SMART is a standard for writing one goal. OKRs are a way of organising goals: an objective that describes a change, and a small number of key results that show whether it happened. KPIs are ongoing measures of how a role, team or process is performing. The three are not competing methods, and most organisations use all of them.
The overlap is where they are most useful together. A well-written key result is usually a SMART goal — specific, measured against a baseline and due by the end of the quarter. A KPI becomes a SMART goal when it needs to move rather than hold steady: the support agent above who wants to lift first-contact resolution from 65% to 75% is turning a KPI into a goal for one quarter, after which it goes back to being monitored.
A practical rule: use KPIs for the work that should stay healthy, SMART goals for the specific changes a person is accountable for this period, and OKRs when a team needs to rally several of those changes around one ambitious objective.
Cascading SMART goals into OKRs
The relevant test in SMART asks which objective a goal serves. In an OKR programme, that answer is the cascade. Four steps keep the two connected.
Start with the organisation objective
Take one annual objective, such as ‘make our service effortless for customers’. It describes a change, not a number, and it should not be copied down unchanged.
Translate it into team key results
Each team asks what distinct contribution it can make. For support, a key result might be ‘bring first-response time on priority tickets under one hour for 95% of cases by the end of Q3’ — already a SMART goal.
Write individual SMART goals beneath the key results
The team lead owns the first-response key result; an agent owns ‘resolve 75% of my tickets on first contact by the end of Q2’; the operations specialist owns the password-reset self-service goal. Each is SMART on its own and traceable upwards in two steps.
Weight the goals and review them together
Weight each person’s goals so the linked ones carry the priority they deserve, and check progress at the same rhythm as the key results. When a key result changes mid-quarter, the goals beneath it are revised in the same conversation.
Two cautions. First, keep the levels few — organisation, team and individual is enough for most organisations, and every extra layer weakens the line of sight. Second, do not push stretch OKR scores straight into individual ratings: stretch key results are meant to be missed sometimes, so many organisations weight committed SMART goals and KPIs in the review and treat stretch results as context.
Common mistakes when writing SMART goals
- Measuring activity instead of outcomes
- ‘Make 50 calls a week’ is measurable, but it rewards effort rather than results. Measure what the activity is supposed to produce, and let the person decide how to get there.
- No baseline
- A target without a starting point cannot be judged as ambitious or trivial. If the data does not exist yet, make establishing it the first goal.
- Too many goals
- Twelve goals get looked at once, at year end. A short, weighted list tells people what matters most and can actually be discussed at every check-in.
- Goals the person cannot influence
- Assigning a company-wide revenue number to someone with no line of influence over it fails the achievable test, however well the sentence is written.
- Set and forget
- A goal agreed in January and not mentioned again until December is documentation, not management. Checkpoints are part of the time-bound criterion for a reason.
- Rewriting goals at year end
- Changing a goal when priorities move is healthy. Changing it after the fact so the result reads better destroys trust in the whole process. Revise openly, at a check-in, with the reason recorded.
Where CLEAR Talent fits
CLEAR Talent is methodology-agnostic: SMART goals, OKRs with key results and weighted KPIs sit on one platform, and different departments and levels can use different frameworks while still rolling up to the same organisation objectives. Through Strategic Linked Goals, an individual goal cannot be created without a parent objective, so the relevant test is built into the structure rather than left to memory.
Ava, the platform’s AI assistant, can suggest SMART goals for a role as a starting point for the employee and manager to edit, and every Ava output is labelled and editable. Goals an employee drafts go to their manager, who can approve them, reject them or send them back with requested changes. A person’s goal weights for a period cannot total more than 100%, goals falling behind are flagged from pace and check-in signals, and goal scores roll into the performance review automatically with the weighting you configure.
What no tool can do is decide which outcomes matter to your organisation this year. That remains a conversation between leaders, managers and the people doing the work.