Operational context
Recruitment reporting was designed around how HR teams monitor jobs, candidate volumes, stage conversion, workload, ageing, progress, and outcomes.
Data Analytics
A Power BI reporting layer that transforms recruitment operations into pipeline, workload, progress, and performance indicators.

Why it matters
My role
Recruitment reporting was designed around how HR teams monitor jobs, candidate volumes, stage conversion, workload, ageing, progress, and outcomes.
Operational Odoo fields are cleaned, standardized, related, and reshaped into reporting entities that preserve job, candidate, stage, owner, and time context.
Power BI measures calculate pipeline movement and recruitment indicators under controlled filters, with totals and stage logic checked against the operational source.
The reporting layer complements ATS Pro: managers see aggregate performance while recruiters can trace the signal back to the underlying recruitment workflow.
The dashboard turns pipeline activity into a shared monitoring view instead of relying on fragmented operational checks.
Technical implementation
Each layer connects an implementation choice to the decision or workflow it supports.
05 layers| Layer | Implementation | Operational purpose |
|---|---|---|
| Operational source | Odoo jobs, candidates, stages, owners, activity and time fields | Preserve the recruitment process behind each reported metric |
| Preparation | Power Query cleaning, typing, reshaping and relationship-ready keys | Convert operational records into analysis-ready reporting entities |
| Data model | Related job, candidate, stage, recruiter and calendar structures | Support consistent slicing by role, stage, owner and period |
| Measures | DAX indicators for pipeline volume, progress, conversion, workload and ageing | Make recruitment flow and bottlenecks measurable |
| Workflow connection | Aggregate Power BI views linked conceptually to underlying ATS records | Let managers monitor performance while recruiters retain operational detail |