Skip to content

Event Production Checklist: From Advance to Strike

A working event production checklist for the handoffs that make or break a show: approvals, crew calls, content, comms, backups, and closeout.

eventools
  • event production
  • guides
  • event advance
  • event planning checklist
  • event production checklist
  • live event production
  • load-in
  • production schedule
  • run of show
  • show day checklist

An event production checklist should catch the handoffs that break shows: the unapproved deck, the crew call that moved, the playback file trapped on one laptop, the truck arriving at a dock nobody booked. This one covers the work from the first advance call through strike and closeout, with enough detail to use on a real production.

What an event production checklist is for

A useful checklist does more than prove that somebody remembered audio. It records what has to happen, who owns it, when it is due, and where the current answer lives.

That last part matters. "Alex has the latest version" is not a document-control strategy. Neither is a folder named FINAL with six files in it, although the exclamation points are a nice touch.

Every line on your master event production checklist should answer four questions:

  • What is the deliverable or decision?
  • Who owns it?
  • When is it due?
  • Where will the team find the approved version?

If a task has no owner, the producer owns it by surprise. If it has no deadline, it will be handled during load-in. If the approved version has no home, every version becomes current at once.

Copy the checklist below into the system your team will actually update. Then add owners and dates. A pristine template that nobody opens is just a very tidy failure.

Event production checklist: kickoff and scope

The kickoff turns a promising idea into a production with edges. Get the boundaries on paper before departments start designing against different assumptions.

  • [ ] Confirm the event objective, audience, format, dates, and expected attendance.
  • [ ] Name the client decision-maker and the production lead.
  • [ ] Define the approval path for budget, creative, technical scope, and show content.
  • [ ] Confirm venue holds, contracted hours, access windows, and hard-out time.
  • [ ] Set the working budget and a process for approving changes.
  • [ ] List the production departments required: audio, video, lighting, staging, rigging, power, scenic, broadcast, streaming, graphics, and labor.
  • [ ] Identify accessibility needs, including captions, assisted listening, interpretation, and accessible routes.
  • [ ] Confirm insurance, permits, security requirements, and venue rules.
  • [ ] Create the project workspace and decide where approved documents will live.
  • [ ] Set the meeting cadence and the channel for urgent production changes.

Scope is not a one-time conversation. Record what changed, who approved it, and what the change does to cost or schedule. "We thought it was included" has funded plenty of overtime.

Venue and site advance checklist

The site advance is where the room stops being a floor plan and starts becoming a set of constraints. Walk it with the people responsible for making the plan fit.

  • [ ] Confirm room dimensions, ceiling heights, stage position, seating layout, and sightlines.
  • [ ] Verify loading dock location, truck access, dock hours, freight elevator dimensions, and parking.
  • [ ] Map the path from dock to room, including door widths, floor protection, stairs, and restricted areas.
  • [ ] Confirm rigging points, load limits, approved riggers, and required engineering.
  • [ ] Verify available power, tie-in rules, cable paths, and generator placement if needed.
  • [ ] Confirm internet service, dedicated bandwidth, wired drops, network restrictions, and support contacts.
  • [ ] Locate front of house, backstage, green rooms, storage, workbox space, and charging areas.
  • [ ] Review fire lanes, egress, occupancy limits, security posts, and emergency procedures.
  • [ ] Confirm house audio, lighting, video, staging, and comms inventory before removing rentals from the quote.
  • [ ] Record venue contacts for event management, engineering, security, catering, IT, and the loading dock.
  • [ ] Photograph the dock, access route, room, power, rigging points, and anything likely to become an argument later.
  • [ ] Put every venue deadline and access window into the production schedule.

Do not leave the walk-through with a page of unlabeled photos and a promise to remember which wall was which. Add notes while you are still in the room.

Technical production and content checklist

Technical design and content are one conversation. A 4K canvas, a confidence monitor, and a scenic opening all sound reasonable until the content arrives in the wrong format ten minutes before rehearsal.

  • [ ] Approve the stage, room, scenic, seating, and front-of-house layouts.
  • [ ] Build the audio input list, output plan, wireless coordination plan, and playback list.
  • [ ] Build the video signal flow, screen plan, playback plan, graphics package, and recording requirements.
  • [ ] Build the lighting plot, fixture schedule, power plan, and focus notes.
  • [ ] Confirm rigging, staging, drape, scenic, and special-effects requirements.
  • [ ] Confirm camera positions, shot requirements, records, stream destinations, and delivery specs.
  • [ ] Define presentation dimensions, frame rate, codecs, fonts, safe areas, and file-naming rules.
  • [ ] Set content deadlines for first drafts, review, final delivery, and emergency revisions.
  • [ ] Assign an owner to every deck, video, walk-on track, voice-over, graphic, and lower third.
  • [ ] Collect speaker names, titles, pronunciations, bios, headshots, and accessibility requirements.
  • [ ] Confirm presenter laptops, adapters, clickers, notes displays, confidence monitors, and teleprompter needs.
  • [ ] Build a backup path for critical playback, presentation, microphones, comms, power, and internet.
  • [ ] Schedule technical tests for streams, remote contributors, captions, playback, and show control.
  • [ ] Store approved content where both the show team and the backup operator can reach it.

The word "final" is not approval metadata. Track who approved the file and when. Keep the previous known-good version until the new one has been tested on the actual show system.

Crew, vendors, and logistics checklist

Gear does not unload itself, no matter how enthusiastic the quote was.

  • [ ] Confirm vendors, scopes, quotes, purchase orders, payment terms, and on-site contacts.
  • [ ] Build the crew plan by department, position, call time, release time, and rate.
  • [ ] Confirm travel, hotels, parking, credentials, per diem, and local transportation.
  • [ ] Check labor minimums, meal rules, turnaround, overtime, and venue or union requirements.
  • [ ] Assign department heads and make reporting lines clear.
  • [ ] Send crew calls with the venue address, parking instructions, entrance, on-site contact, dress code, and required tools.
  • [ ] Build the trucking plan with vehicle sizes, drivers, contents, dock slots, and unload order.
  • [ ] Confirm equipment substitutions and update any plan affected by them.
  • [ ] Schedule deliveries, pickups, couriers, rentals, and return deadlines.
  • [ ] Plan credentials for crew, vendors, talent, clients, and restricted areas.
  • [ ] Confirm water, coffee, meals, dietary needs, and a place for the crew to take a real break.
  • [ ] Share the current production schedule with every department.
  • [ ] Create a contact sheet that works on a phone, because nobody wants to zoom into a 40-column PDF in the dock.

Calls need a single source. A change made in the labor plan but not the production schedule is how one department arrives at 8:00 and the room opens at 10:00.

Final-week event production checklist

The final week should reduce uncertainty. If the meeting creates twelve new creative directions, congratulations on your new rehearsal plan.

  • [ ] Freeze the technical scope or document every approved late change.
  • [ ] Review the budget against current quotes, change orders, labor, travel, and contingency.
  • [ ] Publish the latest production schedule with load-in, rehearsals, show calls, breaks, strike, and hard outs.
  • [ ] Publish the latest run of show with durations, owners, department cues, and fixed-time anchors.
  • [ ] Confirm the room layout, stage plan, technical drawings, signal flows, and patch lists.
  • [ ] Verify that every crew member, vendor, and presenter has the information they need to arrive.
  • [ ] Collect final content and run a technical check on the systems that will play it.
  • [ ] Confirm remote callers, streaming destinations, passwords, and test times.
  • [ ] Print or cache the documents required to work through an internet outage.
  • [ ] Pack adapters, chargers, labels, media, batteries, show drives, and the boring items that become very interesting when missing.
  • [ ] Hold a department-head review focused on conflicts, assumptions, and failure paths.
  • [ ] Confirm weather plans, emergency contacts, medical response, evacuation roles, and client communications.
  • [ ] Decide who can approve a live change and how that decision reaches the crew.

This is also the time to delete stale shared links and stop circulating attachments. One live version beats six PDFs and a group chat full of archaeology.

Load-in and rehearsal checklist

Load-in is the first full test of the plan. Treat every mismatch as useful information, preferably before doors.

  • [ ] Check in with venue operations and confirm access, room turnover, dock, power, network, and hard-out conditions.
  • [ ] Walk the space with department heads before cases spread across the floor.
  • [ ] Hold a safety briefing and confirm emergency exits, work-at-height rules, and first-aid contacts.
  • [ ] Protect floors and walls, mark work zones, and keep egress clear.
  • [ ] Check deliveries against the trucking plan and note shortages immediately.
  • [ ] Build in dependency order: rigging and power before flown systems, infrastructure before dress, testing before rehearsal.
  • [ ] Label signal, power, network, playback, comms, and spare paths clearly.
  • [ ] Test every input and output, including backups.
  • [ ] Confirm comms coverage at front of house, backstage, stage management, camera positions, loading dock, and other working areas.
  • [ ] Load and test every approved deck, video, graphic, walk-on track, and voice-over.
  • [ ] Run remote presenters and streams end to end, including return video, audio, and backup contact methods.
  • [ ] Rehearse transitions, walk-ons, playback, demos, panels, and any cue with several departments moving at once.
  • [ ] Time the show against the current run of show and correct the durations.
  • [ ] Record changes in the live documents while they happen.
  • [ ] Save an approved pre-show version after rehearsal.
  • [ ] Reset the room, charge devices, replace batteries, clear trip hazards, and secure show content.

Rehearsal notes that never reach the rundown are just observations. Update the working document while the problem and the people needed to solve it are still in the room.

Show-day checklist

Show day is for execution. The decisions that could have been made yesterday charge a premium today.

  • [ ] Confirm the room, stage, front of house, backstage, and audience areas are show-ready.
  • [ ] Run system checks for audio, video, lighting, comms, network, playback, records, streams, captions, and show control.
  • [ ] Verify primary and backup playback files against the approved content list.
  • [ ] Check microphones, batteries, frequencies, labels, and handoff positions.
  • [ ] Confirm talent arrival, green-room status, mic times, walk-on routes, and stage management handoffs.
  • [ ] Brief front of house, backstage, camera, security, venue, and client teams on the current plan.
  • [ ] Confirm who is calling the show and who has authority to change it.
  • [ ] Lock public doors, show start, meal service, broadcast windows, and venue curfew as fixed-time anchors.
  • [ ] Keep department heads on the current live run of show.
  • [ ] Log actual start times, incidents, content changes, and decisions that affect later sessions.
  • [ ] Protect breaks and rotate coverage so the crew can eat without abandoning a position.
  • [ ] Reset the room, content, batteries, comms, and notes between sessions or show days.
  • [ ] Save an end-of-day version and brief the next shift on every open issue.

Keep urgent communication short and operational. Headset is a terrible place for a committee meeting.

Strike and closeout checklist

The audience leaving is a milestone, not the end of the job. The venue still wants its room back, vendors want their gear, and finance would eventually like receipts from this decade.

  • [ ] Confirm the room is clear and the strike release has been given.
  • [ ] Review the teardown sequence and keep the hard out visible.
  • [ ] Power down, disconnect, lower, and pack equipment in a safe dependency order.
  • [ ] Check rental gear against manifests and separate damaged or missing items.
  • [ ] Load trucks in the planned order and record changes to destination or contents.
  • [ ] Remove tape, cable ramps, floor protection, signs, credentials, and production waste.
  • [ ] Walk the venue with the appropriate contact and document damage or outstanding work.
  • [ ] Return rentals, radios, credentials, keys, and access devices.
  • [ ] Back up show files, records, photos, logs, and final production documents.
  • [ ] Reconcile purchase orders, invoices, expenses, labor hours, overtime, and change orders.
  • [ ] Send client deliverables with owners and due dates.
  • [ ] Hold a short debrief while the useful details are still fresh.
  • [ ] Record what should become a template, a standard, or a warning for the next show.
  • [ ] Revoke temporary share links and archive the project.

A debrief does not need an hour of mutual admiration. Ask what failed, what nearly failed, what saved the show, and what the team should change next time. Then assign the follow-up work.

How the production documents fit together

The checklist tracks completion. It should point to the working documents, not absorb all of them into one enormous sheet.

The production schedule owns the days and hours around the show: deliveries, crew calls, load-in, rehearsals, breaks, strike, and load-out. The run of show owns the live program: cues, durations, departments, talent, and fixed-time anchors. Labor schedules, trucking plans, technical drawings, contact sheets, budgets, and content lists each answer their own set of questions.

Connect them around shared facts. A crew call should not need to be typed into three places. Neither should a room name, venue address, show date, or contact. Copy-paste is not quality control.

Common checklist mistakes

  • No owners. A list of tasks with nobody accountable is a wish list.
  • No dates. "Before the show" is a deadline only in the loosest legal sense.
  • No dependencies. You cannot test the LED wall before it has power, signal, and an LED wall.
  • No approval state. Draft, reviewed, approved, and superseded are different things.
  • Too much detail in one list. Link to the current technical plan instead of pasting half of it into a checkbox.
  • No field access. If the crew cannot open it on a phone at the dock, it is not the master checklist.
  • No closeout. Unreturned rentals and unbilled change orders are still production problems.
  • Blind reuse. Templates save time until an old venue rule quietly becomes a new-show assumption.

Put the checklist next to the work

eventools.io keeps the project documents that carry a production from prep through show day in one connected workspace. Build the production schedule, labor plan, trucking schedule, budget, flowsheets, and run of show against the same project instead of rebuilding the same facts in separate files.

Use the checklist to ask whether the work is done. Use the live document to do the work.

Build your next show in eventools.io.

Frequently asked questions

What should be included in an event production checklist?

Include the decisions, deliverables, and handoffs from kickoff through closeout. At minimum, cover scope, budget, venue advance, technical design, content, crew, vendors, logistics, the production schedule, the run of show, load-in, rehearsal, show-day checks, strike, and financial reconciliation. Give every line an owner, deadline, and link to the current source.

When should event production planning start?

Start as soon as the event dates, venue, and decision-maker are known. The first version can be rough. Early planning is where you expose long-lead equipment, venue restrictions, labor constraints, content deadlines, and approval bottlenecks before they become rush fees.

Who owns the event production checklist?

The producer or production manager usually owns the master checklist, while individual tasks belong to department heads, vendors, client stakeholders, or venue contacts. Ownership should be explicit. The person maintaining the list does not need to perform every task.

What is the difference between an event planning checklist and an event production checklist?

An event planning checklist covers the whole event, including registration, marketing, sponsorship, guest experience, catering, and programming. An event production checklist focuses on the systems and people that build and run the live experience: venue access, technical design, content, crew, equipment, rehearsals, cues, comms, safety, strike, and closeout.

What should be checked on the day of an event?

Check the room, stage, audio, video, lighting, playback, comms, network, streams, captions, records, show control, content, microphones, talent status, backstage routes, emergency contacts, and all backup paths. Confirm that every team is reading the current run of show and knows who can approve a live change.

How do you manage last-minute event changes?

Put one person in charge of approval, record the decision in the live source, and tell every affected department through the agreed channel. Update timing, labor, budget, content, and technical plans together when the change touches them. A change is not complete because somebody mentioned it on headset.