THE FIRST AMMAN COHORT IS IN PLANNINGGet the details before you decide
apexACADEMYRequest details
IN PERSON · ENGLISH · AMMAN, JORDAN

FIELDNOTE 02 / AI & CREATIVE

From a vague AI prompt to a draft you can check

Turn a vague request into a focused draft, then check the claims and choices before you use it.

Download the worksheetFree to read and adapt. No email required.

“Write a great ad for my business” gives an AI tool very little to work with. The result might sound polished while missing the offer, inventing a benefit or asking the wrong person to act. A useful workflow starts before the prompt and finishes after the first answer.

Use this six-step exercise with a real brief or a completely fictional practice business. The aim is a draft that a person can approve, revise or reject with clear reasons.

1. Gather a small fact sheet

Write down the audience, offer, requested action and practical limits. Include the source and owner of each fact. Separate approved facts from ideas and unknowns. For practice, use synthetic information rather than real customer messages, contact details or order histories.

Our example is Ward El Hara, a fictional Amman florist. Its invented offer includes three birthday bouquet styles and an optional gift note. Prices, availability and delivery arrangements are deliberately unconfirmed.

2. Give the task boundaries

Tell the tool what to produce, where it will appear and which facts it may use. A word limit is more helpful than “keep it short.” Explain what needs checking instead of asking the tool to fill every gap.

Create two social post drafts, each under 50 words.
Practice business: a fictional Amman florist.
Audience: people planning a birthday gift for someone nearby.
Offer: three bouquet styles; an optional gift note.
Action: enquire about availability for a specific date.
Tone: warm, clear and direct.
Use only these facts. Do not add prices, delivery promises,
reviews, discounts or urgency. List missing facts separately.

This instruction reduces ambiguity. It does not prove that the answer will be accurate.

3. Ask for a small, useful variation

Two drafts are enough for this exercise: one opening with the occasion and one opening with the choice of styles. Keep the offer and action consistent so you can compare the writing. Do not ask for twenty versions before deciding what a good answer needs to do.

4. Check every claim against the brief

Read the output line by line. Label each factual claim “supported,” “needs confirmation” or “remove.” If a draft says “same-day delivery across Amman,” remove it: the fact sheet contains no such promise. Asking the same tool whether its answer is correct is not a substitute for checking the underlying evidence.

5. Edit for the customer

A usable practice draft might read: “Planning a birthday gift? Explore three bouquet styles and add a personal note. Message us with your preferred date to ask about availability.” Check that the next step is possible and that someone can answer it. Read the text aloud; replace vague praise with useful information.

6. Save the approved version

Keep the brief, prompt, original output, edits and approval together. Name the approver and record the date. If the offer changes, review the published copy too. A saved decision trail helps the next person understand why a phrase was kept or removed.

Approval checklist

  • Every claim has a checked source or has been removed.
  • The offer and requested action match the brief.
  • The copy contains no invented proof or scarcity.
  • Someone can handle the response the copy requests.
  • A person has approved this version before publication.

Printable worksheet

AI DRAFT REVIEW
Task / channel / word limit:
Audience / offer / requested action:
Approved facts and sources:
Unknowns and prohibited assumptions:
Prompt / version:

Claim | Source | Keep / confirm / remove

Draft selected and reason:
Human edits:
Reply process checked by:
Approved version / person / date:
Next review trigger:

Apply the workflow to Meta and Google

For Meta, ask AI for distinct message angles and copy variations from the approved brief. Review every claim, then inspect placement previews and record the available campaign and Advantage+ controls. Save what you accept, edit and reject.

For Google, ask AI to group supplied search themes, propose relevant ad copy and suggest exclusion candidates. Check intent, match types, negatives and the destination yourself. Keep an unposted Ads Editor file for review. Study AI Max and Performance Max as different automation choices with different controls; a useful suggestion is not necessarily an enforceable setting.

What an API connection actually does

An API lets software pass a defined request to another service. In the course demonstration, an approved fictional fact sheet goes to an external AI model. The response is checked for the required fields and unsupported claims, then saved as a reviewed draft. Personal API keys are not needed for the supplied exercise.

The external model and the ad platform have different roles. A model can prepare or analyse information; Meta and Google operate their own campaign automation. Model credentials do not grant access to an ad account. Account permissions, spending authority and a real launch are separate decisions.

Save the work before the next step

Keep a request identifier, the source facts, original response, validation result, edits and approved version together. A real integration needs a durable queue, retry limits and duplicate handling so a failed request is not silently lost or repeated as a new action. An AI answer alone is not a saved enquiry or an executed campaign change.

Do not paste API keys into prompts, worksheets or browser code. Use a server-side secret store for a real integration. Record failed checks and pause the affected handoff; do not invent missing fields or claim a change succeeded without a platform response. These are workflow principles demonstrated with fictional information, not an active connection from this website.

API practice worksheet

WORKFLOW: APPROVED FACTS TO REVIEWED DRAFT
Task / channel / request identifier:
Approved input and source:
Fields the model must return:
Claims and settings to validate:
Permission needed for the next step:
Usage and retry limits:
Original response / validation result:
Human changes / approval record:
Saved draft location / next action:
Failure or duplicate handling:

Make it useful
for your next campaign.

Download the editable plain-text worksheet. Keep your assumptions, evidence and next decisions together.

Get the worksheetBuild the full campaign in the programme