Write a useful AI brief
Give Studio enough context to produce a reviewable first proposal.
Include six useful details#
Use the Content request field to explain the outcome you want. Include the audience, purpose, main message, approximate length, visual direction and required source constraints.
- Audience: who will use or view the presentation.
- Outcome: what they should understand or do.
- Structure: slide count or the sequence of topics.
- Interaction: tabs, a comparison, a path or another specific behavior.
- Source rules: which claims and values must stay exact.
- Style: brand, tone and any visual references you are allowed to use.
Use a concrete request#
For example: “Create a six-slide presentation for an internal training audience. Begin with the problem, explain the mechanism, show the supplied comparison data, then finish with a recap. Use a restrained blue and white palette. Add evidence tabs on the comparison slide. Preserve the supplied values and citations. Ask about missing information instead of inventing it.”
Put brand, market and language in Project details too, so the saved context supports later work.
Ask for one focused refinement#
Once a project exists, use Builder to request changes. Under Options, choose Whole project, This page or Selected elements. Select the actual page or elements when using a smaller scope.
Use Allowed changes to express whether the request covers Content and design, a Style request · preserve data or a Text request · preserve data. Review the proposal even when you have selected a narrow scope.
Review before accepting#
A clear brief improves direction; it does not establish factual accuracy. Check the wording, charts, source use and behavior of the proposal. If Studio asks to use saved app files for the request, review that disclosure before allowing it.
Use the displayed send action once. If a request has an uncertain outcome, check its retained status before starting another generation.