# Create a briefing you can rely on

Build the first brief in conversation, refine it, and then put the proven instruction on a routine.

## Define the brief

Choose the source, time window, audience, and format. Decide what should happen when there is no new information.

> **Try this**
> Prepare a weekly project brief from our shared notes. Compare with the previous brief and include new decisions, completed actions, and unresolved blockers. Link the source for each item. If nothing changed, say that clearly.

## Run one example

Review the first result. Check source access, dates, links, and whether the teammate compared against the intended previous brief. Ask for corrections before scheduling the task.

If the method should be reusable, save it as a skill. Keep project names and source locations in the routine instruction.

## Schedule and monitor

Create a routine for the teammate, specify the timezone and timing, and inspect its saved settings. Use **Run now** to confirm the same instruction still works.

Review early runs in the conversation. Pause the routine when the project ends or its source access changes. A routine being enabled establishes the schedule; the run result establishes whether a particular brief was completed.

For several teammates contributing to the same report, use a group conversation with explicit ownership of the final brief.