Not every strong freelancer arrives with a list of references you can call. Some clients are confidential. Some past work came through platforms that keep contact details private. New freelancers may have relevant personal, open-source or in-house experience but few independent clients.
You can still make a careful decision. The goal is not to find one perfect substitute for a reference. It is to combine several forms of evidence and keep the first commitment small.
What should I ask for first?
Ask for one or two examples that resemble your project. Then ask the freelancer to explain their role, the constraints and what changed between the first plan and final delivery.
Good answers are specific without revealing confidential information. A developer might explain how they handled a migration while hiding the client's data. A writer can describe the approval process and show a redacted draft. A designer can distinguish the screens they owned from the broader product.
You are listening for a coherent working story, not a flawless success story. Real projects include trade-offs, revisions and limits.
Can I trust a portfolio by itself?
A portfolio shows taste, skill and the ability to present work. It does not always prove that the person completed paid client work or owned everything shown.
Ask process questions that are difficult to answer from a copied final image: What was the brief? Which decision took longest? What feedback changed the result? What files did you hand over? If the freelancer can show dated drafts, repository activity, invoices with private details removed or client confirmation, those add context.
Do not demand confidential materials. Respect for a previous client's privacy is a positive signal.
What does verified work history prove?
A verified work record can confirm parts of a freelancer's professional timeline, such as a recorded contract, role, dates or completion. It does not prove that the person is right for your exact job.
Workli profiles are designed around verified work history, giving freelancers a shareable record alongside skills and other profile evidence. Use that record to choose better questions. Look for work that resembles your scale, duration or type of responsibility.
Identity checks, skills, client reviews and completed contracts answer different questions. Do not treat one label as proof of everything.
Should I use a test task?
Use a paid trial that produces a real, limited deliverable. Good examples include an audit of one workflow, a draft of one section, a small design component or a plan for the first implementation milestone.
Define the time, price, output and acceptance criteria in writing. Do not ask several candidates to complete unpaid production work. The trial should respect the freelancer's time and leave you with something useful even if you do not continue.
Observe more than the output. Did the freelancer clarify ambiguity? Raise risks early? Keep the promised format? Explain decisions? These behaviours are often more predictive than a generic reference.
What if I still feel uncertain?
Reduce the size of the decision. Start with one milestone instead of the whole project. Keep important accounts under your control. Use staged access. Agree how files will be handed over and how either side can stop.
No hiring process removes risk. References themselves can be selective. A sensible process replaces one large leap of faith with several smaller checks: relevant samples, a coherent history, a focused conversation and paid work you can evaluate directly.
Comments0
It’s quiet in here. Fancy breaking the ice?