A Company Needs 100 Workers in the UAE. What Happens Next?

1. The number is the first thing to question

Take a request for 100 people. Perhaps 60 positions are approved, 20 depend on a project award and another 20 are being kept as a buffer for expected drop-off. That is not one requirement. It is three different kinds of demand, and each one should be handled differently.

The approved 60 can move. The next 20 need a decision date. The final 20 may be useful for planning, but they should not be presented to candidates as confirmed jobs. This distinction may sound fussy when the deadline is close. It becomes much less fussy when people have already been screened for positions that never opened.

There is also a business event behind the number: a project award, a new site, an additional shift, a seasonal peak or perhaps a replacement drive. Write down that event and the date on which a shortage starts affecting the operation. That date is more useful than saying the requirement is “very urgent.”

2. A hundred people will not move as one group

The 100 could mean 35 masons, 25 carpenters, 20 steel fixers and 20 helpers. One of those trades may be holding up work at the site while another can join later. A total count hides that problem quite well.

Then there is the practical question of movement. Can the interview panel assess 100 people? Can the responsible parties process everyone at the same time? Can the site induct them on the same morning? Usually, at least one answer is no.

So the requirement becomes a batch plan. Perhaps 20 people are assessed first, followed by 30, then the remaining roles after the employer reviews the pass rate. The exact batch size is not important. What matters is that the people responsible for assessment, decisions, processing and joining can keep up with it.

• The roles and numbers in this batch
• Where and when the assessment will happen
• Who can make the final decision
• The realistic joining window
• How many additional candidates are needed as contingency

3. Then there is the job itself

Job titles are unreliable. An electrician who has spent five years on residential work may not be ready for industrial cable termination. A “technician” in one business may be doing work that another business separates into two or three roles. The title alone will not tell the sourcing team any of this.

A useful brief describes the work in plain language. What will the person do most days? Which tools or equipment will be used? Is the work indoors, outdoors or at an active site? Which parts are safety-critical? What should the candidate be able to demonstrate during an assessment?

We also need to separate a true requirement from a preference. A licence or certificate may be essential. Experience with one particular brand may only be convenient. Even years of experience can be misleading. Asking for eight years instead of four reduces the pool, but it does not prove that the remaining candidates are better at the job.

4. One job, one version of the terms

This one sounds obvious. It often is not.

A role passes from the employer to an adviser, then perhaps to a UAE agency and a source-country partner. By the time it reaches a candidate, overtime has become guaranteed, the worksite has moved to Dubai and the salary has acquired an extra allowance. Nobody may have intended to mislead the candidate. The result is still the same: the candidate has heard a job that does not exist.

There should be one approved version of the terms, with a date on it. If something changes, issue a new version and contact the candidates who were screened against the old one. Editing the master sheet is not enough because the earlier information has already left the sheet.

• Actual duties, worksite and shift
• Wage structure, benefits and any applicable allowances
• Contract duration
• Accommodation and transport arrangements, where relevant
• Expected selection and joining dates
• The party that will employ and sponsor the worker

5. The part everyone assumes someone else has checked

Large requirements often involve several businesses. There is the employer, perhaps an HR consultant, a recruitment agency in the UAE, a source-country agency and the party responsible for employment and work permits. Everyone may know their own piece. That does not mean anyone has checked the entire chain.

We prefer to put the chain on one page. Who approves the requirement? Who is allowed to perform recruitment mediation? Who employs and sponsors the worker? Who handles the permitted source-country activity? The gaps become surprisingly easy to see once every activity has a name beside it.

This is not only good administration. Article 6 of UAE Federal Decree-Law No. 33 of 2021 requires the relevant Ministry permit for a person to work in the UAE and the appropriate Ministry licence for recruitment or employment mediation. MoHRE also distinguishes mediation from temporary employment and outsourcing. The real activity matters here. Calling something “coordination” on an invoice does not change what a party actually did.

6. What counts as a good candidate?

The answer should be written before the CVs arrive. If it is not, the standard tends to change with the pressure of the day.

For a trade role, the evidence may include identity and document validity, relevant employment history, required certification, a practical test, basic safety awareness and confirmation that the candidate understands the approved terms. A CV can point to experience. It cannot prove trade competence.

Professional roles need a different approach. A data engineer may need a structured technical discussion or a small work sample. An IT support candidate may be better assessed through two realistic troubleshooting scenarios than through 20 broad questions. The assessment should resemble the work closely enough to tell us something useful.

Keep genuine minimums as pass-or-fail checks. Score the comparative strengths separately. This makes a rejection easier to explain and stops a preferred quality from quietly becoming mandatory halfway through the campaign.

7. More CVs can make the process slower

Let us say the employer has two assessors and they can complete 30 proper interviews in a day. Sending 300 profiles on Monday does not create ten days of progress. It creates a queue of 270 people before the second day begins.

Those candidates wait. Agencies ask for updates. Some people accept other work. Then everybody spends time replacing candidates who were good when they first entered the process.

We would rather see 30 candidates assessed and decided on than 300 waiting in a folder. Before starting, agree who can decide, which scorecard they will use, when results will be released and what happens when the assessors disagree. Candidate supply is only useful when employer decisions can keep pace with it.

8. The word “selected” causes trouble

One person uses “selected” when the interviewer says yes. Another uses it only after the employer signs the final list. Someone else means that the candidate accepted the offer. All three report the same word, but the candidates are at three different points.

We use a simple rule: a candidate enters a status only when the agreed evidence exists. “Offer accepted” needs a recorded acceptance. “Process initiated” needs the name of the process, the responsible party and a date. “Ready” needs a defined readiness check. There is no benefit in moving somebody forward early just to make the total look better.

• Sourced
• Screened
• Submitted
• Employer-selected
• Offer accepted
• Permit or employment process initiated by the responsible party
• Travel or readiness confirmed
• Joined
• No-show
• Replacement pending

9. Candidates notice the gaps in communication

A candidate does not need a message every morning. But the person should know who will provide an update, where a real question can be raised and what happens when the employer changes a date or term.

Long silence creates its own version of the story. Conflicting answers create several. Both tend to reappear later as withdrawals, delayed documents or no-shows. Communication is not a soft extra in volume hiring. It is one of the delivery controls.

Candidate documents need similar care. CVs, identification and other personal data should sit in an authorised recruitment or document system with controlled access. They should not be copied across personal inboxes, messaging groups and informal spreadsheets. A shared progress view rarely needs the full file or every personal detail.

10. Now, the uncomfortable money question

A contract that says “fee payable for each successful candidate” still leaves a large question unanswered: what is a successful candidate? Is it somebody selected by the employer, somebody whose process has started, somebody with a booked ticket, or somebody who has joined?

The distinction matters when a candidate accepts and later becomes a no-show. It also matters when the employer changes the wage, worksite or start date after selection. These are awkward topics once an invoice is due, so they should be ordinary topics before work begins.

Write down the fee trigger, the evidence needed for invoicing, the payment timing, the definition of a no-show, the replacement period and any clawback or reversal rule. The delivery tracker should record the same trigger. If a fee is at risk, keep that exposure visible rather than hiding it inside the next batch.

11. The site needs to be ready too

It is possible for the candidates to be ready and the employer not to be. The permit route may still be unclear. Contracts may not be final. Accommodation may start next week. The site may be able to induct only half the planned batch.

Before confirming readiness, check the responsible employer or licensed provider, the approved terms and employment documents, and the owner of onboarding. For site roles, check accommodation and transport where applicable, site access, supervisor availability, induction space, PPE and safety orientation.

MoHRE guidance places workplace health and safety responsibilities on employers. So recruitment and site readiness cannot run as two separate plans and meet only on the joining date.

12. The weekly view should be almost boring

There will be detailed candidate records, assessment sheets, document folders and message threads. The weekly employer view does not need to reproduce all of them. It needs to show movement by role and batch, the current blocker and the next person who must act.

This view should become familiar enough that nobody spends the meeting discussing how to read it. Keep the candidate-level workflow in the recruitment system. Use the weekly view to answer a few operational questions.

• Required by role and batch
• Screened, submitted and selected
• Process initiated, ready and joined
• No-show and replacement pending
• Ageing and current blocker
• Owner and next action

So, what should exist before sourcing starts?

Not a 20-page policy. Not a beautiful presentation. One considered page is usually enough to begin.

If the employer and delivery partners can complete the fields below without debating the answers, the requirement is probably ready for a sourcing plan. If they cannot, that discussion is the next piece of work.

This will not remove all the uncertainty

Candidates can change their minds. Project dates can move. A source market that looked promising can produce fewer qualified people than expected. A good brief does not prevent any of that.

What it does prevent is a different kind of delay: candidates assessed for an unapproved role, two versions of the wage, 200 profiles waiting for one decision-maker, or a batch arriving before the site can receive it. Those are not market uncertainties. They are planning gaps.

This is why we would spend one serious working session on the roles, batches, job terms, evidence, decision capacity and responsibility chain before asking the market for hundreds of profiles. It is less visible than a sourcing campaign. It is also where a large part of the campaign is won or lost.

Mesh Workforce helps UAE employers turn a headline requirement into a practical role, batch and delivery-governance plan for execution by the appropriately licensed and responsible providers.