Critical Essay Template 1
Critical thesis: Although [subject] succeeds at [strength], it is limited by [limitation], especially when judged by [criteria].
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.
Effective critical writing is fair to the subject before judging it, identifies the criteria behind the evaluation, supports both strengths and limitations with evidence, and reaches a qualified conclusion that reflects the weight of the analysis.
Critical thesis: Although [subject] succeeds at [strength], it is limited by [limitation], especially when judged by [criteria].
Criterion paragraph: By the criterion of [standard], [subject] performs [assessment]. Evidence: [detail]. This matters because [reason].
Fair-summary frame: The author argues [accurate claim] based on [evidence/method] before I evaluate [specific issue].
Qualified conclusion: Overall, [judgment] is justified for [scope/condition], but not for [boundary].
Source-ledger and revision-history audit for Critical Essay: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
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 → [ ].