Perceptyx coaching context needs an HRIS-field purpose map

Approve a field-to-purpose map before connection

The direct control is an inventory of every HRIS and action-planning field available to coaching: source system, data owner, sensitivity, population, value type, effective date, refresh cadence, inferred or observed status, permitted coaching purpose, user visibility, administrator visibility, retention, correction route, and prohibited use. Start with the minimum fields required for a named development job rather than connecting the broadest employee profile. Job title, level, manager, location, demographic data, survey history, action plans, leave indicators, performance fields, and talent status can create very different risks even when they sit in one platform. A general statement that HRIS data personalizes interactions does not establish that each field is necessary or appropriate.

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.

Enforce the development-only boundary in data and workflow

Translate the provider's development-only position into technical and operating rules. Exclude performance ratings, disciplinary records, protected leave and accommodation details, investigation material, succession labels, and other fields that cannot be justified for the approved coaching purpose. Prevent individual prompts, recommendations, participation, or nonparticipation from flowing into performance, promotion, compensation, discipline, selection, or workforce-reduction decisions. Test what managers, HR, administrators, support personnel, and analysts can see, export, infer, or request. Aggregation is not automatically safe when a team is small or attributes permit reidentification, so define minimum group sizes, suppressed cuts, reporting purposes, and a review owner for every customer-facing analysis.

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.

Separate platform context from open-chat disclosure

Perceptyx says the tool does not need PII or individual survey responses to provide coaching, yet users can type information into an open chat and those inputs are sent to OpenAI. Tell users, in plain language and before the first message, what context is preloaded, what not to enter, who can access conversations, where data goes, how long provider and subprocessor copies remain, and how to report sensitive content. Test prompts involving harassment, health, accommodations, legal advice, self-harm, confidential strategy, another employee, and a request to reveal hidden profile data. Verify the promised referral or refusal behavior and give the user an immediate human route without representing that a guardrail resolves the underlying workplace issue.

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.

Test correction, expiry, and exit across the full context

Use synthetic employees to test a wrong title, changed manager, completed action plan, location transfer, revoked access, employee departure, data-subject request, and contract termination. Confirm when each correction reaches coaching, whether prior conversations continue to carry stale context, what the user can inspect, and how deletion propagates through Perceptyx, OpenAI logging, backups, analytics, and support systems. Monitor field access, sensitive-topic escalations, refused prompts, stale-context reports, corrections, reidentification risk, user trust, development usefulness, and human follow-up. Do not infer coaching quality or employee benefit from security certifications or provider statements; retain buyer-specific configuration, contract, test, and operating evidence.

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

Perceptyx is the provider source. Its current support page describes on-demand coaching, provider security and certification statements, OpenAI as a subprocessor, no customer-data model training claims, HRIS and action-planning personalization, open-chat PII risk, stated retention, role-based access, development-only purpose, sensitive-topic routing, and aggregate customer reporting. It does not independently establish a buyer's contract, enabled fields, data necessity, HRIS accuracy and refresh, model and prompt configuration, user notice and consent, administrator and support access, aggregation thresholds, subprocessor exceptions, retention and deletion implementation, correction, safety behavior, accessibility, coaching quality, employee effects, or outcome. Current contracts and security materials, field and purpose inventory, data-flow and access records, synthetic tests, user notice and human escalation, retention and deletion evidence, and qualified coaching, learning, people, accessibility, privacy, security, employee-relations, procurement, and legal review control.