Skip to content
UGP v1.0 is a public comment draft. Comments close November 23, 2026. The A–D defect counts are provisional.Public comment draft · until November 23, 2026Comment on this draftComment →
UGPUniversal Grading Protocol
The recordNormative§4

The UGP record

PDF

What a UGP record contains, and why the grade is derived from it and never entered by hand.

4.1 Contents of a record

A UGP record shall contain:

  • Identity: class, profile, make, model, model number, storage, colour, region, IMEI or serial number, and the lost/stolen (blacklist) result identity.blacklist: status clear, reported or unchecked, and for clear its basis, either a check (measured or evidenced, with its source and date) or the grader's or seller's declaration that the device is not reported lost or stolen (declared) (§9.3).
  • The eight axes: cosmetic, functional, battery, locks, operator lock, data, parts and kit.
  • Audit fields: UGP version, grader ID, timestamp, method (human, camera, hybrid), verification tier, conformance level, record scope (unit or lot).

4.2 Basis on every value

Each axis value carries a basis (§3).

4.3 Raw observations

Raw observations shall be stored, not only conclusions. That means per-zone defect lists, fault codes, battery readings and part states. A change to a tolerance in a later version can then recompute the grade without re-inspecting the device.

4.4 Derived results

The grade, the status and the core code are derived from the record by a deterministic function. They shall never be entered by hand. Reference behaviour is in Annex E (worked examples). The one exception is the cosmetic value of a supplier-mapped grade, which comes from a published crosswalk (§13.6).