A documentation packet for ADAS Calibration on a Rolls-Royce Phantom should read like a controlled process: what the vehicle reported, what prerequisites were verified, what procedure was completed, and what evidence confirms the result. Include a labeled pre-scan report showing vehicle identification, date/time, scan platform, and a comprehensive module list. Add the calibration outcome record (completion report/certificate/screenshot) tied to the same Rolls-Royce Phantom, then include the post-scan report proving communication health and the absence of relevant DTCs. For static routines, note the target system used and record key setup measurements (distance, height, centerline references), plus floor-level confirmation and lighting controls; photos of target placement and measurement points improve repeatability. For dynamic routines, record verification drive notes such as roadway type, speed range, lane-marking quality, weather/light conditions, and any interruptions or restarts. Document physical inputs that affect geometry: installed windshield/glass spec, camera/radar bracket inspection or replacement details, tire pressures, tire sizes, ride height checks if required, alignment confirmation, and battery support used. If OEM steps include steering-angle initialization or yaw reset, capture those actions and results. Close with a brief technician summary of which ADAS functions were available after ADAS Calibration and store the packet as a single retrievable file.