- Two numbers, 11% apart
- Your brief
- The warehouse you inherit
Put data contracts behind a clinical waiting-time dashboard
Caldervale Health’s waiting-time dashboard and its board pack disagree by 11%, and nobody can say which is wrong. Put a tested contract behind every model, classify the patient data flowing through it, publish the lineage, and leave the clinic’s analysts able to answer "where did this number come from" in under a minute.
PCREATED BYPrepmeetsProject studio, Prepmeets
THE CHALLENGE → YOUR OUTCOME
Real context. Work that matters.
Caldervale runs nine community diagnostic clinics and reports waiting times monthly. Two systems derived from the same warehouse disagree, and the governance lead cannot say which to trust or who can see the underlying referrals. You put contracts and tests behind the models, resolve the metric definition, classify and enforce access to patient columns, and publish lineage the clinic’s own analysts can read.
What’s at stake
Your responsibility: Work as the analytics engineer, data governance—investigate the requirements, implement your approach and verify the result.The warehouse was built over two years by whoever needed a number, which is why it works. The dashboard came first, built by an analyst who has since left; the board pack models were added later by a contractor who could not find the dashboard’s logic and so wrote their own. Both read the same three source systems. Both have been correct enough, for long enough, that nobody checked.
Success means: One documented definition of waiting time, enforced contracts on every mart, a test suite that fails the build on the defects that caused this, patient columns classified and access narrowed to the people who need them, and lineage published so the next disagreement takes an hour rather than a month. Explain the decisions and checks behind your implementation.
WHAT YOU’LL BUILD
01dbt
02Data contracts
03Data quality
Caldervale Health analytics warehouse
INCLUDED WITH YOUR PROJECT
A workspace, not just a document.
Your brief, a Jira-style task board and an interview studio—all in one place.
A look inside your workspace
Start with the full project brief
Build step by step Track your progress Own your interview story
Know where you’re heading.
- 01Two numbers, 11% apart
- 02Your brief
- 03The warehouse you inherit
- 04Where governance sits in the pipeline
- 05Five phases
- 06Breaking it on purpose
- 07What you hand over
- 08Submission and cleanup
Practise explaining your decisions
Which decision mattered most in your solution, and how did you verify it?
Use your own implementation to connect Situation, Task, Action and Result into one interview story.
Before you begin · tools & running costs
Prerequisites: Your own accounts and access to dbt-core 1.8, dbt-expectations, Column classification in dbt meta, dbt docs and the lineage graph.
Additional costs: Cloud and tool usage in your own accounts may incur charges. Set a budget and clean up after testing.
Work in your own accounts and repositories. Never share credentials or confidential data.
What’s included
Project brief, target-design guidance, assigned tasks, resource guidance and interview prompts. Detailed requirements become part of your purchased workspace.
P
MEET YOUR PROJECT EXPERT
Prepmeets
Project studio, PrepmeetsWe are the team that builds Prepmeets. Between us we have run cloud platforms, delivery pipelines, analytics teams and AI governance programmes in banks, hospitals, retailers and government departments, and these projects are the work we used to hand to new joiners in their first fortnight. Every one of them is a real scenario with the client’s name changed, scoped to a week of evenings, and reviewed by the person who originally did the job.
View verified expert profile Expert review is an optional paid service, separate from project access.£19.90Start this project