Driver Size ETL Blueprint

I keep detailed customer data in AWS Athena for my movers-and-packers operation and I’m ready to translate it into a clear blueprint for sizing the right number of drivers on every move. The focal metric is already set: the “Number of items moved” will serve as the target variable for all subsequent modelling and reporting.

Here’s what I need from you:

• A concise data-discovery write-up that confirms where, in the Athena tables, the features influencing driver requirements live, how they join together, and any data-quality issues you detect.
• A short, well-structured document (PDF or Markdown) that justifies the target variable, defines the supporting predictor fields, and spells out the logic behind the driver-size calculation.
• A step-by-step ETL outline—source queries in ANSI SQL, necessary transformations, and the load strategy—so my data engineer can move the refined dataset from Athena into our analytics layer without guesswork.

If you’re comfortable navigating Athena’s partitioned datasets, profiling data via SQL, and translating your findings into practical, engineer-ready instructions, I would love to see your approach.