The mark covers these checks, not the person’s services or claims.
Name comparison
Live portrait comparison
Mobile control challenge (optional)
LinkedIn control challenge
Example check details
Reviewer
ScoutRail reviewer (example)
Policy
Profile verification 0.2
Illustrated check date
12 November 2026
Illustrated expiry
10 February 2027
This example includes the optional mobile check. These are sample details, not a verification receipt. A real badge uses completed checks, current status and the participant’s permission to publish.
For new live checks, this mark means a ScoutRail reviewer completed the three required checks against the exact profile details submitted. Mobile control is optional and appears in the badge details only if it was checked. It is a manual, low-assurance check, not a government identity check.
A photo, phone number or LinkedIn link does not verify someone. The reviewer must actually perform the stated checks.
New live checks
First name and surname
The participant states their name in a live video call. The reviewer compares it with their saved profile and the name on the LinkedIn profile.
Real profile photo
The reviewer visually compares the saved portrait with the participant in that live call. This is not biometric identification.
Mobile number control (optional)
If the participant separately agrees to this check, the reviewer calls the supplied mobile number and reads a single-use code. The participant enters it in their signed-in ScoutRail account. It expires after 15 minutes and locks after five failed attempts. Caller ID alone is not enough.
LinkedIn profile control
The participant temporarily places a unique challenge in their LinkedIn About section. The reviewer opens that exact profile, observes the challenge and compares the name. A link by itself does not pass.
A missing or unfinished mobile check does not block the three required checks. The badge says when mobile control was not checked. The reviewer cannot approve their own profile. Facebook is optional and is not part of this badge.
Previously verified profiles
An owner may record a prior check for an exact existing login and selected profile. Accepted public badges say “Verified”. Open a badge to see whether it records new live checks or “Previously verified · admin attested”. Historical records retain the original date, including when it is unknown. They record the owner’s attestation, not an independent live call or a new LinkedIn challenge. The badge lists only the historical checks attested, when that prior check happened (or explicitly says the date is unknown), and when the record was made. Private references are not published. An unresolved account mapping is not verified.
The owner’s own historical record is also admin-attested, never an independent self-review. This exception does not change the independent-review requirement for new live checks.
Dates, changes and sharing
A completed check lasts up to 90 days. The badge shows when the check happened and when it expires. Changing a checked field, withdrawing a check, or an account being disabled removes eligibility. An expired or unavailable check must not stay green.
Review is private. You review who will receive your details before sharing. Finishing a check does not send an invitation. A public badge requires a separate, explicit sharing choice for the checked name, portrait, LinkedIn link and check dates. For historical records the owner must record permission for public visibility; otherwise the record stays private. Mobile numbers, challenge codes and private review evidence are not published.
“About verification” is an information link, not a positive badge. No public badge can mean that a check has not been completed, is no longer current, or has not been shared. It is not a judgment about the person.
What the mark does not verify
Legal identity, age, employer, business role, signing authority, licences, safety, availability, service quality, truthful messages, payment or a successful outcome.
A profile check and a brief confirmation answer different questions. Neither makes every statement in a brief independently true.
Recorded from an account
A shared brief is tied to the account that submitted it, its exact version and the time ScoutRail accepted it. Receipt details identify the event and content reference. A saved draft has no shared receipt.
This establishes the source account. It does not prove who typed the words or create a digital signature.
Requirements confirmed
The other participant can explicitly confirm selected requirements in that exact brief version. The stamp shows how many requirements they confirmed, their statement and the recorded time.
Partial confirmation stays partial. Confirmation of an earlier version does not carry forward after edits. This is the participant’s attestation, not an independent inspection.
An agreement is a separate step
Sharing or confirming a brief does not accept an offer, reserve capacity, book work, move money or confirm delivery. Review the exact offer and the person’s authority before accepting.
The homepage walkthrough is a design preview, not live checks or agreements. Its marks illustrate the proposed experience; they are not evidence that the featured people completed checks or confirmed that brief. Private-room availability is separately controlled.
The agreement
A private record of the agreed version
The document and lock mark a record with controlled access. A brief, an offer awaiting acceptance and a recorded agreement have different labels. Sharing a brief does not create an agreement.
An accepted agreement keeps the exact offer or amendment, version and content reference. An agreed cancellation creates its own retained revision and cancellation receipt. Record details show the accepting account, represented party, authority reference, accepted event and time when those receipts are available. Missing receipts stay unavailable.
Changes require a new agreed revision. Delivery, review and payment keep their own states. Attached terms are separate files; the document card does not claim a PDF was generated.
What the lock means
Controlled access and a retained version, subject to retention and access rules. It does not mean end-to-end encryption, a digital signature, independent identity verification, legal certification or guaranteed enforceability.
A public, participant-free extract of the design. It is not the full research document, an IETF standard or proof that every proposed feature is active.
Example · ScoutRail profile checked