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 report answers the exact brief, uses a visible structure, prioritizes verified or provided information, separates observation from interpretation, and makes any recommendation traceable to the findings rather than to unsupported opinion.
General report Title: [specific report title] Prepared for: [reader/role] Purpose: [what the report is meant to establish] Context / scope: [where, when, what was examined] Findings • [finding 1 + evidence] • [finding 2 + evidence] • [finding 3 + evidence] Conclusion: [what the findings establish] Recommendation: [only if required and supported]
Event report Heading: [event] Context: [date, place, purpose] Opening: [what happened and who it was for] Main activities: [selected details] Notable outcome: [supported result/response] Closing: [overall significance without invented praise]
Incident report Date/time: [x] Location: [x] People/roles involved: [only known facts] Observed sequence: [fact 1 → fact 2 → fact 3] Immediate impact: [x] Action taken: [x] Follow-up required: [x] Unverified points: [what remains unknown]
Survey / findings report Question: [x] Sample/source: [x] Key finding 1: [value/pattern] Key finding 2: [comparison] Exception/limit: [x] Interpretation: [bounded meaning] Recommendation: [evidence-linked next step]
Recommendation report Problem: [x] Criteria: [cost/time/risk/quality/etc.] Option A: [evidence + tradeoff] Option B: [evidence + tradeoff] Recommendation: [choice] Reason: [why it best fits the criteria] Implementation note: [first next step]
Purpose-and-verification decision audit for Report Writing: 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 Report Writing: 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 Report Writing: 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 Report Writing: 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 Report Writing: 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 → [ ].