How to review a freelancer's work when you're not an expert

Many founders and managers hire freelancers precisely because they lack the skills themselves. That raises an uncomfortable question: how do you know the work is good? You do not need to be an expert to review quality well. You need the right process.

Define "good" before work starts

Quality problems often begin with unclear expectations. For each piece of work, write acceptance criteria: simple statements that must be true when it is done.

For example, for a signup form:

• A new user can sign up with email and password
• Errors are shown clearly next to the right field
• The form works on mobile and with a keyboard only
• A welcome email arrives within a minute

You can test every one of these yourself, without reading a line of code.

Ask for regular demos

A demo every week or two is the most powerful quality tool for non-experts. Ask the freelancer to show the work running, not slides or screenshots. Try it yourself afterward. Click everything. Try to break it.

Use simple checklists

Create a short checklist for each type of work:

For websites and apps

• Works on a phone, a tablet and a laptop
• Loads quickly on a normal connection
• No broken links or obvious errors
• Text is readable, buttons are easy to tap

For design

• Consistent with your brand and existing screens
• All states covered: empty, loading, error and success
• Files organized so another designer could continue

For writing and marketing

• Accurate facts and claims
• Clear goal and call to action
• Consistent with your brand voice

Ask good questions

You do not need technical knowledge to ask revealing questions:

• "What did you test, and how?"
• "What would break first if usage doubled?"
• "What shortcuts did you take, and when should we fix them?"
• "How would another developer get started on this?"

Good freelancers answer clearly and honestly. Vague or defensive answers are a warning sign.

Get a second opinion

For important work, pay another expert for a short independent review. For software, a few hours of code review from a senior developer can reveal structural problems early, when they are cheap to fix. For design or marketing, a peer review works the same way.

This is not about distrust. Good freelancers welcome reviews, because it shows you take quality seriously.

Look at the signals over time

• Bugs after release: a steady stream of the same kind of problem is a warning sign
• Speed over time: if every change gets slower, the foundations may be weak
• Communication: surprises and missed deadlines often indicate deeper issues

See how to measure freelancer performance for a fuller framework.

Insist on documentation and tests

Ask for a short README or handover document and, for software, automated tests for important features. They make quality visible and protect you when the freelancer moves on. See knowledge handover when freelancers leave.

Frequently asked questions

How often should I review a freelancer's work?

Little and often. Weekly or biweekly demos and reviews catch problems early, when they are cheap to fix. A single review at the end of a project is risky.

What if I find quality problems?

Raise them quickly, specifically and calmly, with examples. Most freelancers want to fix issues. Agree on what needs to change and check again at the next review.

Is an independent code review worth the cost?

For important software, usually yes. A few hours of review from a senior developer can uncover structural issues that would cost far more to fix later.

Start with vetted talent

The easiest way to get quality work is to hire people whose quality has already been checked. Every HireCurated freelancer passes a technical review and an interview. Request a shortlist. Read how we vet freelancers.