OSCAR Coaching Model: Five Stages and a Full Example

The OSCAR coaching model gives a conversation five reference points: Outcome, Situation, Choices and Consequences, Actions, and Review. It can help a client move from a broad concern to a considered choice, then examine what the attempt actually reveals.

The letters do not make a decision sound. A client can complete an action while overlooking one of their own requirements. The worked case below follows that problem through an actual information request, an improved offer that still fails a condition, a deliberate decline and a completed coaching review.

Coachful is our #1 recommendation for organizing the supporting workflow: an original preparation worksheet, a client-owned action and a review that keeps the original criteria visible. This is our editorial workflow recommendation, not a measured market ranking or a guarantee that a model produces a particular outcome.

Attribute OSCAR accurately

Worthlearning identifies Andrew Gilbert and Karen Whittleworth as OSCAR's developers, dates the model to 2002 and describes its five elements. Its history gives the same development year. A bibliographic record for their book, The OSCAR Coaching Model, lists a 2009 publication. The model's origin, the book's date and evidence about effectiveness are separate questions.

The ICF Code of Ethics provides professional safeguards around agreements, roles, information and accurate claims about coaching. Those safeguards still apply when a conversational model is used.

The originator presents OSCAR as building on GROW and useful for managers adopting a coaching style. That description does not establish that it outperforms GROW or guarantees employee performance. Originator testimonials are not a controlled comparison, and no such comparison is claimed here.

The formal stage descriptions below are brief attributions. The practical decision checks, questions, case and six-field record are our original application. They do not reproduce Worth's question bank, proprietary forms or source cases. Use the spelling OSCAR consistently; do not substitute another model's similarly named stages without explaining the change.

1. Outcome: decide what the conversation is for

The outcome stage clarifies what the person wants to achieve. In practice, distinguish the wider aspiration from a useful result of this conversation. Wanting a satisfying next career step is a wider aim. Choosing which information to request about an offer can be a realistic session outcome.

Ask what the client wants to be clearer about before the available time ends. Then examine what makes that clarity useful. “Feel confident” might mean having enough facts to decide, rehearsing a difficult question or accepting that uncertainty remains. Do not assume that confidence must end in a yes.

Identify whose choice is involved. A client can decide whether to ask for a change. They cannot promise that a hiring manager will grant it. Recast an outcome that requires controlling another person into a client-owned decision and an honest way to learn about the other's position.

Also identify boundaries that should constrain the choices. If the client says a particular evening commitment is important, record it alongside a weekly workload limit. Those are two criteria. Do not let a convenient improvement in one erase the other.

2. Situation: distinguish facts, interpretations and missing information

The situation stage establishes where the person is now. Our practical emphasis is on enough relevant context to make the next decision responsibly: what is known, which accounts are interpretations and what remains unconfirmed.

A written offer may specify two site days. The client may infer that this means two late evenings. Those statements need different treatment. Check the actual arrival and departure expectations rather than treating the client's fear or the coach's reassurance as the schedule.

Include what already works and what has been tried. A current role might protect an important commitment even while offering fewer development opportunities. That comparison is part of the situation, not proof that staying is always best.

Keep uncertainty visible. A job description's workload estimate is not a measured future working week. A statement that the manager “will probably be flexible” is not an agreed exception. The coach can help prepare a question without providing employment, financial or clinical advice beyond their competence.

3. Choices and consequences: compare feasible routes

This stage generates alternatives and examines what could follow from each. Its practical value lies in considering consequences before a commitment, including the demands placed on other people.

Develop a few meaningfully different choices. Accepting an offer, requesting specified changes and declining are different routes. Three wordings of the same request may help rehearsal but are not three distinct solutions to the underlying decision.

For each route, inspect benefits, costs, conditions and unknowns. A promise to remove work needs a real decision owner and an explanation of whether it is dropped or transferred. If another person must receive it, do not count their agreement or capacity as free. The client can ask about that dependency before treating the option as viable.

Separate a consequence from a prediction. “Declining means this offer will not proceed” can be confirmed through the actual process. “Declining means I will never be promoted” is a much broader belief. Explore what supports it without guaranteeing the opposite. A sensible choice may still involve disappointment and uncertainty.

4. Actions: choose a step that matches authority and capacity

The action stage clarifies next steps and responsibility. Our practical check is whether the step is small enough to perform, specific enough to review and within the client's actual authority.

An information request can be the action. It may be premature to accept, delegate or start a trial while a consequential condition is unknown. Specify what answer is needed, who can provide it and when the client must decide.

Count preparation, composition, sending and receiving as work. If you plan a conversation, allow time for the other person's contribution. If you plan an email, do not treat a sent request as a received answer.

Check willingness without imposing a compulsory confidence score. The client might choose a smaller request, a pause or no action on an option that does not fit. A task should support that choice, not become a compliance test that drives the person toward the coach's preferred result.

5. Review: examine usefulness, not just completion

The review stage creates an ongoing opportunity to evaluate action and progress. In the original practice here, return to the outcome and every criterion used to choose the step.

Ask what was actually attempted, what answer arrived and what changed. Include a failure, a rejected request or an overlooked condition. The client may learn that the desired outcome needs revision or that the situation contained a mistaken assumption.

Completion and usefulness are different. Sending a clear question may be completed even when the answer is no. Getting a concession may be useful while still leaving the whole option unsuitable. Review the substance before deciding whether to continue, adapt or stop.

Agree a review point early enough to inform the next decision. A review after an irrevocable deadline cannot guide that earlier choice. A later learning conversation can still be useful, but name its purpose accurately.

A complete fictional case: two conditions, one tempting improvement

Nora is considering an internal senior-coordinator role. Mel is her external coach. Rafi is the hiring manager and can clarify the proposed duties. The fictional case runs from 5–12 November 2046, in Europe/London time. It concerns a decision process, not a complete reconstruction of anyone's working week.

Nora initially asks Mel to help her become confident enough to accept. In preparation, she spends fifteen minutes gathering the offer details and her own constraints. Mel spends fifteen minutes preparing. Their first forty-five-minute session uses ten minutes for the outcome, ten for the situation, fifteen for choices and consequences, and ten for the action and planned review.

The wider aspiration is meaningful career development. The session outcome becomes narrower: choose what to ask before deciding on the offer. Nora identifies two conditions for acceptance: an expected week of no more than forty hours including travel, and being home by 18:00 on Thursdays for a standing personal commitment. She does not have to disclose the private reason to make that condition part of her decision.

The proposed role contains thirty-seven core working hours before travel, with Tuesday and Thursday site attendance. Each site's return journey requires three hours in total, so the weekly travel estimate is six hours. The planned total is forty-three. Both site days finish at 18:00, with a ninety-minute return home, giving a 19:30 arrival.

Nora's current role has a thirty-seven-hour pattern and meets the Thursday condition, but she would prefer some of the new role's responsibilities. These are the facts and preferences she brings to coaching. No future schedule has yet been tested, and Mel does not declare that Nora can absorb the difference through better personal organization.

Compare the options before sending the request

Nora chooses the information route. The initial action is not accepting the role or assuming that remote attendance will be allowed. It is asking Rafi about both conditions and making room for an answer she may not want.

On 6 November, 10:00–10:10, she composes and sends this complete request:

I am interested in the senior-coordinator role, but need to check two conditions before deciding. My current calculation is thirty-seven core hours plus six hours of weekly travel, totaling forty-three. I also need to be home by 18:00 on Thursdays. Can you authorize a scope reduction that keeps the expected total at forty or below, and a Thursday arrangement that meets that arrival time? Please clarify both by 7 November at 16:00. I have not accepted the offer.

Rafi uses fifteen minutes on 6 November at 15:00 to read the request, check the role requirements and compose and send his reply. The split is five minutes for each activity. He can drop the weekly market-update report entirely, reducing core work by four estimated hours without transferring it to someone else. He cannot change either site day or its fixed 18:00 finish.

His actual reply states: “I can remove the four-hour weekly market update from this role. It will not be reassigned as part of this offer. Tuesday and Thursday site attendance still finishes at 18:00. I cannot authorize an earlier departure or remote Thursday. Please decide by 9 November at noon.”

Preserve the almost-missed condition

Nora spends 7 November, 10:00–10:10 reading that answer and drafting a response. Her first unsent draft thanks Rafi and says the revised thirty-nine-hour estimate makes the role workable. She has focused on the concession and temporarily overlooked Thursday.

She then uses 10:10–10:15 to check the draft against both recorded criteria. Thirty-seven minus four plus six is thirty-nine, one hour below her forty-hour ceiling. But the Thursday arrival remains 19:30, ninety minutes later than her 18:00 condition. The improvement in hours does not make the whole option fit.

Nora does not send the acceptance draft. The case retains that near error as part of the decision process. It is not presented as proof that she had no difficulty or that the model automatically prevented a mistake. The visible criteria gave her something concrete to check.

The corrected decision comparison is:

Complete the action and receive its answer

On 8 November, 10:00–10:10, Nora composes and sends her final decision:

Thank you for removing the market-update report and clarifying the fixed site days. The revised thirty-nine-hour estimate meets my weekly-hours condition. The Thursday 19:30 arrival still does not meet my 18:00 commitment, so I am declining this offer. Please treat the earlier discussion as clarification, not acceptance. I appreciate the opportunity and remain interested in discussing other development routes separately, without assuming another role is available.

Rafi spends five minutes at 11:00 reading and confirming: “I have recorded your decline. No appointment to this role has been agreed. Thank you for making the conditions clear.” Nora spends five minutes during 11:15–11:20 reading that confirmation. No additional acknowledgment is sent.

The decline was completed and sent twenty-five hours and fifty minutes before the stated noon deadline on 9 November. The observed result is a clear decision about this offer with an actual receiving answer. Nora has not tested the role's workload, traveled to the site under the new pattern or obtained a different development opportunity.

She feels disappointed about losing the opportunity and relieved not to have accepted a Thursday arrangement she could not meet. Those mixed reactions are part of her account, not a requirement to describe declining as a personal breakthrough.

Make the review traceable to the original outcome

Nora spends ten minutes preparing the following six-field learning record. It is an original case record, not an official OSCAR worksheet:

Mel reads the record for fifteen minutes before their 12 November thirty-minute review. They spend ten minutes on what actually happened, ten on the two-criterion check and ten on Nora's choice about future development. Mel then spends ten minutes writing internal notes. There is no extra written feedback exchange outside those blocks.

Nora decides she wants to explore development in a later conversation, but does not commit to contacting another manager this week. The original information request and offer decision are complete. The broader career aim remains open. That distinction prevents a clear short-term action from being mistaken for a solved long-term situation.

Account for preparation, receiving and review

The case uses 275 of 320 person-minutes, leaving forty-five: twenty for Nora, fifteen for Mel and ten for Rafi. The thirty-seven-, forty-three- and thirty-nine-hour figures are separate role-pattern comparisons, not additional actual case work being silently omitted from the table. The case does not reconstruct ordinary employment activity.

This is one fictional decision sequence, without a comparison condition or long-term outcome data. It illustrates how to use the model and what a review can inspect. It does not demonstrate that OSCAR caused the decision, prevents mistakes generally or produces better career outcomes than another appropriate conversation.

Connect the action and review in Coachful

Use a short original worksheet to record the client's outcome, relevant facts, alternatives and review questions. Explain which answers are deliberately shared. Do not copy proprietary assessment forms into a resource merely because the five stage names are familiar.

A one-off information request can be a task rather than a daily habit. Keep its wording under the client's control and attach the relevant date. Record the actual response separately. Marking a request sent does not establish Rafi's approval, a role appointment or the wider career outcome.

Coach review on submitted worksheets is private to the authorized coach team and excluded from the response PDF. It is not client-facing feedback. If a response is promised, use the actual agreed client channel and allow receiving time. Mel's actual return in this case is the thirty-minute joint review after fifteen minutes of reading.

Unshared journal pages are not ordinary coach notes; clients can explicitly share eligible journal work through supported specialty features. Private course takeaways have their own narrower rules. Use an intentionally submitted preparation resource when the plan requires coach reading rather than assuming access to personal reflection.

For summarized sessions, check audience and recap approval settings before sensitive employment or personal details are included. Approve before sending holds new unsent recaps; session-type overrides matter, and prior deliveries are not recalled. A recap is a record of permitted session material, not the employer's authoritative offer or confirmation.

Explore Coachful's features for preparation and follow-through. The GROW guide offers another conversational structure, while the goal-setting worksheet guide develops client-owned aims. No universal model ranking is needed to choose an appropriate starting point.

Apply OSCAR without making the conversation mechanical

1. Agree a useful session result. Keep the wider aim and today's decision distinct.
2. Identify the relevant facts and unknowns. Check what the client knows and which authority can answer the rest.
3. Compare real alternatives. Include costs, constraints, receiving work and the option to wait or decline.
4. Choose a specific action. Record owner, time and dependencies without promising another person's response.
5. Review against every criterion. Inspect what happened and whether the action served the outcome.
6. Decide what changes. Continue, revise or stop, retaining unresolved facts and mixed feelings.

Troubleshoot the decision, not the person's compliance

The outcome is still vague: clarify which decision could become more informed today. Do not fill the action stage with an unwanted task to finish the acronym.

Too many options appear: compare a small set that differs meaningfully. Ask which facts would change the choice.

An option improves one thing: check all the original conditions before declaring it viable. A concession does not erase a different constraint.

The manager already decided: explain what is fixed and what remains open. Coaching language should not disguise a mandatory instruction or an assessment role.

An action was missed: examine capacity, information, authority and willingness. A completed task also deserves review of usefulness, not only praise for completion.

Frequently asked questions

What does OSCAR stand for?

Outcome, Situation, Choices and Consequences, Actions, and Review. The originator uses those elements to structure a coaching conversation. The practical checks and case in this guide are original applications.

Is OSCAR better than GROW?

A universal ranking is not established by the originator descriptions used here. Both can support choices and follow-through. Choose and adapt a structure to the person's purpose rather than treating the acronym as proof of effectiveness.

Must all five stages fit one session?

No. A useful session may clarify the outcome or identify missing information. Agree where the conversation should go next and when an actual review can inform the decision.

Can declining be a successful action?

It can be an appropriate client-owned choice. Check it against the person's purposes and evidence, receive any necessary confirmation and keep the consequences visible. Do not require a positive story about every loss.

What if a completed action does not help?

Return to the intended outcome and what the situation revealed. Completion is information, not a verdict on usefulness. The next decision may be to adjust the plan, seek expertise or stop.