Skip to main content

Step 07 · After Arc Studio

10 blocking

Vendor Pack

Turn declared durations, dependencies, kit and contacts into the paperwork an event actually runs on — load-in schedule and critical path, crew calls, pull list and power, permits and insurance, strike and restore, and a role sheet per vendor.


Bring in an evening from Arc Studio

Pull the evening plan you are working on from this browser, or open a plan file you saved from Arc Studio’s Brief step.

Open Arc Studio

No Arc Studio plans saved in this browser yet.

Build the pack from everything so far

Pulls the latest from every step in this browser plus your last Arc Studio plan. It brings across what those steps actually declared — no example vendors, no placeholder names.

What goes in the pack

19 items still undeclared — 10 blocking, 9 open.

Before this can be sent

10 outstanding
  • Event name — A pack without a name is not sendable.
  • Event date — Load-in and the calendar file cannot lock without a date.
  • Venue — Access, power, and strike live at a place.
  • Named contacts — A pack with nobody named on it is just a PDF. Someone has to own it.
  • A phone number — On the day nobody opens email. At least one contact needs a mobile.
  • Run sheet — No cues declared — the day-of has no order.
  • Production tasks — No task, duration, or dependency declared — there is no load-in schedule, no crew call, and no critical path to protect.
  • Pull list — Nothing declares what is being brought, by whom, or what it draws.
  • Insurance (COI) — No certificate tracked for any vendor. Most venues will not open a door without them.
  • Strike sequence — Nothing says what comes down first or who owns the room at the end.
The eventName, date, venue, guests
Production schedulenot declared
Pull list & powernot declared
Permits, curfew, insurance0 permits · 0 certificates
Strike & restore0 steps
Guests & constraintsFindings, pressures, extras
Contacts2 rows · 0 reachable

The order here is the escalation order. On the day nobody opens email, so a row without a mobile is a row nobody can use.

Your vendor library is empty. Save a contact below and it will be here next time, with its certificate dates.

Escalation 1
Escalation 2

Vendor briefing

10 blocking

No calendar file yet: No event date declared — a calendar file would put an invented day in somebody's diary.

Tangled Thistle · Atmosphere OS · Production / vendor pack

Untitled event

Schedule: no production tasks declared. This pack translates design decisions into production language for vendors.

Date
Not declared
Venue
Not declared
Guests
Not declared
Atmosphere
Not declared
Budget band
Not declared
Load-in zero
Not declared
Doors
Not declared
Hard out
Not declared

Generated — · sources: Manual entry only

What is still undeclared

19 items still undeclared — 10 blocking, 9 open.

Blocking — do not send until these are answered

  • Event name: A pack without a name is not sendable. — Vendor Pack cover
  • Event date: Load-in and the calendar file cannot lock without a date. — Vendor Pack
  • Venue: Access, power, and strike live at a place. — Vendor Pack
  • Named contacts: A pack with nobody named on it is just a PDF. Someone has to own it. — Vendor Pack contacts
  • A phone number: On the day nobody opens email. At least one contact needs a mobile. — Vendor Pack contacts
  • Run sheet: No cues declared — the day-of has no order. — Arc Studio
  • Production tasks: No task, duration, or dependency declared — there is no load-in schedule, no crew call, and no critical path to protect. — Vendor Pack · production schedule
  • Pull list: Nothing declares what is being brought, by whom, or what it draws. — Vendor Pack · equipment
  • Insurance (COI): No certificate tracked for any vendor. Most venues will not open a door without them. — Vendor Pack · insurance
  • Strike sequence: Nothing says what comes down first or who owns the room at the end. — Vendor Pack · strike

Open

  • Named atmosphere: Palette and floral have nothing to lock to.
  • Guest count: Volume math and service ratios need a headcount.
  • Energy arc: Lighting and catering have no clock.
  • Floral notes: The florist sheet would be adjectives.
  • Lighting notes: AV would be inventing The Turn.
  • Guest states: Inclusive hospitality cannot be claimed.
  • Permits: No permit named — if this event needs amplified sound, a road closure, or a license, nothing here says who holds it.
  • Curfew & noise: No hard out, no amplified-music cut-off, no dB limit. Strike timing and the AV brief both hang off these.
  • Restore checklist: Nothing says what the venue gets back, or in what condition.

Atmosphere priorities

No priorities declared. Vendors will make the trade-offs for you, in the order that suits them.

Contact sheet

Escalation order is the order below. The first row with a mobile is who gets called first on the day.

#RoleNameMobileEmailOwns
1Lead plannerunnamedno mobileno email
2Venue coordinatorunnamedno mobileno email

Production schedule

No production tasks declared. There is no load-in schedule, no crew call, and no critical path — and this pack will not print six invented beats in their place.

Crew calls

No crew calls — no tasks were declared to derive them from.

Constraints the schedule implies

Each line says what follows from the declared data, and what produced it. None of this is house practice asserted at you.

Nothing to derive yet — no dependencies, spaces, or clock times were declared.

Pull list & power

No pull list declared — nothing says what is being brought, by whom, or what it draws.

Permits, curfew & noise

No permit named. If this event needs amplified sound, a road closure, or a license, nothing here says who holds it.

Hard out
Not declared
Amplified until
Not declared
Noise limit
Not declared
Source
Not declared

Strike timing and the AV brief both hang off these three numbers.

Insurance (COI)

No certificate tracked for any vendor. Most venues will not open a door without them.

Strike & restore

Strike sequence

Nothing says what comes down first or who owns the room at the end.

Restore checklist

Not declared.

Run sheet

No run-sheet cues declared. This pack prints none rather than the same six beats it would print for any event at any scale.

Load-in & site notes

No load-in notes and no venue constraints on file. Curb, dock, lift, long carry, and quiet hours are all still unanswered.

Key constraints

No constraints captured yet.

What this pack does not cover

  • Planning language only — not a signed contract, quote, or production certification.
  • Vendor scopes, access, and site rules must be confirmed directly with each vendor and venue.
  • Timeline times are working cues until the day-of owner locks the call sheet.
  • Budget bands are planning ranges, not guaranteed spend or funds you are known to have.
  • Schedule, crew calls, and the critical path are computed from declared durations and dependencies. They are only as true as what was declared.
  • Power figures are a floor derived from declared draws, not an electrical design. A licensed electrician signs off on distro.
  • Rigging load ratings, structural points, and permission to hang are the venue's and the rigger's to state — this pack does not certify them.

Untitled event

One page · print first

Florist sheet

Untitled event

Do not substitute a stem, a metal, or a cloth without asking. Where a season blocks a hero, the legal substitute is named below. Anything else is undeclared.

Hero moments

  • Not declared.

Volume math (quote range)

  • Volume not declared — run Floral Direction.

Season gate · blocked stems

  • No blocked list on this brief.

Sustainability

  • Not declared.

Vendor language

  • Not declared.

One sheet from the production pack. Anything not written here is undeclared — ask before you substitute it.

Untitled event

Cues against the arc

Lighting / AV sheet

Untitled event

Do not add a color wash, a strobe, or a cool-white house look without asking. The Turn is a declared moment — not a DJ cue.

Reference pattern — not locked cues

  • Not declared. Arc Studio’s six-beat pattern is reference guidance. It is not this event’s cue list.

Lighting notes from the pack

  • Not declared — run Arc Studio.

Hard constraints

  • Not declared.

One sheet from the production pack. Anything not written here is undeclared — ask before you substitute it.

Untitled event

Service windows vs guest state

Catering / bar sheet

Untitled event

Do not collapse a service window to 'when we can'. Guest state is the clock.

Reference pattern — not locked service windows

  • Not declared. Arc Studio’s six-beat pattern is reference guidance. It is not this event’s cue list.

Guest signals

  • Not declared — run Guest Journey.

Inclusive hospitality (first fixes)

  • moving with limited stamina or mobility: Seat near an exit on a step-free path. No queue that cannot be sat in. Staff know the route.
  • sober or non-drinking: Zero-proof equally visible, equally garnished, equally in reach. Never 'the soda gun'.
  • needing a quieter sensory range: No strobe at The Turn. Quiet room at Release, already lit, never used as storage.

One sheet from the production pack. Anything not written here is undeclared — ask before you substitute it.

Untitled event

Schedule · crew · contacts · load-in

Planner day-of sheet

Untitled event

Times are working cues until the day-of owner locks the call sheet.

Critical path — the tasks with no float

  • No production tasks declared — there is no critical path to protect.

Crew calls

  • Not declared.

Blocking gaps before this pack goes out

  • Event name: A pack without a name is not sendable.
  • Event date: Load-in and the calendar file cannot lock without a date.
  • Venue: Access, power, and strike live at a place.
  • Named contacts: A pack with nobody named on it is just a PDF. Someone has to own it.
  • A phone number: On the day nobody opens email. At least one contact needs a mobile.
  • Run sheet: No cues declared — the day-of has no order.
  • Production tasks: No task, duration, or dependency declared — there is no load-in schedule, no crew call, and no critical path to protect.
  • Pull list: Nothing declares what is being brought, by whom, or what it draws.
  • Insurance (COI): No certificate tracked for any vendor. Most venues will not open a door without them.
  • Strike sequence: Nothing says what comes down first or who owns the room at the end.

Working timeline

  • Not declared.

Load-in

  • Not declared.

Contacts (escalation order)

  • 1. · Lead planner · unnamed · no mobile
  • 2. · Venue coordinator · unnamed · no mobile

Strike order

  • Not declared.

Atmosphere priorities (protect)

  • Not declared.

One sheet from the production pack. Anything not written here is undeclared — ask before you substitute it.

Untitled event

The night as accessibility, not only the site

Inclusive hospitality

Untitled event

First fixes are operational. They are not optional styling.

Declared guest states

  • No guest states declared — the pack cannot claim hospitality it has not tested.

First fixes

  • moving with limited stamina or mobility — Seat near an exit on a step-free path. No queue that cannot be sat in. Staff know the route. (Venue + planner)
  • sober or non-drinking — Zero-proof equally visible, equally garnished, equally in reach. Never 'the soda gun'. (Bar)
  • needing a quieter sensory range — No strobe at The Turn. Quiet room at Release, already lit, never used as storage. (AV + planner)

One sheet from the production pack. Anything not written here is undeclared — ask before you substitute it.

Next

The plan is built. The evening still has to happen.

Day Of is the same work read in the order the night happens — the run with real clock times, the cues by role, the numbers to ring, and the questions no record can answer. It is the page to have open in the room.

Or go back and change something

From Vendor Pack · badges show what each step has ready

Execution register

Start an Event Project first

Bring a venue in from Venue Intelligence, or settle one fact in any of the seven steps — a palette, a headcount, a budget. Whichever comes first creates the project, and the register then travels with the same saved event as the rest of the plan.