A consultant or contractor can have the right experience and still be unavailable for the work. Deployment decisions need both capability and the practical conditions of an assignment. Keeping those questions separate makes the next action clearer.
Define the assignment precisely
Describe the work, expected contribution, start and end dates, capacity and location needs. Identify essential evidence and any client-defined readiness checks. Avoid treating a broad job-family match as sufficient for a time-sensitive mission.
Clarify the systems and teams involved in authorising and recording the assignment. HR, procurement and operational managers may each own different parts of the process. Agree the handovers rather than assuming a shortlist automatically becomes a booking.
Keep availability current enough to use
An old statement that someone is ‘available’ has limited value. Collect the period and capacity relevant to the assignment, and decide when it must be reconfirmed. Distinguish interest in the work from a commitment to perform it.
A person may cover part of the requirement. Compare partial capacity, revised dates or another person explicitly. Do not hide an unresolved timing conflict behind a strong capability score.
Track evidence and exceptions
A required document can be missing, awaiting review or approaching expiry. Those are different states with different follow-ups. Show what has actually been checked and which team is responsible for resolving the rest.
Configured workflows can collect missing information, route an exception or carry out an authorised update. The presence of a checklist does not guarantee legal compliance; the client must define applicable requirements and appropriate review for the assignment.
Record the assignment and learn from the handover
Once the agreed conditions are satisfied, complete the assignment through its authorised process and verify the destination record. Keep the latest status available to the people coordinating the work. A request sent to another system is not proof it was accepted.
Review where readiness checks and handovers create avoidable delays. The aim is a dependable process across the client's different markets and assignment types, with enough local detail to make each deployment practical.
Three people, three readiness states
Illustrative mission-readiness board. These are three distinct people, not summed competency records.
Relevant example · available for the period · evidence received
How to read it
The record is ready for the agreed final review. Receipt of evidence is not a completed assignment.
The next useful action
Finish the required checks and run the authorised assignment process.
Compare all 3 cases
| Case | Known information | Next action |
|---|---|---|
| Alex · ready for review | Relevant example · available for the period · evidence received | Finish the required checks and run the authorised assignment process. |
| Sam · date conflict | Relevant expertise · current assignment overlaps | Compare a later start, partial cover or another candidate. |
| Jo · evidence gap | Available · required evidence not yet supplied | Request the missing evidence and route it to the responsible reviewer. |
Illustrative example. These controls explain the method; they do not access client records or execute workforce actions.
Readiness is a set of explicit conditions, not a single impression of suitability.
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.