Responsible use starts with the decision and the people affected by it. A client team needs to understand which information enters the process, how an output is used and who is accountable for the action that follows. A label such as ‘AI-powered’ does not answer those questions.
Define the purpose and the people affected
Be specific about the intended use: development analysis, team discussion, planning, matching or an operational workflow. The consequences and the evidence needed differ. Agree the permitted data and the intended audience for the result.
Bring the relevant client owners into that discussion, including the people responsible for data protection and the operating process. This guide provides questions for that work; the applicable legal requirements and deployment documentation need to be assessed for the actual use case.
Examine evidence quality and interpretation
Ask whether inputs are relevant, current and sufficiently complete for the decision. Distinguish participant statements, assessment perspectives and verified evidence. Examine where missing information or a proxy measure could distort a comparison.
Keep explanations useful to the reviewer. A score alone cannot establish fairness, suitability or the absence of bias. A practical review connects the result to criteria and evidence, identifies limitations and allows the team to question an inappropriate conclusion.
Configure access and action authority deliberately
Employees, managers, HR and other authorised viewers may have access to individual assessments according to the client's chosen use case and role-based permissions. EVA and Customer Success help configure that arrangement. Avoid assuming either that every individual record is visible to everyone or that it can never be shared beyond HR.
Data visibility and authority to execute an action are separate decisions. Define automatic actions, review steps and exceptions for the workflow involved, and make those boundaries understandable to the people using it.
Keep governance practical after launch
Agree who investigates a disputed output, corrects an underlying record and updates a process that is not working as intended. Review meaningful examples and failure cases rather than relying only on a demonstration where everything succeeds.
Use EVA's current transparency and privacy notices for published commitments. Consult current regulatory guidance for the relevant jurisdiction. The ICO's AI and data-protection guidance covers accountability, transparency, fairness and security; its website notes that the guidance is under review following legislative changes. Do not substitute a checklist for that current assessment.
Ask what the reviewer would need to see
Practical governance questions for a configured workforce process.
A reviewer questions why a person was shortlisted
How to read it
The useful evidence is the requirement, relevant source records, missing information and comparison rationale.
The next useful action
Review those inputs and correct the record or criteria where appropriate.
Compare all 3 cases
| Case | Known information | Next action |
|---|---|---|
| A match is disputed | A reviewer questions why a person was shortlisted | Review those inputs and correct the record or criteria where appropriate. |
| Access is unclear | A manager can open an individual assessment | Check the configuration against the client's documented visibility decision. |
| An action is proposed | A workflow would change an assignment | Confirm the configured action boundary and the required review or automatic conditions. |
Illustrative example. These controls explain the method; they do not access client records or execute workforce actions.
Make accountability visible in the evidence, the permissions and the next action.
Explore the relevant EVA capabilitiesSources & further reading
This guide explains EVA's approach and illustrative methods. Follow the current offering and methodology pages for scope and examples.