Keep distance and angular units consistent
Original discussionConfirm whether every target distance is in yards or meters before entering it. Set the profile's angular output to match the optic and the language used in the match plan. Know the turret's click value; an angular solution and a number of clicks are not the same thing. Label handwritten, printed, and exported data with both distance and angular units. When another person shares data, verify its units instead of inferring them from familiar-looking numbers.
Use one working language. Converting can be valid, but switching units mentally under time pressure creates unnecessary failure points. Build and verify the workspace in the units you will actually use.
If The curve looks smooth but every correction is implausible.: Check target-distance and angular units before changing velocity, coefficient, or atmosphere. A unit mismatch can produce internally consistent but unusable rows.