Project writing

How to describe freelance project outcomes without metrics

Show what you delivered and contributed without inventing percentages or claiming results you cannot verify.

Describe the deliverable you can verify

A project outcome can be a completed deliverable, a handover, a documented process, or work accepted by the client. Name what changed or what you produced without adding a number you cannot support.

Distinguish your contribution from a team result. If several people delivered the work, describe your part rather than implying that you alone caused the final outcome.

Use evidence in place of inflated language

Specific nouns and verbs often communicate more than generic claims. Explain what you designed, analysed, repaired, wrote, built, or coordinated, and identify the context where it matters.

Avoid claims such as “transformed the business” unless the evidence explains the transformation and your role in it. Clear scope is useful even when there is no public metric.

Add figures only when you know their source

Before using a percentage, volume, or savings figure, confirm what it measures, which dates it covers, and who recorded it. Check that you have permission to disclose it.

If a result is uncertain, confidential, or not attributable to your work, leave the number out. You can still describe the delivered work accurately and discuss evidence through an approved channel.

UK considerations

If an employer asks for measurable evidence, explain what records you can share and respect client confidentiality when discussing outcomes.

Keep your project history clear

Build a CV around the work you have done.

Start your CV
← All freelance CV articles