Start with a verification matrix that links every requirement to its source, method, product level, article, configuration, facility, condition and pass criterion. Define what qualification, protoflight and acceptance mean for the program and which serials carry each pedigree. Qualification usually establishes design margin; acceptance screens each delivered item. One does not silently replace the other.
The evidence package should include approved procedures, as-run steps, instrument and fixture identity, calibration status, raw RF and environmental data, corrections, uncertainty, plots generated from retained data, monitoring logs, photographs without people where useful, anomalies, nonconformance disposition, waivers and review approvals. Repeat functional and end-to-end RF checks around environmental exposure according to the plan.
Close with the delivered configuration index: serial, BOM, drawings, firmware, calibration constants, materials or process deviations and open actions. State which evidence is inherited by similarity, why it is valid and which future changes trigger re-verification. A certificate or summary pass table alone cannot support configuration acceptance.