Identity verified
The identity check was completed. It does not prove a skill, licence or job eligibility.
Use Someone keeps identity, capability evidence, professional credentials, exact-job eligibility and reliability separate. One badge should never pretend to answer all five questions.
The identity check was completed. It does not prove a skill, licence or job eligibility.
The Someone says they can do this. It is useful information, but it is not proof by itself.
Supporting evidence, verified outcomes or an assessment pathway can strengthen a capability when that evidence genuinely exists.
A relevant ticket, check, registration, certificate or licence has been verified. Its scope and validity still matter.
Use Someone checked the exact activity, location, credential requirements and other applicable conditions for this match.
Commitment behaviour is tracked separately from skill. A talented person can still be unreliable, and a new person can still be a strong match.
The credential system is designed for licences, registrations, tickets, certificates and checks. Victoria examples can include White Card, RSA and WWCC, alongside trade and professional credentials.
Because a credential has a scope. A White Card does not prove every construction skill. An RSA does not authorise every kind of work. A professional credential is checked against the exact job rather than becoming a universal permission.
An assessment appears only when Use Someone has a real assessment pathway for that capability. It can support trust for suitable non-regulated capability, or provide additional evidence, but it never replaces an official credential required by law or policy.
A Buyer should see the Someone's public name, approximate area when relevant, languages, the capability matched to the job, meaningful evidence, job-specific eligibility where checked and useful reliability history. Email, home address, private credential numbers and unrelated documents stay private.
A portfolio can help a Buyer understand relevant experience, but it is still evidence, not a licence or universal permission. Public work samples must be deliberately shared and connected to the relevant capability.
Use Someone is designed to support stronger account controls such as global sign-out, multi-factor authentication and passkeys as the production configuration matures. Only controls that are actually configured and tested should be presented as active.