Claims and evidence, explained
What it means when we label something ‘user-provided’ versus ‘evidence-backed’ — and why we never call an uploaded file verified employment.
By the Patorbit team
Most resume data is an unverified assertion. That's fine — resumes have always worked that way — but it becomes a problem when a platform starts implying verification it hasn't done.
A claim is a statement
When you build a profile in Patorbit, your experience becomes structured claims: I worked at Acme as a Data Engineer from 2022 to 2024. I hold an Azure Data Engineer Associate certification. Each claim starts life as exactly what it is: something you told us.
Evidence is proof attached to a claim
You can attach supporting material to a claim — a document, a link, a reference. The label then reflects reality:
- User-provided — you stated it. We're not asserting anything about it.
- Evidence-backed — a document supports it. We've checked that the document exists and matches the claim, not that an employer confirms it.
What we never do
Uploading a PDF of a job description is not verification of employment. A claim doesn't become “issuer verified” because you attached a file. The trust signal on your profile reflects completeness and support — not a third-party guarantee that hasn't happened.
This is deliberately conservative. The moment a platform overstates verification, every genuine verification on it becomes suspect.
Why it matters for job seekers
An honest label protects you. If everything on your profile is clearly marked by its actual status, nothing you're asked about in an interview can contradict what you claimed. And as you attach real evidence over time, the profile's support strengthens on its own.
Try it yourself
Build a resume, analyze a real job description, and see the gaps reported honestly.