Give the AI a fact sheet first (date, doors, venue access, price, refund rule, what is included), then ask for the description from that sheet only. Read the result line by line against the sheet before publishing. The check matters more than the generator: a fluent paragraph that promises something you are not offering is the real risk.
Most free generators ask for an event name and a mood, then invent the rest. They will cheerfully add "free parking", "all ages welcome" or "refreshments included" because those phrases appear on thousands of event pages. A buyer who turns up expecting them is a refund request, or a bad review. So the method below runs in the opposite direction: you supply every fact, the AI supplies the wording, and you verify.
Why generic generators get ticket pages wrong
A ticket page is a promise with a price on it. Buyers use it to decide three things quickly: is this for me, can I get in, and what happens if I cannot come. Everything else is decoration. Generator tools tuned for "catchy event blurbs" spend their effort on the decoration and leave those three questions to guesswork.
The pattern is predictable. Give a generator "pottery evening, relaxed, beginners" and it returns lines like "all materials provided", "no experience needed" and "leave with your own masterpiece". Two of those might be true. One might mean a glazed piece you collect two weeks later. The tool cannot know, and it is not built to ask.
A general-purpose assistant behaves the same way if you give it a thin brief, but it has one advantage: it will follow instructions about what not to do. That is the lever this tutorial uses. You tell it that the fact sheet is the only source of facts, that anything missing must be flagged rather than filled in, and that it must list every claim it made so you can tick them off.
Build the fact sheet before you open the AI
Ten minutes on the fact sheet saves the rewrite later. Keep it as plain lines, one fact per line, in a document you can paste whole. Do the same for every event so the habit becomes mechanical.
| Fact | What to write down | What goes wrong if you skip it |
|---|---|---|
| Date and times | Date, doors open, start, finish, last entry | The AI writes "evening" and buyers arrive an hour early or late |
| Venue and access | Room name, step-free route, stairs, lift, toilets, nearest drop-off point | "Fully accessible" appears with no basis |
| Capacity | Total tickets, tickets per order, standing or seated | "Limited places" with no number, or a wrong number |
| Price and what it covers | Ticket price, fees shown or added, what is included, what is paid extra | "Refreshments included" when a drink costs extra |
| Age and suitability | Minimum age, children rules, dogs, noise or strobe warnings | "Family friendly" on a late-night event |
| Refunds and transfers | Cut-off date, transfer allowed or not, what happens if you cancel | The AI writes a generous policy you never agreed to |
| People | Only the hosts, speakers or performers confirmed in writing | Invented guests, or a guest who has since dropped out |
| Bring and wear | ID, clothing, bags, cameras, allergens present | Safety-relevant details missing |
Mark anything unconfirmed as "TBC" on the sheet. The prompt below tells the AI to carry the TBC through instead of resolving it. A "TBC" that reaches the ticket page looks sloppy, but it is far better than a confident guess that turns out wrong, and it shows you exactly what still needs a decision.
The prompt that keeps the AI to your facts
This template has four parts: the job, the fact sheet, the rules and the output format. The rules are where the value sits. Copy it, then replace the bracketed parts.
You are drafting the description for an event ticket page.
JOB: Write a ticket-page description of 150 to 200 words for [event type],
aimed at [audience]. Tone: [warm / dry / upbeat], plain words, British spelling.
FACT SHEET (the only source of facts):
[paste the fact sheet, one fact per line]
TONE SAMPLE (style only, take no facts from it):
[paste one paragraph from a past listing, or delete this block]
RULES:
1. Use only facts from the fact sheet. Do not add guests, prices,
inclusions, parking, age limits, accessibility claims or schedule items.
2. If a fact is marked TBC or is missing, write [CONFIRM: what is missing]
in the copy. Never fill the gap yourself.
3. Do not use these phrases: "unforgettable", "like no other",
"something for everyone", "don't miss out", "limited availability".
4. Order: one-line hook, what happens, who it suits, practical facts,
refund and transfer rule.
5. After the copy, add a table headed CLAIMS CHECK listing every factual
claim you made and the fact-sheet line it came from.
OUTPUT: the description, then the CLAIMS CHECK table.The CLAIMS CHECK table is the clever bit. It forces the AI to point at its own source for each sentence. Where it cannot point to a fact-sheet line, the claim has no source, and you delete it. The table does not make the AI honest, but it makes dishonesty visible, which is what you need.
Worked example: a 24-seat pottery evening
Say a small studio runs a beginners' hand-building evening. The fact sheet says: Thursday 14 May, doors 18:30, class 19:00 to 21:00, 24 places, $45 a ticket including clay and tools, one glaze firing included with pieces collected the following Saturday, studio is up one flight of stairs with no lift, ages 16 and over, tea and water provided but no food, refunds up to seven days before, transfers to another date allowed up to 48 hours before, and host is the studio founder.
The AI returns something close to this (illustrative output):
Spend a Thursday evening making a bowl or mug by hand, no wheel and no
experience needed.
Doors open at 18:30 and the class runs from 19:00 to 21:00. You will learn
pinch and coil building with the studio founder, using clay and tools we
supply. Pieces are fired and glazed after the class and ready to collect
the following Saturday.
Best for adults and over-16s who want a hands-on night out in a small
group of 24. Tea and water are provided; there is no food.
Good to know: the studio is up one flight of stairs and there is no lift.
Wear clothes that can get clay on them.
Tickets are $45 and include clay, tools and one glaze firing. Refunds are
available up to seven days before the class, and you can move to another
date up to 48 hours before.
CLAIMS CHECK
- "no wheel and no experience needed": source line 'beginners, hand-building'
- "pinch and coil": NO SOURCE
- "Wear clothes that can get clay on them": NO SOURCETwo claims have no source. "Pinch and coil" is probably true, but if the founder is teaching slab building that week, the page is wrong, so you confirm it with the founder. "Wear clothes that can get clay on them" is sensible advice, not a promise, so you keep it and add it to the fact sheet for next time. That is the whole loop: draft, check, fix, record.
Notice what the AI got right without being told. It stated the stairs plainly instead of saying "accessible", and it did not invent a guest. That is the effect of rule 1 and the fact sheet line, not luck.
Three versions, tested side by side
Ask for three variants of the same event and compare them against the fact sheet before you compare them for charm. Run the prompt three times with one change each, or ask for three versions in the output line. Here is how three versions of the pottery description behaved in a typical run (illustrative, not a benchmark).
| Version | Instruction added | What it did well | What needed fixing |
|---|---|---|---|
| A: plain | "Calm, practical tone" | Clearest on practical facts, shortest claims table | Dull hook; needed one stronger first line |
| B: story-led | "Open with a scene of the evening" | Best opening, most likely to be shared | Added "the smell of fresh clay" and "friendly faces", harmless but unsourced; also drifted on the glaze timing |
| C: listing snippet | "40 words for a listings site" | Fits search results and social cards | Dropped the stairs and the age limit entirely |
The usual outcome is a hybrid: version B's first line, version A's practical block and version C as the short snippet. The lesson from version C is the important one. The shorter the format, the more the practical facts get cut, and access and age are the facts most often lost. If a snippet has to omit something, make it the flourish, never the stairs.
Whichever version wins, save it. A recurring event keeps one approved description and changes only the date block, which stops each new batch of copy from reopening the question of what you promised last time.
The line-by-line check before you publish
Do the check on a printed or split-screen copy, with the fact sheet beside the description. Go in this order, because the high-stakes items come first.
- Numbers. Price, capacity, times, dates, ages. Read each aloud against the sheet. Digits are where fluent text slips: "$45" becomes "$40", "19:00" becomes "7pm" (acceptable) or "6pm" (not).
- Inclusions. Every "included", "provided" and "free" must match a sheet line. Anything the AI listed that you did not is deleted, not softened.
- Access. Compare the access wording to what you know about the room. "Step-free" is a claim someone relies on. If you are unsure, say what is true ("up one flight of stairs") and invite questions through your booking address.
- People. Names and roles come only from written confirmation. No "special guest" unless you can name them to the buyer.
- Refund and transfer rule. It must match your ticketing platform's settings. Some platforms apply their own refund controls, so check what the page says and what the checkout actually does.
- Tone words. Strip superlatives you cannot back up: "best", "award-winning", "sell-out" and "the only".
Then do a final cold read as a buyer: could someone who has never heard of you answer "can I get in, what does it cost, what if I cannot come" from the page alone? If not, the description is missing a fact, not a flourish.
Four more event types, and what the AI tends to invent
The method is the same for every event; the risky invention changes. Here are four more cases, each with the trap to watch.
A charity quiz night in a function room. The AI likes to write "teams of up to six" and "prizes to be won". Both need sources. Prize wording in particular can raise legal and tax questions in some places, so describe prizes only as the organiser has confirmed them and, if raffles are involved, ask a qualified adviser what applies to you. Add the cause line from the fact sheet, not from the AI's idea of what a charity says.
A Saturday makers' market. The AI invents stall counts ("over 40 independent makers") and a list of craft types. Put the confirmed stallholder count in the sheet, or write "stalls announced weekly" instead. Entry is often free; say so only if the sheet does, and say whether card payment is accepted by stallholders only if you know.
A two-hour workshop for a B2B audience. Say a small software reseller runs a customer evening on a new product. The AI writes "walk away with a clear roadmap" and "hands-on labs". The honest version names the actual agenda items, the laptop requirement and whether the session is recorded. Outcome promises are the exaggeration to cut hardest in professional events.
A late-night comedy or music night. The risk is the line-up. The AI will pad a bill with "plus special guests". Unless a name is confirmed in writing, leave it out, and use the text "line-up announced on the night" only if that is how you run it. Add the age restriction and any strobe or loud-sound note, which AI copy tends to omit because ordinary listings do.
A second prompt for fixing a draft you already have
Often you are not starting from nothing. A venue, a co-organiser or last year's page has already produced a description, and you need to tighten it without letting new claims in. Use a short audit prompt instead of a rewrite.
Here is a draft ticket-page description and the fact sheet it must match.
Do not rewrite it. Instead list:
1. Every sentence containing a fact that is NOT on the fact sheet.
2. Every fact on the fact sheet that the draft leaves out.
3. Every phrase a buyer could read as a promise (included, guaranteed,
free, all welcome, fully accessible).
Then suggest the smallest edit for each item.
FACT SHEET: [paste]
DRAFT: [paste]This works well when a venue manager sends over their own blurb. Say a venue's copy for a quiz night says "free bar snacks for all teams" and "family friendly until 9pm". The audit flags both because neither is on your sheet, and you can ask the venue to confirm before the claims reach buyers. It is also a fast way to review a colleague's draft without a long conversation about wording.
Before and after: access and refund lines
These two paragraphs cause the most disputes, so here is a typical before and after for each (illustrative).
Access, before: "Our welcoming venue is fully accessible for all guests." This was unsourced and generic, and it is the kind of sentence an AI adds by default.
Access, after: "The room is on the ground floor with a ramped entrance; the accessible toilet is across the corridor. Please email us before booking if you need seating near the door." It is specific, sourced from the venue visit, and gives the buyer a way to ask.
Refund, before: "Flexible cancellations available." The AI had no idea what "flexible" meant here.
Refund, after: "Full refund up to seven days before the event. After that you can transfer your ticket to another date or another person, up to 48 hours before." This is checkable against the platform's settings, and it protects you in a dispute because the buyer saw it before paying.
Mistakes that show up after publishing
Three realistic ones. First, the copy and the ticketing settings disagree: the description says transfers are allowed but the platform's transfer option is switched off. The fix is a two-minute check of the settings against the sheet each time you publish. Second, copy gets reused for a new date without updating the fact sheet: the new event page still says "ground floor" after the move upstairs. The fix is to rebuild the sheet for every event, even when it looks identical. Third, a changed fact is updated on the ticket page but not on the social posts, emails and listing sites that copied the old text. Keep one master description and list every place it was pasted, so a change becomes a short checklist instead of a hunt.
If a fact does change after tickets are sold, tell buyers directly through the platform's messaging, not only on the page. A rewritten page protects new buyers but does nothing for the people who already paid. The postponed-show messages in this tutorial on postponements and refund replies cover the wording for that case.
Reuse the approved copy across your other channels
Once the description passes the check, it becomes the source for everything else. Ask the AI to cut it into an email announcement, three social posts and a 40-word listing, and tell it each time that the approved description is the fact source. That keeps the claims consistent without repeating the whole check. For social posts, the voice work in writing Instagram captions that sound like you pairs well, and the wider picture of which event jobs suit AI is in which event planning tasks to hand to AI first.
A small habit that helps: keep the fact sheet and the final copy in one document per event, named by date. When a buyer queries something, you can see in seconds what you promised and where it came from. Over a year, that library of tested sheets and descriptions becomes your own template set, which is faster than any generator and far more accurate.
For a wider view of the tools event businesses use for this kind of drafting, this roundup of AI tools for small event planning businesses lists what is worth trying, and the event proposals tutorial applies the same fact-first discipline to paid client work.
A weekly routine that takes twenty minutes
If you list events regularly, fold the whole method into one repeatable slot. Fill in the fact sheet when the booking is confirmed, not when the page is due; the facts are freshest then and the sheet doubles as your briefing for staff. Run the prompt and take the best hook from the three versions. Do the line-by-line check, fix anything flagged, then publish and paste the final copy into your master document along with the list of places it appears. Set a calendar reminder one week before the event to re-read the page against the sheet, because late changes to venue, timing or speakers are where mismatches start. Afterwards, add one line to the sheet noting any buyer question the page failed to answer, and fold that answer into the next version.
Questions organisers ask about AI-written event listings
Can I paste last year's event page into the AI as a starting point?
Yes, but treat it as a style sample, not as facts. Old pages carry old dates, prices, venues and rules, and the AI will happily copy them. Paste it under a heading such as 'tone sample only' and tell the AI to take every fact from the fact sheet.
Should a ticket page say the copy was written with AI?
No rule makes you say it for ordinary event copy, but accuracy is your responsibility either way. Some ticketing platforms have their own policies on automated content, so read the terms of the one you use. The safer habit is to stand behind every sentence as if you typed it.
How long should a ticket-page description be?
For most small events, 120 to 220 words is enough: a one-line hook, what happens, who it suits, the practical facts and the refund rule. Long pages bury the practical facts that buyers scan for. A recurring event can keep one tested version and change only the date block.
Which AI tool should I use for event descriptions?
Any current assistant that lets you paste a fact sheet will do, including ChatGPT, Claude and Gemini. The tool matters less than the fact sheet and the check. Free plans are enough for a handful of events a month.
Further reads
- How Event Planners Use AI to Build Budgets and Run Sheets — Build the budget and run sheet the fact sheet is drawn from.
- AI Event Design for Planners: Mood Boards and Layouts Clients Approve — Make the visuals that sit beside the description.
- How Pubs and Bars Can Use AI for Events, Rotas and Stock — Event copy for pubs and bars, with rotas and stock.
- Donor Thank-You Letters With AI That Still Feel Personal — Follow-up wording for fundraising events.
- How to Write Menu Descriptions With AI That Still Sound Like You — Same fact-first habit for menu and food wording.
- AI for Marketing an Event: A Six-Week Promotion Plan for Venues — A week-by-week promotion calendar for a one-off 120-guest event, with prompts, partner emails, tagged links and a weekly check on ticket sales.
- AI-Powered Marketing Tools for a Motorcycle Dealer: Spring Campaigns — A ten-week spring plan for a motorcycle dealer: which AI tools to use for used-bike posts, service reminders and demo days, with list prices.
- Bookshop Event Ideas: Author Nights, Book Clubs and Signings With AI — A filled-in event plan, a publisher outreach email, ticket-page copy and a promotion run for author nights, signings and book clubs.
- Event Sponsorship Proposal: Tiers and Pitch Emails Drafted With AI — Price four sponsor tiers from your budget gap, then have AI draft the proposal and a four-email pitch sequence. One worked event, with the sums.
- Yoga Workshop Ideas: Plan, Price and Promote a Weekend With AI — A worked weekend workshop: the break-even ticket count, three price tiers, a fact sheet, three emails, five posts and a weekly sales check for studio owners.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: ticketing platforms' own listing guidelines and help pages (check the one you use); no vendor pricing is quoted in this tutorial.