Build a Houston venue advance plan before production scope is fixed.

A venue advance is the controlled handoff from selection to executable scope. It replaces informal room knowledge with sources, responsible owners, verification dates, and explicit effects on design, budget, contract, and schedule.

Begin only after a venue is shortlisted or selected. If the decision is still open, use the Houston venue shortlist guide. Do not use this process to compare venue profiles.

The advance plan should distinguish four states: verified by a current source, confirmed in writing by an authorized owner, assumed for planning, or unresolved. A verbal answer without a source, owner, and verification date remains an assumption.

Collect current venue documents and name the source date

Request the selected venue's current contract exhibits, event or exhibitor guide, scaled room plans, reflected ceiling or rigging information, production rules, service order forms, power and network information, insurance requirements, security requirements, and approval calendar. The useful source is the document governing the contracted room and event dates, not an undated sales sheet.

Log the document title, issuer, version or publication date, date received, verification date, and the person responsible for interpreting it. If two sources conflict, keep both in the log and assign the venue an action to identify the controlling version in writing.

• Venue-issued: contract exhibits, rules, floor plans, engineering criteria, order forms, rate sheets, and contact list.
• Event-issued: program schedule, room assignments, exhibit manual, general-contractor instructions, security plan, and attendee-flow plan.
• Production-issued: equipment plan, drawings, power and network requests, labor forecast, truck plan, rehearsal schedule, and submission register.

Official Houston source: if the program uses a City of Houston street or park, determine permit applicability with the responsible authority. The Mayor's Office of Special Events page was verified August 6, 2026. It does not establish requirements for a private venue by itself.

Confirm access, freight, move-in, and decision authority

Map the full equipment path from arrival boundary to final room position. The plan should identify the approved arrival point, check-in process, vehicle limits, unloading method, material-handling interface, freight route, elevator or door clearances, staging areas, storage, waste route, move-in window, strike window, and contingency process. Dimensions and time allowances should come from current venue documents or a jointly recorded site survey.

Name the person authorized to approve each condition and the person with day-of control. If the contract, venue operations team, hotel events team, show organizer, general contractor, and building management divide authority, write the boundary between them.

• Who approves arrival times, vehicle access, unloading, staging, storage, and changes?
• Which current drawing or survey confirms every door, turn, elevator, ramp, and floor transition on the equipment path?
• What is the approved move-in and strike sequence, and which schedule owner accepts changes?
• Which services must be ordered from the venue, show organizer, general contractor, or another required provider?

Confirm room geometry, sightlines, control positions, and audience paths

Build the proposed layout on the venue's current scaled plan. Confirm usable room dimensions, ceiling conditions, columns, doors, egress paths, accessibility routes, stage and screen positions, seating, interpretation, cameras, front of house, confidence monitors, scenic depth, catering paths, and any concurrent use of adjacent rooms.

Review sightlines from representative front, middle, side, rear, accessible, and camera positions. Record the drawing revision and verification date. A capacity chart does not verify production sightlines after stage, scenic, screens, cameras, and control positions are added.

• Which drawing controls, and who confirms its scale, revision, room orientation, and operable partitions?
• Can every audience zone see primary content, speakers, demonstrations, captions, and interpretation?
• Where can cameras and control positions operate without blocking audience, service, or accessibility paths?
• How do registration, pre-function, general session, breakouts, exhibits, hospitality, and exits connect in the timed audience-flow plan?

Confirm rigging, power, connectivity, labor, and required venue services

Submit the proposed technical design through the venue's current review process. Do not infer structural permission from visible steel, power availability from a receptacle, network performance from general Wi-Fi, or work jurisdiction from a prior event.

For each discipline, identify the controlling document, venue reviewer, required provider, submission format, due date, approval status, order deadline, rate basis, and change process. Separate available infrastructure from approved use.

• Rigging: current plans, engineering criteria, permitted points and loads, review owner, required provider, submission date, and approval record.
• Power: source locations, service type, distribution responsibility, tie-in authority, metering or order terms, cable paths, backup requirements, and approval record.
• Connectivity: wired and wireless service, dedicated circuit options, addressing, firewall or port needs, service-level expectations, test window, support owner, and escalation route.
• Labor and services: jurisdictions, minimums, call rules, supervision, required roles or providers, order dates, rate basis, cancellation terms, and authorized exceptions.

Confirm security, insurance, permitting, and approval owners

List every approval the program may require and assign applicability to an authorized owner. The list may include venue security, building management, fire and life-safety review, insurance, accessibility, temporary structures, pyrotechnics or special effects, food and beverage, alcohol, street or park use, curb use, noise, and other jurisdictional reviews. Applicability must be determined for the specific plan.

For each item, record who prepares it, who reviews it, who pays for it, who receives the final approval, the due date, and where the approval is stored. A vendor certificate, permit application, or submitted drawing is not a final approval.

• Which event elements trigger venue, building, city, county, state, or other jurisdictional review?
• Who is the responsible owner for the security plan, emergency coordination, insurance package, and each permit determination?
• What evidence marks an approval as final, and which production activity depends on it?
• What is the escalation route when an approval is late, conditional, or inconsistent with the current design?

Convert findings into controlled records and the production schedule

The assumption log holds every unverified condition currently used for design, pricing, contracting, or scheduling. Each entry needs a responsible owner, source sought, verification date, due date, current planning value, confidence, and scope effect. Close an assumption only with a dated source or written confirmation from an authorized owner.

The decision register records what was decided, the options considered, approver, date, source inputs, and resulting scope change. The production schedule then carries the confirmed access windows, review dates, order deadlines, drawing submissions, test windows, rehearsals, event activity, and strike.

Keep the three records linked. When an assumption changes, update the affected decision, drawing, budget allowance, contract item, and schedule activity. When a due date passes without verification, keep the item open and escalate it to the named decision owner.

Venue-advance responsibility matrix

Use one row for each material question. The matrix is complete only when confirmed items cite their source and open items have an owner and due date.

At every advance review, publish the matrix with the assumption log, decision register, source register, open approvals, and production schedule. The current verification date should be visible on each export.