Answer capsule
The fourth Global Code of Ethics gives executive buyers a current professional-conduct reference, but membership or adherence still cannot establish AI-specific skill, confidentiality design, or fit for a particular engagement.
What the source establishes
- EMCC Global announced the revised Global Code of Ethics on February 15, 2026.
- EMCC says version 4 was completed in late 2025 through a collaborative process involving 11 signatory professional bodies.
- The announcement says the revision responds to emerging needs, is more firmly anchored in shared professional values, and is intended to recognize cultural diversity and different professional contexts.
- The announcement establishes a current professional-code record, but it does not establish that a particular coach is a member, follows the Code in practice, or has executive-AI capability.
Verify who is actually bound
Ask the named coach which professional body they belong to, the current membership or credential record, the code and version that applies, and the complaint route available to the client. Distinguish a signatory organization, an individual member, and a practitioner who simply says they support the Code. A badge or general website statement can be a research lead, but it is not evidence that the individual is subject to a specific disciplinary process.
The accountable team should translate this point into a named workflow, affected population, source data, human owner, approval right, exception path, retained evidence, and review date. That translation is what separates an interesting AI development from a decision that can be governed and evaluated.
Put confidentiality and technology into the engagement
The contract should identify the client, sponsor, objectives, information boundaries, records, retention, disclosures, conflicts, referrals, emergencies, and ending rights. If the coach uses AI for preparation, notes, research, exercises, or client-facing work, require informed agreement about the exact purpose, provider, data handling, review, and fallback. A professional code can frame expectations; only the engagement record makes the promised practice concrete for this client.
The accountable team should translate this point into a named workflow, affected population, source data, human owner, approval right, exception path, retained evidence, and review date. That translation is what separates an interesting AI development from a decision that can be governed and evaluated.
Observe practice rather than infer from a badge
Use a protected sample conversation or structured interview around a real executive decision. Observe contracting, listening, challenge, uncertainty, boundaries, conflicts, confidentiality questions, and whether the coach distinguishes coaching from consulting, training, therapy, or technical implementation. Test how the practitioner responds when an AI claim is unsupported or a client asks to delegate accountable judgment. Professional affiliation does not substitute for evidence of AI-specific practice.
The accountable team should translate this point into a named workflow, affected population, source data, human owner, approval right, exception path, retained evidence, and review date. That translation is what separates an interesting AI development from a decision that can be governed and evaluated.
Write a conditional fit conclusion
Record verified affiliation, relevant executive and AI experience, observed method, confidentiality terms, technology use, references, conflicts, unresolved questions, and review date. State which client objective and working style the evidence supports and what would reverse the conclusion. Do not turn the Code, credential, or sample into a universal ranking. The buyer remains responsible for contracting, protected information, sponsor boundaries, and monitoring whether the engagement continues to serve its stated purpose. Require the final memo to separate confirmed facts, practitioner claims, observed behavior, contractual commitments, and open diligence items so the sponsor can see exactly what the Code did—and did not—support.
The accountable team should translate this point into a named workflow, affected population, source data, human owner, approval right, exception path, retained evidence, and review date. That translation is what separates an interesting AI development from a decision that can be governed and evaluated.
Decision test
Ask whether the source changes the decision itself, the evidence required, the implementation sequence, or only the language used to describe an existing capability. Record which claims are directly supported, which are provider statements, which require an independent test, and which remain unknown. A source-linked review should make uncertainty easier to see, not bury it inside a blended score.
Questions to take into review
The publication supports research and executive decision preparation. It does not provide legal, financial, accounting, employment, clinical, cybersecurity, investment, procurement, or implementation advice.