What's the (implicit) contract?

I have  blogged before about the importance of contracting for coaching; and the fact that as a supervisor of coaches, whenever I hear a disaster unfolding, my first thought (and often my first question) is What was the contract?.

Occasionally, however, one comes across something that sits outside the normal contract, and that is causing the coach some retrospective anxiety: 'This happened, so I said/did this, and now I'm wondering if I should have...' Often, I hear, 'It felt ok at the time, but now I'm not so sure...'

Naturally, I find such cases interesting. One can't contract for everything, and often we can't talk in terms of absolutes, either. The Confidentiality aspect of the contract is a classic example: coaching is confidential except... {safeguarding, supervision, invoicing...} 

So for example, if a coachee decides to withdraw from a coaching relationship halfway through, one probably has an obligation to tell the client organisation, for reasons connected with invoicing.  Is that a breach of confidentiality?  Might it be perceived as such but the individual?  What if the client organisation asks for the reasons? After all, they have a right to know about the quality of the coaching being delivered...

It is here that I think that the concept of the implicit contract is valuable. You may not have contracted for the specific eventuality that has arisen, but it is worth asking two questions of yourself:

If I had contracted for this specific eventuality, what would I have been discussing with my coachee?

Given the contracting that we did in fact engage in, what would my coachee reasonably expect of me in this specific eventuality?

I find (so far) that asking these two questions helps coachees to evaluate their retrospective anxiety, and to decide whether it is well-founded - and if so what to do differently in the future. If not, of course, they can lay it to rest.

And one of the actions that often becomes clear as desirable, is more explicit contracting...