HEPO's P&C software is designed to make cultural patterns available for responsible interpretation and development. Its readings concern practices within a defined scope; they are not rankings of employees or automatic judgments about a person's worth.

That purpose needs concrete boundaries in use: what evidence enters, what the reading represents, who can inspect it, and who decides what happens next. This page explains those distinctions for employees, People & Culture leaders, representatives, and technical evaluators.

Start with the question and its scope

A team examining follow-through in an approval cycle needs a definition of the practice, the relevant work records, and a meaningful period of review. It does not need an unrestricted account of everything each colleague does.

Observation scopes establish which traits and populations are being examined, with the relevant thresholds and recipients. The organization and its implementation partner configure the use around that question. A record's existing presence in a system is not a reason to include it in every analysis.

The resulting pattern might concern repeated delays at a handoff. Understanding it may require discussion of workload, dependencies, and changed commitments. A named person's presence in an underlying work record does not make the cultural reading a verdict about them.

Keep three kinds of information distinguishable

HEPO contains employee records and personal development journeys. Those facts are compatible with the P&C boundary when their roles and permissions remain clear. A claim that the entire platform contains no personal records or numerical progress would obscure how development actually works.

Games & Gamification can provide activities and feedback. Their results do not establish an individual's character. Campaign recognition also has its own approval and visibility arrangements, separate from cultural assessment.

The responsible person makes the decision

The Recommendation Framework produces a proposal from configured signals and conditions. The recipient examines its basis and decides how to respond. The lifecycle records acknowledgement, action, completion, dismissal, or expiry.

A recommendation about people does not authorize itself. A programme assignment, promotion decision, or other consequential response requires the appropriate human authority and context. The software's role is to support that decision and preserve its trace, rather than replace the person responsible.

An aggregate reading alone also cannot select an individual for action. A leader needs evidence appropriate to the actual decision, with the relevant people and process involved.

Make the basis inspectable within permissions

The evidence path connects definitions, observations, readings, and recommendations. The rule view identifies why a proposal appeared. Governance records help explain who changed configuration and how a response was handled.

Traceability does not mean every participant should see every source record. Access to evidence, configuration, programme information, and wellbeing contributions must follow the role and purpose of the use. A useful demonstration shows both what an authorized reviewer can inspect and what another role cannot access.

For example, reviewing the team's handoff pattern and viewing an employee's programme are different activities. Their shared context does not make their audiences identical.

Local processing is one part of the boundary

HEPO's deployment approach keeps the platform and AI inference on the customer's infrastructure. The organization and implementer establish the agreed sources, integrations, access arrangements, and operational configuration.

Local processing answers where that work occurs. It does not, on its own, settle whether a source, observation scope, or proposed use is appropriate. Those choices remain part of the organization's responsibility for the deployment.

Architecture and security explains the technical context in more detail.

Five questions to work through in a demonstration

These questions turn the trust position into something people can examine. The account should be checked against the configured deployment, rather than treated as proof that no extension or future change could ever violate its purpose.

Keep the boundary visible as the use develops

The organization owns the purpose and decision responsibilities. Employees and their representatives need an understandable account of the use. Consultants help connect the method to that conversation; implementers configure the evidence and access; the delivery partner coordinates the implementation and its review.

When the question, evidence, or scope changes, revisit those arrangements. Human authority and a clear explanation of the reading remain part of the work, not a statement confined to the first presentation.

The P&C method → · Flourish & Wellbeing → · People & Culture overview →

Walk through the evidence and decision boundaries with us.