> ## Documentation Index
> Fetch the complete documentation index at: https://guide.exiqtive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Coach operations

> What a Coach does and doesn't do, how employees become Coaches, and the rules that govern coaching in exIQtive.

A **Coach** is an employee who holds the **Coach badge (125% Readiness)** for a specific responsibility. Coaches train and certify other employees on that responsibility, issuing Apprentice (50%) and Proficient (100%) badges based on inspection.

<Note>
  "Coach" isn't a job title or organizational role. It's a badge level for a specific responsibility. The same employee may be a Coach for one responsibility, Proficient for another, and a Novice for a third. See [The Badge Ladder](/user-guide/readiness/badge-ladder) for the full progression.
</Note>

## What a Coach does

For each responsibility where they hold the Coach badge, a Coach:

* **Guides development**: helps employees learning the responsibility, pointing them to the institutional knowledge (short videos and knowledge articles) and the quizzes they can use to self-assess
* **Conducts inspections**: observes employees doing the work and evaluates their knowledge, abilities, and behavior (KAB) against the inspection protocol
* **Issues badges**: Apprentice (50%) or Proficient (100%), based on the inspection outcome

See [Inspecting a responsibility](/coaching/inspecting-a-responsibility) for the inspection workflow.

## What a Coach doesn't do

* Issue Coach badges to other employees. Only an Architect can do that.
* Issue Architect badges. Those are issued by an administrator.
* Create or maintain the institutional knowledge, quizzes, or inspection protocol. That's the Architect's job.
* Inspect themselves on the responsibility they coach.

## Becoming a Coach

An employee becomes a Coach for a responsibility through a deliberate progression:

<Steps>
  <Step title="Earn Proficient">
    The employee first earns the **Proficient badge (100%)** for the responsibility.
  </Step>

  <Step title="Train under the Architect">
    The employee trains further with the Architect, learning not just how to do the work but how to evaluate others doing it against the inspection protocol.
  </Step>

  <Step title="Receive the Coach badge">
    When the Architect decides the employee is ready, the Architect issues the **Coach badge (125%)**.
  </Step>
</Steps>

Certifying more Coaches **increases training and inspection capacity** for the responsibility. See [Architect operations](/coaching/architect-operations) for how Architects train and certify Coaches.

## The Coach view

## Multiple Coaches per responsibility

An organization can have more than one Coach for the same responsibility. This is common and desirable:

* It spreads the inspection workload.
* It reduces risk if one Coach is unavailable.
* Different Coaches may have different availability for employees.

Any Coach for a responsibility can inspect any employee assigned to it. There's no formal "assigned Coach" per employee.

## Architect acting as a Coach

An Architect for a responsibility automatically has Coach abilities for it. An Architect can choose to:

* Train and certify new Coaches, who then take over Proficient certification (increasing capacity), or
* Act as a Coach themselves, inspecting employees directly (filling capacity when needed)

## If a Coach badge is removed

If an employee loses their Coach badge for a responsibility:

* They keep their Proficient badge. They're still Competent at the work itself.
* They can no longer inspect other employees for that responsibility.
* Badges they previously issued stay in place.

## Rules and constraints

* To act as a Coach for a responsibility, an employee must hold the Coach badge (125%) or the Architect badge (150%) for it.
* A Coach can't inspect themselves.
* A Coach issues Apprentice and Proficient badges, not Coach or Architect badges.
* Coaches inspect against the inspection protocol maintained by the Architect.
* Every inspection and badge issuance records who did it and when.

## Common questions

<AccordionGroup>
  <Accordion title="How do I know who is requesting inspection from me?" />

  <Accordion title="Can I coach for a responsibility that isn't part of my own job?">
    Yes. Coach status for a responsibility is independent of whether that responsibility is part of your position. What matters is that you hold the Coach badge.
  </Accordion>

  <Accordion title="Can I be a Coach without exIQtive access?">
    No. Coaches use exIQtive to record inspections, so they need access.
  </Accordion>

  <Accordion title="What if I think the inspection protocol is wrong?">
    Raise it with the Architect, who owns the protocol. You inspect against the protocol as it stands; changes are made by the Architect.
  </Accordion>

  <Accordion title="Can I hand an inspection to another Coach?">
    Effectively, yes. Any qualified Coach for the responsibility can inspect any employee. If you're unavailable, the employee can reach out to another Coach for the same responsibility.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Inspecting a responsibility" icon="clipboard-check" href="/coaching/inspecting-a-responsibility">
    How a Coach runs an inspection.
  </Card>

  <Card title="Architect operations" icon="compass-drafting" href="/coaching/architect-operations">
    How Architects certify Coaches.
  </Card>

  <Card title="The Badge Ladder" icon="stairs" href="/user-guide/readiness/badge-ladder">
    Novice through Architect.
  </Card>

  <Card title="Personas" icon="users" href="/concepts/personas">
    exIQtive management roles.
  </Card>

  <Card title="Key Readiness concepts" icon="gauge" href="/concepts/readiness">
    Readiness, badges, and zones.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.