One reporting platform instead of separate exports
The problem
Events, requests and tasks lived in separate exports and regional lists, each with its own columns and spellings. Reports were rebuilt by hand, and broke whenever an export changed. Nobody could say how many events the business was really running, or where requests were waiting.
What I built
- One Power BI model for events, requests and tasks — 21 reports on a dimensional model with 8 fact tables, designed from scratch.
- One master list from the regional lists: columns mapped, names aligned, duplicates across regions checked before anything is counted.
- Recurring events matched across years, even after they were renamed. Doubtful pairs go to a person, marked green, yellow or red.
- Where requests wait: time from submission to acceptance to completion, the oldest overdue stages, and the workload per person.
- Automatic refresh from SharePoint, so the reports are always on the latest files — see how the exports stopped breaking it.
From separate exports to one model
What feeds what. The counts are real: 8 fact tables, 21 reports.
Result
Reports always on the latest data. Gaps and delays visible while they can still be fixed, each with a name next to it. Year-over-year comparisons became possible for the first time, and duplicate planning across regions got caught before it cost anything.
Relevant if your role mentions
Power BI dashboardsData modellingAutomating reporting KPI trackingSharePoint listsStakeholder reportingHave reporting that is rebuilt by hand? Two lines by email are enough — what the reports are, and where the data comes from.
Email me