Make the one artefact you will reuse for years

Your first portfolio piece should be one complete worked example on synthetic material, structured and sized exactly like a paid delivery, published where buyers will see it, and rebuilt when your format changes. It replaces "trust me" with "here is exactly what arrives" for every visitor.

This is the production job rather than the argument for it - the case for having one at all makes that properly - and it takes an evening.

Choose material you can publish forever

Two independent requirements, and people usually clear one and miss the other.

You must have a right to use it, and you must have a documented right to publish it, permanently, without a future conversation. Synthetic or constructed material clears both without asking anyone. A volunteer is weaker than it looks, even with written permission: where publication rests on consent, the UK regulator's guidance on valid consent (ICO) says people "must be able to withdraw consent easily at any time", so "permanently" is not something a volunteer can grant. Everything else - a real submission, an anonymised submission, another earner's delivered work - clears neither, and where practice material comes from covers the sourcing in full.

Pick a middle case rather than an easy one. An example built on obviously flattering material demonstrates nothing about your judgement, and an example built on a hard case demonstrates the thing buyers are actually uncertain about, which is whether you can say something specific when the answer is not obvious.

Structure it exactly as you deliver

This is the part that separates a worked example from a writing sample.

The headings must be the headings a buyer receives. The axes must be the axes you score on. The closing summary must be the one you actually write. If your delivered work has a scored table, the example has the same table with the same column names.

A buyer reading it is not evaluating your prose. They are checking whether the thing they would receive is worth the fee, and every element you leave out of the example is an element they assume is not there.

This is also why the example is downstream of your rubric rather than upstream: build the reusable structure first, then produce one instance of it. The rubric you can reuse is the thing the example is advertising.

Length, and where people go wrong

Two failure modes, roughly equally common.

Too short reads as a teaser and raises the question it was meant to answer. Too long reads as an outlier produced for display, and it sets an expectation your paid work will not meet at your actual turnaround.

The correct length is the length of a real delivery at your standard price. If that feels thin as a public artefact, the problem is the delivery rather than the example, and shortening the gap by inflating the example is the one move guaranteed to produce a disappointed first buyer.

For recorded formats, the same rule with an additional constraint: publish the full length rather than an excerpt. An excerpt of a twelve-minute video answers the question "can you talk" and not the question "is twelve minutes of this worth the fee", which is the only question being asked.

Publish it where it is found

On the listing itself if the platform allows an attachment or a link. Otherwise on a single stable page you control, linked from your first line, because a buyer who has to ask to see the example usually does not ask.

Say what it is in one sentence above it. "A complete example, on generic material, in the format you would receive." Without that sentence a proportion of readers assume it is a real client's work, which is a worse impression than having no example.

Keep the file naming and the metadata clean, since a document produced from a personal template will carry the author field with it; Microsoft's guidance on inspecting documents notes that document properties include the author and the name of whoever last saved the file. That is the most common way an otherwise careful separation leaks, and it costs nothing to check before uploading.

Keeping it current

An example rots in three ways, and only one of them is visible.

The format drifts: you add an axis, drop a section, change the summary style, and the example now describes a product you no longer sell. Fix by rebuilding rather than patching, because a patched example accumulates inconsistencies that read as carelessness.

The price drifts: an example implying a scope that no longer matches the fee is an argument you will have with a buyer during a job rather than before one. The scope sentence that prevents most disputes should agree with the example word for word.

The quality drifts, upward. Your work at month nine is better than your work at week one, and an example from week one is now understating you. This is the invisible one, and the reason to diarise a rebuild at six months rather than waiting for a reason.

One rebuild a year is enough for most people. It takes an evening, it is the cheapest marketing available in this trade, and it compounds because each version is built from a better rubric than the last.

What the example is competing against

Not other earners' examples, mostly. It is competing against the free automated output a buyer has already seen, which is instant, generic and costs nothing - the software that produces it is the baseline, and an example that reads like a longer version of it makes the case against hiring you.

The differentiator is specificity: a named person committing to a particular judgement about a particular thing, with reasoning attached. That is precisely what buyers report valuing when they describe a review that was worth the money, from their side of the transaction, and it is what an example should be built to demonstrate rather than assert.

Where your offer includes numerical precision, the example is also where you show that the numbers mean something, which means the conventions have to be the documented ones - the method reference is what a buyer comparing you to a careful competitor is implicitly checking against.

Check before you publish that the platform permits an external link or a hosted example at all, since some route everything through their own listing fields and some prohibit outbound links entirely. The Rate Cock judges page sets out what a listing there can carry, which decides where the artefact lives rather than whether you build it.