SupplierSpy / Trendsi / Dispute

Public issue tracker

Dispute a score for Trendsi

Think a dimension score is wrong? This form routes your dispute to our public issue tracker where every reviewer can see it. 14-day SLA from submission to published outcome at /supplier/trendsi/disputes.

Each dispute targets exactly one dimension. File separate disputes for separate dimensions.

Every dispute must cite at least one public source. Private links or screenshots without a URL may be rejected at triage.

Opens a prefilled GitHub issue in a new tab. You will need a GitHub account to post it.

If you represent the supplier being disputed, please also file a claim at /claim/trendsi first so we can verify. Unclaimed disputes are still reviewed but verified claimants get priority.

What happens next

  1. File. You submit via this form; a GitHub issue opens with the score-dispute label.
  2. Triage within 48 hours. An editor acknowledges the issue and confirms whether it is well-formed.
  3. Reviewer assigned. One SupplierSpy reviewer owns the dispute end-to-end and records their working notes on the issue.
  4. Evidence evaluated. We re-check the dimension against the rubric using the public sources you cited and any additional signals in our dataset.
  5. Outcome published. Within 14 days of filing, the outcome (upheld / rejected / partial / under-review) is appended to /supplier/trendsi/disputes. Score changes land in /corrections.
Prefer email? Write to hello@supplierspy.com with subject Score dispute: trendsi. Please include the same information the form asks for.