Editorial Review and Quality Assurance

Line Edit Pass

Improve flow, precision, rhythm, emphasis, paragraph movement, and voice at sentence level without changing verified meaning or reopening settled structure.

Free editable Markdown · Line editors, writers, and editorial teams · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Pass setup

Draft and version: [File or URL]
Audience and task: [Reader outcome]
Writer: [Name or role]
Line editor: [Name]
Source record: [Links]
Style and voice guides: [Versions]
Out of scope: [Structural, factual, legal, or another review]
Due date: [YYYY-MM-DD]

Paragraph review

Paragraph ID: [Heading and number]
Primary job: [Context, claim, evidence, example, action, or another]
Meaning risk: [Ambiguity or None]
Precision change: [Vague to specific]
Sequence change: [Move and reason]
Emphasis change: [What should land?]
Rhythm issue: [Repetition, clause load, or monotony]
Query: [Question for writer]

Line-edit checks

Subjects and actions are clear where clarity matters.
Conditions remain beside the claims they qualify.
Stronger certainty was not introduced without evidence.
Pronoun and demonstrative references are unambiguous.
Repetition has a reader function or was removed.
Voice remains recognizable without formulaic phrasing.
Quotations and first-hand details retain their meaning.

Handoff

Material queries: [IDs and decisions needed]
Fact checks triggered: [Claim and owner]
Structural issue discovered: [Location and recommendation]
Accepted voice decision: [Boundary example]
Next pass: [Copyedit, proofread, specialist review, or another]
Signoff: [Writer and editor status]

How to use this template

Confirm the brief, audience, approved structure, source record, style guide, and boundaries of the line edit.
Edit one paragraph at a time for meaning, precision, emphasis, sequence, and rhythm.
Query changes that affect facts, interpretation, attribution, voice, or a writer’s first-hand experience.
Read the revised draft aloud and compare material claims with the source and original.
Review tracked changes, resolve queries, and hand off remaining copyedit or structural work explicitly.

Edit for meaning before elegance

Identify the subject, action, object, condition, and emphasis of each important sentence. Replace vague verbs and abstract noun chains when a concrete action is known, but retain necessary technical distinctions. Remove throat-clearing, repeated conclusions, and modifiers that add confidence without evidence. Watch for changed quantities, actors, timelines, and certainty when shortening. In consequential passages, compare every revision with the source or approved fact record. Query ambiguity instead of guessing what the writer intended.

Shape paragraphs as units

Check whether each paragraph has a discernible job and whether sentences arrive in a useful order: context, claim, evidence, implication, or action. Vary length to support attention, not to meet a formula. Place important conditions near the claim they limit. Make references explicit when “this,” “it,” or “they” could point to several things. Use transitions that name a true relationship. A line edit can reveal structural trouble; flag the issue rather than disguising it with polished connective phrases.

Protect the writer and reader

Maintain an agreed voice while removing imitation, clichés, unnecessary intensifiers, and rhythm that becomes monotonous. Keep distinctive first-hand detail when it contributes evidence or perspective. Read aloud to find accidental rhyme, repeated openings, breathless clauses, and misplaced emphasis. Then review the diff, not only the clean copy. Group significant changes into queries so the writer can decide efficiently. End with a handoff that distinguishes accepted edits, open questions, fact checks, and any structural issue outside scope.

See the fields in context

Fictional example: grant timeline paragraph

The grant program and dates are invented.

Original: “Applications are generally quickly reviewed by our team and successful people are soon contacted.”
Problem: Passive voice hides the actor, and “quickly” and “soon” are unsupported.
Revision: “The review team checks complete applications within ten fictional business days. It then emails each applicant a decision.”
Query: Confirm the ten-day period against the source before accepting.
Result: The revision improves action and sequence without adding promotional confidence.

Frequently asked questions

How is line editing different from copyediting?

Line editing improves expression, paragraph movement, emphasis, and voice. Copyediting focuses on correctness, mechanics, style consistency, names, and references. Projects can combine them, but the editor should state which decisions are in scope.

Should a line editor rewrite heavily?

Only when the brief allows it and meaning remains controlled. Prefer queries where intent or experience is uncertain. A large elegant rewrite can erase the writer’s perspective or introduce claims no source supports.

Can line editing happen before fact-checking?

It can, but material facts should be stable enough to avoid polishing text that will change. Flag every claim affected by a rewrite and ensure final fact review covers the edited wording.

Is reading aloud necessary?

It is a valuable diagnostic for rhythm, repetition, breath, and emphasis, but it does not replace visual, accessibility, or factual review. Silent readers and assistive technologies may encounter the text differently.