For recruitment agencies
More assignments for your consultants. Credit that lands on your agency.
Your consultants take marketplace assignments as themselves. Every candidate they submit is credited to them by name and to your agency on the same record — derived from what was written at submission, never typed in afterwards.
How an assignment reaches a consultant
Six steps, in the order the platform performs them. Your agency is not assigned to an assignment — the individuals in it are.
A company opens an assignment against a role it already owns.
It is distributed publicly, or only to the recruiters it invites by name.
Your consultant accepts it, or declines and steps back off it.
They submit candidates into it.
The company shortlists, interviews, rejects, or makes an offer.
It closes filled, cancelled or expired, and the reason is recorded.
What your consultant sees before accepting
The brief, the closing deadline, the per-recruiter submission cap, the fee terms the company set, the guarantee period and the ownership window. Who else is on the assignment is not shown: your consultant is told their own standing — invited, accepted — and not handed a roster of their competitors.
You cannot be cut out of the record
Three mechanisms, each written on the server rather than in a browser.
Credit is derived, never typed
When a placement is recorded, the credited consultant and the credited agency are read from the attribution written at the moment the candidate was first submitted for that role. They are not accepted from the request — not from the company, not from the recruiter, and not from a member of our own staff filling in the form.
One window per candidate and role
Ownership of a candidate on a role belongs to the first valid submission, and it holds for a period set on that assignment and shown to your consultant before they submit. While it is open nobody else may submit that person for that role — not a rival agency, and not a second consultant of your own. Resubmitting your own candidate does not extend it.
A transfer is all or nothing
If credit is ever moved, creating the new claim and retiring the old one are applied together. When the second write fails the first is deleted and nothing changed, so a half-applied transfer cannot leave two live claims behind. A failure is reported as a failure; it is never reported as success.
When two submissions collide
The second submission is refused before any submission record is written, so the same person never reaches the company from two suppliers. The recruiter who lost is told the rule, the date the standing claim expires and that they may resubmit after it — but not who holds it, because naming the holder hands one recruiter a rival’s pipeline and exposes a candidate’s interest in a job to a third party they have no relationship with. The collision itself is recorded as evidence, so it can be reviewed later.
The agency stamp is taken at submission time
A placement record carries the credited consultant, your agency, and the attribution behind both. The agency is read from the consultant’s profile as it stood when the work was done rather than as it stands today, so a consultant who later leaves does not rewrite your book — and does not rewrite the next agency’s either.
The other half is stated plainly: a consultant’s profile and their own placement history belong to the person and travel with them. That is the same arrangement that makes the stamp on your placements permanent — it is one design, not two.
What you can see of your team, and what you cannot
An agency owner — proven against the agency record itself, never against anything the browser sends — gets two sections a consultant does not. These are their limits, stated in full.
Shown to you
- Your roster: each consultant’s name and headline, whether they are verified, their tier, whether they are accepting assignments, and whether the seat is active.
- What NukhbaTalent has recorded for each of them — submissions, interviews and placements. A consultant who has never been measured is counted as unmeasured, not as three zeroes.
- Workload across the team: the highest, the lowest, the average, and how many active consultants are carrying no open assignment at all.
- Your agency’s book, kept per currency, with the fee and each share reported as separately stored figures that are never reconciled against one another.
Not shown to you
- A consultant’s live pipeline. The candidates they are working and the claims they hold belong to the individual who made them, so the roster tells you who your people are without handing one colleague another’s book.
- A colleague’s own subscription and commission standing with NukhbaTalent. That is their commercial relationship with us, not the agency’s business.
- Seat management. Adding a consultant to your roster is a change NukhbaTalent makes, not a field on your screen — ask your account manager for the people who already work for you.
A refusal is enforced where it cannot be bypassed
A candidate who has declined or withdrawn consent cannot be submitted to a company. That is checked on the server at the moment of submission, not in your consultant’s browser, and no workspace setting can switch it off. For an agency operating under PDPL that is a compliance feature, not an obstacle.
Where there is no answer on file the submission is allowed: a consultant putting forward a person they have actually spoken to is a named individual acting case by case. A recorded refusal is a different fact entirely, and the consent state is on the screen either way.
What this costs is not on this page
Fees, how they are split, and guarantee periods are commercial terms agreed per engagement rather than published here. Each assignment states its own fee, its fee type, its guarantee period and its ownership window, and your consultant sees all of it before accepting. If you want the terms for your agency, ask us.
Already with us? Open your workspace
NukhbaTalent
AI Recruitment OS