All workCase study · Healthcare services · Fabric app
A manual QA process, rebuilt as an app inside Fabric.
Utilization QA Console: a review app on the same semantic model as the reports, so the team checks and corrects client data before any report goes out.
- $250K+
- of workload absorbed by the app
- 2 roles
- of engineering work covered after both engineers left
- 1 model
- behind the reports, the app and client PDFs
01The problem
Client utilization reports depended on a manual QA process that was slow, easy to get wrong, and carried by two engineers. When both left, the work had nowhere to go, and every correction still had to land in the reports before the next refresh.
02What we built
- 1An app inside Fabric. It reads the same semantic model as the reports, so the numbers on screen are the numbers clients see.
- 2Edits with an impact preview. The before and after, including billing impact, show before anything is written.
- 3A change log with undo. Corrections write to Fabric SQL with the value they replaced and a reason, and flow back into the lakehouse first.
- 4Client PDFs on demand. Built in the browser from the model, watermarked until they’re final.
03The result
Review cycles now run from one screen, every correction can be traced and undone, and the app absorbed more than $250K of workload.
04 · Inside the app
Rebuilt on fictional data, screen by screen.





Next case studyMetadata-Driven Lakehouse One pipeline for every source. A new table onboards with a config row, and schema checks stop bad data at the door.
Corrections living in spreadsheets and email threads?Talk to us