Build a business-event fact with auditable duplicate handling
Transaction feeds overlap, and source deliveries may be counted as separate business events.
- Transformation
Larger outcome
38 RecipesBuild models that answer the right questions
Recipes for building analytical models with explicit grain, populations, relationships, history, operational time and business rules.
Build a metric with explicit eligibility and reconcilable rollups
A new percentage, rate or average needs a defensible eligible population and missing-value policy.
- Transformation
Build auditable event-to-resource attribution
Revenue or productivity must be reported by employee, asset or team, but responsibility for each event is unclear.
- Transformation
Add dimension history with verified historical fact classification
Customer, asset or vendor attributes change, but past events need a defensible historical classification.
- Transformation
Preserve business-effective history and what was known at each reporting cutoff
A backdated correction must change today's reading of the past, yet a report issued earlier has to stay reproducible as it was published.
- Transformation
Build state durations by entity, location and reporting period
Waiting, idle, available or busy time must be measured by site or zone and hour from operational event histories.
- Transformation
Sessionize event streams and build reproducible funnels from batch exports
Product analytics numbers cannot be reproduced outside the vendor's screen, and nobody can say why two conversion figures differ.
- Transformation
Build fleet utilisation against explicit asset availability
A fleet dashboard labels observed vehicle occupancy as utilisation without an authoritative available-time denominator.
- Transformation
- Supply chain and operations
Build lane-day on-time transport performance with open trips and exceptions shown as approved
A TMS dashboard reports on-time performance by lane, but nobody can inspect how it is calculated or reproduce its figure.
- Transformation
- Supply chain and operations
Build shift revenue, cost and margin with reconciled rollups
A fleet dashboard reports revenue per shift but cannot establish whether a shift covers its applicable costs.
- Transformation
- Supply chain and operations
Build historical event amounts from effective-dated business rules
Historical fees or surcharges change when a current rate is applied to past events.
- Transformation
Assess an existing dbt change for safe merge without modifying it
An existing dbt change builds successfully but reviewers still need evidence that its business answers remain valid.
- Data quality
Score customers with RFM, maintain segments incrementally and explain every move
Marketing segment lists come from a spreadsheet or BI export nobody can reproduce, and the same customer lands in different segments depending on who pulled the list.
- Transformation
Compute historical customer lifetime value with margin
The payback conversation uses a customer value from a spreadsheet nobody can reproduce, and it counts order revenue only, with no refunds and no cost of serving the orders.
- Transformation
- Finance
Build retention cohorts and a churn feature table
Marketing, finance and product each quote a different churn rate because each defines an active and a lost customer differently.
- Transformation
Build a training dataset that uses only information available at prediction time
A model scores well in training but worse in production because training rows used facts, corrections or labels a real prediction could not have seen.
- Transformation
Unify consent and communication preferences with auditable latest-wins logic
A customer who opted out in one system still gets messages from another, because each source says something different and whichever job ran last wins.
- Governance and cost
Attribute conversions to touchpoints under several models side by side
Marketing and Sales each have a spreadsheet crediting their channel with the same revenue, and together they claim more than was booked.
- Transformation
- Revenue operations
Build AML monitoring features at account-day grain
A transaction-monitoring model is fed hand-built features nobody can reproduce, so two runs on the same data disagree.
- Transformation
- Banking
Build one shared calendar and fiscal-period date table
Two reports put the same day in different weeks, months, quarters or fiscal periods because each mart builds its own date logic.
- Transformation
Normalize multi-currency amounts to a reporting currency with as-of rates
Finance adds amounts held in several currencies as if they were one, or restates old transactions at today's rate, and the total changes every time someone reruns it.
- Transformation
- Finance
Build sell-through and stockout risk by store, SKU, and day
Planners cannot tell which items are about to run out because sell-through and stock-outs live in spreadsheets, and each one counts a day with no stock differently.
- Transformation
- Supply chain and operations
Build paid and incurred claims loss triangles by accident and development period
Reserving analysts rebuild loss triangles by hand in spreadsheets, and a late payment or reserve change pushes back into cells that were already reported.
- Transformation
- Finance
Build a thirty-day readmission cohort with explicit exclusions
The quality team rebuilds a readmission rate from a spreadsheet each quarter, and nobody can say who was left out of the rate or why.
- Transformation
- Healthcare
Reconcile billed claims to payer remittances, denials and batch payments by payer
The revenue cycle team matches payer remittances to billed claims by hand, and nobody can say, payer by payer, how much of what was billed was paid, adjusted, denied or is still open.
- Transformation
- Finance
Build loan delinquency roll rates and vintage curves from loan, schedule, payment and event records
Credit risk reads delinquency off a servicer status field that each system refreshes on its own day, so bucket counts and roll rates differ from report to report.
- Transformation
- Finance
Measure trade-promotion lift and the post-promotion dip against an explicit baseline
Trade marketing reports promotion results with whatever comparison each analyst chose, and nobody can say what "without the promotion" meant for a given event.
- Transformation
- Revenue operations
Reconcile meter reads to bills and quantify unbilled energy
Revenue assurance compares metered usage with billed usage in a spreadsheet each month, and nobody can say which differences are real and which are timing, estimates or a meter swap.
- Transformation
- Finance
Land call-detail batches and aggregate them into subscriber-day usage with manifest completeness
Monthly subscriber usage differs by who ran it, because nobody can say which call-detail batches had landed or whether each arrived complete.
- Ingestion
- Telecom
Build clinical-trial enrollment and site-performance models with every screened subject accounted for
Clinical operations rebuilds enrollment and site performance in a spreadsheet each month, and nobody can say who was left out of the enrolled count or why a site looks slow.
- Transformation
- Life sciences
Build the MRR waterfall with net and gross revenue retention
Finance, RevOps and the board each quote a different net revenue retention because each turns subscriptions into monthly recurring revenue its own way.
- Transformation
- Finance
Build overall equipment effectiveness and a downtime Pareto
Plant OEE comes from a hand-built spreadsheet and nobody can say whether stops, slow running or scrap cost a line its points.
- Transformation
- Supply chain and operations
Build nightly occupancy, ADR and RevPAR by property with closed-night restatements
Occupancy, ADR and RevPAR differ between reports because each one counts stays, comps, out-of-order rooms and cancellations its own way.
- Transformation
- Hospitality
Track grant funds per award from authorization to drawdown and flag exceptions
Grants accountants cannot say per award how much is authorized, obligated, spent and drawn, and each report gives a different answer.
- Transformation
- Finance
Attribute warehouse spend to the models and job runs behind it, keeping idle and untied cost visible
The warehouse bill keeps growing and nobody can say which models or jobs are behind it.
- Governance and cost
- IT and FinOps
Add a breaking data contract change as a new version beside the old one and revise its named consumers
A required change to a published relation's grain, column meaning or shape cannot keep the old interface.
- Transformation
Build order-line contribution margin with order and period rollups after refunds and returns
Gross sales minus original item cost overstates order margin because refunds and returns arrive after the order.
- Transformation
- Finance
Match purchase orders, receipts and invoices line by line with an exception ledger
Accounts payable is asked to release payment and cannot say how much of an invoice is covered by the goods actually received.
- Transformation
- Finance