Coaching Agreement Non-Solicitation and Confidentiality

Coaching agreement non-solicitation and confidentiality clauses address different risks. Confidentiality governs information use and disclosure. A non-solicitation restriction concerns specified conduct involving people or business relationships. A ban on coaching an entire sector is another restriction again. Combining them under one heading can hide both an excessive restriction and an incomplete information agreement.

Start with the actual parties, work and jurisdictions. Then agree the information audience, obtain appropriate review of any proposed restriction and implement the resulting terms. The fictional England-based case below completes those decisions and follows a later information incident. Its arrangements are illustrations for review, not universally enforceable contract wording.

Separate four questions before negotiating language

For example, confidentiality can prohibit using a client’s private information to approach a prospective recruit. That does not mean an agreement between businesses never to recruit each other’s workers is a necessary substitute. Conversely, removing a hiring restriction does not authorize disclosure of coaching information.

The ICF Code of Ethics asks relevant ICF professionals to agree information exchange, address disclosure circumstances and handle records appropriately. It is a professional framework, not a universal legal privilege. Explain confidentiality with its actual limits rather than promising that no court, regulator or lawful duty could ever require disclosure.

Write the confidentiality brief around real information

1. Identify information and permitted purposes. Name the kinds of business documents, personal reflections and contact information involved. Distinguish using a document to deliver coaching from reusing it in training or marketing.
2. Identify audiences. Separate participant, authorized delivery team, sponsor, advisers and any legally appropriate recipient. “High-level themes” is too vague if a theme could identify someone or expose a sensitive concern.
3. Reconcile exceptions and obligations. Have applicable legal requirements, valid orders, protected disclosures and safety circumstances reviewed. Do not turn every concern into an automatic HR report.
4. Specify handling and ending. Agree approved systems, access, incidents, retention review and responsibilities after the service ends. Check consistency with the NDA and privacy arrangements.

Confidentiality and data protection overlap but are not identical. A public business email address can still be personal data, while commercially confidential information may concern a company rather than an individual. Identify the actual processing and purposes. The ICO’s controller and processor guidance makes clear that roles depend on who determines purposes and means, not just a contract label. The page is currently under review following the Data (Use and Access) Act.

Also preserve specific statutory protections where they apply. Employment Rights Act 1996 section 43J addresses worker-employer agreements that purport to prevent protected disclosures. That is a defined statutory protection, not permission for anyone to publish any confidential material. Have the actual service and relevant duties reviewed.

Review the restriction itself, not only its title

“Non-solicitation” can describe different provisions. One might concern approaching particular customers; another might prohibit approaching workers. A non-dealing clause can reach accepting business even without an approach. A non-compete can restrict working in a market. Read what the words do before deciding which legal issues need attention.

The CMA’s advice for employers identifies no-poaching agreements between businesses as a competition concern, including agreements not to approach or hire each other’s employees without consent. It notes that informal arrangements and contracted workers can also be involved. A mutual promise is therefore not automatically a harmless or balanced solution.

Under the law of England and Wales, Tillman v Egon Zehnder Ltd [2019] UKSC 32 illustrates the importance of exact wording and the rules concerning restraint of trade and severance. The Supreme Court permitted removal of particular words in that employment covenant. It did not establish a universally safe duration or a rule that a court will repair every overbroad coaching-services restriction.

For U.S. work, the January 2025 DOJ/FTC worker antitrust guidelines distinguish employer no-poach arrangements from other restrictions and explain potential criminal or civil concerns. They state that they have no force of law and do not mandate a specific outcome. Separately, the FTC’s current noncompete-rule page says its 2024 rule is not in effect or enforceable. Neither fact settles every state-law, federal or cross-border restriction.

Define permitted use as well as the recipient

An audience list alone does not answer what someone may do with the information. In the fictional case developed below, Harbor supplies a nonpublic escalation chart to help Samira prepare a meeting. Jules may use it for that engagement. It does not become material for another client’s workshop, a public case study or a recruiting approach.

The completed instruction to the legal reviewers is: “Identify the supplied escalation chart and participant preparation as engagement material. Permit use for the agreed coaching purpose and the specifically approved sponsor update. Reconcile any necessary adviser or legally required disclosures with the full agreement. Do not treat delivery access as permission for training, publication or unrelated commercial use.”

This instruction is useful because it connects the information to an activity and purpose. It does not assert that all business knowledge belongs to Harbor. General experience, independently created resources, public information and confidential documents need their actual status examined. Ownership and licensing are separate questions from whether the coach may disclose a particular account. Jules excludes the actual chart and Samira’s agenda from later teaching material; no publication permission is inferred from the coaching purchase.

A completed procurement and reporting example

All people, entities, proposals and events below are fictional. Jules Coaching Ltd and corporate buyer Harbor Services Ltd operate in England. Jules coaches Harbor employee Samira; Imran is the sponsor. The agreed service is two in-person, unrecorded sessions on 5 and 19 November 2026, with an agreed sponsor update and closing administration through 30 November.

The actual role analysis identifies Jules Coaching Ltd as controller for its own coaching records, whose purposes and means it determines, and Harbor as controller for its own employee administration. This is a fact assumed for this case, not a rule that every coach has the same role. Kemi owns the provider’s privacy response; Ada advises the provider and Ruth represents Harbor’s legal function.

1. Complete the restriction review before signature

Harbor’s first draft contains three proposals: Jules must not coach another business in the sector; both companies must avoid hiring or approaching each other’s workers for twelve months after the engagement; and an alleged breach triggers an automatic £25,000 payment. Jules does not sign while assuming those words are merely standard procurement language.

He gives Ada and Ruth the actual proposals, England working locations, existing service description and the confidential information he expects to encounter. He also discloses the existence of another sector engagement sufficiently to review a potential conflict, without exposing that client’s identity or content. The advisers consider the actual competing interests and information boundaries.

On 3 November the parties accept a revised agreement that removes the sector ban, mutual no-hire proposal and automatic payment provision from this pilot. They agree defined confidentiality and conflict-review arrangements instead. No separate employee or customer non-solicitation restriction is accepted. This is their fictional procurement decision, not a conclusion that those provisions are invalid in every other context.

A different buyer may decline the revision. In that situation, the coach can negotiate, change the proposed work or decline the engagement. Do not tell the buyer that professional ethics automatically cancel a signed contractual restriction or that a coach can ignore it without consequences.

2. Agree the information audience with Samira

Before the first session, Jules, Samira and Imran also confirm the information agreement. Samira can discuss meeting preparation and work decisions privately with Jules. Imran receives the specific approved update, not full session notes, a recording or a maturity assessment. New requests require review of purpose, authority and the actual proposed disclosure.

The following is an original operational excerpt from their fictional agreed reporting plan. It is not a complete NDA or a replacement for the legally reviewed document:

The sponsor update will state the participant’s agreed preparation action and any request for a decision-owner clarification. Jules will obtain Samira’s approval of the exact text and recipient before sending it to Imran. Personal reflections, session notes and unrelated workplace accounts are outside this routine update. A new request will be assessed against the agreement and applicable duties rather than fulfilled automatically.

The buyer’s NDA and this plan are reconciled before the sessions begin. Samira is not asked to prove trust by sharing more private material. Imran accepts that payment gives him the agreed reporting, not a right to every thought discussed in coaching.

3. Send the agreed report and refuse a broader request

Samira prepares a meeting agenda on 9 November and asks the relevant manager to clarify the handoff decision owner on 10 November. When Imran requests Jules’s notes on 12 November, Jules identifies that this exceeds routine reporting. They discuss the information purpose and keep the notes outside the update. No lawful disclosure demand or urgent safety exception is present in this request.

On 13 November Samira approves this exact statement to Imran: “I prepared the cross-team agenda and asked the manager to clarify who approves the proposed handoff. That decision-owner clarification is still outstanding. I would like our next sponsor conversation to address it.” Jules sends it by work email on 16 November, and Imran acknowledges receipt that day.

The wording matters. It reports an action that actually occurred, keeps the unresolved approval visible and omits the private explanation Samira discussed with Jules. It does not claim that an agenda solved the team’s handover problem. Approval of this paragraph also does not authorize later transcripts, journal pages or recruiting disclosures.

4. Handle a later recruiting request separately

Samira discusses whether her role fits her priorities during the second session. The accepted agreement does not classify ordinary career reflection as recruiting, and Jules stays within the agreed coaching purpose. He does not promise that every possible employment dispute is impossible.

On 26 November another business asks Jules to pass along Samira’s private contact details for a vacancy. He refuses to identify or approach a coaching client using private engagement information and records the request under the conflict process. The business acknowledges that it will use its own public recruitment route. Samira’s content is not supplied.

This refusal protects the actual information boundary. It is not a new agreement that the businesses will never compete for workers. Likewise, the fact that a participant later leaves an employer would not by itself establish solicitation, information misuse or liability. Conduct and the applicable agreements still need examination.

Work through the actual information incident

On 17 November provider administrator Evan accidentally sends the approved sponsor paragraph to Ellie, an unrelated external contact, instead of the intended sponsor. Jules had supplied Evan only that approved paragraph for administration, not session notes or Samira’s private reflection. The paragraph still identifies Samira and discloses participation and a workplace action outside its authorized audience.

The ICO’s breach guidance distinguishes likely risk requiring notification to the ICO from high risk requiring notice to affected people without undue delay. It emphasizes reporting promptly, where feasible within seventy-two hours, and updating incomplete information later. The guidance is currently under review following the Data (Use and Access) Act. Apply the relevant controller or processor duties to the actual situation.

Kemi has not established high risk requiring individual notice under that separate threshold. Samira is nevertheless told promptly under the agreed contractual process. She acknowledges the explanation at 11:15 and agrees a minimal incident notice to Imran, sent at 11:20. That notice does not include her private session content.

Seventy-two hours from awareness at 09:15 on Tuesday 17 November reaches 09:15 on Friday 20 November. It is not three working days added after the investigation. The example’s report was made much earlier. A contractual notice or cure provision would not authorize postponing a statutory duty.

At the 19 November session Jules checks what Samira wants to discuss about the incident and completes the agreed coaching work. Kemi separately checks the known recipient response and preserves the uncertainty about copies outside the provider’s control. No further dissemination has been identified in the case record, which is different from proving that none occurred.

The provider changes its administrative sending process to require a deliberate recipient check against the approved recipient record before sending. Evan demonstrates that check on an unsent example addressed to Imran. This is a completed process rehearsal, not proof that every future message will be correct. The incident record retains the original error and response.

Keep retention and closing decisions proportionate

The service ends on 30 November. Jules confirms that the sessions, agreed sponsor update and closing administration are complete. Kemi remains responsible for necessary incident follow-up, which is not erased by the coaching ending. No post-ending hiring restriction is represented as active because none was accepted.

The provider schedules a retention review for 31 May 2027, with separate purposes recorded for signed agreements, delivery material and the incident record. It does not promise to erase every record on that date. Any continuing need, legal hold or request must be assessed before the relevant action.

The ICO’s storage-limitation guidance says retention must be justified by purpose and does not supply universal periods for each record type. It too is under review. “Keep everything forever” and “delete everything immediately” can both fail to reflect the actual duties and purposes.

Implement the agreed boundaries in Coachful

Coachful is our #1 recommendation for organizing original preparation, agreement records and agreed client follow-up. It does not decide whether a restriction is lawful, create a professional privilege or make a provider automatically compliant.

1. Retain the actual signed record. Use the appropriate agreement workflow or signed-PDF record. Signed native copies keep their signed text; eligible uncustomized pending copies can update when the unsigned-copy option is selected. Check the recipient’s actual version.
2. Assign only the intended preparation. Clients > client > Worksheets & resources > Assign provides the ordinary resource route. A copied private link alone does not grant access. Do not request sensitive personal details merely to populate a template.
3. Name the client channel. All messages > Direct supports the agreed client exchange. An authorized sponsor report needs its own approved content and recipient; the sponsor is not automatically included in that conversation.
4. Qualify journal privacy correctly. Unshared journal and takeaway pages remain private. An enabled Share with coach control deliberately exposes a selected page. Samira can keep personal reflection unshared and send a minimal action summary instead.
5. Check recap settings before relying on them. Recaps are automatic by default for summarized sessions. Sessions > settings gear > Session AI > Session recaps includes approval controls, with applicable session-type overrides. Holding a recap is separate from recording permission; the in-person case above has no recording or AI recap.
6. Match access to the agreed purpose. Review the actual authorized staff audience for preparation and provider review records. Saving a coach review does not send a sponsor report. Software access and contractual authority both need attention.

The demo Agreements area illustrates retaining signed-PDF records. It does not show that this fictional buyer’s terms have been reviewed or that an uploaded file establishes a new signature event.

The demo builder illustrates original preparation prompts. A mandatory form response is not a substitute for agreeing confidentiality or a disclosure audience. Review ownership and resource rights and ending terms separately, and explore Coachful’s features for supporting workflows.

Frequently asked questions

Is a twelve-month restriction usually safe?

There is no universal safe period. Examine the conduct, people, interest, jurisdiction and actual wording. A proposed anniversary calculation does not answer enforceability, and a last session may not be the relevant contractual ending event.

Does mutual wording make a no-hire promise fair and lawful?

No. A mutual agreement can still raise competition concerns. Distinguish it from confidentiality and obtain appropriate review of the actual proposal rather than substituting one broad restriction for another.

Does the sponsor own the coaching information because it pays?

Payment does not establish unrestricted access. Use the actual information agreement, legal duties and appropriate permissions. Approve specific reports rather than relying on an undefined promise to share themes.

Should every misdirected message be reported to a regulator?

Assess the facts and applicable reporting thresholds promptly. Preserve the incident and reasoning even when the reporting decision differs from this fictional case. Do not wait for complete certainty or assume deletion removes every issue.

Does confidentiality prevent every lawful disclosure?

No. The actual exceptions and duties need review, including relevant statutory protections and valid requirements. Professional ethics and an NDA are not a universal privilege, and an exception is not permission for indiscriminate disclosure.