Pad-Mount Receiving Check

Sign the freight receipt clean and find damage later, and the burden of proof shifts to you. Pad-Mount Receiving Check builds the transformer's receiving record before the driver leaves: required photos, nameplate-versus-PO compare, and the exact exception line to copy onto the delivery receipt. Every transformer manual says the same thing: inspect for damage and note it on the carrier's freight receipt before signing. Claim reviewers reject vague notes — "subject to inspection" gets treated as worthless. The app composes specific exception text instead, like "Unit S-500-0021: secondary voltage mismatch, ordered 480Y/277, received 208Y/120. Held for vendor disposition." You copy that line onto the paper, then lock the record. The dock procedure, per serial: - Four required angle photos, plus forced photos on leaks, dents, tripped impact indicators, and tilt flags - Nameplate compared against the PO line by line: kVA, voltage, connection, taps, BIL, impedance, and bushing configuration, with a wye voltage cross-check - Pressure-vacuum gauge reading classified, not just noted - A locked, signed record; anything found after acceptance goes in as an addendum that never edits the original Concealed damage has a clock. Notice windows on LTL freight are short and vary by carrier, so the app tracks the window from the delivery date and prompts you to confirm the actual terms printed on your carrier's bill of lading before it counts down. Exports are yours: PDF per unit or per delivery, CSV, JSON, or a ZIP evidence pack with every photo, timestamp, and signature. Records live on the device and the whole flow runs without signal, which matters on a materials yard dock. When the claim question surfaces months later, search past records by serial or PO. This app documents what the receiver saw at the dock. It does not test, certify, energize, or approve a transformer, and it is not legal advice — confirm claim terms on your own carrier's bill of lading. Standards bodies and manufacturers named in checklists are referenced as method descriptors only; no affiliation or endorsement is implied.