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. Your documents can be in English; quotes keep the source wording.
التوجهات والمعايير (Directions & criteria) is the step where you fix the frame every option is built in and judged by, before anyone sees an option. It has three parts: the التوجهات (directions) leadership and the client's documents ask the new model to achieve, the قواعد التصميم (design rules) every option must respect, and the المعايير والأوزان (criteria and weights) options will be compared on. When the frame is ready, you lock it. The lock creates a numbered version that later steps build on.
Who can do what
| Action | Permission |
|---|---|
| Open the step and read the frame, its checks and its versions | View (operating_model.view) |
| Add, edit, turn off and remove directions; accept or reject proposals; edit rules and criteria; أبقِه رغم التنبيه (Keep anyway) | Act (operating_model.act) |
| اقترح توجهات من مستنداتك (Suggest directions from your documents) and افحص مقابل المدخلات (Check against your inputs) | Run AI actions (operating_model.ai.run) |
| قفل المعايير والأوزان (Lock criteria & weights) and فك القفل (Unlock) | Lock and unlock criteria (operating_model.frame.lock) |
Workspace Admin holds all four automatically, and Workforce Architect holds them by default. Every role that held Act before this release was given Run AI actions and Lock and unlock criteria too, so nobody gained or lost access. Without a permission, the button stays disabled and its tooltip names the missing permission, for example "Needs the Run AI actions permission". See Overview.
An archived project shows its directions and criteria read-only.
How the step is laid out
- The مبني على (Built from) button in the step header (a round icon next to Project settings, with a badge counting the documents). It opens a dialog listing the inputs this step reads: strategy and mandate documents, decrees, the ecosystem's "Do-not-take-back list" and the applied scope. Each row opens its source. Its يُستخدم في (Used in) section points ahead to Generate and Approve.
- Three side tabs, each with a status line and a done or warning mark:
- التوجهات (Directions): "N of M on".
- قواعد التصميم (Design rules): for example "Span 3–6 · 6 layers".
- المعايير والأوزان (Criteria & weights): "Total N/100".
- Each section has a check box for the AI check (see Check against your inputs).
- The lock bar, which lives in the step's pinned action bar at the bottom of the screen, so it stays in reach while you scroll: السابق: تجارب مماثلة (Previous: Similar experiences), the lock status ("Lock the criteria before generating options", the number of items not checked against the inputs and of unresolved conflicts) with افحص الآن (Check now), and the قفل المعايير والأوزان (Lock criteria & weights) button. Once the frame is locked, the bar shows the locked version with فك القفل (Unlock).
- The ما يقرؤه كل مستشار (What every consultant reads) button in the step header (a green dot once the criteria are locked) opens a dialog that sums up what later steps will read: the documents, the directions that are on, the rules, and whether the criteria are locked.
While any section needs attention, the step bar shows "Directions & criteria need attention" on this step, and Generate shows "Lock criteria & weights first" until the frame is locked. Once it is locked, التالي: التوليد (Next: Generate) appears in the action bar and leads on.
Directions
A direction is one sentence about what the new model must achieve, for example "Fully separate regulation from service provision". Each direction has:
- Text: one field. New directions are written in Arabic; text taken from an English document keeps the document's wording. There is no pair of fields and no translation. The text is shown as written, in its own reading direction, with a small tag: عربي (Arabic), إنجليزي (English) or مختلط (Mixed).
- أولوية (Priority), from 1 to 3 (default 2). Click the priority pips to change it. Priority 3 means the direction is a must: the check treats contradicting it as a conflict.
- المصدر (Source): the document chips and their quotes for a direction that came from your documents, or a free-text label for one you add yourself, such as "Minister's office" or "Expert panel". A direction you added shows أضفتها أنت (Added by you).
- On / off: a direction that is off stays on the list but leaves the frame. Consultants don't read it, options aren't checked against it, and it is not in the locked version.
Add and edit directions
أضف توجّهًا (Add a direction) opens Direction text (any language), the priority and المصدر (اختياري) (Source (optional)); press إضافة (Add). To edit a text, click عدّل النص (Edit the text): Enter saves, Esc cancels, Shift+Enter starts a new line.
You can turn off any direction, but حذف (Remove) is only for one you added yourself. A direction that came from your documents is turned off instead, so its source stays on record. حذف (Remove) asks you to confirm first, because a removed direction can't be brought back; you would have to add it again.
Each row shows a tag for what changed: New (you added it), Edited (you changed the wording the AI proposed) or أوقفته (Turned off). For an edited direction, استرجع النص الأصلي (Restore original text) puts the AI's wording back.
Suggest directions from your documents
اقترح توجهات من مستنداتك (Suggest directions from your documents) asks the AI to read every document in the project that has not been removed, documents of authority first (mandates, strategies, decrees, statutes), and to propose directions from them.
- Proposals are always written in Arabic, whatever language your documents are in; quotes stay in the document's own language.
- The priority comes from the document's wording: "must" or "shall" gives priority 3.
- The button shows a مدخلات جديدة (New inputs) badge when a document became ready since the last suggestion. It is disabled while a document is still being read.
- Running it again replaces the proposals still waiting for review. Directions you already accepted are not touched.
Proposals wait under مقترحة من مستنداتك (Proposed from your documents), grouped as Proposed from [document] (N). For each proposal you can:
- قبول (Accept) it as it is;
- تعديل ثم قبول (Edit then accept), then حفظ وقبول (Save and accept): it then shows معدّل (Edited), and استرجع النص الأصلي (Restore original text) brings back the AI's wording;
- رفض (Reject) it.
You can also tick several and use Accept selected (N) or Reject selected (N), or accept a whole group with Accept all verified (N).
A proposal is غير متحقق منه (Unverified) when none of its quotes is found word for word in the document, or when it has no quote at all. Unverified proposals are never accepted in bulk: open the source, then accept them one by one. They stay flagged after you accept them.
When a proposal says the same as a direction you already have, it shows "Matches your direction "…"; accepting adds its sources to it." If you edit such a proposal before you accept it, your edit is kept: it becomes a new direction of its own, and a message tells you so.
A proposal that matches a direction you rejected earlier never returns to the main queue. It waits under Previously rejected (N), where you can still accept it on its own.
Directions and the strategy card
When the project has a confirmed strategy card, suggested directions can cite its items. A direction that does shows a chip, "Serves N strategy items"; click it to see the cited items with their types (هدف objective, مستهدف target, and so on). The card's items are context, not quotes: the quotes still come from your documents.
If a confirmed objective is served by no confirmed function, the tab shows a notice: "N confirmed objectives in the strategy card that no confirmed function serves. This is a warning and does not block approval." It is a heads-up to review the card's links or the catalogue; it never blocks Lock.
Instructions for the AI
Next to اقترح توجهات من مستنداتك (Suggest directions from your documents) and in each check box, إضافة تعليمات (اختياري) (Add instructions, optional) lets you steer that run in your own words:
- For suggestions, say what to look for, for example "focus on digital transformation directions".
- For the check, name the focus areas, for example "focus on the ministry's regulatory role". The check still reports every point its rules require, even outside your focus.
An instruction applies to that run only, up to 2,000 characters. It never changes the form of the results or the rules, and instructions saved on documents (see Inputs) are respected too.
Design rules
Design rules are the guardrails every generated option stays within. The usual values for the project's entity kind are filled in when you first open the step (span and layers come from cited benchmarks, see below); each rule shows its الأساس (Basis). Once you change a value, the rule shows its القيمة المعتادة (Usual value) with أعده إلى (Reset to) that value.
| Rule | Usual value | Basis | What you can change |
|---|---|---|---|
| Span of control (direct reports per manager) | The cited benchmark for the entity kind; 3–6 when none is confirmed | The benchmark's population and its sources, shown under the rule. Without one: House rule, no published source sets it (McKinsey's archetypes are 3–5, 6–7 and 8–10) | Minimum from 2 up to the maximum; maximum from the minimum up to 12. A unit never has a single unit under it, whatever the band. Switch off, with a reason |
| Layer cap (from the top of the entity to the front line) | The cited benchmark for the entity kind (kept between 3 and 9); 6 when none is confirmed | The benchmark and its sources. Without one: APSC guidance, 5–7 layers | From 3 to 9. Switch off, with a reason |
| فصل التنظيم عن التشغيل (Separate regulation from delivery) | On | World Bank three-condition test | Ministries: إلزامي للوزارات (Required for ministries). Companies: أوقف الفصل (Turn separation off), with a written reason |
| قاعدة الحدود (Boundary rule) | On | Rejects any function another body owns by statute; fed by the ecosystem's "Do-not-take-back list" (the row shows its count and افتح المنظومة في المدخلات (Open the ecosystem in Inputs)) | Switch off, with a reason |
| دمج الوظائف المتشابهة (Group similar functions) | On | One reporting line per function family | Switch off, with a reason |
| تدرّج أنواع الوحدات (Unit kinds nest in order) | On | Deputyship or sector, then general administration, then administration, then unit or office (TVTC structure guide, 2022) | Switch off, with a reason |
| استقلال المراجعة الداخلية والأمن السيبراني (Independent internal audit and cybersecurity) | On | Internal audit reports directly to the head and holds nothing else (Council of Ministers Resolution 129, 1428H; IIA Global Internal Audit Standards 2024, 7.1). Cybersecurity is independent of IT (NCA ECC-2:2024, control 1-2-1). Applies to functions whose الدور الرقابي (Control role) is set in the function catalogue | Switch off, with a reason |
| تنبيهات جودة التصميم (Design quality warnings) | On | Warnings only: see below | Switch off, with a reason |
| الوحدات الإلزامية نظاماً (Units mandated by statute) | On | The Saudi reference: units a statute requires, such as internal audit. See Mandatory units | Switch off, with a reason |
| الحد الأعلى للقوى العاملة المنقولة (Maximum staff moved) | Not set | The change readiness questionnaire suggests it (see Inputs) | A percentage from 5% to 100%. ضع حداً (Set a limit) starts at 30%; أزل الحد (Remove the limit) clears it. Without Act permission the row reads بلا حد (No limit) |
Cited defaults for span and layers
For a new project, the span band and the layer cap start from the platform's cited benchmarks for the entity kind (for example the span of control of Saudi government bodies), not from a house number. Under each of the two rules the basis line names the benchmark's population, and source chips show where it comes from: hover or click a chip for the quote, the source site and the date the platform read it. Values are kept within the rule's limits (span 2 to 12, layers 3 to 9). When the platform has no confirmed benchmark for the rule, the house value is used and labelled as such.
- Older projects keep their values. A project that already had its rules is never re-seeded. It shows the benchmark it is pinned to as the source, even if its own values differ because you edited them or the project predates the benchmark.
- Each project stays on one version of the benchmarks. When the platform confirms a newer one, the span rule says "صدرت نسخة أحدث من المعايير المرجعية؛ يبقى المشروع على نسخته حتى تحدّثه." and حدّث المعايير المرجعية (Update the reference benchmarks) moves the project to it. Updating changes the source line and the chips; it does not rewrite the values you have, so use أعده إلى (Reset to) or the reset below to take the new numbers. An archived project can't be updated.
- Support-function ratios in Inputs read the same benchmarks.
Maximum staff moved
الحد الأعلى للقوى العاملة المنقولة (Maximum staff moved) caps the share of today's staff that a design may move to another unit, counted in FTE from the activity allocation. It is an optional rule: it exists only while a limit is set, and the change readiness questionnaire suggests one (15%, 30% or 50%). Edit the percentage with the stepper, or clear it with أزل الحد. When a limit is set, the frame lists it as an item, so a change to it counts as a change to the frame. See Generate for how it is checked.
Switching rules off
Every design rule has its own switch: span, layers, boundary, grouping, unit kinds, units mandated by statute, and each internal audit, cybersecurity, control-placement and design quality rule. Separation keeps its own switch (companies only). Turning a rule off asks "Why switch this rule off for this project?"; the reason is shown under the rule with عدّل السبب (Edit the reason), and the rule reads موقوفة (Off). أوقف كل القواعد (Switch all rules off) at the top of the section turns every rule off with one reason, and فعّل كل القواعد (Switch all rules on) turns them back on. The integrity checks (each function placed once, scope, locked units, a sound tree) can't be switched off.
Rules that are off are stored with the reasons in the locked frame version. The engine skips them when it checks alternatives generated or edited on that version, the consultants are told they don't apply, and Check against your inputs reviews the switched-off rules as one item (for a ministry it flags internal audit or cybersecurity rules switched off). Alternatives checked earlier keep their stored results.
Design quality warnings
These never block an option or trigger a repair. They show on the option's check list under جودة التصميم (Design quality):
- Duplicate units: two units with the same or look-alike names, such as "General Administration for Employee Affairs" and "Employee Affairs Administration".
- Thin units: a lowest-level unit that holds a single function.
- Scattered support: enabling and support functions spread over three or more top-level units, or a support unit inside a service-delivery sector. Top-level units grouped by geography (regional branches) are not counted: they may keep their own support teams.
- Central functions in a region: policy and strategy functions inside, or under, a unit grouped by geography. They are designed at headquarters; branches carry out what headquarters sets (MoH 2.0 workforce requirements, 2023).
- Functions without a mandate: when the project has a mandate, decree or statute document, functions whose sources include none of them.
- Mode mismatch: a unit whose declared mode (regulate, deliver, enable, support, lead) does not match the type of most of its functions.
- Regulator owns an operator: the entity owns, or chairs the board of, a body that delivers services in a domain one of its regulating units regulates (OECD principles on the governance of regulators, 2014).
- Control placement (for functions with a control role): risk or compliance inside a service-delivery line (IIA Three Lines Model, 2020); procurement and treasury/payments in the same unit (COSO segregation of duties); the personal data protection function inside, or under, the IT unit (Personal Data Protection Law and its Implementing Regulation).
To use the internal audit and cybersecurity rules, open Inputs → Function catalogue → Edit and set each function's الدور الرقابي (Control role): Internal audit, Cybersecurity, IT, Risk management, Compliance, Procurement, Treasury and payments, or Personal data protection. Functions without a control role are not checked by these rules. Tag cybersecurity governance and oversight as Cybersecurity, not day-to-day IT security operations, which may stay with IT.
What "house rule" means
A house rule is Jadiroon's own default, not an industry standard. The 3–6 span in particular has no published source, so while no cited benchmark is confirmed for the entity kind it is labelled "House rule" wherever it appears. Change it when the client or the entity's context calls for a different span.
Separation for companies
On a company project, أوقف الفصل (Turn separation off) asks "Why is separation off for this company?". The reason is kept with the frame, and عدّل السبب (Edit the reason) changes it later. A ministry can't turn separation off. If a company frame has separation off and you change the project's entity kind to ministry, the rule shows "Separation is off, and it is required for ministries; turn it back on before locking." with أعد تفعيل الفصل (Turn separation back on). You can still edit the other rules meanwhile, but not lock.
Criteria and weights
Criteria say what "better" means when options are compared. Each project starts from the المجموعة المعتادة (house set) for its entity kind:
| Ministry | Weight | Company | Weight |
|---|---|---|---|
| Alignment with the national strategy | 25 | Strategy alignment | 25 |
| Regulatory independence | 23 | Cost efficiency | 20 |
| Transition feasibility | 17 | Customer & market focus | 20 |
| Cost efficiency | 15 | Accountability clarity | 15 |
| Accountability clarity | 11 | Transition feasibility | 10 |
| Agility | 9 | Agility | 10 |
The company set is a house proposal that an expert will confirm before the first company client.
- الأوزان (Weights): one slider per criterion, from 0 to 50. The total shows how far it is from 100 ("N short" or "N over"); the total must be exactly 100 to lock. A moved criterion shows معدّل (Changed) and its old weight ("was N").
- طريقة التقييم (How it is scored): يقيّمه المستشارون مع الاستشهاد بالمصادر (Scored by consultants with citations), or يقيسه النظام (Measured by the engine) with a metric: span of control, number of layers, number of units, cost or transition disruption. A measured criterion needs a metric before you can lock. Nothing is scored in this step; the scoring is used when options are compared. When the project has a strategy card, the strategy alignment criterion is scored against the card's objectives: the score names which objectives the design serves and which it leaves without a unit.
- أضف معياراً (Add a criterion) gives a جديد (New) criterion whose weight starts at 0; move its slider after adding it. You can edit names and descriptions, and remove criteria. Removing one you added yourself asks you to confirm, since أعد إلى مجموعة البداية (Reset to the starting set) won't bring it back.
- أعد إلى مجموعة البداية (Reset to the starting set) puts the criteria and weights back to what the project started with.
When the entity kind changes
If you change the project's entity kind, the tab says "The entity kind changed to [kind]" and offers two choices:
- Reset criteria and rules to the [kind] house set: after you confirm, the criteria, their weights and the rule values are replaced, and this set becomes the new starting point. The span and layer values are the cited defaults for the new kind (the same ones a new project gets), and the maximum staff moved limit is cleared. Criteria you added are removed; no direction is touched.
- أبقِ المجموعة الحالية (Keep the current set): nothing changes, and nothing is marked as changed. The span and layer values stay as they were seeded (for example a ministry's benchmark on a project that is now a company), while the basis line and chips under the rules follow the new entity kind and may describe a different benchmark than the values you hold. Reset to adopt the new kind's cited values.
Check against your inputs
افحص مقابل المدخلات (Check against your inputs) asks the AI to read your frame against the project's evidence: the documents, the function catalogue, the ecosystem and its "Do-not-take-back list", the current state and the applied scope. It reports each point with its sources. It never edits your frame.
What is checked, and when
The button is in every section, and one check covers all three sections. Pending slider or stepper changes are saved first.
- The first check reads the whole frame: every direction, accepted AI proposals included, every rule and the weights.
- After your inputs change (a new document read, an edit to the catalogue, the ecosystem or the current state, a new scope), every item is unchecked again: "Your inputs changed since the last check, so the whole frame is checked again."
- Otherwise a check reads only what is new or changed since it was last checked: an accepted proposal, an edited text, a turned-off direction, a new priority, a moved rule or weight. The check box tells you how many: "You changed N items here that have not been checked", and how many more in the other sections.
Items that are not being checked are still given to the AI as context. You can keep editing while a check runs; what you change in the meantime stays لم يُفحص (Not checked) for the next one. If the AI doesn't answer for one of the items it was given, that item stays لم يُفحص (Not checked) too: it is never assumed to fit, and the next check sends it again. A locked frame can't be checked: "Criteria & weights are locked; unlock to check again."
A progress strip follows the check: Mandate & strategy · Decrees & resolutions · Function catalogue · Ecosystem · Current state & scope · Other directions & rules.
When the AI service is offline
If the AI service is down, the check box and the proposals area each show one line: "AI service is offline; everything else works." افحص مقابل المدخلات (Check against your inputs) and اقترح توجهات من مستنداتك (Suggest directions from your documents) are disabled until it is back. Editing, accepting proposals you already have, and locking still work. A check or a suggestion that was already running doesn't spin: it reads Waiting for the AI service until the service is back.
What the check looks for
For example: regulation and service delivery put back together; a remit another body holds by statute brought back; a number in a direction above the span or layer rules, or against another direction; branches delivering services where a decree says they supervise; edits to text that came from a document (the original quote is shown); turning off a sourced direction; near-duplicate directions; weights that undercut a priority-3 direction or let one criterion dominate (over 40); and a direction whose change lies entirely in units outside the applied scope.
Reading the results
The results start with a summary, such as "What is here is consistent with your inputs" or "What is here contradicts the inputs in N places", and "Last checked [time]". Each item shows a pill:
| Pill | Meaning |
|---|---|
| لم يُفحص (Not checked) | New or changed since the last check, or never checked |
| متوافق (Fits) | The check found nothing against it |
| للانتباه (Watch) | A point to review, worth knowing before you lock |
| تعارض (Conflicts) | It contradicts a priority-3 direction, a decree or a statute |
| أبقيته رغم التنبيه (Kept anyway) | Every Watch and Conflict finding of its latest check was kept with أبقِه رغم التنبيه (Keep anyway) |
Each finding carries source chips: a document chip opens the passage in the المصدر (Source) panel; others jump to the direction, rule or criterion involved.
- A finding that quotes the documents is غير متحقق منه (Unverified) when none of its quotes is found word for word.
- A finding can also rest only on another part of the frame (another direction, a rule, a criterion). It then points to that item instead of quoting a document, and needs no quote. A finding with neither a quote nor such a reference is Unverified.
- An unverified finding still counts at its severity: an unverified conflict is still a conflict, in the pill, on the lock bar and in the version.
Fixes and Keep anyway
A finding can offer a fix button: تعديل (Edit), استرجع النص الأصلي (Restore original text), أعد تفعيله (Turn back on), Remove direction (only for one you added), أعده إلى (Reset to) the rule's usual value, أعد تفعيل الفصل (Turn separation back on), or أعد الأوزان إلى مجموعة البداية (Reset weights to the starting set). A fix changes the value, so the item becomes لم يُفحص (Not checked) again, unless that value was already checked (at the current inputs). حذف التوجّه (Remove direction) asks you to confirm first, like حذف (Remove) on the row.
أبقِه رغم التنبيه (Keep anyway) keeps a finding as it is, in one click, with no reason needed. The item then shows أبقيته رغم التنبيه (Kept anyway). It is recorded in the audit log and in the summary of the version you lock. It applies to that finding of that check only: a newer check of the item starts clean, and a finding like one you kept before shows "You kept this in the previous check" with أبقِه مجدداً (Keep again). This also holds after your inputs change and the whole frame is checked again: what you kept in a check before the change is offered again with أبقِه مجدداً (Keep again).
The check never blocks
"The check never blocks locking; its result is recorded with the version." You can lock with items not checked and with unresolved conflicts. The lock bar lists them with افحص الآن (Check now), and the locked version records them.
Lock and versions
قفل المعايير والأوزان (Lock criteria & weights) needs:
- at least one confirmed direction that is on;
- weights totalling exactly 100;
- a metric for every measured criterion;
- a span minimum no higher than the maximum;
- separation on, unless the project is a company and the reason is written.
Directions still waiting for review don't block the lock; they are not part of the frame. While a check is running, قفل المعايير والأوزان (Lock criteria & weights) is disabled ("A check is running now."): wait for its results, then lock. When the lock can't happen yet, the bar says "It can't be locked yet:" and lists the reasons. Pending slider or stepper changes are saved before the lock.
Locking creates version N: a snapshot of the directions that are on (text, priority and quotes), the rules and the criteria with their weights, together with the check status of every item (fits, watch, conflict, kept anyway or not checked) and, when there is one, the strategy card as confirmed at that moment. The card is frozen with the version: later changes to the card don't alter a locked version, and consultants and the critic read the frozen card. The bar then reads "Criteria & weights locked", "Version N · by [name] · [time] · they will not change during the comparison".
While the frame is locked:
- every edit is disabled: directions, rules, criteria, Keep anyway and accepting proposals ("Criteria & weights are locked; unlock to edit.");
- افحص مقابل المدخلات (Check against your inputs) is disabled;
- اقترح توجهات من مستنداتك (Suggest directions from your documents) still works, but its proposals can be accepted only after you unlock.
If your inputs change after you lock, the step says "Inputs changed after you locked; unlock to re-check." It is a notice only.
فك القفل (Unlock) asks "Unlock the criteria and weights?". Editing is allowed again; version N stays readable and nothing built on it is deleted. Locking again creates version N+1. Later steps will show which version work was built on, and generating options will need a locked frame.
Where your data goes
- Suggesting directions sends the text passages of your documents, your confirmed directions, the catalogue's pillars and the ecosystem to the AI model configured for the studio. A check also sends the frame, the catalogue, the current state and the scope. Each run counts toward the project's monthly AI usage limit. See AI transparency.
- Everything is recorded in the Audit log: starting a suggestion or a check is marked as an AI action; accepting a proposal, every edit, Keep anyway, lock and unlock are recorded as your actions.