How Freelancers Can Prove Work Experience Without Calling an Old Boss
Use concrete project facts, artifacts, and optional first-hand confirmations — then keep them in the same Career Record as your CV.
The employer model does not fit project work
An experienced freelancer may have delivered through a consultancy, an intermediary, and a client team at the same time. The person who signed the contract may never have seen the architecture. The person who saw the architecture may have moved on. Asking for “the old boss” collapses that reality into the wrong relationship.
The better question is: who had first-hand knowledge of this specific work?
Build the claim before asking for proof
A useful project record answers five questions:
- What was the environment?
- What problem had to be solved?
- What did you personally contribute?
- What changed as a result?
- What did you learn or change in your approach?
The wording should stay within what can be disclosed. “Reduced deployment lead time from days to under an hour for fourteen teams” may be appropriate in one project; “introduced self-service delivery with measurable adoption” may be the safer statement in another.
Three useful kinds of evidence
A named confirmation. A client, peer, or lead confirms a specific role or result in their own words. The relationship to the work is visible so the reader can judge the statement.
A public artifact. A talk, repository, architecture note, publication, or case study can show how you think or what you built. Link it to the relevant experience instead of collecting everything in a detached portfolio.
Clear provenance. Even when no external evidence can be public, the record can show that a fact was imported, manually entered, or proposed by an agent and then approved by the owner.
Ask for a narrow confirmation
A strong request is easy to answer:
I am updating the record for our delivery-platform project. Would you be comfortable confirming that I led the rollout and that product teams could deploy without a platform ticket afterward? Please change the wording if that is not how you remember it.
That gives the other person room to correct the claim. It avoids asking them to endorse your whole career or write a generic recommendation.
Keep the evidence with the career fact
The lasting value appears after the first request. If the confirmation lives only in an email, it becomes another attachment to find later. If it remains attached to a stable experience record, a web profile, PDF, or authorized agent can refer to the same evidence.
An MCP-capable agent can help prepare the structured entry and the request. It still cannot approve its own proposal or publish the profile. That boundary prevents fluent generated copy from becoming accepted history without the professional seeing it.
What person.work deliberately does not do
person.work is not a recruiter workflow, reference marketplace, or scoring system. It does not tell a client whom to hire. It gives a project-based professional one portable, owner-approved source for their work history, with optional evidence where it adds clarity.
That is enough. The profile becomes easier to maintain, easier to share, and easier for the next agent to understand without inventing a new version.
