Copywriting, Content and Editorial Writing

01Purpose and scope

• This manual supports the course Copywriting, Content and Editorial Writing and serves as a working reference for how written material is planned, drafted, edited, approved and measured in professional settings. It treats three related kinds of work as one discipline: persuasive copy that asks a reader to act, content that informs or helps a reader complete a task, and editorial writing that shapes the argument, voice and accuracy of a piece under a publication's standards.
• The manual covers the main activities, decisions and deliverables that appear in most of these roles. Those include briefs, outlines, drafts, revision rounds, fact checks, legal or brand review, publication and performance reporting. It does not teach grammar from first principles or replace a house style guide, and it does not cover visual design, although writers often work alongside designers and need to know where their text ends and layout begins.
• Practice changes a great deal by context. A product page written for a retail site, a feature article for a magazine, a benefits explainer for an insurer and a internal policy update all share the same basic moves, but they differ in who approves them, how much risk they carry and how success is judged. Where this manual gives guidance on regulated claims, financial or health information, or legal wording, it describes what to look for and what to ask. It does not replace qualified professional judgment, the approved procedures of the organization, or any required authorization from a reviewer with the right credentials.

02Core principles

• Every piece starts with a single clear purpose. A writer should be able to state in one sentence what the reader should know, feel or do after reading, and who that reader is. If the purpose needs two sentences or includes the phrase and also, the scope is probably too wide and should be split into separate pieces or narrowed before drafting begins.
• Specificity beats generality. A line such as faster checkout with fewer steps is weaker than one that names the number of fields removed or the screen the customer no longer sees, provided the claim is true and can be substantiated. Concrete nouns, plain verbs and named examples make copy more believable and easier to edit, because reviewers can check them against source material.
• Accuracy is a working requirement, not a final polish. Every factual statement, quotation, figure and product feature needs a traceable source that the writer, editor or subject expert can point to. Writers should avoid inferring facts from memory or from competitor material, and should mark anything unverified rather than leaving it to be discovered later.
• Voice is set by the audience and the publisher, not by the writer's preferences. A consistent voice reduces friction for readers and reviewers alike. Editorial writing often carries a stronger obligation to fairness and attribution, while promotional copy has more latitude in tone but less in unsupported claims.
• Editing is a separate act from drafting. Drafting should aim for completeness and momentum. Editing should test whether each sentence earns its place, whether the structure serves the reader and whether the claims survive scrutiny. Writers who try to do both at once usually produce slow drafts and shallow revisions.

03Planning and preparation

• Most problems in written work trace back to a weak brief. A usable brief names the deliverable and its format, the target length, the channel or publication, the audience, the purpose, the required terms or disclaimers, the sources to be used, the approval path and the deadline. For a landing page, the brief might also include the offer, the conversion action, the price or terms that must appear, and the names of the legal or brand reviewers. For a long article, it should include the angle, the interviews already completed and the editorial standard the piece must meet.
• Research comes before outlining. The writer should collect primary sources where possible, such as product specifications, interview transcripts, policy documents, datasets or the publisher's own reporting, and then sort them by reliability. Secondary material such as summaries or aggregators is useful for context but should not be the only support for a factual claim. Keep a source log with links or document references, the date the source was accessed, and the claim it supports. Note that this log is for the team's internal use and is not published.
• Outlines should be built around the reader's questions rather than the writer's notes. For copy, that usually means mapping objections, doubts and next steps. For content and editorial pieces, it means ordering information so that each section answers the question raised by the one before. A good outline is short enough to review in five minutes and specific enough that a reviewer can tell whether the piece will do its job.
• Preparation also includes deciding what not to say. Some claims are legally or commercially risky, some would require approval the writer does not have, and some would undercut the publisher's credibility. Agree on these limits before drafting so that they are not discovered during the final review.

04Recommended workflow

1. 1
   : Confirm the brief in writing with the person who owns the deliverable. Record the purpose, audience, format, length, channel, approvers and deadline, and ask the owner to resolve any conflicts between them, such as a short deadline for a piece that needs expert review.
2. 2
   : Gather and log sources. Pull product data, interview notes, policy text or published research into a shared folder, and record for each source what it supports. Flag any statement that currently has no source so it can be verified or removed.
3. 3
   : Build the outline. Write the working title, the single-sentence purpose, the main sections or sequence of messages, and the key evidence for each section. Send the outline to the owner for a quick agreement on direction before drafting, because a change at this stage costs far less than a change after full drafting.
4. 4
   : Draft for completeness. Write the full first version without stopping to polish. Use bracketed placeholders for missing facts rather than guessing. Keep a separate note of any claim that needs substantiation or legal review.
5. 5
   : Self-edit for structure and clarity. Read the draft aloud or in a plain text view. Check that the opening states the point, that each paragraph does one job, that transitions are clear and that the call to action or conclusion matches the stated purpose. Cut repetition and any sentence that only restates the one before.
6. 6
   : Verify facts and claims. Check every number, name, quotation, date and product feature against the source log. Confirm that quotations are accurate and that attributions are fair. For claims about results, savings or performance, confirm that the evidence exists, that it applies to the audience being addressed and that the comparison is valid.
7. 7
   : Run the editorial or line edit. A second editor should check style, consistency of terms, grammar, reading level and the house style guide. In a publication, the managing editor or section editor usually decides on fairness, sourcing and tone. Track changes so that each revision can be explained.
8. 8
   : Route for legal, brand, medical or financial review where required. Send the marked version with the claim log attached, so reviewers can see exactly what needs their judgment. Do not treat their approval as a general sign-off on the whole piece. Record their decisions and any conditions they set.
9. 9
   : Publish, schedule or hand off to production. Confirm that the final text matches the approved version, that links work, that metadata such as titles and descriptions are filled in and that required disclosures appear where they should. Keep the approved version archived with its approvals.
10. 10
    : Monitor and record outcomes. Track the indicators agreed in the brief, review them at the set interval, and note what the writer would change next time. Feed these notes into the next brief rather than letting them remain in a private file.

05Quality checks, risk controls and compliance

• Quality checks should be applied in layers. Structural checks confirm that the piece fits its format and purpose. Factual checks confirm that every verifiable statement is supported. Language checks cover grammar, consistency of terms, reading level and tone. Compliance checks cover the rules that apply to the specific claim or audience. Keeping these separate helps reviewers focus on the risk they are best placed to judge.
• Advertising and promotional copy carries specific legal risk in most markets. In the United States, for example, the Federal Trade Commission's guidance on advertising, endorsements and testimonials sets expectations about substantiation, disclosure of material connections and misleading net impressions. Other countries and regions have their own rules on comparative claims, pricing, consumer protection, data use and accessibility. These rules depend on jurisdiction and change over time, so the writer should confirm the current requirements with the organization's legal team or the relevant regulator rather than relying on this manual.
• Health, financial, tax and legal content carries higher risk because readers may act on it in ways that cause real harm. Guidance in these areas should be reviewed by a qualified professional with authority over the subject, and should follow the organization's approved procedures. Writers should avoid language that promises outcomes, implies personal advice or presents a general rule as applicable to a specific person's situation. This manual does not replace that professional judgment or any required authorization.
• Editorial writing has its own risk controls. These include a clear separation between reporting and opinion, correction procedures when errors are found, right of reply for people named in critical pieces, and care with anonymous sources. Where a publication has a written ethics code or corrections policy, follow that document rather than a general practice.
• Accessibility and inclusive language should be checked for every public piece. Use descriptive link text, avoid meaning that depends only on color or position, and keep sentences readable for a broad audience. Where accessibility standards apply, such as the Web Content Accessibility Guidelines published by the W3C, check the current version and the level required by the organization.
• Plagiarism and reuse need checking as well. Quotations should be marked, paraphrases should be attributed where the source matters, and content reused from another publication should have permission or a licensing basis. Keep a record of any reused material in the source log.

06Collaboration and documentation

• Most written work involves several people. A subject matter expert supplies facts, a designer shapes layout, a product manager sets the offer, a legal reviewer checks risk and an editor controls the final version. Clear roles prevent the common problem of too many reviewers rewriting the same sentence. Agree in advance who has the final say on facts, who on tone, who on compliance and who on publication timing.
• Use one source of truth for each piece. A shared document with version history or a content management system works well, but comments should be resolved in the document rather than passed around in separate emails. When a reviewer changes wording, the writer should know why, and should be able to accept, reject or modify the change with a short note.
• Keep a decision log for each piece. Record the date of each significant decision, who made it, what was decided and why. This is especially important when a claim is removed at legal review or when an editor overrides a writer's recommendation on framing. The log protects the team if questions arise later and helps new team members understand past choices.
• Feedback should be specific and tied to the brief. Comments such as this feels off are hard to act on. Better comments name the sentence, state the concern, such as the claim lacks a source or the tone is more aggressive than the audience expects, and suggest a direction. Writers should respond to each comment, even if only to say it has been considered and declined.
• Working across contexts changes the documentation load. A fast-moving social campaign may need only a brief and an approval record, while a regulated financial guide may need a full claim log, multiple sign-offs and archived versions. Match the level of documentation to the risk and to the requirements of the publisher or client, rather than applying one template to everything.

07Measures and continuous improvement

• Measures should match the purpose stated in the brief. For conversion copy, typical indicators include click-through rate, completion of the target action, bounce rate on the landing page and the rate of returns or complaints linked to the promise. For content, useful indicators include time on page, scroll depth, search visibility for target queries, return visits and completion of the task the content supports. For editorial work, measures often include corrections issued, reader feedback, citation by other outlets and the outcome of any fact-check escalations. No single indicator tells the whole story, and attribution across channels is usually imperfect.
• Set a baseline before a new piece or change goes live where possible. Without a baseline, it is hard to tell whether a rewrite improved results or whether seasonal demand or a pricing change did the work. Compare like with like, and be cautious about drawing firm conclusions from small samples or short periods.
• Use testing where it fits. A/B tests on headlines, calls to action or introductions can show which version performs better for a defined audience. Testing requires enough traffic to produce meaningful results, and it should not be used to test claims that are not substantiated in the first place. Record test design and results so that the team can build on them.
• Review the pieces that underperform or cause problems. A post-publication review should ask whether the brief was clear, whether sources were sufficient, whether the review path worked and whether the audience reacted as expected. Summarize the lessons in a short note and attach it to the brief template or style guide where it will be seen by the next writer.
• Continuous improvement also means updating reference material. Style guides, claim libraries, approved phrases and disclosure templates go out of date as products change and rules are revised. Assign an owner to each reference document and set a review interval that suits the risk, with more frequent reviews for regulated topics.

08Common mistakes and how to prevent them

• One common mistake is writing before the purpose is clear. The result is a draft that tries to do too many things and satisfies no one. Prevent it by requiring the single-sentence purpose in the brief and confirming it with the owner before drafting begins.
• Another frequent error is an unsupported claim that slips through because it sounds reasonable. Phrases such as the fastest, most trusted or clinically proven need evidence and a clear basis for comparison. Keep a claim library of approved wording and route any new claim to the person who can substantiate it.
• Writers also tend to bury the main point in long introductions, especially in editorial pieces. Ask whether the first two paragraphs would still make sense to a reader who stopped there. If not, move the key information up.
• Editors sometimes change facts when they are trying to improve flow. Prevent this by making fact checks a separate step that happens after the final line edit, and by keeping the source log linked to the text so that changes are visible.
• Reviewers may rewrite the whole piece to suit their own taste. This creates inconsistency and extends timelines. Limit review to the scope of the reviewer's role, and ask that stylistic preferences be raised as suggestions unless they conflict with the style guide.
• Finally, teams often skip the measurement step, which means the same mistakes repeat. Build measurement into the brief and set a review date at the time of publication so that someone is responsible for following up.

09Practical checklist

• Confirm the purpose, audience, format, length, channel, approvers and deadline in writing before drafting.
• Log every source and the specific claim it supports, and mark any unsupported statement.
• Check that the opening states the main point and that each section does one job.
• Verify all figures, names, quotations, dates and product features against the source log.
• Route claims about results, comparisons, health, money, law or tax to the qualified reviewer.
• Confirm required disclosures, terms and accessibility features are present in the final version.
• Keep the approved version, the claim log and the reviewer decisions archived together.
• Record the agreed indicators and set a date for the post-publication review.
• Update the style guide, claim library or brief template with any lessons from the piece.

★Learning sources

• Micro Degree: Copywriting, Content and Editorial Writing
• Micro Degree: 2D Animation Fundamentals
• Micro Degree: 3D Animation Techniques
• Micro Degree: Illustration Fundamentals