Operational Data & Sourcing Methodology
Standard operating procedures, definitions, and database integration mapping governing active sourcing metrics and job schemas.
1. Purpose & Scope
This document outlines the technical framework used by Mahad Manpower to ingest, process, verify, and display live recruitment demand data. Sourcing indicators, job details, and operational volumes displayed across this website (including our Live Demands Directory and Operational Metrics Dashboard) are compiled under this methodology.
2. Data Sources
All sourcing requirements originate directly from client-issued corporate demand letters. These are processed within our internal ERP system and integrated with external compliance registries:
- Internal ERP Platform: Registers the number of workers requested, trade details, contracted salaries, and deployment dates.
- Government Portals (Qiwa / MOHRE): Used strictly where documentation has been supplied to cross-verify client work permit validity and quota availability in KSA and UAE. Qiwa is utilized exclusively for corporate work permit and contract registration (not for candidate screening or skill certification).
- Partner Trade Vetting Centers: Candidate evaluations are conducted at authorized partner trade-test facilities in major sourcing regions, where applicable.
3. Metric Definitions & Database Mapping
To ensure alignment with first-party records, the tables below outline the calculation logic, data source pools, and validation rules applied. A consistent cutover date of 1 July 2026 is used across all metrics.
| Metric | Exact Calculation | Source View / Table | Inclusion / Exclusion | Frequency |
|---|---|---|---|---|
| Confirmed Historical Departures | Static baseline constant of 8,410. | Pre-cutover files. | Inc: Departures Jan 2022 to June 30, 2026. Exc: Post-cutover departures. | Static |
| Post-Cutover Verified Departures | Count of candidate rows marked 'DEPARTED' post-cutover. | public_reporting.site_metrics.total_mobilizations | Inc: Processed departures on/after July 1, 2026. Exc: Pending departures. | Hourly Sync |
| Total Confirmed Departures | Confirmed Historical Departures (8,410) + Post-Cutover Verified Departures | public_reporting.site_metrics.total_mobilizations | Inc: Cumulative verified physical mobilizations. Exc: Selected but unmobilized. | Hourly Sync |
| Screened Profiles | Historical screening baseline (98,820) + post-cutover candidate database profiles | public_reporting.site_metrics.verified_screened | Inc: Registered candidate files in database. Exc: Unstructured inquiries. | Hourly Sync |
| Employer Accounts | Unique corporate account records stored in the internal operations database after deduplication. | public_reporting.site_metrics.partner_count | Inc: Deduplicated employer records. Exc: Internal test accounts. | Hourly Sync |
| Total Sourcing Requirements | Number of distinct registered requirement/order records. | public_reporting.site_metrics.total_requirements | Inc: Checked client requirements/demands. Exc: Draft demands. | Hourly Sync |
| Active Campaigns | Count of distinct publicly eligible active demand_id values. | public_reporting.public_job_registry | Inc: ACTIVE/URGENT rows with review_required = false and a non-empty public slug. Exc: paused/review rows and rows without a public slug. | Hourly Sync |
| Current Openings | Sum of valid positive openings values across publicly eligible active rows. | public_reporting.public_job_registry | Inc: rows with openings > 0. Exc: missing, zero, negative, and guessed fallback quantities. | Hourly Sync |
Baseline constants are owner-confirmed internal operational records and are not described here as independently audited or government-verified totals.
4. Calculation Method & Data Flow
Our public data pipeline uses a strict one-way flow with sanitization boundaries:
5. Demand Verification Checklist
Every demand letter displayed on this site must pass three gates:
- Authenticity Audit: Check signature and embassy attestation documents where supplied.
- Quota Check: Confirm block visa registry details on respective platforms.
- SLA Alignment: Verify contracted terms align with local WPS minimums.
6. Job Lifecycle & States
| State | System Actions |
|---|---|
| Active (Public) | Search engine indexable, listed in sitemaps, renders one valid JobPosting schema. |
| Confidential | Suppresses JobPosting structured data, excluded from sitemap-jobs.xml, and carries noindex directives to prevent indexing of unannounced client projects. |
| Closed / Expired | Excluded from active listings and sitemaps, blocks candidate CV uploads, suppresses JobPosting schema, and queues URL deletion outbox events. |
7. Freshness & Cache Policy
Our live infrastructure utilizes a 10-minute Redis Last Known Good (LKG) snapshot TTL combined with real-time HMAC-signed webhook invalidation (via /api/dashboard-sync). When employer demands or operational metrics change in the dashboard, webhooks trigger instant cache tag invalidation. If database connectivity drops, public endpoints serve validated LKG snapshots stamped with generatedAt timestamps and freshness: "live" | "stale" indicators.
8. Privacy & Anonymization
Sourcing data does not disclose proprietary commercial agreements or candidate identity metrics. Employer brands are anonymized (e.g. Verified UAE contracting group) until publication-approved branding details are submitted.
9. Data Limitations
Active sourcing requirements represent slots allocated for recruitment but are subject to change based on project schedules, cancellation of visa quotas by GCC sponsors, or changes in embassy processing rates.
10. Corrections & Audits
If an error is identified in any published salary, location, or trade details, corrections can be requested. Registered corrections update the database view and propagate via cache tag invalidation within one hour.