Manpower Planning for Riyadh, Jeddah and Dammam: AL AHAD GROUP Employer Guide

Begin with one national requirement and separate site decisions

A business seeking manpower support in Riyadh, Jeddah and Dammam needs a national brief that explains the programme and a separate operating instruction for each receiving site. A combined headcount is useful for budgeting, but it cannot show whether the right duties, supervision and joining conditions have been accepted in every location. Start by identifying the business requirement, the participating establishments, the authorised employer contact and the decisions the proposed AL AHAD GROUP scope is intended to support.

Keep the overall purpose understandable. Your organisation may need recurring facilities coverage, a phased project workforce, warehouse assistance or candidates for direct employment. Those needs can sit within one corporate programme while requiring different service models and evidence. Do not combine them into an undefined national manpower order merely because the same procurement team coordinates the discussion. Describe the common objective and then identify the distinct appointments or service arrangements that need their own review.

This guide concentrates on coordination across locations: master specifications, site schedules, consistent evidence, commercial assumptions and separate readiness decisions. It does not establish offices, a local workforce inventory, live vacancies or confirmed service availability in any city. The actual scope offered, the applicable official requirements, commercial terms and commencement arrangements need confirmation for the particular case. Use the national brief to organise that review, while keeping each receiving operation's responsibilities visible.

Establish who can approve the programme and each assignment

Name the person who owns the overall requirement and the people authorised to decide its components. National procurement may coordinate the commercial discussion, while operations defines the duties and local management confirms the receiving arrangements. Employment or official establishment actions can involve another authorised representative. Write down these distinctions before requesting a proposal. A single business contact can collect information without necessarily having authority to accept every employment, technical or site decision associated with the programme.

For each approval, state what is being accepted. Approving a budget does not approve candidate suitability. Accepting a task schedule does not complete official permissions. Confirming a reporting location does not establish the final commercial agreement. A practical decision register describes the evidence required, the decision-maker and the consequence if the item remains unresolved. This prevents a general approved label from hiding several incomplete conditions that different people still need to address.

Agree an escalation route for conflicts between national and local instructions. A site may request an additional activity that the corporate programme has not included, or procurement may assume a receiving date that local operations cannot support. Resolve the specific difference and issue the accepted revision. Personnel and coordinators should not be left to choose between competing messages. One programme can have several responsible owners, provided each knows the decisions they control and the information they must share.

Distinguish budgets, forecasts and authorised quantities

Label each quantity according to its actual status. A budget allowance is a financial planning input. A demand forecast estimates a possible operating need. An authorised position or accepted service quantity is a more specific decision. A proposed deployment wave may still depend on area release, selection or another condition. These categories should not be mixed in one total without explanation. Otherwise the responding team may be asked to plan against numbers that the employer has not approved for action.

Create a role and location schedule showing the accepted baseline, later phases and conditional requirements. Explain what triggers each conditional line and who will confirm it. For example, an additional warehouse window may depend on a receiving facility opening, while a project trade requirement may depend on the preceding work stage. Keep the dependency attached to the affected line rather than placing a vague subject-to-confirmation note beneath the whole national request.

When the forecast changes, record the change without rewriting history. Identify the previous quantity, current quantity, reason and decision status. This helps distinguish a revised business expectation from a failed mobilisation commitment. The programme owner should be able to explain which figures are ready for scope review and which remain provisional. A well-labelled forecast supports useful preparation; it should not be published as a current vacancy or treated as an accepted staffing order.

Confirm the service model for every component

Direct recruitment supports an employer's selection and appointment of candidates. An operating manpower arrangement needs its own employing, supervision and delivery responsibilities. A defined outsourced service should explain its tasks and acceptance basis. A national programme can contain more than one model, but the proposal must identify which applies to each component. Similar job titles do not make the relationships equivalent, and a common commercial contact does not settle who employs or directs the people involved.

MHRSD's outsourcing announcement describes defined tasks performed by expatriate workers already resident in Saudi Arabia, with direct supervision by the service-providing establishment through Ajeer. The authorised parties should examine that official framework and the applicable service requirements for the actual arrangement. A website, commercial label or previous project does not prove eligibility for every new establishment, worker or task. Keep that review separate from the operating site's access and task-readiness checks.

Ask who signs the employment terms, who accepts the service proposal, who issues daily instructions and who receives completed work. Record where those responsibilities differ between programme components. If the employer needs candidates for its own appointments, a personnel-supply price is not a complete recruitment plan. If it needs operating coverage, a shortlist alone does not define the service. Clarifying the model early reduces the risk of building a detailed schedule around an arrangement the parties have not actually accepted.

Build a master specification that supports useful differences

A master specification should provide a consistent format rather than force identical duties onto every location. Establish common headings for the role or task, purpose, quantity, evidence, working area, resources, supervision, acceptance and exclusions. Then allow the site schedule to state the differences that matter. Standardising the questions helps the programme compare answers. Standardising the answers without examining the work can conceal important requirements and create misleading assumptions about interchangeable personnel or services.

Distinguish a genuinely common criterion from a preference. If a certificate, language ability or type of experience is essential, explain which duty it supports and how it will be reviewed. If it is only desirable, keep that status clear. A requirement inherited from an old tender should not automatically exclude a suitable candidate or dictate an unnecessary service feature. The master specification should help the employer reach a reasoned decision, rather than accumulate conditions that nobody can connect to the actual work.

Use revision control for the common document and its site schedules. A national change should identify which locations and roles are affected. A local change should identify whether it alters a shared assumption. Keep an accepted current version available to the responsible reviewers. This makes the programme more consistent without pretending that a warehouse receiving task, an occupied-office service and a construction workfront require the same evidence or operating instruction.

Prepare the Riyadh schedule from the actual workplace

For a Riyadh requirement, identify the specific receiving location and its operating purpose. A corporate building, warehouse, hospitality property and project site need different task descriptions. State the reporting point, the area in which work will take place and the person responsible for receiving the appointment or service. The city name should locate the enquiry; it should not stand in for the details that determine whether the proposed scope can work.

Describe any conditions that affect the sequence. An occupied commercial property may need coordination around tenant activity. A project may release work areas in phases. A logistics site may have an agreed receiving or dispatch rhythm. These are questions for the actual employer and site representative, rather than assumptions about every business in Riyadh. If several locations participate, give each a separate reference and make clear which duties and quantities belong to it.

Record resources and instructions at the same level of detail. A national statement that transport, tools or supervision will be arranged still needs a responsible owner and a site-specific plan. Do not treat a Riyadh service enquiry as evidence of an AL AHAD GROUP branch, ready personnel or an established project appointment. Confirm the offered scope and receiving conditions through the authorised process, then use the national programme to track how this site relates to the wider requirement.

Prepare the Jeddah schedule around local interfaces

For Jeddah, clarify the business's own operating environment rather than relying on a general description of the city's commercial activity. A warehouse linked to cargo movements, a hotel department, a facility-service zone and a construction workfront have different handover points. Identify who releases the area, who provides the accepted instruction and who receives the task result. Those interfaces belong in the site schedule, even when the programme uses a shared national contract or procurement contact.

If the enquiry mentions a port, airport or major development, establish the actual employer assignment and the relevant access process. A nearby landmark does not establish permission to recruit for an operator, enter a restricted facility or claim a project relationship. Keep geographical context separate from verified appointment evidence. Ask the site owner which details can be shared in the initial requirement and which need a controlled private process before operational arrangements are confirmed.

Use the dedicated Jeddah manpower supply service for its primary local operating purpose and the Jeddah outsourcing guide for detailed service-boundary and handover preparation. A recruitment requirement belongs with the appropriate hiring guidance. The national programme should connect these responsibilities, not reproduce each local page under another title. Record the accepted Jeddah component, its dependencies and its relationship to the other locations so the corporate team can coordinate decisions without obscuring local ownership.

Prepare the Dammam schedule by activity and receiving site

A Dammam requirement should identify the actual activity, system or work area relevant to the employer. Industrial support, materials assistance, warehouse operations, facility tasks and technical appointments need different evidence. Do not infer a specialised capability from a general industrial location label. Describe the duties, responsibility level and boundaries that the receiving organisation needs reviewed, then identify the competent person who will examine the relevant technical or operational information.

Keep Dammam, Khobar, Jubail and other locations distinguishable when a business operates across the Eastern Region. A regional description may be useful in a programme summary, but it does not identify a reporting point or establish that resources can move between sites. Give each actual worksite its own instruction and readiness record. If travel or reassignment is proposed, review it explicitly rather than treating nearby place names as an automatic permission for movement.

For industrial or project-related work, connect the requested roles to the work stage, accepted resources and local control process. The site owner should identify any induction, task authorisation or technical review required before the appointment or service can proceed. The existing Dammam and Jubail guidance can support more specific preparation. This national page helps organise the multi-location decisions while avoiding claims that one city's reviewed assignment automatically establishes readiness for another.

Translate role quantities into comparable operating assumptions

Before adding city totals, agree what each quantity represents. It may describe simultaneous positions, selected candidates, accepted appointments, service task units or a future demand estimate. Adding unlike units produces an impressive number with little planning value. A national summary should state the unit and status of each line. Keep recruitment quantities separate from operating coverage and explain whether the schedule refers to people, positions or a service output.

For coverage planning, state the proposed window and operating days for the task. Record assumptions about access, supervision, resources and any separately assessed handover or relief. These inputs describe the business requirement; they do not establish lawful working hours, payroll treatment or the roster of individuals. The responsible employer and authorised parties must address those matters through the actual arrangement and current requirements. Avoid treating an arithmetic total as proof that a schedule is appropriate.

Use exceptions to explain meaningful differences. Two sites may request the same number of positions but have different operating days or access windows. One may have an accepted baseline while another remains conditional. A useful summary preserves those differences alongside the combined figure. This makes the programme easier to discuss and reduces the risk that a later reader interprets a planning total as a single approved workforce available for allocation anywhere in the country.

Use the three-site planning-hours worksheet carefully

The worksheet multiplies planned positions, coverage hours per operating day and operating days for each site. It then shows the three separate results and their combined illustrative total. Enter business planning assumptions only. The calculation does not set individual working hours, calculate wages, confirm a staffing commitment or determine official eligibility. Its purpose is to make unlike coverage assumptions visible before the employer discusses the proposed service scope and commercial basis.

For example, three positions across an eight-hour planning window for five operating days produce one hundred and twenty position-hours. Four positions across six hours for six days produce one hundred and forty-four. Two positions across eight hours for six days produce ninety-six. Together they illustrate three hundred and sixty coverage hours, while retaining the separate site results. These examples are deliberately arithmetic; they are not recommended rosters, market rates or a statement about the availability of workers.

Set a site's positions to zero when it is outside the current illustration. Do not use zero to conceal a requirement that still needs approval; record that status in the actual programme documents. If the combined result seems inconsistent with the intended operation, inspect the individual inputs before requesting more personnel. A wrong unit or operating-day assumption can create a misleading total. The tool runs locally in the page and does not save or transmit the numbers entered.

Sequence appointments and service starts by real dependencies

One national target date does not mean every site should start together. Identify what each wave depends on: an approved brief, an employer selection decision, completed official steps, a released area or receiving resources. The programme should show which conditions are common and which belong to a particular location. A delay in one component does not automatically require changing every other component, but the authorised parties should examine the actual links before deciding what can proceed.

Consider the order of supervisory and specialist responsibilities. The employer may need an accepted receiving lead before a larger group can be assessed or inducted. An operating service may need resources or a local acceptance method before additional positions are useful. These dependencies should shape the proposed sequence. Do not increase a wave merely because a national total is large if the receiving organisation lacks the capacity to review, instruct or equip it.

Keep desired dates, proposed dates and confirmed arrangements distinguishable. The desired date expresses the business's preference. The proposed date reflects a plan still subject to stated conditions. A confirmed joining or service start needs the responsible parties' actual acceptance. Communicate changes through the recognised programme contact and affected site owners. Avoid presenting a provisional national schedule to candidates or operating teams as if every component has already been cleared for commencement.

Keep recruitment evidence and site acceptance connected

If a programme includes recruitment, agree the evidence needed for each appointment and the employer reviewers who will examine it. A common profile format can support comparison, but it should retain differences in actual task experience, unassessed criteria and professional conditions. Candidate sourcing and interview coordination do not replace the employer's selection decision. Keep the reason for each proposed appointment clear enough that a local receiving manager can understand what has and has not been reviewed.

An assessment conducted for one role should not silently become evidence for another. A technical installation interview may not answer a maintenance requirement. Warehouse packing experience does not establish equipment-operation competence. If a candidate is considered for a different site or duty, ask the appropriate reviewer which findings remain relevant and what further evidence is needed. The national programme should make those decisions traceable rather than treating a candidate reference as an unrestricted allocation unit.

Where professional or regulated duties are involved, the receiving organisation must identify the applicable current requirements and authorised review process. Do not use a general staffing brief to imply clinical, driving, machinery or specialist work approval. Record pending conditions before an offer or site instruction is described as ready. A reliable national tracker connects the appointment evidence, accepted terms and local receiving status without suggesting that one completed interview settles every other stage.

Align employment terms and official actions with the actual case

The proposed employment terms should match the employer, duties and location being considered. Identify a discrepancy before the appointment is treated as accepted, particularly if the programme moves a requirement between sites or changes the service model. A national commercial agreement and an individual's employment contract serve different purposes. Keep their responsibilities and decision processes distinguishable. A procurement summary should not become the only explanation a candidate receives about materially different work.

MHRSD's Contract Management service describes electronic contract documentation and an employee's options to approve, reject or request amendments through Qiwa Individuals. A notification sent is not the same as the employee accepting the current terms. Record the actual status through the responsible parties and relevant channel. This guide does not promise that every contract, transfer or employment situation follows one universal timeline or that a recruitment discussion has completed the required official steps.

For an operating or outsourced arrangement, authorised establishment representatives should review the current official service information and case requirements. The programme record can identify the action owner and the evidence awaited without collecting account passwords or undertaking another person's identity approvals. Keep official eligibility, commercial acceptance and site access separate. A complete record explains how those conditions relate; it does not collapse them into a single assumption that personnel may begin work anywhere named in the programme.

Define supervision and communication at two levels

National coordination should give the business a consistent route for programme questions, accepted revisions and reporting. Local supervision should explain how the actual work is directed and observed at the receiving site under the agreed arrangement. These are complementary functions. A national coordinator is not automatically the competent supervisor for every technical activity, and a local contact is not automatically authorised to vary the national commercial scope. State the authority associated with each role.

Agree what information moves between the levels and when. A local exception that affects one task may need a local decision; a repeated change affecting several locations may require a programme revision. Identify the escalation threshold without inventing a fixed response time. The record should show who receives the issue, what decision is needed and whether another site's plan is affected. This supports useful coordination without copying every minor message to every person in the programme.

Provide alternates for relevant decision windows. A service can be delayed by an unavailable receiver or unclear instruction even when personnel are present. Confirm how an alternate knows the current accepted scope and can communicate a decision. Do not resolve uncertainty by allowing several unofficial instruction chains to develop. A consistent national contact route is valuable when it helps the right local and corporate owners reach a clear, documented decision.

Allocate resources without assuming free movement between cities

Specify tools, consumables, protective equipment and any other resources for each task or role group. Identify the supplying party and the person who confirms suitability at the receiving site. A national statement that equipment is included needs enough detail to be meaningful locally. Different systems or work areas may require different resources, even where the role title is similar. Keep specialist equipment and technical settings with the responsible competent reviewers rather than treating them as general staffing assumptions.

If equipment or personnel may move between locations, describe the proposed movement and the conditions it depends on. Consider authorisation, task suitability, transport, receiving capacity and the effect on the original site's coverage. A resource cannot be counted as simultaneously available in two places merely because both appear in one programme. Keep accepted allocations, possible alternatives and confirmed transfers distinct. The authorised parties should decide whether the proposed change is practical and appropriate for the actual arrangement.

Record issue, return and defect information at the level the operation needs. Avoid an unnecessary collection of personal details in a resource log. If a critical item becomes unavailable, identify the affected tasks and the decision needed before work can continue under the accepted controls. A general commitment to support several cities does not prove that every resource has been allocated, that an alternative is suitable or that movement between sites has been authorised.

Resolve transport and accommodation assumptions in the proposal

A multi-city enquiry should state what the employer expects about reporting transport and accommodation, where relevant, and ask which responsibilities the actual proposal includes. Identify the origin and reporting point at a useful planning level, the service windows and the responsible contact. Do not assume that a national manpower quotation includes every journey, residence arrangement or site transfer. The accepted commercial and employment arrangements need to explain those elements for the particular case.

Keep local reporting transport separate from travel between cities. A routine journey to one site differs from reassignment to another location, and the relevant responsibilities and candidate or worker communication may differ as well. Record the proposed change and its effect on the original requirement. The employer should review the applicable terms and official conditions through the responsible parties instead of treating geographic movement as an informal scheduling adjustment.

Avoid publishing unsupported accommodation standards, journey times, allowances or universal benefits as part of the service description. Obtain the actual agreed details and check any legal entitlement question against current official information for the case. The programme's practical job is to expose assumptions and secure decisions. A clear question about who provides an arrangement is more useful than a broad promise that everything will be handled without specifying what was included or accepted.

Compare commercial scope using the same units and exclusions

Ask for a written proposal against the accepted master requirement and site schedules. Identify the charging unit, contract period, quantities, supervision, resources and relevant responsibilities. Record local differences alongside the common terms. A monthly personnel amount, a recruitment engagement and a defined service-output price do not describe the same purchase. The employer needs to understand the model and inclusions before comparing amounts or combining them into a national budget.

List exclusions that could materially affect the operation. These may concern specialist tasks, additional windows, resource changes, travel or responsibilities retained by the employer. Ask how variations will be reviewed and who can accept them. A low headline amount can be misleading if it assumes a different duty boundary or receiving condition from the one the site actually needs. Discuss the specific proposed AL AHAD GROUP scope rather than relying on an unsupported claim about being the cheapest, largest or best provider.

This page gives no market rate, guaranteed mobilisation date or confirmed service commitment. Request a current proposal for the actual requirement. AL AHAD GROUP does not charge candidates recruitment, registration, interview, placement or processing fees. That policy does not establish that every government or independent third-party expense is waived. Check any legitimate external charge through its proper source and agreed process, and raise requests for unofficial payments through the approved contact route.

Walk through a three-site decision scenario

Consider an illustrative business preparing three different requirements: routine commercial-area coverage in Riyadh, warehouse assistance in Jeddah and a technical appointment for a Dammam operation. This is a fictional planning exercise, not a client case study or a statement of available services or jobs. The national owner has accepted the business purpose, but the Riyadh receiving contact still needs to confirm a window, the Jeddah area is not released and the Dammam employer has not completed its technical review.

The useful next action differs for each component. The Riyadh record needs the authorised receiving decision. The Jeddah record needs the area owner to explain the release condition and its scheduling effect. The Dammam record needs the competent reviewer to resolve the appointment evidence. Marking the whole programme waiting for manpower would obscure all three. Increasing the combined quantity would not resolve any of these issues, and accepting a national price would not complete the missing decisions.

Ask the programme owner which common assumptions remain valid while those actions are addressed. The business can improve the brief, reserve appropriate review capacity and clarify commercial questions without claiming that personnel may commence. When evidence arrives, update the affected site and examine shared dependencies rather than resetting every status automatically. The exercise demonstrates why a national programme needs a clear summary and separate decision records: the summary supports coordination, while the local evidence explains what actually needs to happen next.

Use site readiness evidence instead of a national ready label

Treat readiness as a collection of actual conditions rather than a single colour assigned to the programme. For each site, review the accepted scope, applicable official conditions, receiving arrangements and the authorised decision to proceed. A completed condition at one location does not complete it elsewhere. The readiness tool on this page helps organise the discussion, but its marked boxes do not certify a provider, approve a worker or authorise a service start.

Ask what evidence supports each finding and who can confirm it. An email received may contain a question rather than an acceptance. A resource ordered may not yet be available at the site. A reporting contact named may not have accepted the relevant window. Keep these distinctions visible in the actual programme record. If an essential condition is incomplete, identify its owner and effect before a final instruction is communicated.

Decide how readiness changes will be reported after an initial review. An area release, resource availability or proposed role can change before commencement. The programme should not continue displaying an old ready status when the conditions behind it no longer apply. Update the affected site and examine any shared dependency. A reliable national summary allows the business to see both the accepted components and the unresolved decisions without mistaking either for the whole programme.

Protect task instruction and workplace safety at every site

Use the receiving organisation's responsible safety process for the actual duties and work area. MHRSD's workplace safety guidance addresses precautions against work hazards and appropriate protection and instruction. A national induction document can provide common information while leaving important local conditions unresolved. Identify who gives the task-specific briefing, how personnel can seek clarification and which contact controls the work area. A record of attendance at a briefing is not by itself evidence that every relevant instruction was understood.

Distinguish recruitment screening, site induction and authorisation for particular tasks. An interview does not replace a safe work instruction, and an access badge does not approve every activity inside a facility. Where the proposed work involves technical systems, machinery, vehicles or restricted spaces, the competent parties should identify the required controls. Do not allow a staffing description to imply a technical permission that has not been reviewed for the actual assignment.

For environmental or seasonal conditions, use the current official and site requirements relevant to the date, location and duty. This guide does not set universal outdoor working hours or rely on an old seasonal notice as a complete plan. Record the accepted controls and any scheduling consequences through the appropriate owner. If a task cannot proceed within its accepted conditions, follow the safe reporting and decision process rather than changing duties or moving personnel informally to conceal the interruption.

Manage exceptions without distorting national performance

An exception record should identify the affected site, task or appointment, observed issue, operational effect and decision required. Separate an access delay from a resource shortfall, a changed requirement or an unassessed candidate condition. A national category such as manpower issue is too broad to direct an effective response. Keep the local evidence specific enough that the programme owner can identify the responsible action and decide whether another site is affected.

Do not make a combined attendance or completion percentage conceal a serious gap at one location. A strong result in one city does not correct an unresolved essential task elsewhere. Report individual site findings alongside any programme total and explain the units used. Distinguish approved baseline quantities from conditional demand when presenting progress. Otherwise a changing forecast can make performance appear better or worse without any corresponding change in the work actually accepted.

Close an exception through an evidenced decision, not merely because someone replied. Record whether the task resumed, an appointment condition was resolved, the scope changed or another instruction was accepted. Retain the next action for anything still open. A useful national review examines recurring causes and dependencies. It should improve the programme's actual task definitions and decision process rather than convert incomplete records into a general service-performance claim.

Control changes to quantities, duties and locations

Use a change record that connects the old requirement to the proposed revision. Identify the affected roles or tasks, locations, quantities, windows and responsibilities. Ask which reviews must be repeated before the change is accepted. A new technical duty can matter more than a small headcount adjustment, while moving an appointment between sites may affect terms, permissions and receiving arrangements. The programme should examine the substance of the change rather than its apparent size in a spreadsheet.

State who can authorise the commercial and operational consequences. A site supervisor's request may identify a real need without establishing approval for a contract variation. A national procurement instruction may need local confirmation that the workfront and resources can support it. Keep the accepted decision and its effective date available to the people who give and receive instructions. Avoid allowing different versions of the requirement to circulate simultaneously.

Communicate material changes to affected candidates, personnel and responsible organisations through the agreed process. Retain relevant previous versions privately so the decision history remains explainable. Do not describe an earlier assessment or acceptance as covering a new responsibility when that question was never examined. Controlled changes let the programme adapt while preserving a clear account of what is currently offered, what has been accepted and which conditions still need action.

Keep personal and commercial information proportionate

The first national enquiry should explain the business requirement and the authorised contact, not attach a complete workforce document archive. Later steps may need specific personal records through an approved private process. SDAIA's minimum-data guidance supports limiting collection to information necessary and relevant to the stated purpose. Apply that principle to programme trackers, interview schedules, access discussions and operating reports instead of assuming that every recipient needs the same full file.

Use site, task and candidate reference codes where full identities are unnecessary. Keep private supporting documents separate from the national summary and limit access to the people who need them for the decision. Do not circulate passports, medical records, bank details, portal passwords or verification codes in a general procurement message. Commercially sensitive site instructions and customer information should also follow the organisation's controlled sharing process rather than being copied into a public enquiry or unrestricted link.

Identify who can correct inaccurate information and who manages retention or disposal under the relevant process and applicable rules. This guide does not invent a universal retention deadline or legal basis for sharing. Its practical purpose is to keep the information proportionate to the review stage and decision. A concise, accurate record often makes coordination easier than a large shared archive in which the actual current requirement and outstanding action are difficult to find.

Review continuity, completion and the next requirement separately

Agree how the parties will respond to an absence, delayed resource or interrupted receiving condition under the actual proposal. Identify the notification route, affected tasks and acceptance requirements for any alternative arrangement. Do not infer an instant replacement guarantee or automatic permission to transfer people between cities. An alternative can require suitability, official or site checks, and the original site's coverage may also be affected. Keep those conditions visible while the responsible parties decide what can proceed.

At completion, reconcile each site's accepted tasks or appointments, open exceptions, resources and required handovers. A programme end date does not prove that every local item has been closed. Record what is accepted, what remains unresolved and who owns the next action. Where a further phase is proposed, distinguish it from the completed scope. Similar work in another location still needs its own accepted requirement and relevant readiness decisions.

Send AL AHAD GROUP the master purpose, separate city and site schedules, duties, quantities, proposed arrangement, desired sequence and unresolved dependencies. Ask for the offered scope and commercial assumptions to be explained in writing. Use local service guidance for detailed receiving questions and the national contact route for the wider programme. This creates a practical basis for reviewing a multi-city requirement while leaving availability, terms, permissions and commencement to the actual authorised decisions.

Frequently asked multi-city employer questions

Can one enquiry cover Riyadh, Jeddah and Dammam?

Yes, describe the national purpose while providing separate site schedules and decision owners. State the actual service or recruitment model for each component. One enquiry does not establish identical duties, local availability, branch locations or a confirmed start across all cities. The offered scope and relevant conditions still require review for the particular requirement.

Does a national manpower total mean everyone is interchangeable?

No. Keep role evidence, duty boundaries, employing arrangements, official conditions and receiving locations attached to the relevant positions or appointments. A combined figure supports planning only when its units and status are clear. Moving a person or resource to another site may require a separate suitability, terms and readiness discussion.

How should conditional demand be recorded?

Identify the affected line, the event it depends on and the person who can confirm it. Keep forecasts and budget allowances distinguishable from accepted quantities. When a condition changes, update the requirement and its status without presenting the earlier estimate as a confirmed staffing order or an authorised live vacancy.

Is the planning-hours result a legal roster or price?

No. It multiplies the positions, coverage window and operating days entered for each site and adds the results. It does not determine individual working hours, breaks, payroll, price, headcount availability or official eligibility. Review those matters separately through the actual employment or service arrangement and responsible parties.

What does a zero-position row mean in the tool?

It excludes that site from the current arithmetic illustration. It does not cancel a real requirement or show that an unresolved site is ready. Keep actual demand status in the programme record. At least one site needs a valid active line for a combined result, and incomplete assumptions should be resolved before relying on the illustration.

Can every site begin on the same target date?

Only the responsible parties can confirm the actual arrangements. Review common and local dependencies, selection or service decisions, applicable official conditions and receiving resources. A desired national date is a planning input. Keep proposed and confirmed starts distinguishable, and do not communicate one site's completed condition as approval for another location.

Does an interview clear the candidate for every technical duty?

No. Record what the appropriate reviewer actually examined and which responsibilities remain unassessed. A different system, role or site may need further evidence or authorisation. Recruitment screening, professional requirements, site induction and task permission serve different purposes and should remain distinguishable in the appointment and receiving record.

Does a commercial agreement prove Ajeer eligibility?

The authorised establishment representatives must review current official rules and the actual case requirements. A commercial label or signed amount does not establish eligibility for every establishment, worker, task or location. Keep official completion, service acceptance and site access separate before describing a proposed arrangement as ready to commence.

Who can change a site's duties or quantities?

Use the programme's agreed decision and variation process. A local request can identify a need while commercial or official consequences still require another authorised owner. Record the accepted revision, effective date and affected evidence. Make sure the people giving and receiving instructions use the same current requirement.

Are transport and accommodation automatically included?

Do not assume inclusion. Describe the expectation for each site and ask the actual proposal to identify its responsibilities, assumptions and exclusions. Separate local reporting transport from proposed travel or reassignment between cities. Any employment entitlement question should be checked against current official information for the particular case.

Does AL AHAD GROUP charge candidates recruitment fees?

AL AHAD GROUP does not charge candidates recruitment, registration, interview, placement or processing fees. This does not establish a blanket waiver of independent government or third-party expenses. Confirm legitimate external charges through their proper source and agreed process, and raise unofficial payment requests through the approved contact route.

Does a completed readiness checklist authorise deployment?

No. The checklist is a local preparation aid. It cannot certify a provider, approve a person, complete official requirements or accept a service on behalf of the responsible parties. Review the underlying evidence separately for each site and record the actual authorised conclusions before communicating a final instruction.

Should the first message include employee documents?

Begin with the business requirement and authorised contact details. Agree the necessary purpose and private process before sharing personal supporting records. Use references where identities are unnecessary, and keep sensitive documents away from general tender circulation. Never include official account passwords or verification codes in a recruitment or service enquiry.

What makes a national requirement easier to review?

Provide a clear master purpose, separate site references, role or task quantities, evidence criteria, operating assumptions, desired sequence and unresolved conditions. Identify the relevant decision-makers and proposed service model. This allows the responding team to explain its offered scope and next questions without guessing about duties, availability, commercial terms or permissions.