60-second summary
Quick answer
A useful brief names the exact reader, the result they want, the depth, tone, required examples and topics to avoid. Put those details in the main instruction before opening Advanced Settings.
Before you start
What you need
- Sign in to the Automateed account that owns the relevant project or purchase.
- Have the project, source file or account setting needed for “Name the exact reader” ready before changing anything.
Procedure
Complete the task step by step
- 01
Name the exact reader
Describe experience level, role and problem rather than writing “for everyone.”
Current app screen
The large instruction field is where the audience, promise, boundaries and voice belong. - 02
Define the transformation
Explain what the reader should understand or be able to do by the end.
- 03
Set boundaries
List topics to include, topics to avoid, desired depth and any claims that require caution.
- 04
Add voice direction
Describe tone, point of view, examples and vocabulary that should feel natural for your audience.
- 05
Request a useful structure
Ask for frameworks, examples, exercises or checklists only where they support the reader outcome.
Success check
Confirm that it worked
- The expected result from “Request a useful structure” is visible in the relevant Automateed screen or exported file.
- Refresh the page once and confirm the saved state remains unchanged.
Important notes
- Available controls can differ by book type, plan and current project status.
- Review generated content, facts, usage rights and final files before publishing or selling.
Related guides
Go deeper