Weekly client report starter.

Use this starter in your Project

Copy the prompt, open a Session, and paste it into the composer. You can try the fictional Northstar notes first or replace them with your own material. Name the reporting period before asking for the final document.

These are starting instructions, not an installed Agent or a finished report generated from your files. Opening Workspace does not automatically import the prompt. Keep the source notes in the same Project so you can check and update them later.

Adapt the structure to the client

If your client needs decisions first, change the section order. Add a maximum length and an example of the tone you use. Avoid adding commitments to make the report sound more complete.

When this structure works, store it in Project instructions or build a reusable Agent. Test with a week containing a missed deadline or an unresolved decision; the report should keep that uncertainty visible.

Try it with a small example.

An illustrative result.

Fictional sample, written to show the expected structure. Your result depends on your inputs and needs review.

Northstar Studio — sample weekly update

Progress: Website copy is approved. Three page designs are ready for review.
Blocker: Product photos are still needed before launch timing can be confirmed.
Next step: Maya will send the designs Thursday.
To confirm: The reporting dates and the owner of the photo delivery.

Before you use the result.

• Every named result is supported by a note or file.
• No launch date was invented from a dependency.
• Owners and dates match the reporting period.
• The saved document opens and contains the complete report.