Case studies / BWS Event Support
Case study BWS: a recruitment dashboard instead of manual spreadsheets
- Data from 7 cities, updated automatically every 2 hours
- Registration-to-verification conversion calculated live, not once a month
- Zero errors from a missed status: the filter covers active, hibernated, blocked and deleted at once
Every month someone at BWS opened the Sinch panel and copied into a spreadsheet how many people registered and how many got verified. Seven cities, four candidate statuses, all by hand. The numbers came out too low and nobody knew why.
Now the screen above refreshes itself every 2 hours.
How it works
A Python script asks the Sinch API about every city, calculates conversion and uploads a finished page to the BWS server. GitHub Actions runs it every 2 hours, no human needed. Kraków and Warsaw have their own monthly targets, the other cities share a separate table.
Where the missing 15% went
By default the API returns only active candidates. Anyone hibernated, blocked or deleted vanished from the numbers even though they had registered. The dashboard asks for all four statuses at once, and only then does the total match reality.
The dashboard sits behind a password because it’s internal company data. The marketing I do for BWS is in a separate case study.