Proofreading and Quality Checks

Proofreading is a bounded quality-control service for documents that are already close to finished. The useful result is not a dramatic rewrite. It is a shorter list of concrete corrections: a misspelled customer name, a broken link, a date that conflicts with the approved schedule, a button label that does not match the heading, or a condition that disappeared during editing.

This R06 field guide explains how to test that service without claiming to replace a legal reviewer, technical editor, accessibility auditor, or subject expert. It is general education, not legal, tax, pension, insurance, or benefit advice. There is no income guarantee.

Opportunity and Customer

The best first buyer has one document set that must be accurate before release. Examples include a nonprofit annual report, a membership renewal notice, a conference program, a hiring pack, a product instruction sheet, a grant application, or a website page scheduled for publication. The buyer should be able to name the approved source and the person who resolves disagreements.

This offer fits organizations with a real release deadline but no dedicated proofreader. A communications coordinator may have checked the message while a program specialist owns the facts. A volunteer editor may have improved the flow while introducing inconsistent terminology. The proofreader compares the current draft with those approved inputs and reports uncertainty instead of guessing.

Avoid accepting "check everything" as a project. Define the artifact, version, source of truth, checks included, deadline, and approval route. A proofreading project should not silently become research, policy writing, or a full accessibility review.

Fit and Skills

Good proofreaders notice patterns and tolerate repetition. You need to compare names, dates, abbreviations, capitalization, page numbers, links, calls to action, and conditions without becoming distracted by every possible style preference. Patience matters more than a perfect memory because the work should be supported by a checklist and a second pass.

Plan for your access needs. Use the magnification, contrast, read-aloud, or large display that lets you see small differences. Work in a morning window if late-day eye fatigue creates errors. Take short breaks between the content review and the link check, then record the actual time so a future quote reflects your pace.

You can build a portfolio from public or fictional material. Ask a friend to insert twelve controlled errors into an approved sample, then show the original, the error list, and your correction log. Do not use an unpublished client document for practice.

Startup Budget

An illustrative discovery test may cost 0 to 90 currency units using an existing document editor, a browser, and a fictional sample. A first paid project may spend 20 to 220 on secure file storage, a professional email address, invoicing, a backup drive, and a month of an accessibility or language tool if an actual task requires it.

Keep a separate test budget and do not draw it from essential household reserves. For example, a monthly budget of 120 could cover 30 for storage, 25 for a domain email, 15 for payment processing, and 50 for local contract or privacy advice. The categories are illustrative and must be replaced with real local prices.

Before buying software, measure the obstacle. A spell checker may be included in an approved editor. A link checker may be unnecessary for a five-link memo. A new subscription is justified only when it shortens verification without hiding the evidence.

Skill Acquisition

Learn a fixed sequence:

1. Confirm the draft version and source of truth.
2. Read once for the reader's task, without editing.
3. Check names, dates, numbers, prices, and conditions.
4. Check spelling, punctuation, capitalization, and repeated wording.
5. Check headings, lists, captions, links, and calls to action.
6. Trace every change back to a source or a stated style rule.
7. Separate objective errors from subjective suggestions.

Create a one-page style sheet for the project. It might standardize dates, organization names, currency symbols, phone formats, product capitalization, and serial commas. Do not impose your personal preference when the customer has an approved standard.

Practise a document with mixed English variants, repeated section titles, changing dates, and a link hidden behind the same label twice. Learn how to report "two sources conflict" rather than choosing the more plausible fact.

Setup

Create separate copies for the received draft, working version, and approved final. Record the file hash or version timestamp if available. Keep a correction log with location, original text, proposed text, evidence, severity, and owner decision.

Ask whether the customer wants in-line edits, comments, or a separate issue list. If the document will be published in multiple formats, state which format is authoritative. A correct web page can still differ from a PDF if one version is updated later.

Confirm copyright, confidentiality, records, and industry requirements in the relevant jurisdiction. Some material may contain personal stories, unpublished financial details, or information restricted by an ethics policy. Ask before external tools are used.

Set two review rounds at most for a pilot. A third round should be a new scope if it adds document sections or changes the approved source.

Concrete Offer

An illustrative offer: "I will proofread one approved document of up to 1,500 words against your named source and style sheet. I will correct spelling, punctuation, capitalization, repeated names, visible date and number conflicts, internal links, labels, and stated calls to action. You receive a marked copy, a correction log, and one short question list. One consolidated revision check is included. I will not certify legal accuracy or complete an accessibility audit."

The deliverable is a traceable correction set, not a promise that the publication will be error-free. A customer who needs meaning changes, new facts, technical validation, or accessibility testing should receive a referral or separate scope.

Outreach

Build a list of small organizations whose public documents show a forthcoming change. Look for outdated event pages, mismatched staff listings, or documents with clear release dates. Do not send a public list of their errors or imply incompetence.

A respectful message: "I provide final proofreading for small teams before a document is released. If you have an approved draft, source sheet, and one reviewer, I can check names, links, dates, and stated conditions and return a correction log. Would a sample scope for your next update be useful?"

Ask whether the buyer already uses an editor, a communications lead, or a volunteer proofreader. Position the service as a final check with a paper trail, not a replacement for their expertise. Referrals often come from designers, grant writers, event coordinators, and web maintainers who see the final errors too late.

Pricing and Unit Economics

Estimate the document, not just the word count. Intake, style-sheet setup, proofreading, link checks, questions, revision verification, and handoff all consume time. Dense tables and many cross-references take longer than ordinary paragraphs.

Illustrative arithmetic: a 1,200-word report takes two hours for the first pass, one hour for fact and link checks, forty-five minutes to prepare the log, and thirty minutes for the revision check. If the fee is 315 and direct costs are 15, contribution is 300 across 4.25 hours before tax and general overhead. If the customer adds fifty pages, the quote must change.

Use a minimum project fee or a clearly capped package. Charge for rush work only if the schedule is safe. Do not accept responsibility for facts the customer refuses to confirm. Keep an emergency reserve for rewriting a confused deliverable caused by a wrong source, but do not budget that risk as free unlimited labor.

Delivery Example

The following composite is fictional. A community arts group plans to publish a workshop calendar. The draft and event database are approved inputs. The coordinator says the database is authoritative for dates and prices, while the program manager owns accessibility wording.

The proofreader finds that one workshop time differs between the main heading and the registration section. AI suggests "correcting" the heading to the later time, but the governed source confirms the earlier start. The proofreader marks the registration text for correction and leaves the heading unchanged. The provider also spots that a "Register" button appears twice with different destinations and that a caption names the wrong room.

The reviewer decides which link is current. The proofreader verifies the updated page without redesigning it. At handoff, the coordinator receives a marked draft, a log grouped by severity, a list of unresolved facts, and confirmation that the approved version replaces the earlier file.

Growth

Grow by repeating the same document family and release cycle. Build reusable style sheets for a monthly newsletter, quarterly report, or standard event page. Offer a recurring pre-release check with a capped word and link count. Do not expand into legal certification or technical editing merely because a customer asks for "one more opinion."

Track words or pages reviewed, correction time, review cycles, missed-error reports, and payer delay. If two small projects produce more sales and setup time than editing, raise the minimum or package an update block. Keep a short weekly limit that protects care duties and rest.

Risks

The main risk is pretending to guarantee perfection. Errors can remain, links can fail after publication, and a downstream editor can undo a correction. Define the reviewed version and the verification date. State that final publication belongs to the customer.

Meaning changes are another risk. A grammar correction can alter a legal condition or weaken a safety warning. Preserve the original clause and flag ambiguity for the owner. Do not "fix" a factual conflict unless the approved source resolves it.

Payment processing, taxes, and pension or benefit reporting may be affected by earned income. Ask local advisers or agencies about the rules that apply to your situation. This guide does not promise that the service will earn a target amount or fit every retirement income plan.

Privacy and AI Verification

Receive files through the customer's approved channel or a storage location with access controls. Keep only the data needed for the assigned document. Do not use a personal cloud account for a confidential draft. Check whether retention rules require deletion after the project.

AI can identify possible spelling errors, inconsistent terms, or broken Markdown syntax, but it can also invent a correction and overlook visual context. A human checks every number, condition, link destination, and approval decision against the source. AI output never becomes the fact owner.

If a document includes personal information, remove it from prompts or decline the task. Never put passwords, identity documents, unpublished financial data, or sensitive participant records into a consumer model without explicit organizational permission and suitable data terms.

Stop Conditions

Stop if the customer cannot identify an authoritative version, if facts conflict with no owner able to resolve them, if the work requires legal certification, or if the deadline no longer allows verification. Stop if a reviewer repeatedly adds new sections after each proofreading round.

Stop if privacy controls are inadequate, if you are asked to conceal a material error, or if the project has moved into technical, medical, or regulated advice. Also stop when the fee cannot cover measured delivery time.

At a personal level, pause if eye strain, fatigue, care obligations, or a benefits question makes the schedule unsafe. A small proofreading test should not consume protected savings or turn every weekend into an emergency shift.

30-Day Action Plan

Days 1 to 3: Select one document type and list the checks the service will and will not perform. Record routine hours, access needs, and a maximum test loss.

Days 4 to 7: Create a fictional twelve-error sample and a style sheet. Name twenty small organizations that publish this document type.

Days 8 to 12: Run a full proofread against a fictional source. Record time per pass, correction categories, and unresolved questions. Test whether AI improves the process or creates extra verification work.

Days 13 to 17: Contact twelve prospects with a specific offer for an approved draft. Ask what source is authoritative and who approves corrections.

Days 18 to 21: Confirm one pilot's scope, data channel, revision limit, price, and delivery date. Capture the received version before editing.

Days 22 to 27: Deliver the marked copy and correction log. Verify corrections against the source, not against memory. Obtain written acceptance of the reviewed version.

Days 28 to 30: Compare fee, time, direct costs, correction usefulness, and personal fit. Continue with the same document family, revise the offer, or stop.

Templates

Proofreading scope

• Draft version and owner
• Authoritative source
• Reader and publication date
• Word or page cap
• Style sheet
• Checks included
• Checks excluded
• Reviewer and conflict resolver
• Data channel and deletion date
• One revision check
• Price and final stop date

Correction log

• Location
• Original text
• Proposed correction
• Error category
• Evidence or rule
• Severity
• Owner decision
• Verification result

Handoff note

"The attached version was checked against [source] on [date]. I corrected the items in the log and marked unresolved facts for your decision. I did not certify legal, medical, technical, or eligibility accuracy. Please approve the corrected version before publication."

This guide is educational. Obtain current local advice about operating, tax, insurance, pension, privacy, and consumer obligations, and test demand before relying on proofreading as sustainable income.