How to Evaluate Portfolios and Past Work

Choose portfolio samples that match your deliverable, then ask the professional to explain their contribution and decisions. A polished screenshot is useful for reviewing visual design; a functioning site lets you inspect implementation. An anonymized case study can explain complex work when a client cannot be named.

Review the same requirements across your shortlist. The worksheet below helps you record relevant examples, technical evidence, and the questions to resolve before hiring.

What a Portfolio Should Show

A strong portfolio demonstrates more than just finished outputs. Look for evidence of these five qualities:

1. Relevant Experience

Does the freelancer have experience with projects similar to yours? “Similar” means:

Same industry or audience — A designer who has worked with B2B SaaS companies understands your audience differently than one who specializes in wedding photography.
Same deliverable type — A web designer’s portfolio should show websites, not just social media graphics.
Same scale — If you need a 50-page e-commerce site, a portfolio of single-page landing pages does not demonstrate the right experience.

2. Process, Not Just Output

The best portfolios include case studies that walk you through the freelancer’s thinking:

What was the client’s problem or objective?
What approach did the freelancer take, and why?
What were the results?

A portfolio that only shows finished products tells you what the freelancer can make. A case study can explain decisions, but verify the candidate’s role and the evidence behind any claimed outcome.

3. Range Within a Niche

You want a freelancer who can adapt within their specialty. A copywriter’s portfolio should show they can write in different tones of voice. A designer should show different visual styles. Ask how the examples relate to your own constraints; a narrow specialist can still be suitable for a tightly defined assignment.

4. Recency

Ask when each sample was completed and what has changed since. Older work may remain relevant, and current work may be confidential. Evaluate whether the professional can explain the tools and requirements you need today rather than enforcing an arbitrary age cutoff.

5. Depth Over Volume

Ten mediocre pieces are less impressive than three excellent ones. Pay attention to the quality ceiling, not the quantity.

Evaluation Criteria by Service Type

Different professions demand different evaluation criteria. Here is what to look for based on the type of service you are hiring:

Design (Graphic, Web, UI/UX)

Criteria	What to Look For	Red Flag
Visual quality	Clean composition, intentional color choices, professional typography	Cluttered layouts, inconsistent spacing, amateur font pairings
UX thinking	Clear navigation, logical information hierarchy, accessible design	Beautiful but confusing interfaces; form over function
Brand consistency	Elements follow the particular client’s design system	Unexplained inconsistency within the same project
Responsive design	Mobile and desktop versions shown	No evidence of the mobile work your project requires
Attention to detail	Intentional alignment, consistent icon styles, clean edges	Misaligned elements, inconsistent styling, visible placeholder text

Development (Web, App, Software)

Criteria	What to Look For	Red Flag
Code quality	Clean, well-documented code (if a GitHub or code sample is available)	Unexplained code, unclear licensing, or inability to discuss the sample
Performance	Fast load times on live projects (test with Google PageSpeed Insights)	A performance claim with no measurement context
Responsiveness	Demonstrated behavior on the devices relevant to your project	Broken layouts on mobile devices
Modern tech stack	Uses current frameworks and best practices	Unsupported dependencies or no plan for the environment you need
Live examples	Working URLs you can test yourself	No suitable demonstration of the implementation being claimed

Writing and Content

Criteria	What to Look For	Red Flag
Voice range	Different tones across different client projects	Everything sounds the same regardless of the brand
SEO awareness	Natural keyword integration, structured headings, meta descriptions	Keyword-stuffed content or no evidence of SEO understanding
Engagement	Compelling openings, clear structure, strong conclusions	Generic intros, wall-of-text formatting, weak calls to action
Research depth	Specific data, expert quotes, original insights	Surface-level content that could have been written without any research
Grammar and polish	Error-free, professionally edited	Typos, awkward phrasing, or inconsistent style that the candidate cannot explain or address

Video and Photography

Criteria	What to Look For	Red Flag
Technical quality	Sharp focus, proper exposure, professional color grading	Grainy footage, blown highlights, amateur color correction
Storytelling	Clear narrative arc, purposeful editing, emotional resonance	Random montages with no coherent message
Audio quality	Clean dialogue, balanced music, professional sound design	Muffled audio, inconsistent levels, royalty-free music that distracts
Pacing	Appropriate rhythm for the content type	Too slow (viewers lose interest) or too fast (message gets lost)
Branding integration	Logos, lower thirds, and brand elements feel natural	Branding that looks slapped on as an afterthought

Interpret Technical Evidence Correctly

Google’s PageSpeed Insights reports lab measurements and, when available, real-user field data. Lighthouse score bands are 90 or above for good, 50–89 for needs improvement, and below 50 for poor. Ask the developer which factors affected the result and what improvements were within the project scope. PageSpeed Insights documentation

Ask for the URL, test date, device mode, and relevant conditions. A live site may have changed since the candidate delivered it. Google’s Lighthouse documentation also explains that scores vary even without code changes; its guidance says the median of five runs is more stable than a single result. Use measurements to ask about causes and tradeoffs, not to assign all responsibility for today’s site to one former contributor. Lighthouse variability guidance

Use W3C’s Easy Checks for an initial review of page titles, headings, image alternatives, contrast, and keyboard access. For a full accessibility assessment, ask how the professional evaluates the required standard and documents issues across the agreed scope. W3C Easy Checks

Investigate Gaps Without Assuming Misconduct

Template-based work can be a good fit for an efficient customization project. Ask which elements the professional selected, changed, or built and whether licenses cover your intended use. Review stock imagery, existing code, and AI-assisted assets in the same way.

A missing client name may reflect confidentiality. Ask for a permitted walkthrough, anonymized explanation, or personal demonstration. Upwork’s portfolio guide includes mockups and personal projects as ways to show skills. Have the candidate label those samples and explain what they built.

For claimed results, ask for the baseline, measurement period, data source, and other changes made during the project. A reported increase in sales is not automatically caused by a new design. If evidence cannot be shared, record the outcome as unverified and judge the available work on its own merits.

How to Request Relevant Samples

If a freelancer’s portfolio does not include work that matches your project, you have three options:

Option 1: Ask for Additional Samples

Send a message like: “Your portfolio is impressive. Do you have any examples of [specific type of work] that are not shown here? I am looking for someone with experience in [your industry/deliverable type].”

Ask for material the professional has permission to share. Where client work is confidential, an anonymized walkthrough or a demonstration using sample data can answer your technical questions.

Option 2: Ask for a Case Study Walkthrough

Request a 15-minute video call where the freelancer walks you through their most relevant project. Ask:

What was the client’s goal?
What was your specific contribution?
What challenges did you face, and how did you solve them?
What were the measurable results?

This reveals process and thinking in ways a static portfolio cannot.

Option 3: Commission a Paid Test Project

When important questions remain, a mutually agreed paid pilot can provide additional evidence. Design it to:

Mirror a real subset of your project
Have an agreed effort limit, such as 2–5 hours if suitable for the task
Include clear deliverables and success criteria
Specify compensation and payment timing before work starts

For more on structuring test projects, see our hiring process guide at How to Hire a Freelancer Without Getting Burned.

Portfolio Review Checklist

Use this checklist during your evaluation. Score each item on a 1–5 scale:

#	Evaluation Criteria	Score (1–5)	Notes
1	Relevant experience (similar industry, deliverable, scale)
2	Quality of best work (top 3 pieces)
3	Process and thinking (case studies, context provided)
4	Range and adaptability (different styles, tones, or clients)
5	Current relevance (tools, constraints, and contribution explained)
6	Technical execution (appropriate to their discipline)
7	Attention to detail (polish, consistency, professionalism)
8	Contribution and asset rights clearly described
9	Results orientation (measurable outcomes shown)
10	Presentation quality (portfolio itself is well-organized and easy to navigate)

How to use the worksheet: Define what 1 and 5 mean for each criterion before comparing people. For example, a low relevance score could mean no example of the required deliverable, while a high score could mean a comparable example with a clearly explained contribution. Mark unavailable evidence separately instead of automatically scoring it as poor work.

Use the scores to compare strengths and identify gaps. Treat an essential missing capability as a separate decision even when other scores are high. Record whether an interview, reference, or paid pilot can resolve each question.

When a Paid Pilot Is Useful

A pilot can help evaluate a defined uncertainty, such as whether a developer can work in your existing codebase or a writer can use your source material accurately. Limit access, agree on the deliverable and fee, and decide who may use the output afterward. Do not frame unpaid production work as an application requirement.

A professional may offer paid discovery instead of a pilot. Choose whichever approach answers your main question with a bounded scope and fee. If the assignment requires specialist technical review, include a qualified reviewer in the budget.

Questions to Ask About Portfolio Pieces

Go beyond surface impressions with these questions:

“What was your role in this project?” — Distinguishes between lead creator and contributor.
“What was the client’s primary goal, and how did your work support it?” — Reveals strategic thinking.
“What would you do differently if you could redo this project?” — Shows self-awareness and growth mindset.
“How did the client use or implement this work?” — Indicates whether the work actually shipped and performed.
“What constraints did you work within?” — Budget, timeline, and technical constraints reveal resourcefulness.
“Can I contact this client for a reference?” — Willingness to provide references is itself a positive signal.
“How long did this project take from start to finish?” — Helps you estimate timeline for your own project.

The quality of a freelancer’s answers often tells you more than the portfolio itself. Look for specificity, honesty about challenges, and genuine enthusiasm for the work.

Record the Evidence Behind Your Decision

Keep a short note for each shortlisted candidate: relevant sample, claimed role, evidence reviewed, unresolved questions, and next step. Separate what you observed from what the candidate reported. For a website, that might mean “tested the contact form today” versus “candidate says they built the original integration.”

Allow candidates to demonstrate competence in different ways against the same requirements. A personal project can show technical skill, a reference can clarify collaboration, and a case study can explain reasoning. Carry the strongest relevant evidence into your hiring decision and the final project scope.

Sources

Sources checked November 2, 2026.