Use the request formula
A strong request contains:- Outcome — the question to answer or artifact to produce
- Source — the connected system that should provide the evidence
- Scope — the account, campaign, product, audience, or workspace in bounds
- Window — exact dates or completed periods
- Measures — the metrics or quality criteria that matter
- Constraints — definitions, exclusions, and business rules
- Output — the format you want
- Action boundary — read, draft, ask for approval, or execute under policy
Start from these patterns
Performance analysis
Creative brief
Campaign preparation
Replace vague language
Ask for decision-ready output
Tell Marketer how you will use the result. A useful structure is:- Finding: what changed
- Evidence: source, dates, scope, and values
- Interpretation: the most likely explanation and uncertainty
- Recommendation: the proposed next step
- Approval: what would change and what control applies
Refine without restarting
Use follow-ups to correct one dimension at a time:- “Use only Google Ads. Remove Shopify figures.”
- “Recalculate in the workspace timezone using complete days.”
- “Limit the answer to the attached campaign.”
- “Keep the recommendation, but turn it into a draft with no write actions.”
- “Show the source and calculation behind the first claim.”
A prompt cannot expand your role or bypass workspace controls. Guardrails, autonomy settings, provider permissions, and approval gates still apply.