Your rough notes. A report worth sending.

Keep the source material with the work

Create a Project for the client and add notes, an approved brief, or a status spreadsheet. Put the preferred voice and report structure in Project instructions so the next update starts with the same expectations.

Keep the reporting period explicit. A note saying “approved Monday” is ambiguous without a date or week. Ask the Agent to flag that ambiguity when it affects what the report promises.

Ask for a file and a fact check

Specify the output you want: a concise update, a longer report, or a presentation outline. Ask the Agent to preserve uncertainty and keep proposed next steps separate from agreed commitments.

For example, “Photos still needed; launch depends on photos” should remain a blocker. It should not become “launch confirmed for Friday.” Use the weekly client report starter to try the workflow with fictional notes first.

Open it, revise it, and reuse the structure

Use Preview in the Session or the Project’s Files tab to open the result. Check names, dates, ownership, totals, and unsupported claims before asking for stylistic changes. Review the saved file itself, including later pages.

Ask for specific revisions such as “shorten the introduction” or “put client actions first.” Download the final file when ready. If the same report repeats, keep a reusable prompt or make an Agent with the agreed checklist.

Try it with a small example.