← Earn Online Cookstown · All 125 ideas

Writing & creative · Budget: £0 to £500 · Minimum age: 16+

Technical writing

Technical writing means creating clear, useful content about technical products, services or processes, such as user guides, API documentation and reports. This beginner module focuses on building practical samples and learning how to work with subject matter experts.

Open the interactive guide (checklist, video, read-aloud) →

In plain words

Who it suits

It may suit you if you enjoy explaining how things work, checking details and making complex information easier for a particular audience to use. You do not need to be a technical writer to learn from the GOV.UK technical writing community, although its community is for people working in the public sector or interested in this work.

People and organisations pay for writing that helps readers use products, services or processes correctly. Clear instructions can save time, reduce confusion and help people complete tasks.

Step by step

  1. Choose a subject, reader and task. Pick a subject you understand, such as setting up an app or following a familiar process. Write down who the guide is for and what that reader needs to do. About 20-30 minutes.
  2. Study examples of technical writing. Read a few guides and note what makes each one easy or difficult to use. The GOV.UK style guide covers technical terms, code and instructions GOV.UK. About 30-60 minutes.
  3. Draft a short how-to guide. Use a fictional product or a process you know well. Put the reader’s task first, use plain language, and make each step describe one action. About 1-2 hours.
  4. Ask a reader to test your guide. Choose someone similar to your intended reader and ask them to follow the guide without your help. Note where they pause, ask questions or misunderstand, then revise those parts. About 30-60 minutes, plus any revision.
  5. Create a second writing sample. Try a troubleshooting note, short report or glossary. A fault report can briefly say where and when a fault happened and how it was fixed Emphasis. About 1-2 hours.
  6. Practise checking source information. Gather notes and mark what is confirmed, unclear or conflicting. Ask a subject matter expert to confirm details; technical writers may do this as part of their work Fiona Hurley on LinkedIn. About 1-2 hours.
  7. Learn shared editing and version control. Practise making a small edit, saving a version and recording what changed. The GOV.UK community lists Git and GitHub learning resources and examples of writers using GitHub GOV.UK Service Manual. About 1-3 hours.
  8. Prepare a small, safe portfolio. Include your samples, who each is for and what task it helps with. Add a short note about what you changed after feedback, and remove confidential or private material. About 1-2 hours.
  9. Apply for suitable work and agree terms. Look for entry-level, contract or freelance opportunities and tailor each application to the subject and reader. Before starting, agree the deliverables, review process, deadline and payment terms in writing. About 1-2 hours per application.

Your first 15 minutes

Write a one-page guide for a fictional product, ask someone unfamiliar with it to follow the instructions, and revise the guide using their feedback.

The money

Price by the agreed task and scope, taking account of research, drafting, revisions and meetings. Set out what is included, the deadline and payment terms before work begins; do not assume that a sample or first project will lead to paid work.

Example only: UK week: £120 income from two agreed pieces − £10 costs = £110 before tax. Ireland week: €160 income from two agreed pieces − €12 costs = €148 before tax. These are illustrative amounts, not typical rates or an exchange-rate comparison.

The rules

There's no specific writing licence for this work. Tax and data-protection rules can still apply. Check your situation with HMRC or Revenue, and check with the relevant data-protection body if you handle personal information.

UK and Northern Ireland

Ireland

Checked against official sources: 22 October 2026. Not yet reviewed by a qualified tax or legal adviser. General guidance, not legal advice. Check the official link beside each point before you start.

Common mistakes

AI-made demonstration: this module has a 20-second street-chat video in the interactive guide. The presenter and the people in it are computer-generated, not real people.

Free community guide for Cookstown, Mid Ulster and anyone in the UK or Ireland. Nothing is for sale. About this site, AI, sources and privacy.