Strategy · Goals that guide action
SMART Goals: 20 Examples for Work, Business, and Finance
A useful goal tells people what success looks like, how it will be measured, and when it is due. SMART goals provide a practical way to turn a broad ambition into a clear commitment. This guide explains the five criteria, demonstrates 20 workplace examples, and shows how to connect a goal to the work and evidence needed to achieve it. ← Strategy hub · Strategic Objectives · Strategy ImplementationQuick answer: SMART commonly stands for Specific, Measurable, Achievable, Relevant, and Time-bound. A strong goal defines a result, a way to verify it, a realistic resource commitment, a business purpose, and a deadline. SMART improves the clarity of a goal; it does not guarantee the goal is strategically sound or achievable.
Jump to: The five criteria · Accounting examples · Finance examples · Management examples · Sales and service examples · Goal template
What does SMART stand for?
| Criterion | Question to answer | Practical writing check |
|---|---|---|
| Specific | What result must change, and who owns it? | Name the outcome, scope, and accountable role. |
| Measurable | What evidence will show progress and success? | Define the baseline, target, data source, and calculation or acceptance test. |
| Achievable | Can the team reasonably deliver with its resources and constraints? | Check capacity, skills, budget, authority, and dependencies. |
| Relevant | Why does this result matter? | Connect it to customer value, strategy, risk, or a meaningful development need. |
| Time-bound | When is success due, and when will progress be reviewed? | Specify the deadline and useful interim checkpoints. |
Turn a vague goal into a SMART goal
Before: “Improve the monthly close.” After: “By the third monthly close after launch, the accounting lead will reduce the standard close from 10 to 7 business days for the agreed entity scope, using a close checklist and earlier reconciliation reviews, while completing required approvals and maintaining zero unresolved material reconciliation differences at sign-off.” The revised statement identifies the owner, scope, baseline, target, timing, approach, and quality condition. Before approving it, confirm that the team has the required system access, coverage, and time. A deadline and a number alone cannot establish achievability.How to use the 20 examples
Every example below is hypothetical. The targets are teaching examples, not industry benchmarks or recommended standards for every organization. Each assumes that the named owner has agreed on the scope and secured the necessary capacity and approvals. Replace the assumptions with your actual baseline, workload, risk, and resources. “Within 90 days” means 90 days from an agreed launch date; put actual dates in the final plan. Define materiality, quality criteria, and exclusions before work begins. Keep missed deadlines and exceptions visible rather than changing the denominator after seeing results.SMART goal examples for accounting
1. Complete the monthly close sooner
Vague: “Close faster.” SMART: By the third close after launch, the accounting lead will reduce the standard monthly close from 10 to 7 business days across the five in-scope entities by introducing a dependency-based checklist, while retaining all required reviews and resolving material reconciliation differences before sign-off. Track: business days from month-end to approved close; checklist completion and unresolved differences. Purpose: give management timely, reliable information.2. Reduce overdue bank reconciliations
Vague: “Keep reconciliations current.” SMART: Within 60 days, the reconciliation lead will reduce overdue bank reconciliations from 12 to zero for the agreed 12-account backlog, with reviewer approval and every unresolved item assigned an owner and resolution date, using two protected work sessions each week. Track: overdue reconciliations by account and period, reviewer sign-off, and open-item aging. Purpose: improve confidence in cash records.3. Prevent duplicate vendor bills
Vague: “Make fewer AP errors.” SMART: By the end of the third month, the AP lead will reduce confirmed duplicate bills posted from 8 to no more than 2 per 1,000 bills entered, using vendor-and-invoice checks and exception review without delaying complete, valid bills beyond the agreed processing standard. Track: confirmed duplicates ÷ bills entered × 1,000, with the same detection window and scope each month. Purpose: reduce avoidable corrections and payment risk.4. Improve invoice approval turnaround
Vague: “Get approvals quicker.” SMART: Over the next 90 days, the AP manager and department approvers will increase complete invoices approved within three business days from 60% to at least 85%, using a shared queue and twice-weekly escalation while preserving authorization limits. Track: invoices approved within the standard ÷ complete invoices entering the defined approval cohort × 100; report still-open invoices after the three-day window. Purpose: avoid preventable payment delays.5. Deliver reporting packages on time
Vague: “Improve reporting.” SMART: By the third monthly close, the reporting lead will increase packages delivered within 10 business days from 14 of 20 to at least 19 of 20, using an intake calendar and reviewer schedule while completing all mandatory quality checks before release. Track: on-time packages ÷ packages due × 100, plus correction severity. Purpose: make reporting dependable. See the related 90-day implementation example.SMART goal examples for finance and FP&A
6. Improve short-term cash forecasting
Vague: “Forecast cash better.” SMART: Within 12 weeks, the treasury analyst will reduce the mean absolute weekly error in the one-week-ahead ending-cash forecast from $20,000 to $10,000 or less, measured over the final six weekly forecasts, using a payment calendar and collection updates while flagging potential minimum-cash breaches immediately. Track: average absolute difference between each frozen forecast and actual ending cash. Purpose: improve funding decisions; keep forecast timing consistent.7. Explain budget variances
Vague: “Do better variance analysis.” SMART: Starting with the next monthly review and continuing for three months, the FP&A lead will deliver explanations and assigned follow-up actions for 100% of expense variances meeting both the preapproved $5,000 and 10% thresholds, within five business days of receiving the approved close. Track: qualifying variances with supported explanations and actions ÷ all qualifying variances. Purpose: focus management attention on material drivers. Escalate other significant risks even if they fall below the thresholds.8. Reduce overdue receivables
Vague: “Collect faster.” SMART: Over the next 90 days, the collections lead will reduce the agreed starting cohort of receivables more than 60 days overdue from $100,000 to $70,000 or less through documented customer follow-up and dispute resolution, with no unapproved write-offs or concessions. Track: remaining balance in that fixed cohort; report cash collected, credits, and write-offs separately. Purpose: improve liquidity without disguising losses as collections.9. Improve revenue forecast accuracy
Vague: “Make the forecast accurate.” SMART: For the next three monthly forecasts, the FP&A analyst will reduce average absolute percentage error from 12% to 8% or less for the agreed nonzero-revenue business scope, using pipeline and renewal inputs collected by the forecast cutoff. Track: average of |frozen forecast − actual revenue| ÷ actual revenue × 100 across the three periods. Purpose: improve planning; use an agreed alternative when actual revenue is zero and disclose the treatment.10. Build a decision-ready investment case
Vague: “Analyze the new system.” SMART: Within six weeks, the finance lead will deliver a reviewed business case for the proposed reporting system, including documented costs, cash timing, base/downside/upside assumptions, sensitivity analysis, and an implementation recommendation, with every material assumption assigned a source and owner. Track: acceptance against the agreed review checklist, rather than a forced favorable result. Purpose: support a sound resource decision. Separate released staff capacity from actual cash savings.SMART goal examples for managers and professional development
11. Improve action-item follow-through
Vague: “Make meetings productive.” SMART: Within eight weeks, the team manager will increase actions completed by their agreed due date from 65% to at least 90%, using named owners and weekly blocker reviews, while retaining original dates and documenting approved changes. Track: actions completed on time ÷ actions due in the period × 100. Purpose: turn meetings into accountable execution.12. Establish backup coverage
Vague: “Cross-train the team.” SMART: Within 90 days, the department manager will establish one assessed backup for each of four critical recurring processes, with each backup independently completing a supervised test cycle against the approved checklist and access rules. Track: critical processes with a qualified backup ÷ four. Purpose: reduce key-person dependency without weakening review controls.13. Demonstrate Excel reporting proficiency
Vague: “Learn advanced Excel.” SMART: Within eight weeks, the analyst will use three protected practice hours per week to build a repeatable monthly reporting workbook with structured tables, lookup formulas, and a PivotTable, refresh it successfully for two sample periods, and reconcile every reported total to the approved source data. Track: completed workbook, successful refresh tests, and reviewer sign-off. Purpose: turn learning time into a demonstrable reporting capability.14. Make onboarding repeatable
Vague: “Improve onboarding.” SMART: Within 60 days, the team lead will document and test the first-30-day onboarding plan for the AP role with one pilot hire or designated tester, covering system access, core workflows, review responsibilities, and escalation routes, with all critical checklist items accepted by the process owner. Track: tested checklist and resolved critical gaps. Purpose: reduce avoidable confusion; a completed document alone does not demonstrate an effective experience.15. Strengthen coaching follow-through
Vague: “Develop my employees.” SMART: During the next quarter, the manager will agree on one role-relevant development outcome with each of six team members, hold a monthly progress conversation with each, and document evidence of progress and one next action at every review. Track: completed reviews and progress against each individual outcome. Purpose: support capability growth; meeting counts alone are not proof of improved performance.SMART goal examples for sales, customer service, and operations
16. Improve lead qualification
Vague: “Get better leads.” SMART: Within 90 days, the sales lead will increase the share of inbound leads meeting the agreed customer-fit criteria from 25% to 35%, using revised intake questions and targeted messaging while maintaining at least the baseline number of qualified leads per month. Track: qualified leads ÷ all in-scope inbound leads, plus the absolute count. Purpose: improve fit without creating a better percentage by shrinking useful demand.17. Improve proposal conversion
Vague: “Win more business.” SMART: By the end of the next quarter, the sales manager will increase the win rate for the defined completed-proposal cohort from 20% to 25%, using a standardized discovery checklist and follow-up plan while preserving the approved minimum pricing policy. Track: won proposals ÷ won-and-lost proposals in the cohort × 100; report still-open proposals separately. Purpose: win suitable business without hiding long-running decisions.18. Improve customer response times
Vague: “Respond faster.” SMART: Within eight weeks, the service lead will increase tickets receiving a meaningful first response within one business day from 70% to 90%, using queue ownership and coverage scheduling, with automated acknowledgments excluded from the response measure. Track: eligible tickets meeting the standard ÷ eligible tickets whose response window has elapsed. Purpose: improve responsiveness; monitor resolution quality separately.19. Reduce repeat customer issues
Vague: “Fix complaints.” SMART: By the end of the third month, the operations lead will reduce repeat tickets for the same documented issue within 14 days of closure from 15% to 10% or less, using root-cause reviews and a resolution checklist while allowing customers to reopen unresolved cases. Track: closed tickets with a same-issue repeat ÷ closed tickets with a full 14-day observation window × 100. Purpose: improve lasting resolution instead of closing tickets prematurely.20. Improve on-time order delivery
Vague: “Make operations efficient.” SMART: Within 90 days, the operations manager will increase orders delivered by the originally confirmed date from 85% to at least 95%, using a capacity review and exception alerts while keeping the damaged-order rate at or below its 1% baseline. Track: on-time orders ÷ orders due in the period × 100; report damage separately. Purpose: improve reliability without sacrificing product condition or moving promised dates to improve results.A reusable SMART goal template
Goal statement: By [deadline], [owner] will improve or deliver [defined outcome] for [scope], moving from [baseline and period] to [target], through [main actions], in support of [business purpose], while maintaining [quality, cost, or risk condition].
Implementation notes: Record the metric formula, source, reporting cutoff, available resources, dependencies, review dates, and escalation trigger. A short goal statement can link to these details instead of becoming an unreadable paragraph.
For a deliverable goal, replace a numeric improvement with an explicit acceptance test: what must exist, work correctly, and pass review? “Finish the spreadsheet” is weak; “refresh the workbook for two periods and reconcile all reported totals” is verifiable.
Choose the KPI and monitor progress
A goal states the result and deadline. A KPI is the measure used to evaluate performance. An initiative is the work intended to improve it. For example, on-time delivery is the KPI, 95% by the third close is the target, and redesigning intake is an initiative.- Freeze the baseline: record its period, scope, and known limitations.
- Define the measure: specify numerator, denominator, timing, exclusions, and the source owner.
- Assign feasible work: secure capacity and authority, then set milestones and dependencies.
- Review evidence: compare actual performance with the target, trend, and quality guardrails.
- Decide: continue, adjust the work, resolve a constraint, or reconsider an assumption. Record why.
Common SMART goal mistakes
- Picking a target before checking the baseline: understand normal variation and the actual constraint first.
- Assuming a precise number is achievable: validate workload, budget, skills, and authority.
- Measuring activity as the final result: training sessions, calls, or checklists may be useful inputs but do not prove better outcomes.
- Rewarding speed without quality: add approval, accuracy, safety, or customer guardrails as appropriate.
- Hiding exceptions: show missing data, still-open work, and changes to scope or dates.
- Making every goal a stretch: distinguish minimum obligations, expected improvements, and experiments with uncertain results.