When a freelancer is the right answer
A freelancer is one of several ways to add capacity, and the right choice depends on where the work is stuck. The marketing team of one guide puts it simply: freelancers suit bounded tasks with a clear output, such as copywriting, while agencies suit work that needs sustained specialist attention or scale. The in-house versus agency comparison sets out what each staffing model does best and how a hybrid divides the work, and the guide to selecting, briefing and reviewing agencies covers agencies. This guide is about individual writers. When the work is a continuing content programme with planning, account management and reporting rather than separate commissions, the guide to hiring and evaluating a content marketing agency covers what stays with the business, the questions to put in writing and the file to keep for the handover.
The most common misjudgement is capacity. A freelancer adds drafting hours. They do not add review hours, expert time or approval decisions, and those are where content usually waits. The content production too slow page traces pieces from idea to publication and finds that waiting dwarfs working, with the waits clustered at one or two stages, often review. Speeding up drafting when review is the constraint only lengthens the queue in front of the reviewer. Before commissioning anyone, look at where the last few pieces waited.
| Situation | Is a freelancer the answer? | Why |
|---|---|---|
| The calendar has more slots than drafting hours, and briefs are ready | Yes | The freelancer adds exactly the missing capacity |
| A specialist subject the team cannot write about credibly | Yes, a writer who knows the subject | Knowledge arrives with the writer, though an expert still reviews |
| Drafts already wait for review or approval | No, not yet | More drafts join the same queue |
| No briefs, no style guide, no review criteria | Not yet | The freelancer guesses, and a rewrite follows |
| A sustained programme across several channels with account management | Consider an agency | The agencies guide covers that arrangement |
| Pieces that depend on the organisation's own first-hand experience | Only with access to experts | The writer needs interview time to get the material |
Finding writers who know the subject
Start from the subject, not from general polish. A writer who has worked in the field, writes for the publications your readers trust or has written well on neighbouring topics will produce a better first draft from the same brief than a fluent generalist, because they ask better questions and recognise a weak claim. Google's guidance on helpful content asks whether a page shows first-hand experience and expertise, the qualities summarised as E-E-A-TExperience, Expertise, Authoritativeness, Trust.. In a commissioned piece those qualities come from one of two places: the writer's own experience, or your experts' knowledge reached through interviews, which the subject-matter expert interview tutorial covers. Know which one you are buying before you look.
Good places to look, as general practice:
- Referrals. Ask other content leads, editors at publications in your field and your own experts whom they have worked with and would hire again.
- Bylines. Note the writers behind pieces in your field that you found useful, especially in publications your readers already read.
- Practitioners who write. People who do the work your readers do, and write about it, can be excellent writers for a specialist subject.
- Your own network. Former colleagues, customers who write and writers who have pitched you thoughtfully before.
Read samples close to your subject and format, and look past the prose. Does the writer source claims? Do they quote real people? Do they explain a method clearly enough that a reader could follow it? Then talk briefly: how would they approach a brief like yours, what would they need from you, how do they use AI tools, and how do they handle a fact they cannot verify. The questions a writer asks in that conversation predict the questions they will ask of a brief.
A paid trial piece
A trial piece shows how a writer works with your brief, your subject and your feedback, which samples cannot. As general practice, pay for it. A paid trial respects the writer's time, attracts experienced writers whom an unpaid test tends to put off, and gets their real effort. Agree the terms of the trial in writing first, as for any commission: the payment, whether you may publish the piece and on what terms, and the AI rules.
Use a real brief for a piece you would publish if it were good, and give each candidate the same brief, so the drafts can be compared fairly. Include one round of feedback in the trial, because how a writer responds to feedback matters as much as the first draft. Then judge the draft against the brief's own review criteria, not against how you would have written it. The same reasoning applies to linguists, and the guide to choosing and managing translation suppliers has the test piece judged by a reviewer who reads the target language.
| What to judge | What a strong trial shows | What a weak trial shows |
|---|---|---|
| The brief's question | Answered early and completely, for the brief's reader | A survey of the topic that answers nothing in particular |
| Claims and sources | Each claim sourced or flagged; nothing invented | Confident statements with no source, or sources that do not say what the draft says |
| Structure | Follows the outline, or explains a better order | Ignores the outline without saying why |
| House style | Matches the style guide's choices | The writer's own conventions throughout |
| Questions | Asked before drafting, about gaps in the brief | None, followed by guesses |
| Response to feedback | Fixes the pattern, not only the marked instance | Fixes each comment literally and repeats the problem elsewhere |
| Deadline | Met, or warned about early | Missed without notice |
What to send with every commission
A freelancer starts each piece with only what you send. The items that save most rewrites are the ones teams most often assume the writer already knows.
| Item | Why the writer needs it | Where it comes from |
|---|---|---|
| The brief | The goal, reader, question, angle, proof list, outline and review criteria | The content brief tutorial and the content brief template |
| The house style guide | Spelling, terms, tone, formatting and how sources are cited | The editorial style guide tutorial |
| Access to an expert | The first-hand material the piece needs | An interview slot booked before the commission is sent |
| Sources and examples | The documents the proof list names, and published pieces that show the standard | The brief's proof list; your best existing pages |
| Where the piece sits | The Content PillarOne of a small set of recurring themes that a brand's content is planned around., the slot in the Editorial CalendarA shared schedule of what content will be published, on which channel, when and by whom. and the pages it links to | The calendar and the brief's link list |
| The AI use policy | Which tools and uses are allowed, and the data rule | The policy the organisation already follows |
| Dates and rounds | When the draft is due, when feedback will come, how many revision rounds are included | Agreed for each commission |
The editorial standards behind the style guide, including how content is reviewed, approved and disclosed, sit in the content governance guide. Send the parts a writer needs; a freelancer should not have to read a governance document to find out how you spell a product name. The parts of the editorial standardsThe rules for how content is made and kept honest: who writes and reviews it, how claims are sourced, how it is funded, where AI helps and how it is corrected. worth sending are those that change the draft, such as how claims are sourced and what has to be disclosed.
Feedback that improves the next draft
Feedback has two jobs: to make this draft publishable, and to make the next draft need less of it. Comments based on taste do neither, because the writer cannot predict them. Give feedback against the brief's review criteria and the house style guide, so every comment points at something written down that the writer can apply next time.
A few habits make the difference, as general practice:
- Structure before sentences. If the draft answers the wrong question or follows the wrong order, say so first and hold back line edits that will be thrown away. The pass-by-pass routine in the writing for the web guide sets the order for an editor's work.
- Must-fix and suggestions, marked differently. The writer should know which comments block publication.
- Patterns, not every instance. Point out a recurring problem once, with two examples, and ask for it to be fixed throughout.
- One voice. Consolidate comments from every reviewer into one set before the writer sees them, and resolve contradictions yourself. Conflicting comments from several reviewers are one of the causes the production too slow page traces.
- The reason. "Cut this section because the reader at this stage already knows it" teaches; "cut this" does not.
Keep a short record of the feedback each writer receives. When the same comment appears for several writers, the gap is in the brief or the style guide, and the fix belongs there. Ask writers, too, what the brief failed to tell them.
Rights, AI use and bylines in writing
Agree the terms of the work in writing before it starts, not after the first piece is published. The questions below are general practice; the answers that carry legal weight are for your adviser. The copyright and training data guide frames ownership of work and what contracts with agencies and freelancers should say about AI use as questions for counsel, without legal conclusions, and this guide does the same.
| Question to settle in writing | What to discuss | Who answers it |
|---|---|---|
| Who owns the finished work | Ownership, and anything the writer keeps | Your legal adviser |
| Where it may be reused | Formats, channels, derivatives, translations, edits after publication | The content lead, then your adviser |
| Whether and how AI tools may be used | Allowed uses, tools, the data rule, what the writer tells you | The owner of the AI use policy |
| Confidentiality | What the writer may see, and what must stay private | Your adviser |
| Byline and credit | Whose name the piece carries, and how the writer is credited | The content lead, under the house policy |
| Portfolio use | Whether and when the writer may show the piece | The content lead |
| Payment | Terms as agreed, and paid on time | Whoever pays suppliers |
For AI use, the simplest arrangement is that the freelancer works to the same policy as the team. The AI use policy tutorial sets out how that policy is written: the uses allowed by tier, a data rule about what may go into any tool, review requirements and disclosure. Send it with the first commission, and ask the writer to say which tools they use and for what. Whatever the policy allows, the draft passes the same review gate as any other piece.
Bylines follow the rule in the AI-assisted content guide: a byline is the answer to the question Google's helpful content guidance suggests publishers consider, who created the content, and no piece goes out under a name that did not review it. A freelancer whose own experience the piece draws on can carry the byline. A freelancer who drafted from your expert's interview is usually credited as the house policy says, with the expert as the named author once the expert has reviewed the draft.
Finally, pay as agreed and on time. It is general practice rather than a rule from any source this site cites, and it is the single habit that most decides whether good writers come back.
Building and keeping a bench
A bench is a small group of writers who know your brief format, your style and your subject, and who can take a commission without a long induction. It is worth more than a long list of names, because each writer on it has already absorbed the feedback that a new writer would need again.
Keep a short record for each writer: the subjects and formats they handle well, the feedback they have received, their availability and the written agreements on file. Give the bench steady work and early sight of the calendar, so writers can plan around you. Share what their pieces did after publication, invite them to briefings with experts and treat them as part of the production process rather than a vendor at the end of it.
Review the bench against the same criteria as the trial: whether drafts answer the brief, how many revision rounds they need, whether deadlines hold and whether errors surface after publication. Spread pillars across writers so the programme does not depend on one person. A RACI matrix for the commission makes the roles explicit: the content lead accountable for what is published, the writer responsible for the draft, the expert consulted on substance, and each decision with one accountable owner.
A software company's freelance bench (illustrative)
Hazelpip Project Software builds a bench of two writers
Hazelpip Project Software, an invented project-management software company, has one content lead and a calendar of 8 pieces a month, of which she can draft 3. Review is not the problem: a product manager has a fixed weekly review slot. She shortlists 5 writers from referrals and from bylines in two trade titles her customers read, talks to each, and commissions paid trial pieces from 3, all from the same brief: a guide to running a project retrospective, with a 30-minute interview with a product manager offered to each writer. Judged against the brief's 6 review criteria, 2 drafts answer the question, source their claims and use the interview; the third is fluent but generic and skipped the interview. Hazelpip keeps the first 2. Every commission now goes out with the brief, the house style guide and a booked interview slot. Feedback comes from the content lead alone, in one document, against the criteria; by the fourth commission each writer's drafts need 1 revision round instead of 3. Each writer's contract, drafted with the company's adviser, records reuse rights for the website, newsletter and sales material, and attaches the AI use policy: outlining and grammar tools allowed, no customer data in any tool. Pieces carry the product manager's byline, with the writer credited as editor, once the product manager has reviewed them.
Common mistakes
- Hiring for drafting when review is the bottleneck. More drafts wait in the same queue. Check where pieces wait before commissioning.
- Choosing on writing polish alone. A fluent generalist writes a smooth summary of what is already published.
- Unpaid tests. Experienced writers decline them, and the ones who accept may not give a test their best work.
- Commissioning without a brief or style guide. The writer guesses, and the first draft becomes the brief.
- Feedback based on taste. The writer cannot predict it, so the next draft needs as much.
- Several reviewers commenting directly. Contradictory comments reach the writer, and the piece stalls.
- Rights and AI use settled after publication. Agree them in writing before the first piece starts, with your adviser on the terms that carry legal weight.
- A byline nobody reviewed. No piece goes out under a name that did not review it.
- Paying late. Good writers have other clients, and they will put them first.
- Depending on one writer. Spread the pillars, and keep the bench's records current.
