Reep Register

Submissions

Send corrections or drop mapping data.

Correction reports and mapping-data drops are separate review inputs. Neither path writes directly to the register.

Correction reports

Report something wrong in the public register.

Paste the IDs, URLs, or names you already have. Group related references into a case, then send several cases under one receipt.

  • No lookup or Reep ID required.
  • References are reviewed privately, with no public lookup.
  • Accepted reports get a receipt reference.

Mapping data drop

Drop a file of provider mappings or supporting evidence.

Use the anonymous drop for bulk or semi-structured mapping data: CSVs, JSON, sheets exported as CSV, or evidence packets that map two or more provider IDs.

  • Best for provider-to-provider mappings and larger packets.
  • Files go to object storage via the existing anonymous drop path.
  • No account, no tracking, no direct register write.
Drop a mapping file here CSV preferred · 10 MB max · include context or evidence where possible

Useful packets include: provider ID pairs, Reep IDs where known, source links, club-season context, DOB or role context, confidence notes, and any ambiguity we should not auto-resolve.