Operating the Leader Portal

• You generate an invite. /leader/invite → Generate code → share QR or link. After sign-up + email confirmation, the pairing creates automatically.
• Performer enters your code. They open Me → Connections → Add code on their app and enter your IND-XXXXXX code.
• Enterprise admin pairs you. Your organization's admin pairs you to performers on your roster. (Available once the Team plan ships — see Enterprise support.)

After pairing, the Performer appears at /leader/performers. They see a banner on their next dashboard load: "You're connected to {your name} as your Leader." A Performer can be paired with multiple Leaders simultaneously and with an Engineer at the same time.

Pairing a Performer to your roster auto-promotes them to Premium tier for as long as the pairing is active. Your $79/mo plan covers it. The Performer sees "Premium · Group Rate" in their tier display and cannot downgrade themselves while the pairing is active. Removing the last Leader pairing reverts their tier — see Removing a pairing.

Each Performer controls four flags on their profile that gate which sections of their detail page populate for you.

Your own writes — observations, KDG ratings, tools you assign, messages you send — are not consent-gated.

/leader opens four sections, top to bottom: At-Risk Strip, Roster snapshot tiles, Recent activity feed, and Roster table.

The At-Risk Strip flags Performers needing attention based on four triggers: Deployment overdue (14+ days since your last rating with 3+ tools completed since), Self-vs-Leader gap > 3 points, stale engagement (14+ days no tool completion), and pending observations (3+ unreviewed). Each card shows a one-tap action — Open detail or Rate now.

If a flagged Performer is also paired with an Engineer who has acted in the last 7 days, the card displays an "Engineer active" badge and moves to the end of the strip.

Full roster with search, sort, and filter. Columns: name and domain, level pill (L1–L6), last KDG rating (date and percentage), last check-in, pending observation count, group memberships. Click a row to open the per-Performer detail (seven sub-tabs: Overview, Reflections, KDG History, Observations, Scripts, Goals, Messages).

An observation is a structured record of a single performance moment — distinct from a Deployment rating, which covers a whole session. Six fields: Performer, Quadrant (Q1/Q2/Q3/Q4), Marker (free-text plus curated chip suggestions), Severity (Low / Moderate / Severe), Context note, KDG slider (1–10, required, represents this single moment).

There is a 24-hour edit window from submission, after which the observation locks. Per-row actions on the inbox: Acknowledge, Mark monitored, Mark resolved, AI insight.

The rating UI has a big readout (defaults to 70 if no rating exists for today), quick-pick chips at every 10%, fine-tune buttons (−5 / −1 / +1 / +5), and an optional 200-character context note. The Date of session field defaults to today and accepts any date within the last 7 days. The Performer's Track tab graphs ratings against session date, not submission date.

Rating bands. 90–100 Peak · 75–89 Strong · 60–74 Building · 45–59 Holding · 30–44 Slipping · 0–29 Not Deploying. Aim for the full 1–10 scale; if everyone is a 6 or 7, the gap signal collapses.

How the gauge composes. When both your rating and the Performer's KDG self-assessment exist, the composite is 0.6 × Leader + 0.4 × Self. When only one input exists, that input is 100% of the gauge.

The Dashboard At-Risk Strip flags a Performer as overdue when 14+ days have passed since your last rating and the Performer has completed 3+ tools in that interval.

The Reflections sub-tab on a Performer's detail surfaces their Q4 reflection narratives — Post-Event Reflection, Performance Debrief, Goal Reality Check — paired with any observations you logged on the same event. When the Performer's self-rating diverges from your observation rating, a colored badge surfaces.

Each state points to a different intervention. Aligned ratings confirm the architecture. Performer overrating typically reflects masking or environmental gap — the practice room differs from the live arena. Performer underrating often signals echo-voice activation rather than under-deployment. Opposite quadrants suggests the Performer attributed the moment to a different mechanism than you observed; this is the most informative gap to discuss directly.

Named cohorts of paired Performers. A Performer can belong to any number of groups. Removing a Performer from a group does not affect the pairing. Two-column layout: groups list on the left (with member counts), member roster + four actions on the right — Add Member, Bulk Assign Tool, Rename, Delete.

Bulk Assign opens the same picker as single-Performer assignment, filtered to the Leader-pushable allowlist. Cohort filtering is exposed on the Roster table. Cohort analytics show a read-only summary — average Readiness Score, most common limiters, completion rates.

Tools assigned by a Leader appear as a Quick Action on the Performer's Home tab and a row in their Train tab Pending Assignments section. When the Performer completes the tool, you receive a notification and the assignment marks complete in your view.

The picker is filtered to the Leader-pushable allowlist. Engineer-only tools (Mirror Work, Belief Inventory, Identity Map, Belief Reframe, Recovery Loop, Balanced Thinking, Energy Zone Training, Window of Tolerance Capacity Check, BTE 3C Template) are not assignable from the Leader Portal — attempting to push one returns a server-side error and the picker filters them out.

Visualization scripts are pushed via the Scripts sub-tab on a per-Performer detail, not the tool picker.

Open /leader/performers/[id] → Settings to remove a pairing. Removing the last Leader pairing on a Performer immediately reverts their tier:

• If the Performer has an independent paid subscription, the tier reverts to that subscription level.
• If they have no independent subscription, the tier reverts to Free, and Premium features are no longer accessible.

There is no grace period. The Remove dialog displays a billing-impact warning identifying the resulting tier before confirmation. Re-pairing is supported — the Performer's history is preserved and the Group Rate re-fires when the pairing re-establishes.