SMART Goals Framework for Coaches: A Worked Guide

The SMART goals framework for coaches is useful when it makes an objective understandable, feasible and reviewable. A polished sentence is only the beginning. The client still needs meaningful evidence, actual ownership, room to act and a way to revise the plan.

This guide distinguishes the original wording from a common later version, builds a complete goal and follows three actual fictional attempts through a mixed review. It includes a failed update, an extra time cost and a useful question that the client should not try to eliminate.

Define the SMART version you are using

George T. Doran’s 1981 Management Review article used Specific, Measurable, Assignable, Realistic and Time-related. It also cautioned against insisting on quantification everywhere or expecting every objective to meet all five criteria. The objective and its action plan belonged together.

A common later version uses Specific, Measurable, Achievable, Relevant and Time-bound. The CDC’s current learning-objective guidance uses that formulation in a training context. Its existence does not establish that this acronym is a validated coaching assessment or guarantees achievement.

The table below uses the later wording while retaining explicit ownership and resources checks. Say which version you mean. A client using another familiar version is not automatically wrong.

Use these as questions, not a five-point personality score. A goal can satisfy the wording and still aim at an unhelpful result, such as preventing colleagues from asking necessary questions.

Begin with a worthwhile difference

Ask what the client wants to use the goal for before making it more precise. “Improve executive presence” might mean explaining a recommendation, hearing objections or staying within a decision role. Those are different tasks.

Find one recent situation and identify the actual starting point. What was asked, what did the client do and what consequence matters? Avoid turning another person’s broad criticism into the client’s objective without discussion.

A required organizational outcome and a personal development goal can coexist. A client may need to deliver a report while choosing to work on how they clarify its scope. Agree the relationship between those goals and what will appropriately be shared.

The ICF Code of Ethics supports clear roles, agreements and information exchange. Sponsor requirements do not automatically make personal reflections a performance report.

If the client is still choosing a direction, a learning objective may be more useful than a premature output target. Investigating two possible roles can be worthwhile before setting a weekly job-application number. Precision should serve the decision rather than lock the client into the first idea.

Choose evidence before choosing a target number

Separate the client’s action, the quality of that action and the response it receives. Sending three briefs is an activity count. Sending briefs with the agreed information is a quality question. A colleague understanding the next step provides a different observation.

Specify the unit. Are you counting people, opportunities, documents, questions or completed reviews? A numerator without its eligible denominator can make incomplete evidence appear stronger than it is.

Include a baseline where it helps. Use a comparable period or explain what differs. Three historical examples and three later examples can support a discussion, but they do not establish a stable rate or prove coaching caused a difference.

Qualitative evidence can be more appropriate than an arbitrary score. A work sample, a decision with reasons or a colleague’s actual words can answer a useful question. Record the source and what remains unknown.

For subjective ratings, agree what the scale means to the client. A move from four to six is not automatically a fifty-percent improvement in confidence or ability. Ask what happened in the situation and retain contrary evidence.

Check feasibility and choose performance or learning

Check the actual time, skills, information, authority and support needed. A client can own their preparation while another person owns a resource decision. Obtain that person’s acceptance before writing the dependency as settled.

The HSE role standard emphasizes clear responsibilities and routes for raising uncertainty. A goal cannot create authority that the organization has not provided. A lower ambition also cannot by itself resolve incompatible obligations.

Locke and Latham’s 2002 goal-setting review discusses feedback and task complexity as important conditions. It distinguishes acquiring a useful strategy on unfamiliar complex work from simply pursuing a demanding performance result. It is a broader research review, not a trial of this worksheet or proof of every SMART formulation.

For familiar work, an appropriate performance objective may be useful. For unfamiliar work, a learning objective could specify testing two approaches, identifying what works and explaining the choice. Do not demand a perfect result before the client has learned the necessary method.

Keep required controls intact. A goal to delegate does not authorize abandoning review. A goal to reduce unnecessary questions should not discourage clarification of an actual risk.

Use dates to coordinate work and review

Distinguish the external deadline from the date chosen for practice. A client may need a decision by Friday but review their approach after one meeting. Those dates serve different purposes.

Include dependencies and notice when they change. If a review partner withdraws, do not silently retain a promise that relied on that input. Agree a substitute, revise the sequence or record that the original plan cannot currently be delivered.

Define a revision condition: a changed role, missing resource, unsuitable indicator or unexpected consequence may justify changing course. A missed action might instead need a smaller step or clearer instruction. Review the reason rather than automatically tightening the deadline.

A target date is not proof that an owner accepted the work. A saved task is not proof it happened. Keep those states visible in the review record.

Complete fictional example: clearer handovers without silencing questions

All people, dates, records and results below are invented. Rina manages an operations team. Meredith provides two forty-five-minute coaching meetings on 3 and 24 November 2026, with no asynchronous coaching included.

Rina initially wants her colleagues to stop interrupting her with questions. They inspect three routine handovers from 26, 28 and 30 October. Each generated one later question: two concerned information Rina had not supplied or updated; one concerned a genuine tradeoff not resolved by the brief.

The baseline is three handovers with three later questions, classified as two avoidable information gaps and one useful tradeoff question. The classification is an original working distinction, not a judgment that the colleagues should have stayed quiet.

Rina chooses a different purpose: help the receiving person identify the current priority and next step while keeping necessary questions welcome. She does not set a target of zero questions.

Write the objective and its actual dependencies

For my three routine handovers on 5, 12 and 19 November, I will send one current brief showing the priority, decision owner, precise due date and known constraint or uncertainty. I will ask the receiving colleague to describe the next step, and record later priority changes in the same current brief. I will retain later questions and their cause for review on 24 November.

This is Rina’s chosen objective. It includes both initial quality and later updating; merely sending three files will not fulfill it.

On 4 November, her manager Inez agrees to protect three twenty-minute blocks for Rina’s brief preparation and recording, one per handover. Tess and Omar agree to the short receiving-person readback within their existing handover conversations. These acceptances occur before the planned work.

The sixty protected minutes cover only Rina’s stated preparation and record work. They do not represent whole organizational effort, the handover meetings or the coaching sessions. Other work still has to be coordinated through the team’s normal arrangements.

Fill the goal worksheet

Keep all three attempts, including the failures

5 November: complete first brief, failed later update

Rina sends Tess a brief with all four agreed fields. Tess describes the intended next step during the handover. On 6 November, Inez changes the priority. Rina passes the change on verbally but does not update the brief.

Tess later asks which priority now applies because the document and conversation differ. This is an avoidable information gap in the agreed process, not evidence that Tess is resisting ownership.

Rina updates the brief to version two on 6 November, states the changed priority and sends it to Tess. Tess acknowledges the update and describes the revised next step. The repair occurs, but the initial failure to log the change remains in the review.

That repair takes ten additional minutes of Rina’s preparation and record work beyond the first protected twenty-minute block. It is not silently absorbed into the original allowance.

12 November: readback finds a missing deadline

The first brief sent to Omar contains the priority, owner and known constraint but says only “by Friday” for the deadline. During the handover, Omar asks which time is intended.

Rina confirms 15:00 UTC on 13 November and updates the brief before they finish. Omar repeats the next step and the precise deadline. This is an initial completeness failure detected and repaired during handover, not a later question after handover.

The correction and recording fit within that handover’s twenty-minute preparation/record block. Do not count its question in a different time window simply to make the later-question metric look better.

19 November: complete brief and a legitimate later uncertainty

Rina sends Tess a brief with all four fields and receives a next-step readback. Later, a dependency involving information from another department becomes uncertain. Tess asks which route to use if that information is not supplied.

The brief did not eliminate this new question. Rina records it as useful, and the resource decision remains open at the review cutoff. She does not mark the underlying work complete because the handover document was complete.

This third preparation and recording block takes twenty minutes. Across the three handovers, Rina uses sixty planned minutes plus the ten-minute first-case repair: seventy minutes in that defined work category, ten above its protected allowance. Other participants’ effort remains outside this subtotal.

Review the right denominators and the whole objective

At the 24 November review, Rina’s draft says she completed the goal successfully on all three occasions. Meredith asks whether that statement includes the original quality and update conditions. It does not.

Rina replaces it with this account:

I issued three briefs and completed three readbacks. Two first versions contained all agreed fields. One deadline was clarified during handover. I failed to log a later priority change until a colleague asked, then repaired it. One later question concerned a new legitimate uncertainty that remains open. My preparation and record work exceeded its protected allowance by ten minutes.

The historical and later question counts describe different small sets of work. The later two questions compare with three earlier questions, but the tasks and circumstances are not controlled. Do not report a coaching-caused reduction or invent time savings from the count.

The goal was partly achieved, with useful feedback about its design and implementation. The unmet updating condition is not erased by a later repair, and a legitimate question is not a failure to be suppressed.

Choose the next action without rewriting history

Rina decides that the next issue is keeping priority decisions and written updates connected. She does not simply increase the target to ten handovers or demand fewer questions from colleagues.

On 25 November she asks Inez, Tess and Omar to agree an operational review on 1 December about how priority changes enter the current brief. All three accept that date. The review will consider the open resource issue as well, rather than treating it as resolved.

The 1 December conversation and any revised process remain future work. Meredith’s coaching service ended with the 24 November session; the internal meeting does not add another coaching obligation. Rina keeps the original goal and observed review alongside the proposed next action.

A changed objective should have a date and reason. Do not alter the original standard retrospectively so every past attempt appears successful. If the client chooses to stop pursuing a goal, record the choice and what remains owed to other people.

Contrast a learning goal for unfamiliar work

Consider a separate hypothetical manager who has never structured a handover. A target to produce three flawless briefs may not address the missing skill. A more useful first goal could be to compare two approved example structures, draft one invented practice brief and explain how its owner, deadline and uncertainties are shown by the next training review.

Its evidence would be the comparison, draft and explanation, not the absence of questions from a live team. After relevant feedback and instruction, the manager might choose an appropriate workplace trial. Neither the practice draft nor a SMART sentence establishes readiness for a consequential task.

This contrast illustrates goal selection; it is not another observed coaching result. Use the actual task and competence rather than assume that raising difficulty always raises performance.

Use qualitative evidence when a count misses the purpose

A separate hypothetical client wants to explain a recommendation more clearly. A target of five contributions per meeting could reward repetition without improving understanding. Instead, the client could prepare one short recommendation for the next review, distinguishing the chosen option, supporting evidence, main uncertainty and decision required.

The review question would be whether an appropriate receiving person can identify those elements and explain what decision is being requested. The output might read: “Choose option A because it meets the stated requirement using the available resource. The unresolved dependency is the external input. Today’s request is approval to investigate that dependency, not approval to begin delivery.”

That original sample provides material to examine without inventing a confidence percentage. The actual receiver must still be available and willing to review it, and the client needs to retain any misunderstanding or disagreement. A fluent rehearsal alone is insufficient evidence.

The goal can have a date and a concrete review method while its main evidence remains the quality of an explanation. Numerical activity can be recorded where useful, but should not replace the purpose of the work.

Keep the chosen goal and evidence organized in Coachful

Coachful is our #1 recommendation for connecting selected goals, actions and coaching review. This is our editorial recommendation as its publisher. A completion count can support the discussion, but does not establish that a complex objective has been achieved.

Prepare an original worksheet with the purpose, starting evidence, objective, owner, resource decisions and review questions. Deliberately assign it through Clients > the client > Worksheets & resources > Assign. A copied private link alone does not grant access, and staff preview is not a submitted answer.

The goal activity image illustrates linked tasks and habits with reflection areas. Keep the client’s original goal wording and quality evidence available rather than treating task ticks as a complete result. Business briefs and their actual approvals remain in the organization’s approved systems; the coaching record can contain the selected de-identified learning summary.

Explain the actual review audience before submission. If a summarized session contains sensitive context, check the automatic recap default and the workspace and session-type approval settings. Review a held recap before sending appropriate selected content; a software setting is not sponsor-disclosure permission.

Use the goal-setting worksheet guide to explore purpose before fixing the target, and the recalibration guide for a deliberate revision. Explore Coachful’s features for coordinated preparation and follow-through.

Frequently asked questions

Does SMART have one universal expansion?

No. Doran’s original Assignable and Realistic wording differs from common later versions. Name the one you use and preserve practical checks for ownership, resources and purpose.

Must a useful goal contain a number?

No. A work sample, explanation or decision can provide meaningful evidence. Define how you will review it rather than manufacture a number that misses the purpose.

Does completing every task mean the goal is achieved?

No. Activity, quality and outcome can differ. In the example, three issued briefs did not fulfill every initial-quality and later-update condition.

Should all follow-up questions disappear?

No. Some reveal missing information; others identify new uncertainty or a genuine tradeoff. A goal that discourages necessary questions can undermine the work.

When should a learning goal come first?

Consider it where the person needs to acquire or test an unfamiliar strategy. Appropriate instruction and feedback may be necessary before a demanding live performance target.

Can the client revise the goal?

Yes. Record the reason, date and next decision while retaining the original standard and observations. Revision should improve the plan rather than hide a missed condition.