Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
A strong letter to the editor makes one main point quickly, gives enough verifiable context for readers to understand it, connects evidence or experience to the claim, and ends with a proportionate implication or request rather than trying to solve every aspect of the issue.
Letter to the editor — issue response Reference: [article/issue + date if relevant] Opening claim: [one clear position] Evidence/example: [specific fact or experience] Reasoning: [why it matters] Counterpoint/limit: [optional] Closing: [specific implication or action] Submission details: [follow publication rules]
Correction letter Published statement: [briefly identify] Correction: [accurate information] Evidence/source: [verifiable reference] Why the distinction matters: [x] Requested action: [correction/clarification if appropriate]
Community issue letter Problem: [specific local issue] Affected readers/group: [x] Concrete effect: [x] Evidence: [observed/verified detail] Feasible response: [x] Closing: [why timely attention matters]
Counterpoint letter Original argument: [fair summary] Point of agreement: [x] Missing distinction/evidence: [x] Your claim: [x] Evidence: [x] Closing: [bounded conclusion]
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].