AI Video for Event Promo: Booth Loops, Speaker Bumpers, and Recap Teasers

AI video for event promo works when every clip has a physical job. A save-the-date gets the calendar block. A social teaser explains why the room is worth the trip. A booth loop holds attention at ten feet. A speaker bumper introduces a real person with a real session title. A recap teaser extends the story after the doors close, without pretending generated crowds were in the hall.

Do not start by prompting a generic "exciting conference montage." Start with facts the attendee can verify: date, city, venue or booth, who should come, and what they will be able to do on site. If those facts are fuzzy, the video will sell a vibe instead of an event.

This page is for in-person and hybrid gatherings: conferences, trade shows, product launches, community meetups, partner summits, and roadshows. It is not a webinar registration playbook. If the "event" is a fully virtual session with a signup page and a replay, use AI video for webinars and treat this guide as optional support for any on-site component.

For marketing teams that need a broader creative stack around campaigns, see AI creative tools for marketing teams. For testing short clips in one workspace, start with the AI video generator after you have a fact sheet, not before.

The short answer

A usable event promo clip usually does five things:

1. Makes the gathering recognizable in the first frame (event name, product, stage, or booth cue).
2. Tells a muted viewer the time-and-place job: save a date, visit a booth, hear a speaker, or watch a recap.
3. Keeps date, city, venue, and agenda aligned with the live event page.
4. Treats speaker faces and names as rights-sensitive assets, not prompt decorations.
5. Uses generated people and crowds as illustration only, never as attendance proof.

The better workflow is still -> motion -> overlay -> placement QA. Generate a few short variations, then overlay the verified date and CTA in edit. That is usually more reliable than asking a model to spell the venue correctly inside the pixels.

Event promo is a place problem, not a registration funnel

Webinar video often has one conversion: register, then attend, then watch the replay. In-person and hybrid promo has several conversions that do not collapse into one landing page.

Typical jobs:

• Get a calendar hold months out, when the agenda is still thin.
• Get a booth visit during a noisy show floor.
• Get a room filled for a 30-minute talk.
• Get a product launch RSVP for a city venue with a hard capacity.
• Get a meetup RSVP from a local community that already knows the host.
• Get a recap click that does not invent a packed house.

If you copy a webinar teaser structure onto a trade show booth screen, you will often get a clip that asks people to "register" while they are already standing in the aisle. Match the clip to the distance and the decision in front of the viewer.

Email packaging is its own constraint. If the teaser will live in a nurture sequence, pair this workflow with AI video for email marketing. If the audience is on LinkedIn, use AI video for LinkedIn for crop, tone, and claim safety, then keep event facts from this page.

Who this workflow is for

Use this guide if you are:

• a conference or community marketer building a promo kit without a film crew
• a product marketer launching in a venue, not only on a website
• a field or events team that needs booth loops and speaker bumpers in the same week
• an agency producing event assets for a client who already locked a date and venue
• a founder hosting a meetup or small launch and needing honest, short clips

This is a weaker fit if:

• you need a documentary of the live day (hire or assign a real camera)
• you need legal-grade proof of attendance, sponsors, or crowd size
• you need a two-minute cinematic brand film with no review time
• you are promoting a purely virtual webinar (use the webinar article)

AI video can still help those teams with titles, bumpers, and social crops. It should not replace the live capture you will later need for recap honesty.

Lock the event facts before any prompt

Write a one-page fact sheet and treat it as source of truth. Prompts should borrow from it. They should not invent missing pieces.

Minimum fields:

1. Official event name (including year or season if that is how you brand it).
2. Date range and timezone if attendees travel.
3. City and venue (or "booth number" for a show floor).
4. Audience (who should spend the trip or the hour).
5. One reason to attend that is still true if the keynote slides change.
6. Must-not-claim list (attendance numbers, sponsor logos you cannot show, features not shipping, "sold out" unless operations confirms it).
7. Speaker list with approval status (approved photo, approved title, approved session name).
8. Hybrid note (what is on site vs livestream vs later replay).

Example fact sheet:

• Event: Northwind Product Launch Night
• Date: 12 November 2026, doors 18:00
• Place: Warehouse Studio, Berlin
• Audience: existing customers and invited press
• Reason: see the new handheld scanner in a 12-minute live demo, then Q&A
• Must not claim: "1,000 attendees," invented press logos, a feature that is waitlist-only
• Speakers: Maya Chen, Head of Product (photo approved); guest user (photo not approved, do not animate)
• Hybrid: in-person only; no livestream; recap email after

If you cannot fill the fact sheet, you are not ready to generate promo. You are still in event design.

On-screen text is the most common factual failure. Models often misspell venues, invent street names, or shift dates. Prefer a clean visual with empty caption space, then add the verified line in your editor. That is slower in the first hour and faster across a ten-asset kit.

Map the asset kit, one job per clip

Most event programs need a small library, not one hero film.

Pre-event

1. Save-the-date: month, city, event name. No fake agenda.
2. Reason-to-attend teaser: one outcome or one demo moment.
3. Speaker bumper: one person, one session, approved still.
4. Agenda motion: chapters as graphics, not a voiced manifesto.
5. Reminder: date plus one logistical cue (doors, booth number, transit).

On-site

6. Booth loop: readable at walking distance, comfortable for hours.
7. Stage bumper: short intro before a talk.
8. Wayfinding loop: "this way to demo" style, only if operations wants it.

Post-event

9. Recap teaser: one real takeaway plus a next step (on-demand demo, next city, waitlist).
10. Thank-you bumper: for email or LinkedIn, using real stills when people are shown.

Do not merge 1, 6, and 9 into a single 45-second clip. A booth loop that contains a "register now" end card will look wrong on the floor. A recap that still says "join us tomorrow" will look careless.

For stronger social openings, use the AI video hook generator workflow on teasers only. Hooks are for feeds. Booths need loops. Do not force a hook structure onto a repeating kiosk clip.

When to use AI video for events, and when not to

Use it when

• you need many short crops from one approved visual system
• the venue will not allow a pre-shoot, or the booth build is not ready
• speaker photos exist but you lack bumper footage
• you want mood tests before paying for a live crew day
• you need a looping product or logo motion for a silent screen
• the recap needs graphic glue around real photos you already have

Do not rely on it alone when

• sponsor contracts require exact logo lockups in broadcast quality
• you must prove who was in the room
• a speaker has not approved promotional use of their face
• the product shape, color, or UI must match a shipping SKU exactly and you have no source still
• local advertising rules require disclosures you have not reviewed
• the clip will play next to a physical product that looks different from the generated one

A generated "hero product on a dark stage" can still be useful as a teaser if the real SKU is shown on the event page and in the booth. It becomes a problem when the booth screen shows a different colorway than the table.

Decision tree: pick the generation path

Start at the top. Stop at the first yes.

1. Will this clip repeat for a long time on a physical screen?
   Yes: treat it as a loop. Design first and last frames to match. Use the AI seamless loop video rules, then return here for event facts.

2. Must a real logo, product, UI, or face stay recognizable?
   Yes: create or choose an approved still with the AI image generator or from your brand kit, then animate with the image to video AI generator.

3. Is this only a mood or lighting test before design lock?
   Yes: a short text-to-video test can be fine. Do not publish it with dates until facts are overlaid and checked.

4. Is the session fully virtual?
   Yes: switch to AI video for webinars. Keep this page only if you also have a physical booth or afterparty.

5. Is this a recap that will show people?
   Yes: start from real photography or video. Use AI for titles, transitions, and product B-roll. Do not generate a packed auditorium and caption it as last week's turnout.

6. Otherwise: lock a mute-safe first frame, generate a short take, overlay facts, export per placement.

That tree saves credits because you stop generating cinematic crowds when the job is a date lockup.

Cost follows volume. A conference kit with ten loops and twenty speaker bumpers can spend more than a single social teaser. Compare routes on the current models page and check pricing before you batch. Cliprise uses credits for generation. Do not plan a show-floor library from a screenshot of someone else's price list.

First frames for events: readable at a glance, honest at a pause

Event video is often watched muted, in a bright hall, or in a noisy feed. The opening still has to work without audio. For composition rules that apply beyond events, use AI video first frame design.

Event-specific first-frame tests:

• Ten-foot test: on a phone at arm's length, can you tell it is this event, not a stock "business conference"?
• Pause test: if someone screenshots second zero, does the image still make sense?
• Caption room: is there a quiet band for date, booth number, or speaker name?
• Logo integrity: does the mark look like your files, or like a cousin of your files?
• People honesty: if a face is shown, is it an approved speaker or an obvious illustration?

A first frame that needs a voiceover to explain "Summit 2026, Austin" is not ready for social or for a booth.

Build the still first when you care about lockups. Animate second. Text-to-video can invent a beautiful hall that is not your hall. That is acceptable for mood boards. It is risky as the only asset on the event page.

Model choice for event work: job first, demo second

Choose the route by the job, not by the most cinematic sample on the internet.

Check current models for what you can actually run today. Availability and credit cost can change. If two routes can both do "slow push-in on a lockup," pick the one your team can review fastest, not the one with the flashiest trailer.

Prompt patterns that keep events specific

Keep prompts visual. Put legal facts in overlays. Say what the camera does. Say what must not happen.

Save-the-date, empty caption band

Clean event key art: dark studio, single spotlight on a product silhouette,
subtle dust in the air, slow camera push-in,
large empty lower third for later date text,
no readable letters, no crowd, no invented skyline,
premium product launch teaser, 16:9

Booth loop, product truth

Locked camera on a physical handheld scanner on a matte black plinth,
soft light sweep left to right, logo facing camera the whole time,
no people, no text, loop-friendly motion,
product shape must stay accurate, 16:9

Speaker bumper from an approved still

Animate this approved headshot only:
subtle breathing, tiny eye light shift, camera locked,
neutral office bokeh, no new clothing, no extra fingers,
leave the lower third empty for name and session title,
no captions generated in the image

Reason-to-attend teaser (outcome, not crowd)

Over-shoulder view of a demo table with one device and a simple diagram card,
slow dolly in, shallow depth of field,
trade show booth lighting, no readable UI text,
no crowd, empty right side for later overlay,
professional event promo

Meetup, local and small

Warm cafe interior, one communal table, evening window light,
slow pan across empty chairs and name badges on a table,
no faces, no city name text,
friendly community meetup mood, 4:5

Recap graphic, no fake attendance

Motion graphic style: event logo lockup on charcoal,
thin gold line drawing a simple floor-plan shape,
slow opacity fade, no photoreal people,
empty area for a real photo to be placed in edit,
post-event title card

If you need a social hook on top of these stills, write the hook as a separate overlay line ("See the scanner live in Berlin") rather than asking the model to typeset it. Overlay text is easier to correct when the date slips by a day.

After you have a still you trust, generate motion in Cliprise with available video routes. For campaign-scale marketing production beyond a single event, marketing solutions outlines how teams often batch creatives. Stay event-specific here: every take should still map to a row in your asset kit.

Booth loops: the clip has to survive a long day

A booth loop is not a trailer. People will see it 40 times while they talk to your staff. If it jumps, strobes, or cycles a hard CTA every five seconds, it becomes noise.

Practical booth rules:

• Duration: many teams land between 4 and 8 seconds per cycle. Longer can work if motion is calm.
• Motion: light sweep, slow orbit, gentle parallax. Avoid whip pans.
• Text inside pixels: avoid. Overlay a booth number or "Live demo every 20 minutes" in a tool you control, or print it on the physical backwall.
• Audio: assume the floor is loud. Design for mute. If you add sound, keep it optional and not dependent on dialogue.
• Viewing distance: large subject, high contrast, simple background.
• Hardware: confirm the player, resolution, and whether the screen letterboxes 9:16 files.

Loop join quality is a separate craft. Use AI seamless loop video for first-last frame matching, then run the event QA in this article (logo, product, agenda honesty).

Booth loop checklist:

• First frame readable at ten feet
• Last frame close to first
• Five muted repeats feel comfortable
• Logo and product do not morph
• No "register by Friday" card if the show is already open
• File plays on the actual media player, not only on a laptop
• Brightness holds up under hall lighting

If the booth has both a vertical totem and a horizontal TV, generate two crops from the same still. Do not stretch one file.

Speaker bumpers and likeness rights

Speaker bumpers are high trust and high risk. A good bumper is five to ten seconds: approved portrait, accurate name, accurate session title, then a cut to the host or the slides.

Rights and review:

• Get written permission for promotional use of the photo and any animation of that photo.
• Do not invent quotes, employers, or talk titles.
• Do not swap in a lookalike or a generated "same energy" face.
• If the speaker sends a new headshot the week of the show, rebuild the bumper from that still.
• Disclose synthetic presenters if your legal or brand policy requires it. Many teams skip synthetic hosts entirely for live events.

When permission is missing, promote the session topic with branded graphics:

Bold typographic stage card, event colors,
slow gradient shift, empty lower third,
no faces, no fake audience,
session bumper background

Then overlay "Pricing roundtable • Room B • 14:10" from the official agenda.

Do not use a generated audience clapping behind a real speaker. That reads as fake social proof even if you meant it as decoration.

Save-the-date and social teasers

Social teasers have a different clock than booth loops. The job is often a calendar hold or a profile click.

A simple timing pattern:

• Seconds 0 to 2: event or product recognition
• Seconds 2 to 6: one reason to attend
• Seconds 6 to 12: date or city cue (overlay)
• Final seconds: next step (RSVP, booth number, "save the date")

For feed openings, borrow structure from the AI video hook generator workflow, then keep event facts conservative. Curiosity is fine. Fake scarcity is not ("only 12 seats left") unless operations confirms it.

Channel notes:

• LinkedIn: professional framing, one claim, less party-confetti energy. See AI video for LinkedIn.
• Email: thumbnail or GIF preview, hosted video on the event page. See AI video for email marketing.
• Stories and short-form: 9:16, captions, no tiny booth maps.

Save-the-date anti-patterns:

• Rendering a calendar with the wrong weekday
• Showing a skyline that is not the host city
• Listing speakers who are "invited" but not confirmed
• Using last year's venue photo as if it were this year's

If the city is part of the brand ("London Summit"), you can use a licensed or owned city still, then animate clouds or light. Generating "iconic London" from a prompt often invents architecture. That can be fine as illustration if you do not caption it as the venue. It is not fine if viewers think they will walk into that exact building.

Product launches, conferences, trade shows, meetups

The same kit logic applies. The emphasis changes.

Product launch in a venue

Sell the demo moment, not a music-video crowd. Attendees want to know what they will see, whether there is hands-on time, and whether press rules apply.

Good teaser promise: "See the scanner capture a damaged label in one pass, then ask the team."
Weak teaser promise: "The future of logistics is here" with fireworks.

If the product must stay on-model, start from a pack shot or CAD still, then use image-to-video. Compare the output against the physical unit before the screen goes up.

Conference (your own or a sponsored track)

You may need a program teaser plus many speaker bumpers. Batch the bumpers from a portrait template. Change only the still, the overlay name, and the session title. Do not regenerate a new cinematic world for each speaker. Consistency makes the stage look intentional.

Agenda accuracy matters more than motion quality. A beautiful bumper with last year's talk title is still a miss.

Trade show booth

The aisle is the channel. Assume three seconds of attention from a walker, then a longer look from someone who stops. The loop should make sense to both. Staff should be able to talk over it. Avoid dialogue.

If you share a booth with a partner, do not generate their logo. Use provided artwork.

Community meetup

Small rooms punish overproduction. A clip that looks like a 5,000-person keynote will feel disconnected from a 40-person Tuesday evening. Show tables, badges, a simple map pin overlay, and the host's real face if they agree.

Meetup recap: a few real phone stills plus a title card will often beat a generated "packed house."

Hybrid events: split the kit, do not blend the promises

Hybrid usually means some people are in the room and some people are on a stream. Those groups need different CTAs.

• On-site clip: doors, badge pickup, booth hours, stage room.
• Remote clip: stream link, start time with timezone, what they will not get (no hallway conversations, no swag).
• Shared clip: topic and speakers, if those are the same.

Do not tell remote viewers to "find us at booth 2142" unless you also give them a stream action. Do not tell in-person attendees to "register for the webinar" as the only CTA on a looping TV.

For the virtual session pieces (registration reminder, opener, replay), use AI video for webinars. Keep this article for the physical layer: signage, booth, stage bumpers, city RSVP.

Recap teasers without inventing the room

Post-event video is where teams most often overreach. A generated crowd looks like proof. It is not proof.

Honest recap stack:

1. Real photos or clips you have rights to use.
2. Graphic titles for the event name and date (past tense).
3. Optional AI B-roll of the product or of abstract brand motion.
4. One takeaway that was actually said or shown.
5. A next step that exists: demo booking, next city, on-demand recording if you recorded.

Label illustrative B-roll if a reasonable viewer could think it was documentary ("artist's impression of the hall" is clearer than nothing, and often you should just not use a fake hall).

Recap claims to avoid unless operations confirms them:

• headcount
• "standing room only"
• named customers in the audience
• press outlets that did not attend
• quotes nobody approved

If you have almost no real photography, a graphic recap is allowed. A photoreal recap of a room you cannot show is not a good substitute.

Scenario walkthroughs

Scenario A: SaaS booth at a three-day conference

Goal: silent 16:9 loop on a backwall TV, plus a 9:16 teaser for LinkedIn.

Process:

1. Lock facts: booth C41, live demo every 20 minutes, no attendance claims.
2. Build a still of the actual product UI from a screenshot, simplified, with a large device in frame.
3. Animate a slow light sweep only.
4. Overlay "Booth C41 • Live demo" in edit.
5. Export 16:9 for the TV and a separate 9:16 crop for social, captions added.
6. QA the loop for five minutes on a laptop, then on the real player if you can get it early.

Reject if: the UI labels turn into gibberish, or the overlay still says "Register."

Scenario B: City product launch, 120-person cap

Goal: RSVP teaser that does not imply a stadium.

Process:

1. Fact sheet includes venue name and "invitation only."
2. First frame: product on a table, warm warehouse light, empty foreground for overlay.
3. Motion: slow push-in, no crowd.
4. Overlay date, neighborhood, and RSVP.
5. Email uses a still thumbnail that matches the first frame. Full clip lives on the event page.

Reject if: the model adds a cheering audience or a red carpet that the venue will not have.

Scenario C: Monthly meetup, volunteer-run

Goal: one 8-second 4:5 clip for social, reusable monthly with new overlays.

Process:

1. Create a durable still: cafe table, notebooks, event color stripe, no faces.
2. Light parallax only, loop-friendly if you also post it as a story background.
3. Each month, change only the overlay: date, topic, RSVP link.
4. After the meetup, post two real photos. Do not generate "highlights."

Reject if: the clip looks like a corporate keynote and the room is a back room of a bar.

Scenario D: Speaker series bumpers for a one-day summit

Goal: twelve bumpers that feel like one show.

Process:

1. Collect approved headshots and session titles in a spreadsheet.
2. One lighting template. One motion recipe (locked camera, subtle life).
3. Generate from each still with the same prompt.
4. Overlay names from the spreadsheet, not from the model.
5. Speaker review: send a private preview. Replace any clip they reject.
6. Keep rejected stills out of recap videos too.

Reject if: hair, clothing, or face structure drift, or the overlay title does not match the program PDF.

Scenario E: Recap for a trade show week

Goal: 12-second LinkedIn clip after the show.

Process:

1. Select three real booth photos (staff consented).
2. Generate only a title card and a product motion insert from an approved pack shot.
3. Edit: title card, real photo, product insert, real photo, next-city overlay.
4. Caption: what you demoed, not how many people "flocked."

Reject if: any shot of a generated queue is used as if it were the aisle.

Production checklist (pre-generation)

• Fact sheet signed off by events or ops
• Asset kit listed by placement (booth, stage, social, email, recap)
• Approved stills collected (logo, product, portraits)
• Must-not-claim list shared with whoever writes overlays
• Hybrid CTAs split if needed
• Current models chosen for still vs motion
• Credit budget checked against pricing
• Speaker approval path named (who sends previews)

Generation checklist

• One job per prompt
• Empty caption band in the frame
• Restrained camera move
• No requested crowd for recap or "proof"
• Short takes first, not 30-second epics
• Variations change one variable (crop, move, background), not the date

Placement and export checklist

Match files to screens. Then run a technical pass using AI video export settings.

Keep a protected master. Make delivery copies per placement. Do not auto-crop a booth loop into a story and assume the logo still sits in the safe area.

Event promo QA scorecard

Score each clip from 1 to 5. Publish only if nothing critical is a 1 or 2.

1. Fact match: date, city, venue, booth, and agenda match the live page.
2. First-frame clarity: muted, small screen, event is recognizable.
3. Job fit: save-the-date, booth, bumper, or recap is obvious.
4. Product or brand truth: logo, SKU, and colors survive motion.
5. Likeness and naming: faces and titles are approved and spelled right.
6. Crowd honesty: no generated attendance presented as documentary.
7. Loop comfort: if it repeats, the join and pacing are tolerable.
8. Caption coexistence: overlays do not cover faces or logos.
9. Placement crop: safe areas work on the real screen or feed.
10. Claim safety: no unofficial sponsors, capacity boasts, or shipping promises.

Automatic reject:

• wrong date or weekday
• speaker who declined promotional use
• morphing logo
• photoreal crowd used as recap proof
• CTA that contradicts the placement (register-now on an open booth)
• UI or product details that would mislead someone walking up to the table

Have one person who did not write the prompt do a "stranger test": watch muted, then say what event they think it is and what they should do next. If they cannot, regenerate or recut.

Common mistakes

Starting with "epic event energy." Energy is not a fact. You get fireworks, flying cameras, and no booth number.

Putting the agenda inside the generated pixels. Session titles will drift. Overlay from the program.

Using one clip for social, booth, and recap. The CTA and tense will be wrong for at least one of those.

Animating speakers without a paper trail. Even a flattering motion can be a rights problem.

Generating the venue as if it were a photograph of the contract location. Illustrative interiors are fine if you do not imply that is the hall. Real venue photos from the venue's press kit are safer when you need recognition.

Fake social proof. Generated queues, fake badges, invented press walls, and "sold out" stickers used as decoration.

Ignoring the ten-foot booth test. A clip that looks sharp on a laptop can collapse under show lighting.

Forgetting mute. Halls and feeds are loud. If the joke is in the VO, the booth TV will look idle.

Skipping the loop watch. A 6-second clip that jumps will annoy staff by lunch.

Treating credits as unlimited because "it is just events." Speaker batches add up. Plan variations, then stop. Check pricing and current model costs before you generate a portrait for every lightning-talk speaker on a maybe list.

Copying a webinar funnel. "Register to save your seat" on a walk-up meetup poster video wastes the first two seconds.

Publishing recap video before photo consent is clear. Staff and attendees in real photos still need a rights path. AI does not solve that. It can make it worse if you generate lookalikes.

Where Cliprise helps in this workflow

Cliprise is an AI creative workspace at www.cliprise.app. For event promo, it is useful when you want to:

• build key art and first frames with the AI image generator
• turn approved stills into short motion with image-to-video
• generate and compare short takes in the AI video generator
• check which video and image routes are available on models before you promise a client a specific look

It does not replace operations, speaker contracts, or a recap photographer. Human review still owns facts, likeness, and what you imply about who showed up.

For a full event kit, a practical Cliprise pass looks like this:

1. Still lockups for save-the-date and booth.
2. Portrait bumpers from approved headshots.
3. Two or three social teasers with different hooks, same facts.
4. One loop candidate per screen ratio.
5. Recap title cards only, then edit with real photos outside the generator.

Soft midpoint CTA: if you already have a fact sheet and a logo still, create a few booth-loop and teaser concepts in Cliprise before you book a crew day you may not need for every asset.

A one-week production plan (example)

This is a planning sketch, not a promise about generation speed.

Day 1: Fact sheet, asset kit, rights list, collect stills.
Day 2: First frames for booth and save-the-date. Internal review of lockups only.
Day 3: Image-to-video for loops and one social teaser. Overlay facts.
Day 4: Speaker bumpers. Send previews.
Day 5: Fixes, second crops, email thumbnail. Export masters.
Show week: load booth files early, test on hardware.
After: recap edit from real stills plus title cards you already made.

If speaker approvals slip, ship topic bumpers. Empty stage cards are better than unapproved faces.

Next step

Pick one upcoming gathering. Write the fact sheet. Choose a single clip job (usually a booth loop or a save-the-date). Design a mute-safe still with empty caption space. Animate one restrained take. Overlay the real date. Watch it muted on a phone, then watch it loop if it will play on a screen. Only then make variations.

Create those first event promo concepts in Cliprise from a prompt or an approved still, compare a few short outputs, and keep agenda, likeness, and recap honesty in your review, not in the prompt.

Related Articles

• AI Video for Webinars
• AI Video First Frame Design
• AI Seamless Loop Video
• AI Video Hook Generator Workflow
• AI Video for Email Marketing
• AI Video for LinkedIn
• AI Video Export Settings Checklist