Registration Operations Dashboards
The reporting layer for the Biometric Identification Exercise and the ID Card Project — daily, weekly and monthly Power BI reporting to management, plus camp-wise reports for government counterparts.
Screenshots of live humanitarian systems are not published. Where visuals appear, they are illustrative rebuilds created with synthetic data that reproduce the structure and design of the original work without exposing any operational or personal information — on data-protection grounds.
Context
Since 2024 I have been responsible for the reporting layer on two concurrent registration activities: the Biometric Identification Exercise (BIE) and the ID Card Project. That means building and maintaining the dashboards and Power BI reports that go to management daily, weekly and monthly, and the camp-wise reports shared with Camp-in-Charge (CIC) government counterparts.
What existed before were static periodic reports, out of date by the time they circulated. The harder part is that these are two different audiences. Management needs throughput, bottlenecks and data quality. CIC counterparts need coverage and completeness for their own camps. The same numbers, framed for different decisions — and they have to agree with each other.
Approach
- Pipeline. Data modelled in SQL Server with SSIS pipelines feeding a star schema, rather than reports querying operational tables directly.
- Measures defined once. DAX measures for throughput, coverage and completeness are written once and reused across every report, so a daily figure and a monthly figure can never disagree about what they are counting.
- Three cadences off one model. Daily operational views, weekly trend reporting and monthly summaries are different framings of the same measures — not three separately maintained reports.
- Camp-wise reporting for CIC. A separate layout aggregated by camp for government counterparts, at the granularity they actually work in, drawing on the same underlying measures as the internal view.
- Coverage. BIE and the ID Card Project are the two primary activities, alongside headcounting, stock management and overall registration performance.
How it looks
Daily registration throughput
Synthetic values across two illustrative sites
Data completeness
Synthetic value — a real measure in the suite
Outcome
Daily · weekly · monthly reporting
Live operational insight replaced manual reporting cycles. The suite carries daily, weekly and monthly reporting to senior management on both BIE and the ID Card Project, and the camp-wise reports shared with CIC counterparts.
Because both sides read from the same measures, it has become the reference the two look at together — which removes an entire category of argument about whose numbers are right.
What I’d do differently
Row-level security is the obvious gap. Today the CIC-facing layout is a separate report; it should be one model with RLS so each counterpart sees their own area automatically. That is a change to the semantic model rather than the reports, and it would retire the duplicate-layout maintenance entirely.