The answer to “who approves?” is not the same job title at every organisation. What matters is that the procedure identifies who generates the report, checks its technical integrity and is competent to assess product impact.
Separate the workflow into three tasks
The downloader matches shipment and device IDs and preserves the raw file. The technical reviewer checks clock, sampling interval, missing data and alarm flags. The quality role compares the record with product conditions and starts an assessment if an excursion appears.
Document authority and backup coverage for the product scope and quality system. The approval record should identify shipment, reviewed file version, date, reviewer and findings. If an excursion is detected, segregate affected stock under the procedure; a report signature is not automatic release.
Trial the form on a shipment: who holds the report, how long technical review takes and how an excursion reaches quality. The record reveals missing roles or delays.