EVA 8.0 brought four related parts of the talent process into focus: maintaining skills information, finding relevant people, presenting opportunities and reviewing candidate evidence. The release connected conversational engagement with the work recruiters and talent teams needed to do next. Its history also offers a useful way to examine a matching process today.
Skills updates through EVA Bot
The December 2024 announcement described an extension to the Skill Taxonomy Widget. Participants could select relevant skills during EVA Bot conversations, while re-engagement campaigns asked them to confirm proficiency information or report changes. The intent was to give teams a practical way to refresh talent records using their own skills vocabulary.
The distinction still matters today: an updated record is a dated account of what was collected. A newly reported skill or proficiency is not automatically verified. Define who is providing the assessment, what supporting examples are appropriate and when a review is needed. This keeps profile maintenance connected to the decision the information will support.
Contextual matching with retrieval-augmented generation
EVA 8.0 announced retrieval-augmented generation, or RAG, within Smart Match alongside its existing search and matching approaches. The release described using a knowledge base to interpret requirements and related terms, including differences in how education and professional experience may be written.
In a current matching exercise, distinguish interpreting the language from checking the requirement. Related wording can make a record worth reviewing without proving that the person holds a specified qualification or has performed a particular task. Where a requirement depends on an external register, document which source was checked and when. An explanation of relevance should make gaps easier to inspect, rather than turn incomplete evidence into a definitive match.
Configurable job details and public pages
The release also described job-page templates that client administrators could configure, including branding, HTML-enabled presentation and custom fields. This gave teams more control over how they explained an opportunity and which information appeared on public job pages.
The practical question is what a participant needs to understand before applying. Make the work, location, timing, essential requirements and next steps clear. Assign ownership for deadlines and other details that change. A reusable template helps keep presentation consistent, while the responsible team still needs to keep each opportunity accurate.
Candidate cards for a more focused review
Candidate Cards brought role-relevant information into a consolidated view. The announcement covered skills, certifications, experience, achievements and availability, with fit categories intended to help recruiters organise their review. Those categories were part of the historical release description, rather than a substitute for the evidence behind a recommendation.
When evaluating a candidate card today, ask why a record was surfaced, which requirements are supported and what remains unknown. Keep a hard eligibility requirement distinct from a useful preference. Availability is another separate question: a person may have relevant experience but be committed elsewhere during the required period. A consistent display can support comparison; it does not establish fairness or accuracy by itself.
How to explore the current EVA offering
Today, the relevant starting point is EVA Talent Matching: comparing people with a role, project or assignment using agreed requirements and accessible evidence. Recruitment, internal mobility and contingent deployment each bring different sources, availability constraints and review steps. Bring one of those use cases and a representative set of records to the discussion.
Other EVA modules support the work where needed. Competency Mapping structures role expectations; Team & Leadership Analytics examines the wider team picture; Workforce Planning tests demand and capacity; configured automation handles follow-up and approvals. The original announcement also previewed research for a later release. That historical roadmap is not evidence of what is available in a current client environment, so confirm scope against the intended workflow.
A relevant profile is the start of the review
Illustrative requirement: a software engineer for a November project. Compare three evidence situations and the next useful action.
The role says ‘software engineering’; the profile describes ‘application development’.
How to read it
The wording may describe relevant work. Similar terms justify inspecting the experience; they do not establish proficiency or duration.
The next useful action
Review the project examples and the person's contribution against the actual role requirements.
Compare all 3 cases
| Case | Known information | Next action |
|---|---|---|
| Related terminology | The role says ‘software engineering’; the profile describes ‘application development’. | Review the project examples and the person's contribution against the actual role requirements. |
| Missing qualification | Experience appears relevant, but evidence of an essential qualification is absent. | Request the required evidence or route the record for review before treating it as eligible. |
| Availability conflict | Skills evidence is relevant; the person is committed to another project until January. | Confirm whether release or timing can change. If it cannot, consider another candidate or a different project start date. |
Illustrative example. These controls explain the method; they do not access client records or execute workforce actions.
Evaluate the complete path from a requirement to the evidence, the availability check and the next action. That is where a matching recommendation becomes useful to an operating team.
Explore the relevant EVA capabilitiesSources & further reading
The release history is based on EVA's 13 December 2024 feature announcement. Current evaluation guidance was added in September 2026. Historical roadmap items are not presented as delivered capabilities; use the current scope pages below when planning an implementation.