Hisham Alhussain
All work

Case study

ESRA: Environmental & Social Responsibility Application

The application NEOM's contractors use to submit their monthly environmental sheets, feeding validated data straight into compliance dashboards.

For
NEOM
My role
Lead architect (40%) & hands-on builder (60%)
Stack
Online forms, Data pipelines, Data quality, KPI modeling

Problem

Monthly compliance reporting depended on contractor spreadsheets, manual Excel consolidation and reconciliation, risking missed deadlines and inconsistent numbers in leadership meetings.

What I built

Contractors submit monthly sheets through online forms into structured data objects, a standardized KPI model, validation pipelines and executive dashboards.

Outcome

Compliance reporting went from ~4 weeks to ~1 hour and became the standard procedure for all 800 contractors.

monthly compliance reporting
4 wks → 1 hrmonthly compliance reporting
contractors on the standard procedure
800contractors on the standard procedure
less analyst effort
~90%less analyst effort
adopted by other sectors
Templateadopted by other sectors

Architecture

  1. 01Contractor submissionsMonthly sheets via online forms
  2. 02Structured objectsWaste & environmental data
  3. 03Standard KPI modelOne definition per metric
  4. 04Validation pipelinesChecks before anything is published
  5. 05Executive dashboardsSingle source of truth
  • Compliance-sensitive
  • Validated
  • Auditable
  • Template for other sectors

The problem

Every month, NEOM's contractors report their environmental and waste data, and that reporting has a fixed deadline and a regulator behind it. It used to arrive as spreadsheets that analysts exported, consolidated and reconciled by hand in Excel. It took weeks, errors crept in, and different meetings sometimes saw different numbers.

The approach

ESRA (Environmental & Social Responsibility Application) moved reporting from a people-driven process to a system-driven one:

  • Contractors submit their monthly sheets through online forms that write straight into structured data objects.
  • Those objects feed a standardized environmental data model, so every KPI has one definition across all submissions.
  • Automated pipelines validate, transform and propagate the data, and validation checks stop bad data before it reaches leadership.
  • The output is a set of executive-ready dashboards that serve as the authoritative view.

My role

Architecture, end-to-end pipelines, KPI definition and standardization, and alignment with compliance and operations stakeholders so the system met regulatory expectations.

Outcome

  • Compliance reporting went from ~4 weeks to ~1 hour
  • Adopted as the standard reporting procedure by all 800 contractors
  • Analyst effort dropped by ~90%, with far fewer errors and inconsistencies
  • Leadership trusted the numbers, and the process became auditable
  • It became a dependency for other dashboards and a template adopted by other sectors

Details are kept high-level because this is internal NEOM work.

Internal NEOM work, shared at a high level without confidential data.
Next case studyEnviroGPT