Employer recruitment technical guide
A shortlist scorecard converts an employer requirement into consistent, explainable evidence for every candidate decision.
A shortlist scorecard converts an employer requirement into consistent, explainable evidence for every candidate decision.
Readers frequently seek practical answers around saudi recruitment agency in lahore. This page answers a narrower operational question so it supports, rather than duplicates, the existing hub already helping visitors.
Before a campaign is opened, the employer should assign a legal entity, authorized approver, worksite, role schedule, written terms and decision method. Keep mandatory criteria separate from preferences, and do not advertise a role until the employer page and candidate-facing terms are internally consistent.
The sequence below is designed for Saudi employers. Complete it in order, retain evidence for material decisions and stop where the legal page or identity record cannot be verified.
Translate the job description into mandatory and preferred fields. Mandatory criteria can include occupation experience, licence, trade method or client approval. Desirable criteria can improve ranking but should not silently reject an otherwise qualified person.
For each criterion, record the source: CV, certificate, employer reference, structured interview, demonstration or practical assessment. A score without a source is an opinion, not selection evidence.
A technically suitable candidate may not yet have current documents, medical readiness or availability. Show job fit and mobilisation readiness in separate columns so employers do not reject skill for a temporary administrative gap.
Give greater weight to safety-critical or output-critical competencies, but set weights before reviewing candidates. Avoid changing the scoring model to favor a preferred person after interviews begin.
Record any gap the employer accepts, such as a licence conversion, equipment orientation or language training. Name the condition owner and deadline so a conditional selection cannot be mistaken for final clearance.
Use selected, reserve, hold or rejected with a concise reason. Keep rejection reasons job-related and consistent. The date and approver should be visible for later audit and replacement analysis.
After each batch, compare shortlist conversion, rejection reasons, joining rates and early attrition. Feed the findings back into sourcing channels and screening questions instead of simply requesting more CVs.
Use the result labels as decision controls, not marketing claims. Each status should have a date, owner, supporting evidence and next action.
Meets mandatory criteria, evidence is sufficient and the employer has approved the candidate.
Suitable subject to a named document, test, licence or availability condition.
Meets the role but is held behind selected candidates for the same approved requirement.
Does not meet a stated mandatory criterion; record a concise job-related reason.
Most avoidable failures are caused by an unverified source, the wrong reference, incomplete written terms or an assumption that one completed step proves the entire case.
A keyword match does not prove duty competence. Require interview or practical evidence for critical criteria.
A temporary notice period should not distort the technical score. Track readiness separately.
Every scored criterion needs a source or an explicit not-verified status.
Approve the model before use and version any changes.
Send only the data needed for the employer decision through controlled access.
Use one worker-level tracker with role, selection, condition, document, official-stage, medical and travel fields. Restrict sensitive data, keep version history and record who changed each field. A campaign total must never hide a worker-specific mismatch or an unapproved change in terms.
Retain only the information needed for the active purpose. Do not publish passport, Iqama, visa, medical, salary or contact data in public posts. Where a correction is needed, change the controlling source and preserve the previous value, date and reason in the restricted case record.
Verbal updates can support coordination but should not replace the written contract, official portal result, employer approval or government document. If two sources conflict, pause the affected action and ask the accountable owner to reconcile them.
Open one dated record for the case before the first decision. The record should state the responsible organization, authorized contact, subject or worker reference, purpose, source checked, result observed, evidence location, next action, owner and review date. Record the literal result before adding an interpretation so another authorized reviewer can distinguish evidence from opinion.
For this topic, begin with Freeze essential and desirable criteria: Translate the job description into mandatory and preferred fields. Mandatory criteria can include occupation experience, licence, trade method or client approval. Desirable criteria can improve ranking but should not silently reject an otherwise qualified person. Then complete the remaining controls in sequence. Close the record only after use scorecards to improve sourcing has been addressed: After each batch, compare shortlist conversion, rejection reasons, joining rates and early attrition. Feed the findings back into sourcing channels and screening questions instead of simply requesting more CVs.
Use masked identifiers in routine coordination, limit access to people who need the information, and avoid moving passports, identity records or account credentials through public groups. If an update changes eligibility, terms, timing or the accountable party, retain the earlier value and document who approved the change.
A reviewer following this guide may reach the status Selected. In practical terms, Meets mandatory criteria, evidence is sufficient and the employer has approved the candidate. That statement is a control outcome for the current evidence and date; it is not a promise that a later authority, employer or applicant action will produce the same result.
The first escalation trigger is Scoring CV keywords. A keyword match does not prove duty competence. Require interview or practical evidence for critical criteria. The reviewer should pause only the affected step, identify the controlling source, request the minimum corrective evidence and set a dated follow-up. Unrelated workers or requirements should not be delayed unless the same defect applies to them.
When the issue is corrected, repeat the relevant check against the current official or employer-controlled source, note the new result and preserve the audit trail. A screenshot alone is not enough when it omits the source URL, date, reference type or surrounding status message.
Before handover, confirm that the record names the accountable owner, the next action, the evidence still required and the date on which the result must be reviewed. The receiving person should be able to understand the case without relying on a private chat or an undocumented verbal explanation.
Do not mark a case complete merely because a form was submitted or a portal page opened. Completion means the required decision is recorded, the relevant party has received it through an authorized page, sensitive material is stored appropriately and any remaining dependency is clearly assigned.
Government approvals, work authorization and processing times remain with the competent authorities. AL AHAD GROUP can coordinate a verified employer requirement, but it cannot guarantee an official decision, a fixed date or immediate worker availability.
Official procedures can change. Confirm the current requirement for the exact country, occupation, employer and person at the time of action. The sources below are starting points; follow their current instructions and notices.
A keyword match does not prove duty competence. Require interview or practical evidence for critical criteria.
A temporary notice period should not distort the technical score. Track readiness separately.
Every scored criterion needs a source or an explicit not-verified status.
Approve the model before use and version any changes.
Send only the data needed for the employer decision through controlled access.
This guide has one technical intent. Use the pages below for the broader service or candidate context instead of repeating that material here.
Share a role-by-role employer brief before sourcing starts.
