DEV Community

Okeke Jenny
Okeke Jenny

Posted on

A verification page that survives a skeptic: redaction, dates, and publishing the resets

A verification page that survives a skeptic

Every service in a market like this one has a results page. Almost none of them is worth reading, because the format is the same: logos, a big number, no dates, no method, and a selection rule you cannot see. The page is written to be skimmed by someone already convinced.

The question worth designing for is different: what would this page have to contain for a skeptical reader to be able to check it?

1. Redaction that keeps the evidence

The instinct is to remove names, then remove account numbers, then remove the date because it feels identifying, and end up with a logo wall that proves nothing.

Redaction should remove identity, not evidence. Keep:

  • the firm and the plan,
  • the account size,
  • the pass or reset date,
  • the phase and the result,
  • the certificate or statement, with the account number masked.

What is left is a claim a reader can compare against the firm's own timeline and payout mechanics. "Alpha Capital Group, $100k, passed 12 September" is checkable in a way "500+ challenges passed" is not. The dates also make the page expensive to fake at scale, which is why they are the first thing a bad results page drops.

The version of this that a buyer can actually read is passed prop firm challenges — certificates in, names out, dates intact.

2. Publish the resets

This is the part almost nobody does, and it is the only part that converts the page from marketing into data.

Any process with a failure rate has failures. If a results page shows none, one of three things is true: the sample is curated, the failures are renamed as something else, or the volume is too small to have any. A reader cannot tell which, so the rational move is to discount all of it.

Publishing resets alongside passes does something a testimonial cannot: it sets a denominator. If you show twenty passes and one reset, the reader has a rate instead of a claim, and a rate can be argued with. It also forces the operator to write down why each reset happened, which is usually more informative than the passes: a breach on the news window, a trailing floor touched on an overnight gap, a consistency check at review.

3. Dates on the rules, not just the results

Results age. So do rules. A comparison page dated 2024 is not wrong, it is stale, and the reader has no way to tell which sentences have expired.

So each figure carries a checked date, and the page says what that date promises: which source was read, what happens when a firm does not publish a figure, and what the page does when a firm changes a rule after publication. That policy is the thing that makes a date mean something — without it, "updated" is a timestamp on a build, not a fact about the content. The one I work to is written up at how we check firm rules, including the corrections log.

A corrections log is uncomfortable and worth it. A page that has visibly corrected a figure is more credible than one that has never needed to, because the second one either got lucky or is not checking.

4. Separate the checkable claims from the persuasive ones

There is a version of this page that puts a success rate at the top, and it is the version that gets discounted. Success rates depend on the sample, the definition of success, and who was allowed to buy — none of which the reader can audit.

The claims that survive scrutiny are the ones with a paper trail:

  • a fee, and what it covers,
  • what happens on a retry,
  • a payout split,
  • a dated price comparison across providers.

The full breakdown, including what is and is not refundable, is on the cost page. Note the shape of it: prices and terms, no percentages. That is deliberate. The numbers a reader can verify against their own invoice are the numbers that belong on a page like this.

5. Make the page boring to maintain

A verification page decays the moment it becomes a project. Two fields per record, appended to a text file, rendered at build time:

{ "firm": "Example", "size": 100000, "outcome": "pass", "date": "2026-09-12", "evidence": "certificate" }
{ "firm": "Example", "size": 100000, "outcome": "reset", "date": "2026-09-19", "reason": "daily loss" }
Enter fullscreen mode Exit fullscreen mode

If adding a row takes more than a minute, the resets stop being added first, and then the page is a logo wall again. The format should be dull enough that nobody needs to be in the right mood to update it.


None of this is exotic. It is the ordinary discipline of publishing a denominator, dating your claims, and letting a stranger check the arithmetic. It is rare in this market because it is only worth doing if the results survive being checked — which is exactly the filter a skeptical reader is applying.

Top comments (0)