Psychological Contract in Executive Coaching: A Guide
Nour
Founder, Coachful
A psychological contract in executive coaching concerns what a person believes has been promised and what they believe they owe in return. A participant might think that accepting coaching means accepting an assessment for promotion. A sponsor might think that paying includes a session-by-session account. The coach may believe that neither arrangement exists.
These differences need investigation before reassurance. Ask what each person understood, what created that understanding and who can confirm the obligation. This guide develops that inquiry through a complete fictional engagement, including a coach's missed commitment, an actual repair and a closing report with limits. The focus is the meaning people give to promises, rather than a general contract template.
Distinguish an expectation from a perceived promise
Denise Rousseau's 1989 theoretical paper locates the psychological contract in an individual's beliefs about reciprocal obligations to an organization. It distinguishes this from implied obligations considered at the relationship level. Two people can therefore believe they share an understanding without interpreting it identically. The theory developed in organizational relationships; using it in coaching is an application, not a validated assessment of a coaching relationship.
The useful question is not simply, “What do you expect?” Follow it with, “What makes this something you believe was promised?” A hope can deserve attention without becoming a commitment. Equally, a promise need not appear in the main service document to influence participation. Review relevant conversations and actual communications rather than deciding from the document's length.
| Statement | What needs checking | Possible next action |
|---|---|---|
| “I hope coaching helps me progress.” | A desired outcome, with no promise identified yet. | Define a development focus without promising advancement. |
| “I agreed because my manager said I would get protected time.” | A reported commitment that influenced participation. | Check the manager's words and scheduling authority. |
| “The agreement includes two written replies.” | A specified service obligation. | Read its scope, channel and deadlines, then deliver or address a failure. |
| “The sponsor pays, so surely they receive everything.” | An inference about information rights. | Check the actual reporting agreement and applicable duties before sharing. |
Do not classify the person as demanding or mistaken before hearing their account. “Who said that, and what did it mean to you?” can reveal an authorized assurance, ambiguous language or an assumption nobody has yet checked. Those findings call for different responses.
Understand why reciprocal commitments matter
In their 1993 chapter, Rousseau and Judi McLean Parks distinguish broader expectations from exchanges involving perceived promises. They explain delayed repayment and reliance: someone contributes now while depending on a future return, potentially foregoing alternatives. Their account concerns organizational contracting and develops propositions; it does not establish that a particular coaching conversation repairs trust.
They also describe a continuum from narrowly specified transactions to broader relationships containing economic and socioemotional elements. This helps explain why counting delivered sessions may leave a concern unanswered. A person may believe the relationship also includes dependable support. The categories describe exchange arrangements, not good and bad client personalities.
Applied to coaching, ask what the person has already done in reliance on the understanding. Have they reserved work time, declined another development opportunity or prepared for a particular kind of discussion? Identify the concrete consequence. Do not imply that the participant owes intimate disclosure, agreement with the coach or gratitude in exchange for funding.
A coach can honor a bounded service without becoming continuously available. Warmth and clear limits can coexist. Problems arise when the reassuring phrase “I am here whenever you need me” is left beside a service that includes only scheduled contact, without explaining how the two fit together.
Separate an unmet commitment from its emotional meaning
Elizabeth Wolfe Morrison and Sandra Robinson's 1997 theoretical paper, When Employees Feel Betrayed, examines the sensemaking preceding psychological contract violation. Its primary abstract describes violation in terms of anger and betrayal associated with an employee's belief that organizational obligations were not fulfilled. It presents a model for research, rather than a tested coaching repair procedure.
This suggests two practical inquiries: what commitment appears unmet, and what does the event mean to this person? “The reply arrived late” and “I now think my concerns do not matter” describe different aspects of one event. Investigate both without diagnosing the person or insisting on a particular feeling. Someone can identify a missed commitment while remaining willing to continue.
The word perceived should not become a way to evade responsibility. If the coach promised a reply by noon and did not send it, that missed deadline is an observable fact. A discussion of interpretation does not make it disappear. Conversely, disappointment about an outcome the coach could not promise requires honest clarification rather than a false admission that promotion was guaranteed.
Use a structured inquiry before deciding what to change
The following sequence is an original practice aid. It is not a psychological-contract inventory or a legal test. Work through the consequential issue first; a large survey of every preference can obscure the commitment that is currently blocking participation.
- Invite each account. Ask, “What did you understand would happen, and what did you understand your part to be?” Offer a private conversation when a sponsor's presence would constrain the answer.
- Locate the basis. Read the relevant sentence or hear the remembered conversation. Separate a recorded statement from a recollection and label uncertainty honestly.
- Identify reliance and effect. Ask what the person did because of that understanding and what happened when it was not met. Avoid demanding sensitive evidence that is unnecessary for resolving the issue.
- Check authority. Determine who can make the promise. A coach can commit to a reply; a coach usually cannot grant a promotion or override a manager's workload decision.
- Decide and record. Confirm the obligation, correct an inaccurate assurance, negotiate a specific change or leave delivery blocked while an essential condition remains unresolved.
- Review actual conduct. Set a date to check whether the agreed action happened. An acknowledged document is evidence of an arrangement, not evidence that confidence has fully returned.
Professional responsibilities remain relevant throughout. The current ICF Code of Ethics, effective April 2025, addresses agreements before coaching begins, clear information exchange, confidentiality and relevant disclosure obligations. It also addresses records and changes in value. These standards provide professional responsibilities for ICF professionals; they do not turn every expectation into a legal entitlement. Information limits and applicable exceptions need a clear discussion, not an absolute promise of secrecy.
Complete fictional case: hear three different understandings
Everything in this case is invented. Amira is a division manager, Beth is her manager and authorized sponsor, and Hugo is an external coach. They are arranging three private 60-minute sessions on 9 November, 23 November and 7 December 2026. A 30-minute initial joint meeting and a separate 15-minute closing joint review are included.
Before the initial meeting on 2 November, Hugo invites Amira to identify any concern privately. She replies by company email: “Your message said you were here whenever I needed you. I assumed I could send something before a difficult conversation and get an answer that day. Beth also said this would help me get ready for a director role. Is that what you assess?”
Beth separately says she understood “keeping you informed” in Hugo's proposal to mean a short account of each session. Hugo had intended only an agreed closing review. Neither phrase specified its boundary. He acknowledges that his own wording contributed rather than asking Amira to reinterpret it alone.
| Understanding | Evidence examined | Resolution before sessions begin |
|---|---|---|
| Same-day support whenever needed. | Hugo's welcome email, alongside the proposal's “brief support by arrangement.” | Replace both with two defined written rounds, and check whether that service fits Amira's needs. |
| Coaching assesses readiness for promotion. | Amira's recollection and Beth's explanation of “get ready.” | Beth confirms coaching is development, not a promotion assessment or promise. Selection remains the company's separate process. |
| Sponsor receives every session's content. | Beth's interpretation of “keeping you informed.” | Agree specific attendance information and a participant-approved closing summary; no routine private-session account. |
| Session time is protected. | Beth's actual calendar commitment. | Beth confirms Amira can attend the three sessions in work time and resolves direct scheduling conflicts as manager. |
Amira wants practice in making a clear request when priorities conflict. She does not want promotion assessment through the coaching. Beth accepts that distinction, confirms her purchasing authority covers this development service and agrees the proposed reporting scope. Amira then explicitly chooses to participate. Hugo updates the written working arrangements before the first session; all three acknowledge the shared version by company email.
Show the resulting working arrangement
The shared case record contains the following original text. It supplements the wider service terms, including their payment, cancellation and applicable confidentiality provisions; it does not replace them.
Purpose: Amira will use three private sessions to examine and practice clear requests about conflicting work priorities. Hugo will not assess promotion readiness. Beth retains ordinary management and company selection responsibilities.
Written support: Amira may submit one question of up to 150 words in each of two rounds, through her one-to-one Coachful Messages conversation with Hugo. The cutoffs are Wednesday 11 November and Wednesday 25 November at 12:00, Europe/London. Hugo will reply in the same conversation by 12:00 the following Thursday. Each round concerns applying the current session work and includes one reply. It is not an urgent advice service or continuing conversation.
Information: Hugo may confirm whether the three sessions took place. The closing summary can describe Amira's chosen practice and her own account of what happened, using wording she approves before Hugo sends it. Private session notes, raw messages and worksheet answers are not routine sponsor reports. Any change to this arrangement needs discussion and agreement, alongside applicable duties.
Time and review: Beth protects the scheduled work-time sessions. The final joint review is 7 December. Any request for assessment, extra support or a different report is considered separately before Hugo undertakes it.
Hugo checks the actual Messages audience with Amira. In this fictional solo practice, Hugo is the only team member who can access their coaching conversation; Beth has no staff login or recipient access to it. Shared contracting decisions stay in the company email thread containing all three. Private preparation and the two support replies stay in the named coaching conversation.
Amira confirms the two rounds are sufficient and plans important work conversations without depending on immediate answers. Hugo removes “whenever you need me” from this welcome message. That changes what is offered; it does not erase the earlier wording or the reason the clarification was necessary.
Retain the actual missed promise and repair its consequences
After the first session, Amira submits her first question on Wednesday 11 November at 10:00. She asks how to make a concise priority request without offering to absorb every deadline. Her manager conversation is Thursday at 15:00. The agreed reply is due Thursday at 12:00, but Hugo overlooks it and replies Friday at 09:00.
Amira says the answer arrived too late for that conversation. She had prepared a request herself; when another demand appeared, she reverted to accepting both deadlines. That is her account of the event, not proof that a timely coaching reply would have changed the outcome.
Hugo does not call this a misunderstanding. His Friday message says:
“I agreed to reply by Thursday at 12:00 and did not. My reply arrived after the conversation you had prepared for. I am sorry. You do not need to treat the late answer as usable support for that event. Would you prefer to review what happened in our next session, or discuss whether the remaining arrangement still works for you? I have added the second round's cutoff and reply deadline to my own work schedule.”
Amira chooses to continue and to review the event on 23 November. She does not request another written round. Hugo records the missed deadline and her choice, retains the original messages and allocates 25 additional minutes of his own administrative time to the repair and scheduling check. He does not reduce a private session or the second round to absorb that work.
At the second session, Amira describes feeling less sure that the coach would follow through. Hugo asks what would make the next commitment observable. They retain the existing second-round deadline rather than adding vague assurances. Amira submits on 25 November at 10:30; Hugo replies on 26 November at 11:00, within the agreed window. She acknowledges reading it that afternoon.
Her next priority conversation on 30 November produces a clearer request and an explicit discussion of which task should move. One deadline changes; another remains. Amira says the written reply helped her prepare, while emphasizing that Beth's willingness to discuss the workload mattered too. Neither person claims that one timely reply restored the entire relationship or proved coaching effectiveness.
Close with a checked report and a bounded outcome
Hugo's first closing draft says, “Amira now handles priority conflicts confidently.” Amira rejects that wording. It generalizes from two conversations and claims an internal state she has not reported. She approves this replacement after the final private session:
“The three scheduled coaching sessions took place. Amira practiced making a clear request about conflicting priorities. In her account of two workplace conversations, she accepted both deadlines in the first; in the second, she made the request and one deadline changed. These are her reported examples, not an independent assessment of leadership competence or promotion readiness.
“Amira intends to continue using a short written request before selected priority conversations. Any further coaching or assessment would require a separate agreement. The present coaching engagement closes after today's joint review.”
Hugo sends exactly that text in the agreed company email thread. At the 15-minute joint review, Beth acknowledges its limited purpose and confirms that company selection decisions remain separate. She asks for no private messages. The late reply and repair remain in Hugo and Amira's restricted service record; Amira has not authorized their inclusion in this sponsor summary.
The service record distinguishes delivery from reliability: three sessions delivered, two written rounds answered, one of those replies late, one timely, and the closing review completed. It does not relabel both rounds “on time” because Amira continued. Hugo's planned work was 180 minutes of private sessions, 45 minutes of joint meetings, 60 minutes preparation, 20 minutes written replies and 30 minutes administration: 335 minutes. The 25-minute repair brings actual work to 360 minutes, or six hours.
At closing, Amira says the later follow-through made continuing worthwhile but that she will still plan without relying on urgent coaching access. That is a mixed, specific account. Promotion, future workplace performance and later confidence are unobserved. The engagement ends on 7 December; using the request independently does not create another support period.
Keep a practical expectation record in Coachful
Coachful is our #1 recommendation for coordinating the agreed work in an executive coaching engagement. The useful workflow brings together deliberately shared preparation, private communication and the actual agreement record. Software cannot decide what a person meant by a promise or reconcile conflicting accounts for them.
- Create original preparation prompts. In Forms & worksheets, ask what the participant understood, its source, what they relied on and what needs clarification. Assign deliberately to the participant. Explain the actual staff audience and keep private answers out of sponsor materials unless appropriately agreed. A copied private link alone does not grant access.
- Use the agreed communication route. Name one-to-one Messages for the two support rounds and replies in this case. Put deadlines in the service wording and the coach's own work schedule. A message arriving does not itself promise immediate availability.
- Preserve the actual agreement. Use Agreements for formal service documents where appropriate. Signed copies retain their signed content. Saving a template version can update eligible pending unsigned copies when that option is selected; customized copies are excluded. Check which copy each person is being asked to accept.
- Share the chosen outcome separately. Record the participant's approved practice and follow-through without copying private reflections into a shared summary. Check the actual audience before sharing a takeaway. Task completion shows an action was marked complete, not that trust or leadership capability has been established.
The My Coaching image illustrates preparation and next actions, while the worksheet editor below illustrates original prompts. Neither screenshot demonstrates sponsor permissions or proves that a particular agreement was accepted. Use the saved records and appropriate access checks for those questions. Explore the relevant Coachful features alongside the service design.
Use a concise record when circumstances change
This reusable structure keeps the question and resulting action together. Leave genuinely unresolved items open rather than filling them with reassuring language.
| Field | What to record |
|---|---|
| Understanding and source | The person's account, relevant words or record, and what remains uncertain. |
| Reliance and effect | The relevant action already taken and the actual consequence reported. |
| Authority and decision | Who can confirm the obligation, what was agreed or refused, and any blocked work. |
| Action, audience and deadline | The actual owner, submission and reply channels, permitted recipients and review date. |
| Observed follow-through | What happened, what was late or incomplete, and the person's account without an invented satisfaction score. |
For example, a replacement sponsor requests retrospective session notes. The previous participant-approved reporting scope is not evidence that the participant authorized this new request. Establish who the replacement is, what information is needed and the relevant authority and obligations. Keep the requested disclosure blocked while its basis is unresolved; changing a contact name does not settle the question.
A different response fits an actual missed commitment. If a manager confirmed protected time but repeatedly assigns conflicting work, check the events with the participant and manager. Do not substitute an exercise about the participant's “resistance” for the unresolved scheduling obligation. The next step may be a revised workload arrangement, a pause or an appropriate termination process.
For the wider three-party structure, use the separate guide to tripartite contracting. For service allowances and renewal decisions, see structuring an executive coaching retainer. Here, the distinguishing check remains what each person believed was owed, why, and what the subsequent conduct actually shows.
Frequently asked questions
Is a psychological contract the same as a coaching agreement?
No. The psychological contract concerns an individual's beliefs about reciprocal obligations. A written agreement records specified terms. Reading both the document and the person's account helps identify differences; neither automatically tells you everything the other person understood.
Does disappointment prove that the coach broke a promise?
No. Identify the alleged commitment and its basis. A desired promotion may never have been promised, while a specific missed reply deadline can be verified. Acknowledge the effect without inventing an obligation or denying an actual failure.
Should a coach promise complete confidentiality?
Explain the actual confidentiality arrangement, reporting scope and applicable exceptions clearly. Avoid an absolute assurance that contradicts relevant obligations. Paying for coaching does not by itself settle the scope of access to private session material.
Can a written update repair trust immediately?
It can clarify the arrangement and record a correction. Follow-through and the participant's own account are needed to understand what happens afterward. In the fictional case, a timely second reply supports continuing, but the first failure remains in the record.
What if the participant no longer accepts the service?
Discuss the specific mismatch and available choices without pressure to continue. A changed arrangement needs real agreement. If appropriate conditions cannot be met, use the agreed pause or ending process and address relevant contractual and professional responsibilities.
Is a psychological contract legally enforceable?
The theory is not a ruling on enforceability. A particular statement's legal consequences depend on facts and applicable law. Obtain appropriate advice for that question rather than using the theory or a software signature record as a universal legal conclusion.
