Concert Production Schedule Template: Load-In to Load-Out

TL;DR — A concert production schedule turns venue access, crew calls, load-in, setup, checks, meals, doors, sets, curfew, strike, and hard-out into one timed plan. Each row needs a start, finish, owner, location, dependency, and status. Lock immovable constraints first, schedule work in dependency order, allow realistic handoffs, and publish one current timezone-labeled revision. A rider supplies requirements; the production schedule assigns when the agreed work happens.

Table of contents

1. What a production schedule controls
2. Copyable concert schedule template
3. Build the schedule in dependency order
4. Schedule checks, doors, and performances
5. Manage changes on show day
6. FAQ

What a production schedule controls

A concert production schedule is the operational timeline for preparing, running, and clearing a show. It coordinates departments and spaces; it is not merely a list of artist set times.

The schedule should answer:

• When can each team and vehicle enter?
• Who reports at each call?
• Which task must finish before another starts?
• Where does each activity happen?
• When are the stage, PA, lighting, backline, and power ready?
• When can line check, soundcheck, doors, and performances occur?
• What are the noise curfew, venue curfew, and hard-out?
• Who decides and communicates a change?

A tech rider describes performance requirements. A venue tech pack describes the room and installed resources. The production schedule converts the reconciled plan into timed work.

Copyable concert schedule template

Use a table that can be filtered by department while preserving one master chronology.

These times are illustrative. Derive actual durations from the room, access route, labor rules, production design, artist requirements, curfews, and experienced department leads. Never copy example times into a live plan without validating them.

Fields worth keeping

Every schedule row should have:

• start and finish, not only a start;
• activity and deliverable;
• one accountable owner;
• location;
• prerequisite or dependency;
• status or decision note.

Also place the show date, local timezone, venue and room, revision timestamp, schedule owner, and emergency/decision contacts at the top.

Build the schedule in dependency order

1. Lock immovable constraints

Start with facts the show must respect:

• building and loading-dock access;
• permitted work and noise windows;
• audience doors;
• advertised performance times;
• legal or venue curfews;
• required breaks or staffing constraints;
• transport departure;
• hard-out and building closure.

Confirm whether curfew means amplified-audio stop, performance end, audience clear, crew clear, or building closed. These are different milestones.

2. Inventory the work

Break production into real activities:

• dock control and unload;
• rigging, staging, power, lighting, video, and audio setup;
• backline placement and tuning;
• cable, stage-box, and input patch;
• RF coordination;
• line check;
• soundcheck or rehearsal;
• support-act checks;
• stage reset;
• front-of-house, backstage, security, and ticketing readiness;
• performance changeovers;
• strike, pack, load-out, and venue reset.

Avoid one row called setup. It hides dependencies and prevents departments from knowing when the space or system will be ready for them.

3. Estimate with department owners

Ask the people responsible for audio, lighting, video, staging, rigging, backline, venue operations, and touring production to estimate their work.

Account for:

• equipment quantity and complexity;
• shared lifts, docks, forklifts, power, and stage space;
• whether tasks can run safely in parallel;
• local crew familiarity;
• travel arrival uncertainty;
• changeovers between acts;
• pack and load-out order.

A large console does not shorten a late patch. A short input list does not guarantee a short load-in if access, backline, RF, or staging is complex.

4. Connect dependencies

Write the dependency in plain language:

Stage power approved
→ backline and playback powered
→ inputs patched
→ line check complete
→ artist soundcheck
→ stage reset
→ show-ready approval
→ doors

Some tasks can overlap, but only when they do not compete for the same people, equipment, or unsafe work area. The production manager and department leads decide that sequence.

5. Add handoff time

Allow time for:

• moving people and equipment;
• re-patching and labeling;
• saving or recalling show files;
• clearing cases and cable paths;
• crew briefings;
• artist movement;
• security sweeps and public-area checks;
• documenting the next department's approval.

Unallocated handoffs are where an apparently complete schedule loses time.

Schedule checks, doors, and performances

Line check

A line check verifies that each intended source reaches the required destination and is labeled or routed correctly. Schedule it after the physical patch is ready and before soundcheck.

For a repeatable sequence, read Line Check vs Soundcheck.

Soundcheck

Soundcheck evaluates the working performance system with the artist. The schedule should state:

• artist or act;
• stage-ready time;
• check start and finish;
• whether the room must be quiet or closed;
• FOH, monitor, backline, playback, and artist attendance;
• what reset follows.

If there is no full soundcheck, record the agreed line-check or changeover workflow rather than leaving an impossible soundcheck slot in the plan.

Doors and show-ready approval

Doors is when the audience is admitted. Before that milestone, define who confirms:

• production work over public areas is complete;
• stage and emergency routes are clear;
• barriers and public areas are ready;
• audio, lighting, video, and communications are in show state;
• backstage and artist access are controlled;
• ticketing, security, medical, and venue teams are ready.

Do not schedule noisy or overhead work across open doors unless the venue's approved operating plan explicitly allows it.

Set times and changeovers

For each act, include:

• stage call;
• set start and finish;
• maximum set length;
• changeover owner and duration;
• equipment removed, retained, or added;
• playback or show-file handoff;
• curfew consequence if the schedule slips.

Use Festival Stage Plot and Changeover Guide when several acts share a stage.

Strike and load-out

The show is not finished at the last song. Schedule:

1. audience and backstage movement;
2. safe shutdown;
3. artist equipment pack;
4. house and rental strike;
5. dock sequence;
6. vehicle loading;
7. room reset and waste removal;
8. final venue sign-off;
9. crew and building clear.

Work backward from hard-out to test whether the strike plan is credible.

Manage changes on show day

Keep one source of truth

Publish one master schedule with a revision timestamp and owner. Department extracts may be useful, but they must point back to the current master.

Do not circulate multiple attachments named FINAL, FINAL-2, and NEW-FINAL. When a technical change affects the stage plot or input list, invite the responsible people to edit and save the same Rider and inspect history.

Record decisions, not every conversation

For a meaningful change, capture:

• what changed;
• new time or sequence;
• reason;
• decision owner;
• affected departments;
• time communicated;
• next dependency.

Keep personal phone numbers or sensitive travel details in a restricted contact sheet rather than a broadly shared public schedule.

Use escalation thresholds

Decide before doors who can:

• move a crew or artist call;
• shorten or remove a soundcheck;
• adjust a support set or changeover;
• approve overtime or extra labor;
• delay doors;
• change the advertised performance schedule;
• enforce the curfew or stop work.

The schedule records authority; it does not replace venue safety plans, contracts, permits, labor arrangements, or qualified judgment.

Run a final schedule review

Before publication, ask:

• Are all times in the same local timezone?
• Does every task have enough people, space, and equipment?
• Are dependencies in the right order?
• Do the technical and hospitality plans use the same arrival and meal times?
• Is there a safe stopping point for every break?
• Does the plan reach doors, curfew, and hard-out?
• Has each owner accepted their rows?

Common schedule mistakes

Listing milestones without finish times. Nobody can see whether the next task overlaps.

Treating every call as all crew. Use department and individual calls so people know when they are actually required.

Planning from set time forward. Build backward from doors and forward from access, then reconcile the two.

Ignoring shared resources. Two departments cannot both have exclusive use of one dock, lift, work platform, or stage area.

Confusing soundcheck with line check. They have different people, prerequisites, and goals.

Ending at the encore. Strike, load-out, reset, and hard-out remain production work.

Pre-publish checklist

• Show date, venue, room, timezone, and revision are visible.
• Access, doors, curfew, and hard-out are confirmed.
• Each row has start, finish, owner, location, and dependency.
• Crew, artist, vehicle, and department calls are distinct.
• Load-in, setup, patch, line check, soundcheck, and reset are sequenced.
• Meals and breaks have workable coverage.
• Doors have a named show-ready approval.
• Every act and changeover has a start, finish, and owner.
• Strike and load-out finish before hard-out.
• Change authority and communication channels are clear.

FAQ

What is a concert production schedule?

It is the timed operational plan for preparing, running, and clearing a concert. It coordinates access, crew calls, load-in, technical setup, checks, meals, doors, performances, changeovers, strike, load-out, locations, owners, and dependencies.

What should a show day schedule include?

Include the date, local timezone, venue, revision, contacts, venue and dock access, crew and artist calls, setup tasks, line check, soundcheck, meals, show-ready approval, doors, set times, changeovers, curfew, strike, load-out, hard-out, owners, locations, and dependencies.

How do you schedule load-in and soundcheck?

Confirm access and unload first, then sequence staging, power, backline, audio systems, input patch, and line check. Soundcheck starts only when the artist, stage, signal paths, FOH, monitors, and required crew are ready. Validate durations with department leads.

What is the difference between doors and show time?

Doors is when audience entry begins. Show time is when the performance starts. The gap may support audience entry, ticketing, seating, safety checks, and preshow operation; its length depends on the event and venue plan.

Who creates the concert production schedule?

The production manager commonly owns the master schedule, using confirmed constraints and estimates from the venue, promoter, tour manager, stage manager, and department leads. The named owner publishes revisions and coordinates approved changes.

Turn requirements into a workable day

Build the current technical Rider in Techrider.live, invite the production team to edit it, and use the confirmed stage, input, monitor, and backline plan to create an achievable show-day schedule.

---

Last updated: 2026-07-29 · Reviewed for access, crew calls, dependencies, line check, soundcheck, doors, performances, curfew, strike, and hard-out.