Know who on the roster is available and willing today. Decide who deploys.
EVA is an AI agent that talks to each roster member before a request arrives, records dated availability, willingness and certificate expiry, and shows where every finding comes from.
EVA provides evidence and recommendations. Your people make the decisions.
Live within the United Nations and LVMH, across 120+ countries.
Who fits this mission, wants to go and can actually be released?
Being on a roster does not establish current readiness. Availability, recent experience and employer release can change between deployments. A useful roster distinguishes capability, willingness and required clearances, then lets the authorised team confirm a real deployment.
Keep roster facts current for the next mission review.
Start with one roster and its deployment criteria.
Use the roster’s existing competency framework and records. Agree who owns release, travel, security and specialist clearance checks. Scope the refresh cadence around the readiness window; urgent mobilisation still uses established duty procedures.
Refresh the facts that change.
Ask roster members about current availability, deployment interest, languages, recent experience and relevant certificate dates. Confirm location only to the level needed for mobilisation. Keep a respondent’s statement separate from a check completed by an authorised owner.
Review a mission-specific shortlist.
Compare current evidence with the mission’s role, timing and operating context. Show gaps and expiry dates alongside possible candidates. Capture post-deployment observations for review, so the next mobilisation can draw on recent work.
See possible responders and what still needs confirming.
Review the dated accounts, the checks still open and the person responsible for the next action.
| Roster member | Dated availability and willingness | Evidence | Outstanding condition (owner) |
|---|---|---|---|
| R-021 · Logistics | Available 1–30 Nov, wants to go (confirmed 24 Sep) | Recent field assignment; French B2 (self-declared) | Employer release requested 25 Sep; roster manager |
| R-058 · Information management | Last confirmed 4 Aug; recheck due | Relevant examples (supervisor, June 2026) | Fresh confirmation; coordinator contacts the member |
| R-094 · Technical specialist | Available, wants to go (confirmed 22 Sep) | Required certificate expired 15 Sep | Renewal or clearance; deployment owner holds the decision |
Keep availability, release and clearance separate.
Roster entry is not clearance
A strong capability match does not establish fitness, security approval or deployment permission. Each mandatory check keeps its own owner.
Readiness has a timestamp
Show when availability was confirmed and when it should be checked again. A monthly refresh does not guarantee readiness at the moment of mobilisation.
Keep sensitive checks with their owners
Use only necessary readiness status and review dates. Medical details and specialist clearance records stay in the appropriate authorised process.
Start with one roster and one mission request.
Bring one roster, its role framework and a recent deployment request. Agree a refresh that shows who confirmed availability and when, who wants to go, certificate dates, and the release and clearance checks still open, each with its owner. Urgent mobilisation keeps your duty procedures.
Proposed application. Delivery, language coverage and connections are agreed in scope.
Capacity mapping and matching at UNDP.
23,000 staff and contractors mapped
Shortlists in under 1 hour with EVA Talent Matching
United Nations Development Programme.
EVA's capacity mapping at UNDP provides context. This page describes a new application for a surge roster, not a result demonstrated by that deployment.
Does a current roster cut the time to a reviewed shortlist?
Compare the time and effort to reach a reviewed mission shortlist with your current process. Keep response freshness, employer release and clearance work separate from matching speed.
Current-response coverage
Count members with dated responses covering the mission window.
Coordinator chasing
Record coordinator effort spent obtaining availability and release confirmations.
Time to a reviewed shortlist
Measure from the mission brief to a reviewed shortlist, including rework.
Clearance gaps resolved
Track required checks resolved by their authorised owners before mobilisation.
Measures are agreed with you against your baseline; they are not promised results.
- Decision owner
- Surge or emergency operations director answers for mobilisation quality and readiness.
- Working lead
- Roster or deployment manager coordinates member updates before each request.
- Review and control partners
- Network mobilisation lead coordinates a national society or civil-protection network with a shared framework and named clearance owners.
Questions before you start.
3 questions to explore
Does EVA dispatch responders?
This concept supports evidence refresh and review. It does not replace command, duty-officer or emergency-dispatch systems, and it does not independently authorise mobilisation.
You might also want to know
Where this connects.
End of Assignment
The conversation after deployment that keeps the roster honest.
Explore this decision →Volunteer & Membership Networks
For response volunteers: willingness and availability, with clearance kept separate.
Explore this decision →Competency Mapping
The evidence record underneath every EVA conversation.
Explore this decision →Discuss one roster and a recent deployment request.
Use the call to describe one roster and mission request, the people involved and what a useful first output would look like. No personal records are needed.