Pakistan-to-Saudi Recruitment Procurement Scorecard

This scorecard is for a Saudi employer that has a genuine workforce need and must compare potential recruitment partners in Pakistan. It is not a ranking of agencies and it does not treat a sales presentation as delivery evidence. The purpose is to create a consistent record of what was checked, what remains conditional, who owns each decision and whether the campaign is ready to move from planning into candidate outreach.

Score the partner against the approved requirement, not against generic claims about database size, speed or industry coverage. A partner can be suitable for one occupation or city and unsuitable for another. The employer should therefore retain role-level evidence and record any limitation instead of averaging every category into a single optimistic result.

• Use one controlled version of the requirement and scorecard
• Separate mandatory pass or fail gates from comparative preferences
• Name the evidence reviewed for every material score
• Record conditions that must be closed before launch

A partner cannot produce a defensible shortlist from an undefined request. The employer brief should state each occupation, headcount, work location, reporting line, essential duties, minimum experience, qualifications, shift pattern, contract terms, benefits, site conditions and target joining sequence. Keep mandatory criteria separate from preferences so candidates are not screened out for conditions that were never approved.

Check that the job title, actual work and proposed occupation remain aligned. If the employer changes duties, location, salary, benefits or quantity, pause the affected role and issue a controlled revision. The recruitment partner should be able to show which candidates were assessed against which version rather than quietly applying new terms to an existing pool.

• Role-by-role duties and minimum evidence
• Salary, benefits, deductions and work schedule stated clearly
• Saudi city, site type and access conditions confirmed
• Interview authority and selection deadline assigned
• Revision number and approval date shown on the brief

Define a common screening record for every candidate in the same role. It should show the mandatory checks completed, relevant work history, qualification or licence evidence where applicable, language or communication needs, notice or availability information, and any point that still requires employer confirmation. The record should explain why the candidate advanced rather than merely repeat a CV.

Shortlist quality also depends on disciplined exclusions. The partner should record why a person did not meet a mandatory criterion without using discriminatory or irrelevant preferences. A reserve list should be genuinely assessed and clearly labelled; it must not be counted as selected. This creates a usable audit trail if requirements change or an employer reviewer challenges the result.

• One screening template used per role
• Pass, reserve and decline reasons recorded consistently
• Conditional evidence identified rather than assumed
• Personal data limited to what the decision requires

Set the interview format, panel members, questions, evidence available to the panel and decision deadline before the first candidate is presented. Use the same core questions for candidates in the same role and record the employer outcome as selected, reserve, declined or pending clarification. Verbal selections should be converted into an approved record before the partner communicates a final outcome.

The employer should also confirm who may change a decision and how candidate queries will be answered. Do not promise a job, visa or travel date from an interview result alone. Selection remains distinct from official approvals, document readiness, medical steps and travel preparation. A responsible partner will keep those statuses separate and explain exceptions without inventing certainty.

• Panel and authorized selector identified
• Consistent role questions and scorecard used
• Outcome and conditions captured per candidate
• Candidate communication owner and timing agreed

Create a responsibility matrix covering the Saudi employer, the Pakistan recruitment partner, the worker and any authorized processing party. For each stage, state who supplies the input, who checks it, who submits it, who can approve it and who communicates the status. This is especially important for demand documentation, visa-related employer actions, medical or identity steps, Pakistan emigration formalities, ticketing and arrival arrangements.

Do not ask a recruitment partner to guarantee an official decision controlled by a ministry, platform, mission, medical authority or airline. Instead, score the partner on whether it names dependencies, checks files before submission, reports returned items accurately and updates the forecast when a dependency changes. Official requirements should be checked again for each campaign because published conditions can change.

• Owner, checker, submitter and approver named per stage
• Official and commercial dependencies kept separate
• Returned or corrected files tracked visibly
• No guaranteed approval or travel claim accepted

A credible schedule begins with an approved requirement and works through sourcing, screening, assessment, employer decision, worker acceptance, official processing and travel readiness. Ask for ranges or dependency-based milestones instead of one guaranteed deployment date. The plan should identify employer-side inputs, worker-side inputs, official decisions and operational preparation at the Saudi site.

For large campaigns, require role and batch sequencing. Schedule-critical trades may need an earlier shortlist, while accommodation, transport, access badges, induction and supervision must be ready for the planned arrivals. Score the partner on the quality of its ageing report and exception handling, not on whether every case appears green. Honest red and amber statuses are more useful than an unsupported promise.

• Milestones linked to named dependencies
• Role and batch priorities agreed
• Exception ageing and escalation route defined
• Saudi arrival and site-readiness owners confirmed

Different worker categories require different proof. A construction trade may need a practical test and safety evidence; a driver may require licence and vehicle-class checks; a healthcare professional may need qualification and professional-registration review; an engineer may need project evidence and technical interview depth. Hospitality and facilities roles may place more weight on service standards, communication and shift suitability.

Keep the common procurement gates—identity, terms, data control, reporting and commercial scope—but attach a role annex for the technical criteria. This prevents a partner with strong delivery in one category from receiving an automatic pass for unrelated roles. It also helps the employer appoint more than one specialist partner without losing a consistent governance framework.

• Technical criteria tailored by occupation
• Credential and licence checks separated from practical tests
• Common governance gates retained across all categories
• Specialist limitations recorded before award

Mark legal identity, authority, worker-term consistency, data handling and ethical-payment controls as mandatory gates. Apply employer-set weights only after those gates pass. Suggested comparative dimensions include role-level sourcing, screening quality, assessment control, reporting, schedule realism, commercial clarity and category experience. The weights should reflect the project risk; there is no universal percentage that fits every campaign.

For each score, record the evidence, reviewer, date and any condition. Avoid unsupported labels such as best, number one or guaranteed. The final paper should state why the selected partner fits this specific requirement, which risks remain, which conditions must close before launch and when the employer will review performance. Keep unsuccessful proposals and scoring records according to the employer's retention policy.

• Mandatory gates resolved before weighted scoring
• Weights reflect the actual project and role risks
• Evidence, reviewer and date retained for every score
• Award conditions and post-award review date documented

Proceed only when the legal entities are verified, the employer requirement is approved, the screening and assessment methods are documented, the worker-facing terms are consistent, the commercial scope is understood, the responsibility matrix is assigned and the reporting route is ready. Place unresolved items in a dated condition log with an owner; do not hide them inside a general promise to mobilize quickly.

Pause when licence or identity evidence cannot be verified, terms conflict, unauthorized payment instructions appear, candidate data is requested without a necessary purpose, a partner guarantees official approval, or the job and proposed occupation do not align. Re-check current Saudi and Pakistan official guidance before every campaign and obtain qualified legal advice where the facts or obligations are uncertain.

• All mandatory procurement gates passed
• Open conditions have owners and closure dates
• Employer, partner and worker communications align
• Current official requirements checked before launch