EVA.ai Workforce Decision Intelligence

The method behind the readout.

Define the question. Gather the relevant information. Review what the evidence supports. Decide what should happen next.

EVA Analysis Methodology · September 2026

What this guide is for

This guide explains an approach to planning and interpreting workforce readouts. Use it to prepare a discussion about capability, development, staffing or future demand, and to understand the questions behind EVA's illustrative samples.

Keep the scope clear. The website samples describe a fictional organisation using synthetic data. This guide does not report customer outcomes or certify an assessment method. Your population, questions, framework, calculations and deliverables are agreed for the engagement.

1. Start with a decision

Write down the work to be done, who owns the decision and when an answer is needed. “What competencies do we have?” becomes more useful when it is connected to a proposed role, programme, development priority or staffing requirement.

For an EVA Competency Mapping engagement, the starting scope is up to 100 profiles, one competency framework and one language. A board-ready analysis in less than 10 weeks, guaranteed. Recurring capture, wider populations, matching and connected workflow are scoped separately.

2. Establish the information you have

Review the agreed source files and records. Check what each field means, who supplied it, when it was last updated and whether it is relevant to the decision. Agree access and ownership before collection or comparison.

Record missing information as unknown. Do not silently turn an unanswered question into a zero score, lack of capability or available capacity.

3. Gather examples and perspectives

Use structured conversations to gather relevant information. Context, Action, Result gives an example a practical shape: what was happening, what the person did and what followed.

Keep employee and manager assessments alongside one another. Agreement adds context. A difference is a question to investigate: the participants may have seen different work, interpreted a level differently or used different examples. Do not automatically average away that difference.

Agree competency definitions and proficiency levels before making comparisons. For broader programmes, confirm language coverage and how participants will understand the framework.

4. Choose the analysis that serves the question

Competency mapping

Review the competency picture by person or unit. Compare assessment perspectives and inspect the supporting examples. Treat assessment differences and missing evidence as distinct findings.

Leadership alignment

Look at how the agreed perspectives describe leadership behaviour. Examine patterns and disagreement in context. Aggregated feedback does not, by itself, establish readiness for a particular role.

Team development

Connect findings to the work the team needs to perform. Distinguish an evidence check from a learning need, and consider practice, coaching or a different assignment alongside courses.

Future demand

Record managers' expected capability needs, timing and assumptions. A manager forecast is an input for review. Validate it against programme plans and distinguish proficiency gaps from shortages of people.

Time effectiveness

Review how people report the use of their time and the obstacles they experience. Define the reporting period and categories. Time reported against an activity is not automatically a productivity measure or recoverable saving.

Geographic capability

Examine where relevant experience is represented in the reviewed population. Location does not establish availability to move. Confirm interest, release, timing and any assignment requirements separately.

For any numerical analysis, agree the scale, population, denominator, weighting and treatment of missing values before interpreting the output. Read the definitions in the particular sample or engagement; do not assume a universal scoring formula across readouts.

5. Review a match before acting on it

Where a role or assignment requires matching, agree job-relevant criteria, their relative importance and eligibility conditions. Inspect the criterion-level information behind the EVA Talent Matching result.

A score summarises the configured comparison. It is not a probability of success, a hiring decision or clearance to deploy. Follow up on missing evidence, current interest and availability. For internal movement, include the current manager's release decision and transition needs.

6. Turn a finding into a reviewed next step

  1. State the finding. What does the available information support, and what remains uncertain?
  2. Examine the options. Consider further assessment, development, movement, recruitment or external support where appropriate.
  3. Check the dependencies. Include ownership, release, availability, timing and the additional information needed.
  4. Agree an action and review point. Record who will do what and how the team will know whether it helped.

Finance and delivery leaders supply the cost and timing assumptions for an economic comparison. Do not count an internal move as an automatic saving or a training recommendation as a measured return.

Agree access before collection

EVA and Customer Success configure role-based access for each client and use case. Employees, managers, HR and other authorised viewers can see individual assessments and aggregate analyses according to the agreed permissions. Agree access to raw answers, assessment perspectives, individual analyses and aggregate views, together with any disclosure thresholds.

A useful analysis makes its limits visible

Bring your question and the information you already have. EVA's team can help scope the capabilities and review process needed for that decision.

See how EVA works · Book 15 minutes