Isaac Oresanya Reporting & Operations Analyst Résumé
Menu
Work / dated evidence index

Work in practice

Professional work leads

Three professional systems first, followed by clearly labelled technical and earlier evidence.

Professional systems / fixed orderView résumé →

Professional systems

Jan 2024–Present Professional current

Recurring Reporting System

My ownership spans the recurring KPI cycle, from source checks and preparation to management summary and recurring questions.

Preparation reduced 35%, from about eight hours to five per cycle.

See the reporting system
V-101 / Weekly reporting cadence
Weekly reporting cadence Weekly reporting moves from recurring inputs through definition checks, preparation, management review, and recorded action. INPUTSDEFINITIONSPREPAREREVIEWACTION
Recurring inputs are checked and prepared before management review; the next action returns to the following cycle.
Jun 2024–Jan 2025 Paid client

Multi-Source Data Quality Recovery

Across seven paid months, I collected and standardized three sources, led the quality recovery, and documented the client handoff.

163,229 consolidated records produced 141,228 analysis-ready records.

See the recovery case
V-201 / Source · validate · recover
Three-source data-quality recovery Three anonymous source platforms with different structures enter a repeatable collection workflow that retains lineage before validation and recovery. SOURCE ASOURCE BSOURCE C VALIDATERETAIN LINEAGE RECOVERCOMMON WORKFLOW
Anonymous sources stay distinct until a common workflow can validate and account for them.
Jan 21–Mar 4, 2026 Professional current

Programme Operations System

For a distributed cohort, I coordinated intake, team formation, progress visibility, blocker follow-up, submission, feedback, and reusable handoff.

35 participants, seven teams, and a reusable 16-phase process.

See the operations system
V-301 / Teams · phases · handoff
Thirty-five participants across seven teams Thirty-five anonymous participants were coordinated across seven teams through one shared operating rhythm; no individual data is shown. T1T2T3T4T5T6T7 35 PARTICIPANTS · 7 TEAMS · ONE OPERATING RHYTHM
Seven anonymous team lanes converge on a shared checkpoint and handoff rhythm.
Synthetic case study · Aug 2026

Synthetic portfolio project — not paid production experience.

Operations Reporting Control Tower

A bounded Power BI and reporting-controls case with a documented model, 12/12 quality controls, 7/7 reconciliations, and a static PBIX.

12/12 controls · 7/7 reconciliationsInspect the technical case →
Original synthetic-proof abstraction
Synthetic inputsSQL modelControlsStatic PBIX
12/12 quality controls7/7 reconciliations

Static technical evidence only. No live refresh, client, cloud, or production environment is implied.

Supporting / different evidence status
PUBLIC_ANALYSIS / PORTFOLIO_RECONSTRUCTIONOriginal work/source: 2023Audited portfolio reconstruction: 2026

Freelancer Market Intelligence Audit

A public-data cleaning audit that accounted for 29,326 inputs, 27,348 clean records, and 1,978 repeated IDs.

100% of inputs accounted for · 93.26% cleanView the public dataset (opens in a new tab)
PUBLIC_ANALYSIS / PORTFOLIO_RECONSTRUCTIONOriginal work: 2025Portfolio reconstruction: 2026

GitHub Ecosystem Monitor

A public-metadata audit with 14,644 clean repository rows and zero duplicate owner/repository identities.

14,644 clean rows · zero duplicate identitiesView the public dataset (opens in a new tab)
EARLIER_PROJECTEarlier work · 2023

BookLens

An earlier SQL/PostgreSQL project retained as historical evidence, not as the ceiling of current work.

Historical PostgreSQL / SQL method evidenceView BookLens on GitHub (opens in a new tab)