QASWAThe problem
Weekly labor and overtime performance for a portfolio of senior living communities ran on a single 25 MB Excel workbook. It only refreshed when someone opened it, community and role logic was hardcoded inside Power Query, and anyone with the file could see every community and every employee. If the file broke, the process stopped.
What we built
We recoded the workbook's logic — penny for penny — into a governed Azure platform running entirely inside Heritage's own tenant, reusing every data feed they already had. No new integrations, no more refresh button.
“Qaswa has delivered five platforms for us across four departments, all running inside our own Azure environment. What stands out is the discipline: every number ties back to the source, and nothing changes in our systems unless one of our people approves it.”
Farhan Khan, CEO, Heritage Communities · 
How it works
- Refreshes itself from the payroll, staffing and occupancy feeds Heritage already had — ready by 9:00 AM Central every day, without anyone opening a workbook
- Overtime flagged mid-week, while there are still two scheduling days left to prevent it
- A built-in analyst answers the common questions — who is at risk of overtime this week, why a community's overtime spiked — from governed queries, and shows the query under every answer
Security and control
- Sign-in through Heritage's own identity provider, with access limited to approved users
- Managed identities for every data connection — no stored passwords
- Every budget or staffing edit validated and logged
Reconciled, not taken on faith
Because the workbook's logic was recoded penny for penny, the platform's figures could be reconciled against the workbook it replaces — and they were, before anyone relied on them. How we build →