This is the first article in The facilitation journey: 100 tips and reflections, a ten-part series working through facilitation stage by stage, from contracting through to presence and self-care.

Contracting: ten tips and reflections

Contracting is the stage most facilitators rush past to get to the parts that feel like the real work, the design, the room, the delivery. But nearly every difficult session I have ever run traces back to something left unclarified or unspoken at the very start. The conversations you have before anything is agreed shape what becomes possible later far more than any activity you design. These ten tips are about slowing down at exactly the point where most of us are eager to speed up.

1. Ask for the real problem, not the presenting one

Every client arrives with a want, and the want is rarely the same as the need. They ask for a workshop, a strategy day, an offsite, when what they are actually seeking is permission to face something they already know but have not said aloud. Your task in the first conversation is not to take the request at face value but to stay in the question long enough for something truer to surface.

This requires a kind of patience that clients do not always expect from a consultant, since most of the market trains them to expect quick answers to quick briefs. Staying with the question is itself an intervention. It tells the client, before any work has begun, that you are willing to be in service of what is real rather than what is convenient.

In practice: ask “what happens if you do nothing?” If the answer is vague or low stakes, you probably have not found the real problem yet. Keep asking “and what does that mean for you?” two or three times past your first instinct to stop.

2. Name the doubt in the room, including your own

Contracting conversations are full of unstated doubt. The client doubts whether the group can be honest with each other. You doubt whether the client is ready to hear what might emerge. Neither of you says this out loud, and the unspoken doubt quietly shapes everything that follows. Naming it early, plainly and without apology, is an act of respect rather than a risk.

When you say “I have some doubt about whether this group is ready for this conversation,” you are not undermining the engagement, you are creating the conditions for an authentic one. Clients are so used to being sold certainty that a consultant willing to name uncertainty often earns more trust, not less.

In practice: try the sentence starter “I want to name something before we go further” and finish it honestly. Watch how the client responds. Their reaction tells you more about the engagement ahead than anything else in that first call.

3. Insist on choice over compliance

A contract built on compliance produces a session where people show up because they were told to, not because they chose to be there. Ask the client directly whether attendance is a genuine choice or an expectation dressed as one. If it is the latter, say so, and explore what would need to change for people to attend in freedom rather than obligation.

This is uncomfortable to raise because most organisational life runs on obligation, and clients are not always used to being asked to justify it. But a room full of people who did not choose to be there will produce compliant behaviour, not engagement, and no amount of skilful facilitation later in the process can fully compensate for that at the outset.

In practice: ask directly, “if someone chose not to come, what would happen to them?” A real answer here tells you exactly how much genuine choice actually exists.

4. Refuse to be the expert who has the answer

Clients often want to hire you as the person who will fix things, and there is a pull to accept that role because it feels flattering and it closes the sale quickly. Resist it. Your value is not in having the answer, it is in creating the conditions where the group finds its own. Say this plainly during contracting, since it changes what the client is actually buying.

This does not mean withholding expertise or hiding behind process. It means being honest that the deepest and most durable answers will come from the people who have to live with them afterwards, not from you. A client who understands this from the first conversation will engage differently with the whole process that follows.

In practice: when a client asks “what would you do?”, try responding with “what I can do is help your team find the answer that will actually stick, want me to show you how that works?” rather than answering the question directly.

5. Ask what the client is willing to risk

Every meaningful session asks something of the client beyond a fee. It asks them to risk being seen differently, to risk a decision they cannot easily reverse, to risk the group discovering something inconvenient about how things really work. Ask directly what the client is prepared to risk, and notice what happens in the pause before they answer.

If the honest answer is nothing, the engagement you are being asked to deliver is likely to be a performance of change rather than change itself. That is worth knowing before you design a single activity, since designing well for the wrong kind of engagement only produces a more convincing performance.

In practice: ask “what’s the worst thing that could come out in that room, and are you genuinely prepared for it to?” A hesitant or evasive answer is itself useful data for how you design and set expectations.

6. Treat the contract as a relationship, not a transaction

A written agreement matters, but it is not the contract in the fullest sense. The real contract is the quality of relationship you establish in these early conversations, built on directness, mutual disclosure and a willingness to say difficult things to each other before the money changes hands. If that relationship cannot bear an honest exchange now, it will not bear one under pressure later.

This is why the first meeting matters more than the paperwork that follows it. Notice how the client responds when you push back gently on something they have said. Their response tells you more about what is possible in the room than any brief they hand you.

In practice: deliberately push back gently on one thing the client says in your first conversation, a timeline, an assumption, a framing, and pay close attention to whether they engage with the challenge or simply reassert their original position.

7. Decline work that asks you to collude

Sometimes a client wants a facilitator not to open something up but to manage it closed, to create the appearance of participation around a decision that has already been made. You will be tempted to take the work anyway, because turning down income is hard and you can tell yourself you will find a way to make it more honest once you are inside.

Do not collude. Name what you are noticing, offer the client a genuine choice about whether they want authentic engagement or stage management, and be willing to walk away if they choose the latter. Every time you accept a collusive contract, you make the next one easier to accept, and the work drifts further from what you say you stand for.

In practice: ask plainly, “has this decision already been made?” If the answer is yes, offer the client an honest choice, brief the group as an informing session rather than dressing it up as consultation, or genuinely open the decision back up.

8. Let the client experience your presence, not just your process

Clients are contracting with you as much as with your methodology, though they rarely say this outright. What they are sensing across these early conversations is whether you can hold the room when things get difficult, whether your calm is genuine or performed, whether you will stay present when the group’s anxiety rises. This cannot be demonstrated through a proposal document.

Let the contracting conversation itself be a small example of the quality of attention you will bring to the session. If you are distracted, rushed or overly eager to close the sale, the client is learning something true about what to expect, whatever your credentials say.

In practice: protect the first contracting call from multitasking entirely, no email open, no notes typed while they are still talking. Clients notice full attention, and they notice its absence just as clearly.

9. Make accountability mutual from the start

It is easy to let contracting conversations imply that the facilitator is accountable for the day going well and the client is accountable for nothing beyond payment. This is a quiet distortion that sets up problems later. Be explicit that the client shares accountability too, for preparing the group honestly, for being available if things need adjusting, for their own follow through afterwards.

Say this early rather than discovering the imbalance mid engagement, when a client who feels no ownership starts treating a disappointing outcome as something that happened to them rather than something they were part of creating.

In practice: write two or three explicit client responsibilities into your proposal or agreement, briefing the group honestly beforehand, being reachable if the design needs adjusting, owning follow through afterwards, so accountability is on paper, not just implied in conversation.

10. Trust that the answer to how is yes

Clients will offer reasons why deeper engagement is not possible here, not with this group, not with these time pressures, not in this culture. Some of these reasons are real constraints worth respecting. Many are simply the how question arriving too early, before the client has fully committed to what they actually want.

When you sense genuine commitment underneath the hesitation, keep the conversation focused on what the group truly needs rather than immediately problem solving the obstacles. The practical arrangements usually resolve themselves once the commitment is clear. Solving for how before the client has said yes to what tends to produce a smaller, safer version of the work than anyone actually wanted.

In practice: when a client raises a practical objection early, try parking it explicitly, “let’s agree what good looks like first, then come back to whether it’s possible”, rather than letting the objection quietly shrink the ambition of the whole design.

In closing

None of this makes contracting comfortable. If anything, done well, it becomes more uncomfortable, since it asks both you and the client to say things you might otherwise have left unsaid until they became a problem later. But an engagement built on this kind of honesty tends to hold up under pressure in a way that one built on polite assumption rarely does. The session you deliver is only ever as strong as the conversation that contracted it.

Reflection questions

1. When a client last brought you a brief, how much of it was the presenting request and how much was the underlying need, and did you find out before you agreed to anything?
2. Where in your practice do you tend to accept a role blur, coach, trainer, mediator, facilitator, rather than naming it explicitly at the outset?
3. Can you recall an engagement where you sensed a mismatch between what the client said they wanted and what they were actually prepared to risk? What did you do with that sense at the time?
4. How comfortable are you naming your own doubt to a client before the work has begun, and what tends to stop you?
5. What is one contracting conversation, past or upcoming, where the written agreement might need less attention than the quality of the relationship being formed around it?

This article is part of The facilitation journey: 100 tips and reflections. The next stage in the series covers design.

Image by Geralt from Pixabay