Workforce requirements

For HR administrators

The studio runs in Arabic. Screen labels are shown below in Arabic, with an English gloss in brackets, so you can find them on screen. Library names, seat titles and anything you type are shown as written.

متطلبات القوى العاملة (Workforce requirements) is the last step of a project. It turns the approved structure into the numbers you budget and hire against: how many people each unit needs, how many of today's staff land there, the gap and the surplus, how the gap is closed, and draft seats in Hire. The step shows up once you approve an alternative in Approve, and it starts by itself.

The AI never produces a headcount. Every number comes from a formula in code over a parameter whose source is always shown. The AI only does two things: it matches the sizing library's functions (the rows) to the units of the approved structure, and it proposes values for parameters it can back with a quote from your documents. Any value it cannot back is labelled as an assumption.

Who can do what

ActionPermission
Open the step, read every section, open past plansView (operating_model.view)
Edit the plan and save, refresh from current inputs, refresh from the libraryAct (operating_model.act)
ابدأ الربط (Start mapping), أعد المحاولة (Try again), أعد الربط (Map again)Run AI actions (operating_model.ai.run)
أرسل … إلى التوظيف (Send … to Hire)Act, and Open / close hiring (recruitment.hiring.open) in the Recruitment module

Without a permission the control is disabled and its tooltip says which one is missing (for example «تحتاج صلاحية فتح الشواغر في التوظيف»). In an archived project the plan is read-only.

How the plan starts

Approving an alternative starts the plan, once, with no extra click. The approval dialog says so and shows the time estimate for the run (or «التقدير غير متاح» if the AI service is offline; approval is never blocked). While it runs the step shows نربط مكتبة التحجيم بوحدات الهيكل المعتمد (We are mapping the sizing library to the units of the approved structure) and live progress lines: mapping, checking the result against your units, functions and parameters, correcting what the check found (one pass at most), and finishing.

  • The run counts toward the project's monthly AI usage limit and is recorded in the Audit log as an AI action by the person who approved.
  • If it fails, the step says تعذّر ربط القوى العاملة (Workforce mapping failed) with the reason, and أعد المحاولة starts the same plan again. If the AI service was offline at approval, the plan starts as failed, and أعد المحاولة starts it once the service is back. In the rare case that no plan exists yet, the step offers ابدأ الربط (Start mapping).
  • Reopening the decision cancels a running mapping and marks the plan سُحبت (Withdrawn). It stays readable, see Past plans.

What the plan is based on

When the plan starts it freezes its basis: the approved structure's units, the in-scope current units with their headcount, their functions, and which current unit each new unit continues. The numbers keep reading this frozen basis, so a later change to your inputs never moves a number by surprise. The step shows المدخلات بتاريخ … (Inputs as of …) next to the revision.

If your inputs change after approval, the banner تغيّرت المدخلات بعد الاعتماد (Inputs changed since approval) appears. حدّث من المدخلات الحالية (Refresh from current inputs) re-reads the current units, their headcount and their functions. The approved structure does not change, and mapping entries for functions that no longer exist are dropped (the step tells you how many). It needs Act and uses no AI.

The plan also holds its own copy of the sizing library for your entity kind. When the library changes afterwards, حُدّثت مكتبة التحجيم بعد إنشاء هذه الخطة (The sizing library was updated after this plan was created) appears, and حدّث من المكتبة (Refresh from library) takes the new default values for parameters that neither you nor the AI changed. The mapping stays as it is, and new library rows arrive unassigned.

For a company project, while the library has fewer than 15 rows, the banner مكتبة الشركات ما زالت محدودة (The company library is still thin) says what is covered (support services). What the library does not cover, the AI adds as custom rows with default values; replace them with client data.

The summary bar

At the top of a ready plan:

TileMeaning
المطلوب (Required)Total headcount the structure needs, with the difference from today
مغطّى بموظفي اليوم (Covered by today's staff)How much of the requirement today's staff cover, and the share
الفجوة (Gap)What is missing, split into internal and external
تعيين خارجي (External hires)The part closed by hiring, with the number of first-of-kind senior hires through the international channel
الرواتب السنوية (Annual payroll)Required × cost per employee, with the difference from today
افتراضات تحتاج بيانات العميل (Assumptions that need client data)Parameters without a source and custom rows

Two reconciliation lines are always computed and shown, and a mismatch would be shown as an engine error, never hidden: covered + gap = required, and covered + surplus + transferred out = today's staff. Under the bar, ملاحظات على الخطة (Notes on the plan) lists what needs a look: a unit with no rows («لم تُحجَّم بعد», not sized yet, so everyone reaching it counts as surplus), library rows no unit holds, a row held by two units (the first takes it), a function that does not reach a unit, a unit with no headcount (counted as zero), and ratios that do not converge. Orphan rows and unsized units have a select to assign them in place.

If the required number changed since your last visit, a notice shows the old and new figure.

The five sections

الافتراضات والطرق (Assumptions and methods)

Six sliders, each with its range and a live effect against the house value, so you can see what an assumption is worth before you save it:

AssumptionHouse value
ساعات العمل اليومية (Daily working hours)8
نسبة الوقت المنتج (Productive time share)80%. The tile notes that it is not yet checked against Ministry of Human Resources norms
أيام العمل في السنة (Working days a year)210
حصة المنشآت عالية المخاطر (High-risk share of establishments)44%, used only by the risk-based inspection model
الشكاوى المحلولة قبل التصعيد (Complaints resolved before escalation)65%
التكلفة السنوية للموظف (Annual cost per employee)SAR 360,000

You also choose the inspection model (حسب المخاطر risk-based or سنوي لكل المنشآت annual for all establishments) and the half-year the first hiring wave starts. The capability floor (70%) is fixed. A value you set is tagged حدّدته أنت (Set by you); the rest are افتراض داخلي (House assumption).

Four cards show the sizing methods and how much each contributes:

MethodWhat it does
تقدير الخبراء (Expert estimate)A fixed number of staff for the function
عبء العمل (Workload)Annual volume × hours per transaction ÷ productive hours per employee. Complaints and inspection have their own variants
نسبة معيارية (Standard ratio)A number per 1,000 of the rest of the workforce, for support services. Solved iteratively; the card shows how many rounds it took, and flags a ratio that does not converge
كما هو (As is)The function stays at the size of the staff that reach it today. When the project has an activity allocation, each unit's headcount is split across its functions by that allocation, rescaled to the unit's headcount; otherwise it is split evenly across the functions it holds

Each unit also gets one leader, a house assumption (قائد لكل وحدة): the unit, its level-2 units and every current unit it carries.

المتطلبات حسب الوحدة (Requirements by unit)

A bar shows how the requirement splits by method. Below it, every unit of the approved structure opens to its rows: method, driver, required headcount, source, today's staff, and the gap. Hover a number to see its formula. Units the design left untouched show خارج النطاق (Out of scope), greyed, and are left out of every number.

Every parameter carries a source chip:

ChipMeaning
افتراض داخلي (House assumption)The library default. Replace it with client data when you have it
مرجع المكتبة (Library reference)The library value, backed by a reference
مستشهد به (Cited)The AI took it from your documents; click to open the passage
افتراض — يُستبدل ببيانات العميل (Assumption, replace with client data)The AI proposed it without a source in your documents
أدخلتها أنت (Entered by you)You set it, with an optional note
موظفو اليوم (Today's staff)An as-is row, sized at today's staff

Other flags: جديدة (New, a function nobody performs today), مخصص (Custom, not in the library), a factor such as × 1.3, and جاهزية أقل من الحد الأدنى (Capability below the floor).

When two library rows cover the same function in one unit, the first row takes the whole share of that function's staff; the second sees none of them. A hint on the second row says so.

تعديل (Edit) opens the row editor, where you can:

  • change the functions a row covers (only functions that reach that unit);
  • set a factor (above 0, at most 10) with a mandatory reason;
  • override a parameter, with an optional note, or reset it to the library value (up to 100,000 staff, a volume of 10,000,000 a year, 1,000 hours per item, and 1,000 per 1,000);
  • move the row to another unit, or mark it غير منطبق على هذا المشروع (Not applicable) with a reason, and bring it back later from صفوف غير منطبقة;
  • add a custom row (أضف صفاً مخصصاً) with its method, driver, seat title and parameters, and remove it again.

التسكين (Placement)

Who covers the requirement from today's staff. Each unit's headcount is split across its functions by the activity allocation when there is one, or evenly when there is none, and each share follows its function to the unit it moves to, and each unit is rounded to whole people. With an allocation, the people a function has in other units move with that function. A unit's unallocated time follows the box that carries the unit; if no box carries it, it is spread over the unit's own functions in proportion to their allocated time (evenly, if it has none). The cards group rows into الفئة I (today's staff fully cover it), الفئة II (done today but needs reinforcement) and الفئة III (new functions nobody performs today). The table shows, per unit, required, covered, gap, surplus, categories and capability (جاهز ready or للتأهيل to upskill, using the library's capability percentage). The reconciliation lines appear again here: staff transferred with their functions to other bodies in the ecosystem, and staff on discontinued functions (counted in the surplus).

مصادر التغطية (Sourcing)

How the gap closes, in this order: إعادة توزيع (redeploy the surplus), تأهيل (upskill), then تعيين خارجي (external hire). Only the surplus of the same unit feeds redeploy and upskill. How much of the surplus can be redeployed or upskilled is judged by skills where the project has them (see Skill-based shares). The section shows the split across the hiring channels (التوظيف الحكومي government hiring, جهات التوظيف agencies, الاستقطاب الدولي international recruitment) and three موجات التنفيذ (implementation waves), each a half-year, starting from the half-year you chose.

Skill-based shares

When the project has an activity allocation from the Organizational Structure, the split of a unit's surplus into redeploy and upskill comes from the skills of the people who are there, not from a house percentage:

  • The skills a function needs are the skills of the job descriptions of the tasks mapped to it (all skills of those job descriptions together).
  • The pool is every filled position in scope whose job description is not one of the function's own job descriptions (not only the unit's surplus positions). For each of them, the share of those needed skills its job description already covers is its overlap. At 60% or more its people are counted as redeployable; from 30% up to 60% as upskill; below 30% they are not drawn on.
  • The shares are weighted by how many people fill each position, and they replace the library's house shares for that row. They are then applied to the unit's surplus.

Each gap row shows which basis it used, in an info tip next to it: مبني على مهارات الموظفين الحاليين (Based on current employees' skills) or افتراض داخلي (House assumption). A row falls back to the house shares when there is no skills data to read: no function needs skills yet (no tasks mapped to it), no filled position outside the function's job descriptions carries skills, the function is new, the row is a leader row, or the current state came from Excel (which has no seats or job descriptions). Everything else about the plan is unchanged, and the figures are frozen with the plan's basis. The skills are copied onto the positions when the current state is imported, and حدّث من المدخلات الحالية (Refresh from current inputs) only re-reads that copy. After you change skills, first import the current state again in Inputs, then refresh the plan.

Nitaqat hiring flag

For a company project with a Nitaqat baseline, a warning line تنبيه نطاقات (Nitaqat alert) appears under the plan's issues when the external hiring the plan asks for could push an activity out of its Nitaqat band. Click it to see each activity: its band now, the band it could fall to, and the least number of Saudis among the new hires that keeps it in the band.

  • The baseline is the workspace's Saudi and total headcount for each Nitaqat activity, copied when the current state is imported, and taken into the plan when it starts. حدّث من المدخلات الحالية (Refresh from current inputs) only re-reads that copy: to pick up new Nitaqat counts or activities, import the current state again in Inputs first, then refresh the plan. Positions are tied to an activity through their Nitaqat activity; units with no activity are left out. A ministry project has no Nitaqat flag.
  • The worst case. The flag assumes every external hire is non-Saudi, and asks how many of them would need to be Saudi for the activity to stay in its band. A hire is counted in the activity that has the most filled seats in the units it comes from.
  • The assumption is conservative. The surplus that is redeployed and the staff who transfer out of a unit are not subtracted from the headcount, so the flag can overstate a drop for an activity whose staff leave; it never hides one.
  • When even all-Saudi hiring cannot hold the band. If the hiring grows the establishment so much that the Nitaqat bar rises above what an all-Saudi intake would reach, the line says حتى لو كان جميع المعيَّنين سعوديين (even if all those hired are Saudi). This is counted as a drop too.
  • A note under the detail says the figures come from the company's Nitaqat baseline, not from data about people. The decision report's workforce annex carries a short line with the number of activities that could drop.

The flag is a warning for planning the recruitment mix; it does not change the plan's numbers or block a requisition.

طلبات التوظيف ← التوظيف (Requisitions to Hire)

See Sending requisitions to Hire.

Editing the plan

You change the plan in the browser and the numbers recompute live with the same engine the server uses. A bar shows N تعديلات غير محفوظة (N unsaved edits); احفظ (Save) writes them and adds one to the plan's المراجعة (revision), تراجع (Discard) drops them. A save carries at most 200 edits. If someone else saved first, you are told, the plan reloads and your unsaved edits are dropped. Edits are recorded in the Audit log. Leaving the page with unsaved edits asks you first.

This is the last step, so its pinned action bar at the bottom of the screen holds only السابق: النموذج المعتمد (Previous: Approved). The bar is hidden while the unsaved-edits bar is shown.

Map again

أعد الربط (Map again, needs Run AI actions) asks the AI to map the library to your units from scratch. The dialog warns that the new mapping replaces all your manual edits to rows, functions and parameters; your assumptions stay. If seats were already sent to Hire, the dialog lists them: they stay in Hire as they are, and one that matches a new requisition is flagged موجود في التوظيف (Already in Hire).

While it runs, the current numbers stay visible, read-only. The plan's revision goes up when the new result lands, not when Map again starts. If it fails, the previous mapping stays and the step shows the failure.

Instructions for the mapping

أعد المحاولة (Try again) and أعد الربط (Map again) both offer إضافة تعليمات (اختياري) (Add instructions, optional), for example "keep support functions lean and centralised". The instruction steers that run only, up to 2,000 characters. The mapping is still checked by the same rules: every library row is placed or marked not applicable, and out-of-scope boxes are never used.

Sending requisitions to Hire

For every gap that needs external hiring, the step lists a requisition: number (REQ-yy-nnn), seat title (المسمى), unit, count, channel, priority (the wave), placement, job description, and status. Filter by priority, select the visible ones, or pick rows one by one.

  • التسكين (Placement): the seat is placed in an organizational unit only when its unit is the unchanged or renamed successor of exactly one current unit of your workspace. Otherwise it reads غير مُسكّن (Unplaced). The studio does not change your Organizational Structure: its output is the approved design and its report, so seats for new, merged, split or moved units stay unplaced until your team builds those units in the Organizational Structure.
  • الوصف الوظيفي (Job description) is optional. The picker offers only your workspace's completed, non-archived job descriptions that have a sub-sector and a family. Nothing is created for you.
  • A requisition already in Hire from this plan or an earlier one, for the same unit and the same library row, is flagged موجود في التوظيف and unselected by default.

أرسل N إلى التوظيف (Send N to Hire) creates, for each selected requisition, one seat in Hire. The seat is an authorised, closed placeholder seat: it exists in Hire with the requisition's title and capacity equal to its count, but no one is hiring against it yet. Until recruitment completes or archives it, the seat counts toward workload capacity and the Nitaqat board. The hiring team opens and runs it from Hire.

Each requisition shows a status:

StatusMeaning
لم يُرسل (Not sent)Not in Hire yet
في التوظيف (In Hire)The seat exists and matches the current requisition (the status links to it)
تغيّر بعد الإرسال (Changed since sent)Count, title or channel changed. Send again to update the seat
قيد التوظيف — عدّله في التوظيف (In hiring, change it in Hire)Someone worked on the seat in Hire. Sending again will not touch it
لم يعد مطلوباً (No longer needed)A recompute removed the requirement. The seat stays in Hire, untouched
حُذف في التوظيف (Deleted in Hire)Someone deleted the seat. Sending again recreates it once

Sending again updates a seat only if nobody worked on it in Hire: still closed and not archived, title, capacity, job description and placement unchanged since the send, and no pipeline, interview rubric, agency submission, supplier contract position, invitation, referral or employee linked to it. Otherwise it stays as it is and the row says قيد التوظيف. A seat is never deleted or reduced to zero from here.

If Hire refuses some requisitions (for example a count above 100,000), the others are still sent and the message says how many were not sent.

You need Act and Open / close hiring. The send is recorded in the Audit log, and each seat has Hire's own audit entry.

Past plans

Reopening the decision withdraws its plan: from that moment no edit or send is accepted on it, even if the withdrawal itself was delayed. خطط القوى العاملة السابقة (Past workforce plans) lists them: the alternative and version, when it was approved and withdrawn, the required headcount and the seats sent. اعرض (View) opens one read-only, with its sent seats. Seats from a withdrawn plan stay in Hire as they are. Approving again starts a new plan.

The approved structure and the PDF

The النموذج المعتمد (Approved) step shows a workforce card with the status and the four main numbers, and the approved alternative's pane in the البدائل (Alternatives) step gains a read-only Workforce tab by unit. The decision PDF gains a workforce annex for a ready plan (also while it is being mapped again, from its last mapping), and for a withdrawn one marked «سُحبت». If the annex cannot be produced, the PDF comes without it. It is headed with the plan's revision, its date and the date of the inputs, and holds the totals, the notes, the assumptions line, the per-unit table, the waves and the requisitions with their Hire status. Because the plan stays editable after approval, the annex shows the plan's current revision; the rest of the PDF stays frozen from the decision.

For the Jadiroon team: the sizing library

The platform Console has a Sizing library tab beside the house register under Operating model library (permission om_library: view to read, act to edit). It holds the library rows per entity kind (ministry, company): name, category, method, parameters, the basis text, whether the value is a house assumption or sourced (a source is then required), capability, redeploy and upskill shares, channel, senior share, wave, seat title and whether it is a new function. Rows are never deleted, only archived. Each save raises the row's revision. A row's key cannot change once created. Edits never change an existing plan; plans see them through Refresh from library.

Where your data goes

  • The mapping run sends the structure's units and functions, the sizing library and the evidence chunks your project may cite to the AI model. Numbers are computed in code, never by the model.
  • Starting, finishing or failing the run, every saved edit, a refresh, a remap, a withdrawal and every send to Hire are recorded in the Audit log.
  • Seats sent to Hire go through Hire's normal audit and integration events.