Skip to main content
Mahad Manpower and Taj HR Services are Krewex workforce brands. Overseas recruitment processing is legally handled through Taj HR Services, MEA-registered Recruiting Agent Licence B-3252/DEL/PER/1000+/5/11251/2025.   ✦   Mahad Manpower and Taj HR Services are Krewex workforce brands. Overseas recruitment processing is legally handled through Taj HR Services, MEA-registered Recruiting Agent Licence B-3252/DEL/PER/1000+/5/11251/2025.   ✦   
Compliance & Verification

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 **July 1, 2026** is used across all metrics.

MetricExact CalculationSource View / TableInclusion / ExclusionFrequency
Confirmed Historical DeparturesStatic baseline constant of 8,410.Pre-cutover files.Inc: Departures Jan 2022 to June 30, 2026. Exc: Post-cutover departures.Static
Post-Cutover Verified DeparturesCount of candidate rows marked 'DEPARTED' post-cutover.public_reporting.site_metrics.total_mobilizationsInc: Processed departures on/after July 1, 2026. Exc: Pending departures.Hourly Sync
Total Confirmed DeparturesConfirmed Historical Departures (8,410) + Post-Cutover Verified Departurespublic_reporting.site_metrics.total_mobilizationsInc: Cumulative verified physical mobilizations. Exc: Selected but unmobilized.Hourly Sync
Screened ProfilesHistorical screening baseline (98,820) + post-cutover candidate database profilespublic_reporting.site_metrics.verified_screenedInc: Registered candidate files in database. Exc: Unstructured inquiries.Hourly Sync
Employer AccountsUnique corporate account records stored in the internal operations database after deduplication.public_reporting.site_metrics.partner_countInc: Deduplicated employer records. Exc: Internal test accounts.Hourly Sync
Total Sourcing RequirementsNumber of distinct registered requirement/order records.public_reporting.site_metrics.total_requirementsInc: Checked client requirements/demands. Exc: Draft demands.Hourly Sync
Active CampaignsCount of registered active requirements in database.public_reporting.site_metrics.active_demands_countInc: Requirements with state = 'ACTIVE'. Exc: CLOSED or EXPIRED demands.Hourly Sync
Current OpeningsSum of remaining worker positions across active requirements.public_reporting.site_metrics.current_openingsInc: Unfilled allocation slots. Exc: Filled allocations, closed campaigns.Hourly Sync

4. Calculation Method & Data Flow

Our public data pipeline uses a strict one-way flow with sanitization boundaries:

1. Internal Dashboard (Primary business logic / database)
2. Restricted public_reporting views (SELECT-only reporting schema)
3. Sanitized Server-Side Loader (Website reads mapping values)
4. Cached Public Pages (Static page pre-rendering)
5. Webhook Revalidation (Tags cleared on update)

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

StateSystem Actions
Active (Public)Search engine indexable, listed in sitemaps, renders one valid JobPosting schema.
ConfidentialCrawlable for general search, but suppresses all JobPosting structured data. Excluded from sitemap-jobs.xml.
Closed / ExpiredExcluded from sitemaps, blocks candidate CV uploads, suppresses JobPosting schema.

7. Freshness & Cache Policy

We employ Incremental Static Regeneration (ISR) with a revalidation window of 3,600 seconds (1 hour). When changes are committed inside the dashboard, a webhook revalidates the cache tag, pushing the fresh dataset live.

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.