One set of business objects, two frontends
Asia Talent Hub and MSV Internal Operations are two windows onto the same records. There is no separate Asia candidate and internal candidate, and no separate Asia request. Each screen shows a filtered view of the shared record.
- Candidate — identity, source, professions, evidence, consent, readiness, availability, sharing state, profile review state.
- Agency — the sourcing partner. Every candidate belongs to exactly one.
- Request — client demand grouped by profession, owned by MSV.
- Profession demand — how many people of one profession a request needs right now.
- Agency allocation — how much of one profession demand one agency was asked to cover, what it committed to and what it delivered.
- Selection — one candidate against one profession inside one request, with client outcome, interviews, information requests and offers.
- Offer version — every issued version is kept. A signed version is never replaced.
- Activity — notes, tasks and mentions, each with a visibility scope.
- History entry — who changed what, when, and why.
What each side may see
| Information | MSV Internal Operations | Asia Talent Hub |
|---|---|---|
| Full candidate dossier | Everything | Only its own candidates, without MSV internal notes |
| MSV internal notes | Yes | Never |
| Notes marked shared with agency | Yes | Yes, for that agency only |
| Client confidential notes | Yes, restricted roles | Never |
| Client name and project detail | Yes | Only what MSV chooses to publish |
| Request demand | All professions and quantities | Only its own allocation |
| Other agencies' progress | Yes | Never |
| Client outcomes | Full detail | Simplified outcome only |
| Offer versions | All versions and reasons | Latest version to be signed |
Integration points still to build
- A single candidate record both apps read and write, with the MSV ID as the shared key.
- Publishing a request allocation to an agency, and receiving acknowledgement and commitment back.
- Agency progress updates flowing into the sourcing view.
- Candidate submissions to a request, always landing in MSV review first.
- Information requests going out and material coming back for MSV review.
- Offer versions going out and signed copies coming back.
- Shared notes and mentions crossing between the two apps, internal notes never crossing.
- A shared history log so both sides see the same sequence of events.
Replacement wording
- Replacement candidate — someone is lost during selection or before arrival, and the request demand reopens. In use now.
- Replacement worker for a client — a worker is lost in Romania and the client needs another one. Later module.
- Relocation candidate — a worker already in Romania needs a new employer. Later module.
Points that need a decision
- A client can ask for an interview before MSV has approved a profile. This build shows the request and blocks scheduling until approval. Confirm that is the rule.
- Reducing a request's demand can drop below what agencies already delivered or committed. This build keeps commitments valid and flags the difference rather than deleting work.
- A candidate may sit in several selections at once, but only one confirmed commitment. Confirm whether the others should withdraw automatically or wait for a person to decide.
- The candidate employment offer and the client's firm job offer are different documents. Confirm who issues each and in what order.