CoachHub AIMY's Workday nominations need an eligibility-and-removal lifecycle

Make nomination a human workforce decision

The direct answer is to define why a population is being offered AIMY and who is accountable for that choice before connecting the nomination flow. Eligibility might relate to a voluntary development program, a role transition, leadership support, or broad employee access, but it should not be inferred from a convenient Workday field without review. The buyer should identify the purpose, eligible and excluded populations, lawful and appropriate source fields, sponsor, cost owner, invitation and choice model, accessibility and language needs, and what the nomination does not mean. Access to coaching should not be presented as evidence of performance deficiency, promotion readiness, mental-health status, or any other employment conclusion.

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.

Reconcile identity and status before granting access

A representative review should cover duplicate worker records, preferred and legal names, contingent workers, employees on leave, recent hires, internal transfers, cross-border populations, managers who change, and people who previously declined. The organization should know which Workday system and field is authoritative for nomination, when the extract or event occurred, which identity received the invitation, and who corrected a mismatch. The platform connection may transport or match information, but it cannot decide that a field is current, that the purpose remains valid, or that a person should participate. Uncertain eligibility should pause the invitation rather than becoming a silent exclusion or an unwanted disclosure.

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.

Define removal, retention, and sponsor visibility together

The lifecycle record should state what happens when a person changes role, manager, location, or employment status; takes leave; finishes the program; withdraws; loses eligibility; or disputes the source record. It should distinguish ending future access, revoking connected identity, handling completed sessions and self-assessments, retaining required business records, deleting eligible participant data, and removing the person from sponsor reporting. CoachHub's public confidentiality statement usefully distinguishes conversations from aggregated and anonymized HR insights, but the buyer still needs exact configured fields, aggregation rules, small-cohort treatment, retention, access roles, and evidence that a removal propagates to every relevant view and downstream system.

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.

Keep coaching participation outside employment evaluation

Program governance should separate invitation, enrollment, usage, self-assessment, goal progress, coaching content, aggregate sponsor insight, and workplace outcome. A person who does not enroll, pauses, or uses the system differently should not receive an adverse employment inference. Sponsor reporting should be reviewed for re-identification risk and should not turn coaching themes into individual performance, promotion, discipline, pay, or separation evidence. Reapprove when eligibility rules, Workday fields, population, region, identity provider, coaching mode, analytics, retention, or sponsor purpose changes. The platform can support access and coaching interactions; the employer remains responsible for fair eligibility, meaningful notice and choice, employment decisions, and the complete participant lifecycle.

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.

Limitations and unknowns

CoachHub is the provider source. Its current AIMY page describes Workday-connected employee nomination, participant personalization, situational and goal-based coaching, self-assessments, video role-play, progress tracking, smart nudges, participant-conversation confidentiality, and aggregated and anonymized HR insights. It does not independently establish a buyer's contract, enabled integration, source fields and triggers, identity matching, eligibility and exclusion rules, notice and choice, accessibility, removal events, retention and deletion, administrator visibility, aggregation and re-identification controls, employment-use boundary, coaching quality, behavior change, or workforce outcome. Current contracts, Workday and identity configuration, eligibility and participant records, data-flow and access evidence, representative lifecycle tests, participant review, and qualified coaching, workforce, accessibility, privacy, security, procurement, and legal review control.