Readability and Plain Language

Meaning-Preservation Edit Log

Record high-impact clarity edits and confirm that changes to terms, conditions, numbers, certainty, chronology, or scope did not alter intended meaning.

Free editable Markdown · Editors, subject-matter experts, and localization teams · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Edit record

Edit ID: [Stable identifier]
Page and section: [Location]
Source wording: [Exact text]
Source version: [Date or file version]
Proposed wording: [Exact revision]
Edit operation: [Replace, split, reorder, list, summarize, or localize]
Reason for edit: [Reader difficulty or requirement]
Semantic risk: [Term, condition, certainty, scope, number, chronology, or agency]
Meaning invariant: [What must remain true]

Verification

Authority or evidence: [Source, definition, calculation, or expert]
Back-check question: [Question that tests equivalence]
Subject reviewer: [Name/role and decision]
Editorial reviewer: [Name/role and decision]
Locale reviewer: [If applicable]
Context affected: [Heading, link, chart, action, or surrounding claim]
Repeated occurrences: [Locations to update]
Final decision: [Approve, revise, reject, or escalate]

Meaning checks

Defined terms retain their approved meaning.
Negation, conditions, and exceptions remain attached correctly.
Certainty and obligation have not increased or decreased silently.
Population, period, jurisdiction, and version remain bounded.
Numbers, units, and comparisons are unchanged or reverified.
Chronology and causal relationships remain accurate.
Full-context reading supports the same interpretation.
All summaries and translations receive the approved change.

How to use this template

Identify edits with semantic risk and capture the exact source wording plus context.
Define the meaning that must remain, including scope, certainty, conditions, numbers, and sequence.
Record the proposed wording, edit operation, evidence, and potential failure mode.
Obtain the appropriate subject, editorial, and localization checks in full page context.
Approve, revise, or reject the edit and propagate the decision to every repeated occurrence.

Identify semantic risk before rewriting

Mark source wording that contains defined terms, negation, thresholds, quantities, time boundaries, probability, causation, scope, exceptions, or ordered steps. These features are easy to shift while shortening a sentence. “May,” “will,” and “must” are not interchangeable; “people in the sample” is narrower than “people”; and moving “unless” can reverse a rule. Give each risky passage an ID so reviewers can compare source, proposal, and approved version without relying on memory.

State what changed and what must remain

Describe the edit operation—replace a term, split a sentence, reorder conditions, convert prose to a list, localize an example, or summarize evidence. Then write the invariant: the exact relationship that must survive. Attach the source, definition, policy, calculation, or expert rationale. Back-translate specialized or localized content when appropriate, but do not treat literal similarity as proof of equivalent meaning. A cleaner sentence should still preserve certainty, population, period, agency, and consequence.

Verify in full context

Read the revised passage inside the section and user journey. A sentence may remain accurate alone but become misleading beneath a new heading or beside a changed button. Ask the subject expert to explain whether any condition moved, and ask an editor to confirm that readers can understand the revision. Recheck summaries, charts, captions, metadata, schema, and translations that repeat the claim. If reviewers disagree, keep both interpretations visible and resolve the source meaning before publication.

See the fields in context

Fictional example: workshop eligibility rule

Harbor Bench is an invented workshop, and its eligibility rule exists only for this editing example.

Source: “Members aged 16 or 17 may attend when a registered guardian remains on site.”
Rejected edit: “Members 16 and older may attend with guardian permission.”
Meaning change: “Permission” removes the fictional on-site condition and “older” incorrectly expands the rule.
Approved clarity edit: “Members who are 16 or 17 may attend only while a registered guardian remains on site.”
Verification: The fictional policy owner confirms age range, obligation, and location condition are preserved.

Frequently asked questions

Which edits are high impact?

Prioritize changes affecting rights, eligibility, safety, cost, obligations, scientific meaning, material facts, or any decision with meaningful consequences.

Is a tracked-changes document enough?

It shows textual differences but may not explain intended meaning, evidence, reviewer decisions, or repeated occurrences across other surfaces.

Can simpler wording be less accurate?

Yes. Simplification can remove a condition or technical distinction. The goal is the clearest wording that preserves the required meaning.

When should an edit be rejected?

Reject or escalate it when equivalence cannot be established, the source meaning is disputed, or required qualified approval is unavailable.