Plain-Language Editing

Plain-language editing is a useful service when a small organization has an important document that readers struggle to understand. The editor reduces unnecessary complexity, improves headings and sentence flow, and makes instructions more accessible. The work is not a licence to simplify away legal conditions, technical distinctions, safety warnings, or uncertainty.

This R05 field guide is written for a retiree who wants a bounded editorial project with a clear review step. It assumes that you may work in short sessions, need accessible reading tools, and want to avoid becoming a full-time legal or compliance adviser. This is general education, not legal, medical, tax, insurance, pension, or benefit advice. It does not promise better comprehension, fewer support calls, or business results. There is no income guarantee.

Opportunity and Customer

A strong first customer has one recurring document that ordinary readers must use. Examples include a membership renewal notice, a volunteer handbook section, a service cancellation policy, a patient-intake instruction sheet, a grant applicant checklist, or a local program eligibility page. The buyer should be able to show a current version, a reader complaint, a support question, or a documented accessibility concern.

Avoid positioning the service as "make everything sound friendly." Friendly language can accidentally weaken a condition. Choose one document type and define the intended reader, their task, and the part that must remain exact. Ask who owns legal meaning and who can approve a change.

The buyer might be an operations manager, nonprofit director, communications lead, or small business owner. The provider can propose structure and wording, but the owner must approve any substantive change. A subject-matter expert, legal reviewer, or regulated professional should sign off where the document affects rights, money, health, safety, or eligibility.

Fit and Skills

Plain-language editing requires curiosity and restraint. You need to notice confusing structure, long sentences, jargon, ambiguous pronouns, hidden conditions, and visual barriers. You also need to know when not to change a word because it carries a legal or technical distinction.

Build a small portfolio using fictional documents. Before drafting, write the reader's task and the facts that must remain unchanged. Then show a before-and-after version with annotations explaining each edit. A simple, explicit example is more persuasive than a claim to have edited "hundreds of documents."

Accessibility matters in your own workflow. If small type or eye fatigue affects you, use magnification, high contrast, read-aloud, or a larger display. A short morning editing window may produce better judgment than a long afternoon sprint. State a reasonable review turnaround and avoid promising instant edits for documents you have not seen.

Startup Budget

Illustrative discovery can cost 0 to 80 currency units using existing document tools, a fictional sample, and a short call. The first paid project may cost 20 to 250 for a professional email address, secure file storage, invoicing, accessibility software, and a backup copy. A major grammar subscription is not required before a customer values the result.

Ask which platform the customer uses and whether the document can be shared with tracked changes. Keep the original file and your working copy separate. Reserve some money for local contract and privacy advice if the document contains personal information. A document may look ordinary while including health, financial, or identity details.

Do not spend essential household reserves on editing software. Test one workflow on a sanitized sample, then buy only the tool that removes a measured obstacle. A maximum test loss and a written stop date make it easier to decide when the experiment is not producing paid work.

Skill Acquisition

Learn a repeatable editing sequence:

1. Identify the reader, task, and consequence of misunderstanding.
2. Mark facts, conditions, and terms that cannot change.
3. Outline the information in the order a reader needs it.
4. Rewrite one section at a time in short sentences.
5. Check every number, name, date, condition, and cross-reference.
6. Ask a subject-matter reviewer to compare meaning.
7. Test the final document with a real reader when the customer permits.

Use a test document with sections that contain exceptions and nested conditions. Practise turning passive or abstract wording into a direct instruction without removing who is responsible. For example, "Requests may be denied" should become "The office may deny a request when [condition] only if that is truly what the source says." Do not invent the condition to make the sentence clearer.

Read the final version aloud. This catches clauses that look acceptable on screen but are hard to follow when heard. Test headings and link labels without relying on color or surrounding layout. Ask whether the intended reader can find the next action.

Setup

Write a project scope that names the document, reader group, word limit, allowed level of intervention, review owner, revision rounds, delivery format, and completion date. Decide whether you are editing structure, sentence clarity, spelling, or accessibility, and state which services are excluded. If the customer asks for legal simplification, respond with a proposed clarity edit and require specialist approval.

Create separate files for the source, working copy, change log, reviewer comments, and final approved version. Use version names and an issue date. Preserve every number and condition in the change log so the reviewer can compare meaning rather than only reading a clean final paragraph.

Confirm privacy, copyright, records, and industry requirements in the relevant jurisdiction. A document may belong to a regulated service, contain personal examples, or reuse third-party guidance. Do not copy a style guide or template you do not have permission to use.

Set a review process. A good pilot leaves the customer responsible for substantive approval and gives them a short list of unresolved questions. The editor should not silently resolve contradictions between two source documents.

Concrete Offer

An illustrative offer: "I will produce a plain-language edit of one approved document of up to 1,200 words, preserving all names, numbers, conditions, and cited rules. The pilot includes a reader-task brief, a marked draft, a clean draft, and one revision round. Your subject-matter reviewer approves every substantive change. I will not provide legal, medical, financial, or eligibility advice."

The customer buys a clearer draft and a traceable change process. The composite example does not promise a particular result. After a successful document, offer a small review block for another document in the same family or a quarterly consistency pass. Keep each document and each review cycle priced separately.

Outreach

Look for small organizations with public documents that contain long paragraphs, nested conditions, unclear headings, or important instructions buried in general text. Do not publicly criticize the organization's intelligence or claim that its current document is defective. Describe the workflow you offer and ask about the reader's actual difficulty.

A message could say: "Hello [Name], I help small organizations make routine instructions easier to scan while preserving every condition and reference. I noticed [specific public document or update]. Would a short conversation about where readers usually ask for clarification be useful? A paid diagnostic can compare the current document with a proposed structure."

Use referrals from a satisfied reviewer, a professional association, or a local accessibility group when available. Track whether the source produces a document conversation, a paid diagnostic, and a completed edit. Mass messaging is less useful than a small, carefully researched list.

Pricing and Unit Economics

Estimate the entire project: intake, source review, editing, change log, clarification questions, one revision round, and final cleanup. Include the time needed to learn the document's terms and to wait for expert review. A low per-word price can become poor value when every paragraph requires a specialist call.

An illustrative calculation: a 900-word document takes three editing hours and two hours of review and administration. If the fee is 360 and direct costs are 20, contribution is 340 across five hours before tax and general overhead. If the customer adds a second document without a new scope, the contribution may fall. If specialist review takes two more hours, the project may no longer meet the provider's floor.

Set revision limits and a late-change rule. Request a deposit when the document owner may delay. Do not price a regulated handbook as an ordinary marketing edit. Protect cash by sending an invoice with clear terms and a due date.

Delivery Example

This illustrative composite is fictional. A small community center needs an intake instruction guide for a fall program. The current document mixes eligibility, forms, dates, and a payment condition in long paragraphs. The provider receives an approved source file and a named reviewer. The customer rejects any change to the eligibility wording until a program specialist confirms it.

The editor outlines the reader's journey, adds task-based headings, breaks one sentence into a list, explains an abbreviation, and removes repeated commentary. AI suggests shorter alternatives. The editor compares the cleaner version with the source and notices that an AI edit changed "may be available" into "is available." The editor restores the original condition and flags the sentence for the reviewer.

The specialist approves the eligibility section after a short conversation. The editor updates a link label and checks that the reading order makes sense without the visual layout. At handoff, the customer receives a marked draft, clean draft, change log, unresolved question list, and approval note. The provider records the actual hours and decides whether the offer should include one or two revision rounds.

Growth

Grow by repeating the same document family and reader task. Standardize the intake questions, tracked-change format, and review checklist. Do not advertise a general promise that all documents will produce better outcomes. Add a second service only when a customer asks for a measurable next result, such as a document index or an accessibility review.

Track delivery hours, review hours, number of unresolved questions, correction rate, and repeat work. If small projects create excessive sales and setup time, raise the minimum project size or sell a document-family package with a clear cap. Keep time for administration and rest.

Risks

The central risk is changing meaning. A clearer sentence can remove a condition, create a promise, or shift responsibility. Keep a source comparison and require subject-matter approval. Do not accept a request to make a vague policy sound certain without an authoritative decision.

Copyright, personal stories, and confidential policies can create permission issues. Working with accessibility tools does not automatically make the final document accessible to every reader. Test the format and ask for feedback where possible.

Paid editing can affect tax, pension, or benefit reporting. Confirm local rules with the relevant agency or adviser. The guide does not imply that an editing business will produce a particular amount of income, reduce support requests, or improve a measured comprehension score.

Privacy and AI Verification

Keep source documents in approved storage. Remove unnecessary personal details from any sample or AI prompt. Do not upload a customer's confidential policy, unpublished price, or personal story to a consumer tool without explicit permission and adequate data terms.

AI may suggest sentence structure, plain replacements, headings, and missing transitions. A human verifies every number, condition, reference, variation in meaning, and source citation. The subject-matter reviewer has the final authority on substance. Keep an edit log that distinguishes clarity changes from factual changes.

Stop Conditions

Stop if the owner cannot identify a meaning reviewer, if the source contains contradictions that nobody can resolve, if the requested work has become legal or regulated advice, or if the document keeps expanding without a new scope. Stop if a late source changes the purpose after the draft is already under review.

Set personal limits for daily reading, revision rounds, and maximum project loss. If eye strain, fatigue, care duties, or a benefits reporting question makes the schedule unsafe, pause. A small editorial experiment should not consume the reserve that supports your chosen life.

30-Day Action Plan

Days 1 to 3: Choose a document type and reader task. Record available editing hours, accessibility needs, test budget, and any local question.

Days 4 to 7: Create a fictional before-and-after sample and a source-preservation checklist. Name 20 organizations with a plausible review document.

Days 8 to 12: Test one full edit with and without AI. Record time, corrections, and specialist questions. Simplify the offer if the sample is too large.

Days 13 to 17: Contact 12 to 15 prospects with a specific, respectful observation. Offer a small paid diagnostic or document edit.

Days 18 to 21: Agree on the reviewer, source hierarchy, revision limit, and data handling. Capture the original file and create a change log.

Days 22 to 27: Deliver the first version, verify every condition, and get substantive approval. Do not publish or replace the source until the owner approves.

Days 28 to 30: Review contribution, time, corrections, reviewer usefulness, and personal fit. Continue with a same-family document, revise the scope, or stop.

Templates

Edit brief

• Document and owner
• Reader group and task
• Source of truth
• Facts, conditions, and terms that cannot change
• Allowed intervention level
• Subject-matter reviewer
• Revision rounds and deadlines
• Files and data limits
• Price and stop date

Meaning-preservation check

• Names and organizations
• Dates and time windows
• Numbers, percentages, and prices
• Who must act
• Conditions, exceptions, and eligibility
• Links and references
• Safety or legal warnings
• Reviewer comments and unresolved issues

Reviewer handoff

"The attached clean draft should mean the same as the approved source. I changed structure and wording to improve readability. The following source passages need your explicit decision: [list]. Please mark each as approved, revise, or remove. No external publication is authorized by this handoff."

This guide is educational. Obtain local advice before relying on the work for tax, insurance, pension, privacy, or regulated-content decisions, and test demand before treating the service as sustainable income.