--- name: report-drafting description: Plan and draft formal academic, research, technical, or professional reports from a brief and source material. Use for first drafts, report outlines, executive summaries based on supplied findings, and selection of applicable reporting standards. --- # Report drafting Build a report around the question it answers, the evidence it can use, and the audience's purpose. For a whole-draft revision, use [report-review](../report-review/SKILL.md). ## Establish the brief Identify the audience, report type, question or decision, scope, source material, and requested deliverable. Check the applicable brief, rubric, author instructions, contract, house template, or regulator's reporting rules. Preserve the author's established terminology and any approved wording. When a missing detail changes the structure, governing rules, or conclusions, ask a focused question or make the affected part provisional. Proceed with the parts the available material supports. For coursework, confirm what drafting assistance the stated assessment rules permit. ## Select the reporting requirements Use the [standards guide](references/report-standards.md) when the user names a standard, asks which rules apply, or the report type calls for discipline-specific guidance. Treat its entries as candidates. Confirm the edition and scope with the issuing body and the actual instructions for the deliverable. Distinguish binding requirements, adopted guidance, and editorial defaults. A report can have separate authorities for required content, citations, submission format, and accessibility. If they appear to conflict, record the exact requirements and resolve them with their governing instructions before claiming coverage. For paywalled or inaccessible requirements, use an authorised copy or mark the affected checks unverified. For a standards-led draft, keep a compact record with the source and edition, clause or checklist item, applicability, planned section, evidence, and status. Mark items covered, partial, missing, unverified, or inapplicable with a reason. A heading can show coverage only when its content meets the applicable requirement. ## Outline from evidence For each proposed section, identify the reader question it answers and the source, analysis, table, or decision it depends on. Choose a structure that follows the brief: - Empirical research usually needs the research question, methods, findings, interpretation, and limitations. Use the venue's structure for results and discussion. - Technical evaluations usually need requirements or criteria, the system or method, test conditions, observations, and what the results establish about the criteria. - Decision reports usually need the decision sought, options, evaluation criteria, trade-offs, the recommendation and its conditions, and implementation responsibilities if requested. - Literature syntheses usually need the review question, search and selection scope, thematic or comparative findings, and limitations. A systematic review also needs the applicable reporting guideline and the actual review records. Put evidence gaps where they affect the draft. Mark the missing input and the claim it would support. Use a clear placeholder for required material such as an unconfirmed result, approval, declaration, or citation. Leave invented values and sources out of the draft. ## Draft and check the argument Develop findings before drafting the abstract, executive summary, or conclusion. Tie each consequential claim to the source and scope it depends on. Preserve units, denominators, assumptions, uncertainty and attribution. Label examples, forecasts, and proposals so readers can distinguish them from observations. Explain how recommendations follow from findings, including constraints that could change the decision. For paraphrases and syntheses, read the source for meaning, write independently for the report's purpose, and cite the source where it supports the claim. Use a quotation only when the original wording matters and verify the exact wording and locator. Treat reproduced or adapted tables and figures as separate attribution and permissions checks. Before handoff, reconcile the summary and conclusions with the body, check that consequential claims have traceable evidence, and account for each required item. Deliver the requested outline or draft with the material assumptions, open evidence gaps, and standards checks still pending. ## Continue with the applicable skill - [Report clarity](../report-clarity/SKILL.md) for prose, terminology and reader context. - [Report evidence](../report-evidence/SKILL.md) for deeper verification of claims, results and sources. - [Report review](../report-review/SKILL.md) for a rubric-led review or revision plan. - [Report release](../report-release/SKILL.md) for the built deliverable and visual checks. For optional citation and document-tool handoffs, see [working with other skills](references/companion-tools.md).