Inspect source meanings
Bring together the required account and subscription records. Check keys, date fields and the event that represents an eligible renewal.
Scientist · Data preparation
Build the population before explaining the pattern.
Connect sources and transform records for investigation. Scientist keeps selection, joins and derived fields within the analytical workflow, where collaborators can examine how preparation shapes the question the data can answer.
Data preparation
Prepare subscription records for a renewal study
Prepare account and subscription data for a renewal study, with explicit handling of paused subscriptions and missing dates.
Source data
Account records · Subscription activity
Preparation choices
Align date fields · Review missing renewal dates
Research dataset
Eligible subscriptions with documented cohort fields
Make the preparation choices part of the research workflow.
Follow the investigation
A concrete path through the research.
A renewal comparison depends on how the team handles paused subscriptions, missing dates and accounts with multiple subscriptions. Those are research choices, not housekeeping to hide before the analysis.
Make exclusions explicit
Align dates and define how incomplete or paused subscriptions enter the study. Derive the cohort fields from that agreed definition.
Review the prepared population
Inspect retained and excluded cases. Confirm that the workflow represents the intended observation period before comparing groups.
What to examine
Put the analytical choices in view.
The useful output is not just a completed run. It is an analysis whose inputs, assumptions and limits another researcher can question.
Record relationship
Do the joined rows represent accounts, subscriptions or renewal events?
Boundary handling
What happens to a missing renewal date or a subscription paused during the period?
Analytical readiness
Can another researcher explain why a record entered the cohort?
Scientist in the DO Stack
Take the research to the right next owner.
Coworker can supply company context that helps explain the business definitions behind a dataset. Keep those explanations distinct from the records actually analyzed in Scientist, and validate the access and transfer arrangements.
What should we validate for implementation?
Confirm each required source, connection method, data format, access permission and execution location. No universal connector catalog, automatic data-quality guarantee or in-database execution is implied.
What should the team bring to a first discussion?
Bring one research question, its source requirements, a relevant workflow and the review criteria. Confirm available capabilities, access and operating requirements before using sensitive material or applying a finding operationally.
Start with a question worth investigating.
Bring the question, the available data and the people who understand it. We’ll work through the analytical path, the review points and the implementation requirements.