How a Member Result Gets Verified Before It's Published

Every published member result on The Real World passes a four-stage verification process before it appears: documentary evidence, identity match, two-reviewer sign-off, and a typical-results disclosure fixed to the published item. Submissions that fail any stage are not published. That is a deliberate choice, and it costs us the most persuasive marketing material a platform like this could run. Here is the standard, who applies it, what gets rejected, and why a screenshot on its own never clears it.

The four stages, in order

A member who wants a result published submits a claim, along with written consent for that claim to appear publicly. That consent can be withdrawn later, and withdrawal removes the item from publication. The claim itself has to be specific: a milestone, a date, and a campus, not a vague statement of success.

Stage 1: submission, consent and the claim being made

The first stage is administrative, not evidentiary. A member describes what happened, when, and where inside the platform. Nothing is published at this point. The submission simply opens a file and states, in the member's own words, what they are claiming.

Stage 2: the documentary evidence test

The claim is then tested against documentary evidence. This is the stage that decides whether a submission has any chance of publication at all, because a claim with no verifiable record behind it goes no further. What counts as documentary evidence, and what does not, is covered in detail below.

Stage 3: two-reviewer sign-off

Two separate reviewers examine the evidence independently and must both agree before a result proceeds. Neither reviewer may be the member's own mentor. The reasoning behind that separation, and what happens when the two reviewers disagree, is covered further down.

Stage 4: publication with the disclosure attached

Once a submission clears review, it is published with a typical-results disclosure fixed to it and a date attached. The published item states the milestone, the campus, and when it happened. Monetary amounts are not part of the published item, for reasons explained below.

What counts as evidence and what does not

Documentary evidence has to be a primary record of the thing being claimed, not a description of it. A primary record is something that was generated by a third party or a system independent of the member's own account of events: an order confirmation from a marketplace, a signed client contract, a platform record of a completed module, a dashboard entry viewed directly rather than photographed.

Documents we accept

We accept records that originate outside the member's own narration of events. That includes contracts with a counterparty's identifying details visible, order or transaction confirmations issued by a third-party platform, and records held inside a dashboard that a reviewer can view directly during a live session rather than as a submitted image. The common thread is that the record was not created by the member for the purpose of proving the claim; it existed already, as a by-product of the thing actually happening.

Documents we reject on sight

We reject material that only the member could have produced or altered: a screenshot with no visible source, an edited or cropped image, a document with identifying details removed or obscured, and any submission where the underlying figure cannot be independently viewed. A written account with no attached record is rejected regardless of how detailed or plausible it reads. Detail is not evidence.

The live-session rule for anything held in a dashboard

Where the record a member is pointing to sits inside a dashboard rather than existing as an exportable document, a reviewer views that dashboard directly with the member present, in a live session, rather than accepting a screenshot of it. This closes the gap between "a screenshot of a number" and "the number, viewed at source." A screenshot of a dashboard can be edited before it is sent. A dashboard viewed live, in the member's own account, cannot.

Stage	Evidence required	Failure condition
Submission and consent	A specific claim, with written consent to publish	Claim is vague, unspecific, or consent is withheld or later withdrawn
Documentary evidence	A primary record independent of the member's own account: contract, third-party confirmation, or a dashboard viewed live	Only a screenshot, an edited image, or a description with nothing behind it
Two-reviewer sign-off	Two independent reviewers, excluding the member's own mentor, both agreeing the evidence meets the standard	One reviewer declines to sign off, or the reviewers disagree and the disagreement is not resolved
Publication with disclosure	A typical-results disclosure and a date attached to the published milestone	Evidence supports a monetary figure rather than a milestone, which is withheld rather than published

Why a screenshot on its own is never enough

A screenshot is an image, not a record. It says something happened, but it cannot say where it came from, whether it has been altered, or what happened immediately afterwards.

Provenance: an image carries no proof of where it came from

An image file does not, by itself, tell a reviewer which account produced it, when it was actually taken, or whether it has been cropped or edited before submission. Metadata that might answer those questions can be stripped or altered without leaving an obvious trace. Treating a screenshot as proof means trusting the person who sent it, which is precisely the trust the verification process exists to remove from the equation. A screenshot is treated as a pointer to where a record might be found, never as the record itself.

A screenshot cannot show what happened next

Even a genuine, unaltered screenshot captures a single moment. It cannot show whether a client relationship continued, whether an order was later refunded, or whether a milestone reached on one day was reversed the next. A verified result has to reflect a state of affairs a reviewer can actually confirm, not a moment frozen out of context. This is part of why dashboard records are viewed live rather than accepted as static images: a live view can be checked against what is currently true, not just what a single frame once showed.

Who reviews a submission, and who is barred from reviewing it

Reviewing a submission is a distinct role from mentoring a member. The person who has been coaching a member through their work is closest to that member's account of events and has the least reason to doubt it. That closeness is exactly why they are excluded from reviewing that member's submission.

The two-person rule

Two reviewers examine each submission independently, without conferring before they have each formed a view. Independent review catches what a single reviewer might miss and removes the possibility that one person's judgement, however careful, is the only thing standing between a weak submission and publication. Where the two reviewers reach different conclusions, the submission does not default to publication; the disagreement is resolved before any decision is made, and an unresolved disagreement means the submission is not published.

Why a member's own mentor never signs off their result

A mentor has an ongoing relationship with the member and, often, an interest in that member's visible success. That is not a suggestion of dishonesty; it is a structural conflict that exists regardless of how careful any individual is. Removing the mentor from the reviewing pair removes the conflict rather than asking anyone to manage it. Both reviewers on a given submission come from outside the member's direct mentoring relationship.

Submissions that get rejected

A submission fails at the evidence stage when the record offered is not a primary document: a screenshot with no independently viewable source, a description unsupported by anything, or a document that has been edited or has identifying details obscured. A submission fails at the review stage when reviewers cannot independently confirm what is being claimed, even if the underlying activity may be genuine, because the standard is what can be verified, not what is asserted. A submission also fails, structurally, when the claim itself is a monetary or earnings figure rather than a milestone, because that category of claim is not published regardless of the evidence behind it. A member whose submission fails can resubmit once, with additional evidence, before the file is closed.

Why gross revenue is not profit, and how the distinction is enforced

A figure describing money that moved into an account says nothing about what it cost to get there. Gross revenue, before costs, tools, advertising spend, platform fees or time, is not profit, and presenting one as the other misrepresents the underlying result regardless of whether the number itself is accurate. This distinction is not a caveat added after the fact; it is enforced by what gets published in the first place. Monetary figures, gross or net, are kept in the underlying file rather than appearing on the published item. What is published instead is the milestone: a first client signed, a first store live, a first commissioned piece, a portfolio completed, a campus completed. A milestone is a fact a reviewer can confirm directly. A profit figure depends on a member's own accounting, which a reviewer cannot independently verify to the same standard, and which varies member to member in ways a single headline number would flatten and mislead.

The typical-results disclosure attached to every published item exists for the same reason. A disclosure does not, by itself, make an atypical result fair to present as ordinary; a caption under an unrepresentative claim does not fix the claim. That is why the more direct control is withholding the unrepresentative figure rather than publishing it with a disclaimer attached. The disclosure is a floor, not the whole answer.

Why verification of a past result never implies a future one

A verified result confirms that something happened, once, to one member, under conditions that are not the same as any other member's conditions. It says a milestone was reached and that the evidence behind it met the standard above. It does not say the same outcome is typical, likely, or repeatable for anyone else, and it should not be read that way. Effort, market conditions, prior experience, and time invested all vary between members, and a single verified result cannot control for any of them. The verification process establishes that a claim is true. It does not and cannot establish that a claim is representative.

How to read a published result

A published result on The Real World tells you three things you can rely on: the milestone happened, it was checked against a primary record rather than taken on trust, and two independent reviewers agreed the evidence met the standard. It does not tell you that the same outcome awaits anyone else, and it is not published as if it does. Read it as confirmation of one event, not as a projection.

If you see a result circulating that claims to come from The Real World but was not published through this process, treat it with the same caution you would apply to any unverified claim online. Material that was never submitted through the platform's own verification route has not passed any of the four stages described here, and its accuracy has not been checked by anyone connected to the platform.

If you believe a result published through this process is false, or that a claim being circulated in the platform's name misrepresents what actually happened, you can report it through the platform's standard support or contact channel, describing the claim and where you encountered it. A report does not require you to prove the claim is false; it opens a review of the underlying file against the standard set out above.

For more on what the platform does and does not claim about outcomes, see our page on non-promises. For a broader look at whether the platform works as described, see does it actually work. Our approach to reviews generally, including how we treat feedback we did not solicit, is covered on the reviews page, and for a wider judgement on value, see is it worth it.

The evidence file kept behind a published result

The published item itself is deliberately spare: a milestone, a campus, and a date. The material that supports it is not thrown away once a result clears review. The documentary evidence, the reviewers' notes, and the record of which two reviewers signed off are kept on file, separate from the public page. This matters for two reasons. First, it means a challenged result can be checked again against the original evidence rather than against the published summary alone. Second, it means the standard applied to a result does not depend on memory or on trusting that a review happened; there is a file that shows it did, and what was looked at.

Keeping the file also supports the withdrawal route described above. A member who submitted a result under written consent can withdraw that consent later, and the published item comes down. Because the underlying file exists independently of the public page, withdrawal is a straightforward administrative act rather than something that requires reconstructing what was originally claimed.

Why the process applies the same way regardless of the size of the claim

It would be simpler to apply a lighter check to a modest milestone and a heavier one to a striking claim. The process does not work that way. A first client signed and a portfolio completed go through the same four stages as any other submission, with the same evidence standard and the same two-reviewer requirement. A bigger or more surprising claim is not treated as more suspicious by default, and a small one is not waved through on the assumption that nobody would bother fabricating something modest. The stages are fixed to the process, not to how impressive the claim sounds.

This consistency is also what makes the disclosure meaningful. A typical-results statement attached to every published item, regardless of size, tells a reader that the same check was applied whether the milestone was large or small. Varying the standard by claim size would undermine that signal.

Questions people ask

Is every member result published on The Real World independently verified?

Every result published through the platform's own process has passed the four stages described above: submission and consent, documentary evidence, two-reviewer sign-off, and publication with a disclosure attached. Material circulating elsewhere in the platform's name, but not submitted through this process, has not been checked by us.

Can a member submit a result and have it published immediately?

No. A submission has to clear documentary evidence review and receive independent sign-off from two reviewers before anything is published. There is no route that skips evidence review, regardless of how the claim is worded.

Does a screenshot ever count as sufficient evidence on its own?

No. A screenshot carries no proof of where it came from, can be edited without an obvious trace, and cannot show what happened after the moment it captures. Where a figure sits in a dashboard, a reviewer views the dashboard directly in a live session rather than accepting an image of it.

Why does a member's mentor never review their own result?

A mentor has an ongoing relationship with the member submitting the claim and, often, a stake in that member's visible progress. Reviewers are drawn from outside that relationship so the sign-off is not affected by it.

Why is a monetary figure withheld even when the underlying evidence is genuine?

Gross revenue is not profit, and a single monetary figure cannot reflect the costs, time and conditions behind it in a way that is fair to present as a headline. Published results describe a milestone instead, which is something a reviewer can confirm directly and which does not require translating a member's private accounting into a public claim.

Does a verified result mean the same outcome is likely for someone else?

No. Verification confirms that a specific event happened and that the evidence behind it met the standard. It says nothing about how typical that outcome is or whether the conditions behind it would repeat for anyone else.

What can I do if I think a published result is false?

You can report it through the platform's support or contact channel, describing the claim and where you saw it. That opens a review of the file behind the published item against the standard described here.

What happens if a submission fails verification?

A member can resubmit once with additional evidence. If the second submission still does not meet the standard, the file is closed and the result is not published.