Food Truck Vendor Applications: Draft Festival Forms With AI

Keep one facts sheet about your truck, paste each organiser's own rules into an AI assistant, and have it turn them into a requirements table before it drafts a single answer. Then draft from the facts sheet only, check every claim and attachment against the organiser's wording, and submit the documents yourself.

An assistant is a fast drafter and a poor witness. It will happily polish your bio, and just as happily add "award-winning" or "locally sourced" if nothing stops it. Organisers decide on paperwork, fit and reliability, and an invented claim damages all three.

Follow me on Instagram@sagnikteaches

What a food truck vendor application is really asking

Forms differ from one organiser to the next, but the questions fall into four groups. Knowing which group a question belongs to tells you what a good answer looks like, and where an assistant can help.

Connect on LinkedInSagnik Bhattacharya

• Paperwork. A certificate of insurance that names the organiser as an additional insured, usually with a stated minimum (for example, $1,000,000 of general liability per occurrence, sometimes with the venue named as well). Then a business licence, a food-business permit, a fire inspection permit, a letter from your prep kitchen, a unit certificate.
• Fit. What you sell, what dietary options you offer, whether you trade from a truck, trailer or tent, and which events you have done before. An organiser building a line-up is looking for variety as much as quality.
• Logistics. Power, water, vehicle length, load-in window, and whether you will stay open the whole event. Some events provide no power, water or ice and set a noise limit for generators, so the form is checking that you can trade self-sufficiently.
• Reliability. Previous events, and the terms you accept by applying, which commonly include a non-refundable fee charged after approval, a rain-or-shine clause with no refunds, and a rule that only menu items you listed may be sold.

An assistant is most useful on paperwork (checklists and expiry dates) and on fit (tailoring a short answer to what this organiser said they want). It is least useful on logistics and reliability, where the only good answer is the true one and your own records are the only source. Allow roughly this much time once the system is in place:

Subscribe on YouTube@sagnikteaches

Stage 1: a one-page facts sheet you write yourself

An assistant knows nothing about your truck. Every good answer starts from a sheet of facts that you wrote, so the assistant has something true to work from and nothing to invent. Keep it to a page, update it every quarter, and keep it in a ChatGPT Project or Claude Project (both are available on free plans, with limits on files) so you are not pasting it into every chat. Here is the shape, filled in for an illustrative dumpling truck.

TRUCK FACTS SHEET (updated [month])
Trading name: [trading name]      Legal name: [exactly as on the insurance]
Contact: [name], [phone], [email]      Social: [handle]
Format: truck, 5.2 m long, 2.4 m wide, 3.1 m high; awning out makes it 3.6 m wide
Power: own quiet inverter generator, no hook-up needed
Water: 60-litre fresh tank, 60-litre waste tank
Gas: two propane cylinders, fixed, last checked [date]
Crew: 2 (owner and one), 3 for events over six hours
Capacity: about 40 plates an hour at peak
Core menu: pork and chive dumplings (6) $9; mushroom dumplings (6, vegan) $9;
  chilli noodles $11; cucumber salad $5; iced tea $3.50
Dietary: one vegan main; noodles can be made without wheat (check the recipe card)
Allergens: see recipe cards (soy, wheat, sesame, egg in some items)
Event history: 9 markets, 2 festivals, 1 private wedding (dates and organisers listed below)
Documents (file name, expiry): COI_current.pdf, [date]; food_permit.pdf, [date];
  fire_gas_check.pdf, [date]; prep_kitchen_letter.pdf, [date]
Photos: truck_front.jpg, menu_board.jpg, plate_dumplings.jpg, setup_footprint.jpg (cropped only)
Claims we can prove: fillings made from scratch the day before; dumplings steamed to order
Claims we cannot prove (never use): award-winning, locally sourced, best in town

The last two lines do the most work. A "cannot prove" list gives the assistant an explicit set of phrases to avoid, and gives you a quick way to scan a draft for them.

If you only have rough notes, an interview prompt gets you to a clean sheet quickly:

Here are my rough notes about my food truck. Turn them into a one-page facts sheet with
these headings: names, contact, format and dimensions, power and water, gas, crew,
capacity, core menu with prices, dietary options, allergens, event history, documents with
expiry dates, photos, claims we can prove, claims we cannot prove. Ask me up to ten
questions about anything missing. Write [MISSING] where you are unsure. Do not invent
anything. Notes: [paste]

Two safety habits belong here. Leave policy numbers, home addresses and licence numbers out of anything you paste, and type them into the form yourself. And on a free consumer plan, check the model-training switch in the privacy settings and decide whether you want it on. Business details are not secret, but a facts sheet with your full documents in it should not be sitting in a chat history. For a staff-wide version of this rule, see stopping staff pasting data into free tools.

Stage 2: turn the organiser's rules into a requirements table

Do this before any drafting. Paste the organiser's brief (the text on their page, the vendor pack, the terms) and ask for a table that quotes the brief's own words. Quoting matters: it lets you check every row in seconds, and it stops the assistant paraphrasing a number. Here is an illustrative brief, invented for this example.

Autumn street food fair (illustrative brief). Saturday, 10:00 to 17:00, six food vendors. Applications close 3 March; decisions by 17 March. Fee: $180 flat, non-refundable, charged after approval, plus 8% of takings. Required: certificate of insurance naming the organiser as additional insured, minimum $1,000,000 per occurrence; current food-business permit; fire and gas safety certificate dated within the last 12 months. Only items listed in your application may be sold. Trucks up to 6 metres. No power or water provided; generators must be quiet. Load-in 07:00 to 09:00; stay open until 17:00. Rain or shine, no refunds. We want variety: no more than two vendors of the same cuisine, and at least one vegetarian main among the six. The form asks: describe your business (80 words), list your menu with prices (8 items maximum), why this fair (50 words), events attended in the last two years, three photos (truck, menu board, a plate).

Here is an organiser's brief for a festival. Make a requirements table with these columns:
requirement, the brief's exact wording, limit or deadline, attachment needed (yes/no).
Quote the brief's own words and never paraphrase a number. After the table list:
(1) anything ambiguous I should ask the organiser, (2) any clause that could cost me
money (fees, refunds, weather), (3) any selection cue about what kind of vendor they want.
Brief: [paste]

The table that comes back should look something like this (illustrative).

Below the table the assistant should list what to ask the organiser (is the 8% charged on gross takings or on takings after tax; is there a numeric limit for "quiet"; how many people came last year) and what could cost you money (a $180 fee you lose if you cannot attend, and 8% on top, with no refunds if the weather turns). The selection cue is the line to hold on to: no more than two vendors of the same cuisine, and at least one vegetarian main.

Check the table against the brief before you trust it. Three slips are typical, and all three are worth looking for. The first pass often shows the fee as $180 and drops the 8%, which is exactly the line where a mistake costs money. It may mark photos as optional because they sit in the form rather than the rules. And it can merge "fire and gas safety certificate" into one document when the organiser may need two. Where the wording is ambiguous, put the question to the organiser rather than guessing.

Stage 3: draft from the facts sheet only

Now the drafting prompt. Three rules do the work: the assistant may use only facts from your sheet, it must flag anything missing rather than fill the gap, and it must tag each sentence with the line of the sheet it came from.

Using only my facts sheet, draft answers to the questions below. Rules:
- Stay inside each word or item limit and tell me the count.
- Use only facts from the sheet. If an answer needs a fact that isn't there, write
  [MISSING: what you need] instead of filling the gap.
- Never use anything on the "claims we cannot prove" list, and avoid superlatives.
- After each sentence, add the facts-sheet line it came from in square brackets.
- Plain, specific wording, no marketing language. Match the organiser's spelling.
Questions and limits: [paste]. The organiser's selection cues: [paste].

The source tags are the useful trick. With them, you can audit a draft in a minute: read down the brackets, and any sentence without one, or with a bracket that points at the wrong line, is a claim to question. Delete the tags before pasting into the form; a find-and-replace on the square brackets does it in one pass.

Drafting works best one question at a time for the longer answers, and in one go for the short fields such as power and staffing. Keep each organiser in its own chat inside the Project, so the word limits and cues of one application never leak into another.

Stage 4: a photo shot list, and why none can be generated

The photos are the one part of the application the assistant must stay out of. An organiser is judging the real truck, the real menu board and the real plate. A generated image of a perfect dumpling is a misrepresentation, and it shows up the moment you arrive. Where a form asks whether AI was used on any part of the submission, say so honestly.

What an assistant can do is help you plan and caption real ones. Shoot once a season, in daylight, and keep the originals:

1. The truck from about three metres away, hatch open, name and menu readable.
2. The menu board close enough to read every price.
3. One plate on the counter, unstyled, the way a customer receives it.
4. Your set-up footprint: truck, awning, queue line and any barrier, from the side or above.
5. The crew in uniform, if staff are happy to appear.

Name the files plainly (truck_front.jpg, menu_board.jpg, plate_dumplings.jpg) so the names match your facts sheet and the organiser's categories. Crop and adjust brightness if you like, but do not retouch the food or the truck so they look different from reality. Check the organiser's limits on number and file size before you upload, and whether the count is a minimum or an exact number; this brief asks for exactly three.

For captions and alt text, describe each photo in a sentence and ask for a one-line caption of under 125 characters that says only what is visible. A prompt that works: "Here is my description of the photo. Write a caption and alt text that mention only what I've described. Don't add claims about taste, sourcing or awards." If you also use photos on delivery apps or menus, where AI food photography is and isn't acceptable sets out the line.

Stage 5: the insurance and licence checklist, with a gap check

This is the part of the application where a drafted answer cannot rescue a missing document. Which papers an event wants is up to the organiser and the place you trade, so the brief's list is the one that counts. The table below shows what such lists tend to contain and what to confirm before you attach each one.

The assistant's job here is comparison. Give it your requirements table and a plain list of your documents with names, limits and expiry dates (not the documents themselves), and ask it to say which requirements are met, which are not, and which it cannot tell.

Below are (1) the requirements table from this organiser's brief and (2) a list of my
documents with issuer, cover or scope, and expiry date. For each requirement say MET,
NOT MET or CAN'T TELL, with one sentence of reason. Then list the actions I must take,
who has to do each (me, my insurer, an inspector), and the latest date to start so I
meet the deadline of [date]. Don't assume a document says anything I haven't listed.
Requirements: [paste]. Documents: [paste].

For the dumpling truck, the check might come back like this (illustrative): insurance, cover of $1,000,000 per occurrence meets the minimum but the certificate does not yet name the organiser, so ask the insurer for a revised certificate; food permit, met, expires after the event; fire and gas check, not met because the certificate is dated 14 months ago and the brief wants 12, so book a new check. What matters is the last part: the revised certificate can only come from your insurer and the new check only from an inspector. The assistant can tell you what to ask for and the date to start, but it cannot produce either. Lead times for both can be longer than the weeks left before a deadline, which is the main reason to run this check the day you find the brief.

Keep an expiry tracker as a simple sheet: document, issuer, expiry, reminder date (60 days earlier), and the folder where the file lives. An assistant can build it from your documents list in a minute, and a reminder 60 days out is worth more than any amount of polished prose.

One application worked through, field by field

Take the illustrative autumn street food fair brief and the dumpling truck's facts sheet. Here is what happened to each field between the assistant's first draft and what was submitted.

Business description (80 words)

The first draft, produced from a one-line instruction without the rules above, read:

[Truck] is passionate about bringing award-winning, authentic dumplings made with locally sourced ingredients to food lovers everywhere. Our expert chefs have delighted thousands of customers with unforgettable flavours at festivals.

Five phrases fail the audit. "Award-winning" and "locally sourced" are on the cannot-prove list. "Expert chefs" is two people. "Thousands of customers" appears nowhere in the sheet. "Unforgettable" is the assistant's opinion. Run again with the drafting prompt, and edited by the owner, the submitted version was:

[Truck name] is a two-person dumpling truck. We make the fillings from scratch the day before and steam the dumplings to order. The core menu has five items, including one vegan main, and at peak we serve about 40 plates an hour. We have traded at nine markets and two festivals. We bring our own quiet generator, so we need no power from the organiser.

That is about 65 words, every sentence traceable to the sheet, and it quietly answers two of the organiser's concerns (a vegetarian option and no power needed) without announcing that it is doing so.

Menu (8 items maximum)

The brief says only listed items may be sold, so the list should include everything you might sell on the day, up to the limit, and not just your headline dishes. The assistant lined the core menu up against the brief and flagged one gap: the sheet had no bottled water, but the owner usually carries some. It wrote [MISSING: price and whether you sell water], the owner replied "$2.00, yes", and the sheet was updated.

The assistant never decides allergens or dietary labels. Those come from your recipe cards, and a label the owner has not checked is a risk, not a draft. If you need a method for the labels themselves, allergen icons and dietary labels before you print covers it. To set the prices for a festival day, where the fee and the volume differ from a market, use the sums in setting menu prices after fees, fuel and pitch costs.

Why this fair (50 words)

The first draft opened "We love food festivals and would be thrilled to be part of your amazing event", which could be sent to any organiser in the world. Told to use the brief's selection cues, it produced something better, and the owner trimmed it to 48 words:

Your brief asks for variety and a vegetarian main. Our vegan mushroom dumplings cover the second, and as a single dumpling truck we take one cuisine slot. We have done two festivals before, bring our own generator, and can load in at 07:00 and stay open until 17:00.

Note that the load-in and closing times weren't on the sheet. The assistant flagged them as [MISSING], the owner confirmed both, and they went onto the sheet for next time.

Events, space and photos

• Events in the last two years: nine markets and two festivals, listed with month and organiser from the sheet. The private wedding was left out because the form asks about events attended, and the owner chose to list public events only.
• Space and power: truck 5.2 metres (limit 6), awning out 3.6 metres wide, own quiet generator, no water or power needed from the organiser.
• Photos: truck_front.jpg, menu_board.jpg and plate_dumplings.jpg, one for each item the brief names.
• Attachments: revised certificate of insurance naming the fair, current food permit, new fire and gas certificate, all checked against the brief.

Stage 6: a second read as the organiser's selection panel

Before you submit, ask the assistant to read the whole application the way the organiser will, with the brief beside it. A fresh chat works better than the one that drafted it, because the drafting chat has already agreed with itself.

Act as the selection panel for this event. Here are the organiser's brief and my complete
application. Do the following and nothing else:
1. List any requirement in the brief that my application does not meet or does not evidence.
2. List the three weakest answers and say why, quoting the brief's own selection cues.
3. Quote any sentence that makes a claim you can't find in the attached facts sheet.
4. Check each answer against its word or item limit and give the counts.
Do not rewrite anything yet. Brief: [paste]. Application: [paste]. Facts sheet: [paste].

On the dumpling application, an honest reply (illustrative) would flag that "two festivals" has no dates, that the events answer lists no organiser names so the panel cannot verify anything, and that the menu calls the mushroom dumplings vegan while the facts sheet's allergen line says egg appears in some items, so the owner should confirm the wrapper recipe before the word "vegan" goes to an organiser. Each is a quick fix, and the last is the kind of mismatch that only shows when someone reads the form against the sheet.

Then do the checks only a person can do:

• The legal and trading names are identical on every document and on the form.
• Every date on a certificate runs past the event date.
• File types and sizes meet the form's limits, and nothing is generated.
• The fee, its refund terms and the weather policy are in your calendar, with the date the card is charged.
• You have read the terms and conditions yourself, not asked a chatbot to summarise them.

Questions to put to the organiser before you pay

The requirements table gives you a list of ambiguities. Turn them into one short email rather than four. Ask the assistant to draft it in your voice from the list, and keep it to questions only the organiser can answer.

Hello [first name], we are preparing an application for [event] and have a few questions. Is the 8% charged on gross takings or on takings after tax? Is there a figure for the generator noise limit? Roughly how many visitors came last year, and how many food vendors shared them? What happens to the fee if the event is cancelled for weather on your side? Thank you, [your name], [truck name]

The attendance and vendor numbers feed straight into a go or no-go decision. The festival example in the pricing tutorial linked above shows how to turn them into the number of portions you would have to sell to cover the fee. If the organiser doesn't answer, treat that as information about how the rest of the event will run.

Tracking deadlines, fees and outcomes

Once you apply to more than two events a season, memory fails. A tracker with one row per event keeps the dull facts in one place, and an assistant can maintain it from the emails you forward or paste.

The outcome column is where the learning sits. After a decline, a short, polite reply asking what would strengthen next year's application often gets an answer, and an assistant can help word it:

Thank you for letting us know. If you have a moment, could you tell us whether anything in our application held us back, such as the menu mix or the paperwork? We'd like to apply again next year with a stronger submission. [your name], [truck name]

Paste any feedback you receive into the Project and ask the assistant to propose one change to the facts sheet, not to the answers. Improving the source improves every later application, and that is the real advantage of working this way.

Six ways an AI draft sinks a vendor application

• Invented credentials. "Award-winning", "locally sourced", "ten years' experience". It shows up as a bracket-less sentence when you audit the source tags. Fix it with the cannot-prove list.
• One organiser's limits leaking into another's. A draft sized for 80 words is pasted into a field capped at 50, and the form truncates it mid-sentence. Keep each application in its own chat and have the assistant report the word count.
• A stale facts sheet. The draft quotes last year's permit date or a crew size that has changed. Put a refresh date at the top and treat any draft older than three months with suspicion.
• A tone that is not yours. Read the final text aloud. If you would not say it to the organiser across a counter, rewrite it.
• A menu list that stops at the headline dishes. When only listed items may be sold, an unlisted drink or special on the day is a breach. List everything you might sell, up to the limit, including drinks and sides.
• Documents pasted into a chat. Certificates carry policy numbers and addresses. Describe them in a line of plain text instead, as the gap-check prompt does.

For planning which pitches to chase in the first place, how food trucks use AI to plan stock, pitches and posts picks up where this stops, and a draft, check and sign-off routine like the AI content approval workflow suits any customer-facing text you reuse, from a bio to a menu board.

Questions about using AI on vendor forms

Should I tell an organiser I used AI to draft my application?

If the form or its terms ask, or restrict AI use, follow them and answer honestly. Otherwise the answers are yours, built from facts you supplied, and you remain responsible for every claim. Keep the facts sheet so you can show where any statement came from if an organiser queries it.

Is it safe to paste my insurance certificate into a chatbot?

Avoid it. The assistant only needs the insurer's name, the cover limit, the named insureds and the dates, which you can type in as plain text. Leave policy numbers, home addresses and licence numbers out, and type them into the form yourself. Check the model-training switch in your privacy settings too.

What if I don't have a document the form asks for?

Say so plainly and give the date you expect to have it, or ask the organiser whether a later upload is allowed. Never use an assistant to produce a plausible-looking certificate or letter. Only your insurer, inspector or prep kitchen can issue those, and organisers do check.

Can an AI agent fill in and submit the form for me?

I would keep submission manual. These forms often carry a non-refundable fee and binding terms, and Anthropic's own safety page for its browser agent advises avoiding financial accounts and legal documents or contracts. Let the assistant draft the text, then paste it in and press submit yourself.

Further reads

• Food Truck Marketing: Build an Email and SMS Regulars List With AI — Build a regulars list so events aren't your only source of customers.
• Food Truck Booking Software: Screen Private-Event Requests With AI — Handle private-event enquiries that arrive after a good festival.
• Food Truck Ordering App: Pre-Orders, Pitches and Where AI Helps — Add pre-orders to cut queues at busy pitches.
• Street Food Stall Business Plan: Pitch Fees, Margins and Stock With AI — See how pitch fees and margins fit a yearly plan.
• How to Write Menu Descriptions With AI That Still Sound Like You — Write menu descriptions for the form in your own voice.
• Food Truck Name Generator AI: Prompts, Trademark and Domain Checks — Check names and trademarks before they go on a form.
• Can AI Write a Business Plan for a Food Truck? A Worked Example — See festivals and markets inside a full food truck plan.
• Coffee Cart Business Plan: Costs, Pitch and Menu Built With ChatGPT — Plan start-up costs, pitch fees, per-cup margins and break-even cups for a coffee cart in one spreadsheet, with ChatGPT drafting and you checking.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: OpenAI's and Anthropic's help pages on Projects, and Anthropic's safety guidance for Claude in Chrome (October 2026). The sample brief, facts sheet, answers and figures are illustrative; each organiser's own vendor pack governs.