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 action log makes accountability visible without turning every task into bureaucracy. Each entry uses one accountable owner, a concrete next action or deliverable, a realistic date or review point, status definitions that are understood by the team, and closure evidence when completion matters.
Action log ID: [x] Action/deliverable: [x] Owner: [one accountable owner] Created from: [meeting/decision/finding/link] Opened: [date] Due/review date: [date] Status: [defined status] Dependency/blocker: [x] Latest note: [x] Closure evidence/date: [x]
Meeting action register Decision/context: [x] Action: [verb + deliverable] Owner: [x] Due: [x] Dependency: [x] Next review: [x] Status: [x]
Corrective follow-up action Finding/issue: [ID] Required action: [x] Owner: [x] Containment already complete: [x] Target date: [x] Verification required: [x] Verifier/closure authority: [x]
Action quality check One owner? [ ] Observable output? [ ] Source/context linked? [ ] Date or review trigger? [ ] Dependency visible? [ ] Closure condition clear? [ ]
Purpose-and-verification decision audit for Action Log: real writing job → [ ]; plausible choice A → [ ]; plausible choice B → [ ]; downstream consequence of each → [ ]; facts/evidence/canon to verify → [ ]; reader or genre boundary → [ ]; final purpose-fit reason → [ ].
Publication-readiness audit for Action Log: claim/advice/example → [ ]; strongest available source tier → [ ]; important disagreement or uncertainty → [ ]; what would change the conclusion → [ ]; publish now / qualify / revise / hold → [ ]; final verifier or source of truth → [ ].
Provenance and classification audit for Action Log: draft statement/example → [ ]; classify as fact / interpretation / recommendation / convention / original example → [ ]; source or internal provenance → [ ]; source date / version / checked date → [ ]; attribution needed → [ ]; recency risk → [ ]; final publishable wording → [ ].
Source-record and update audit for Action Log: statement / example → [ ]; external fact, project fact, interpretation, recommendation, convention, or original example → [ ]; controlling first-party / primary source → [ ]; secondary source if used → [ ]; source record / locator → [ ]; date or version checked → [ ]; update trigger → [ ]; publish / qualify / revise / hold → [ ].
Source-ledger and revision-history audit for Action Log: 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 → [ ].