A request such as 'improve this report' leaves a lot for the model to infer. Write the audience, the decision the report supports, the source material and the required output. Those details make the result easier to review.
Try this structure: prepare a one-page operating summary for the department head, using the supplied weekly figures. Keep the numbers unchanged. Identify missing information. Separate observations from proposed actions. Return a draft with source references for every numerical statement.
Give it the relevant context rather than the whole archive by default. Confirm that the tool and its data settings are approved for the material you are using. A sensitive file does not become suitable for a tool just because uploading it is convenient.
Keep a small set of examples: one ordinary report, one with missing rows and one where the source contradicts itself. Compare drafts with the same criteria each time. Ask a colleague to review what changed.
Save the useful brief, its inputs and its review checklist. Reusing a tested pattern is a practical way for a team to learn together.
Use the workflow scorecard ↗