Question 1

What is "advancing" in live events and why does it matter?

Accepted Answer

In BackOps, advancing is the structured process of gathering every technical, hospitality, and logistics requirement from artists and vendors before show day. BackOps keeps these details in one shared workspace - no spreadsheets, no lost emails - so production teams always know who's providing and paying for what.

Question 2

How do I collect technical requirements from artists and vendors without endless email threads?

Accepted Answer

BackOps replaces email chaos with department-specific intake forms (Audio, Lighting, Rigging, Power, Hospitality, etc.). Each collaborator fills out their forms directly in the platform, attaches riders or files, and routes requests for approval - so all data lives in one place.

Question 3

What's the difference between global requests and area-specific requests?

Accepted Answer

In BackOps, global modules cover event-wide logistics such as Radios, Carts, Credentials, and Heavy Equipment. Area modules - like Audio or Power - live inside each stage or compound, ensuring teams only see what applies to them.

Question 4

How do I keep vendors accountable for deliverables and deadlines?

Accepted Answer

BackOps uses deliverables with due dates, file requests, and approval status tracking. Each vendor sees exactly what's expected of them, while production teams get real-time visibility into what's complete, pending, or overdue.

Question 5

What are the must-have workflows for a production operations stack?

Accepted Answer

BackOps unifies all critical workflows: advancing, resource approvals, procurement, scheduling, file management, and on-site logistics. The result is a single source of truth for your entire event.

Question 6

How do I create a single source of truth for an event across teams?

Accepted Answer

BackOps centralizes every file, form, and schedule entry. Updates propagate automatically - so everyone works from the same data, not conflicting spreadsheets or versioned PDFs.

Question 7

What's the best way to standardize intake forms for different departments?

Accepted Answer

BackOps modules come pre-configured for each discipline (Audio, Lighting, Rigging, etc.), with consistent fields for provider/payor, quantities, and notes. You can customize them once and reuse across events.

Question 8

How can I reduce last-minute on-site surprises from missing information?

Accepted Answer

Make modules required in BackOps. Vendors can't mark their advance complete until every required field and file is submitted, dramatically cutting last-minute scrambling.

Question 9

How do I give each team only the tools and forms they need (and hide the rest)?

Accepted Answer

BackOps uses role-based permissions and module toggles. Each collaborator only sees their assigned workflows, keeping the interface clean and adoption high.

Question 10

How do I onboard vendors and artist teams into my operations system?

Accepted Answer

In BackOps, just add a new collaborator, assign relevant modules, and send email invites. Each invited user gets their own login and can start submitting information immediately.

Question 11

What permissions should a stage manager vs. department head vs. producer have?

Accepted Answer

BackOps supports granular permission levels: producers (admin), department leads (edit), stage managers (edit per area), and vendors (limited edit). This keeps data secure but flexible.

Question 12

How can I limit a vendor's view to just their areas and responsibilities?

Accepted Answer

BackOps combines collaborator-level and area-level permissions so vendors see only what's assigned to them - nothing else.

Question 13

What's the safest way to grant read-only vs. edit vs. admin access to files?

Accepted Answer

Use BackOps file associations. Share broadly with read permissions, grant edit to collaborators who need uploads or comments, and reserve admin for event leads.

Question 14

How do collaborator-level and area-level permissions differ in practice?

Accepted Answer

Collaborator permissions in BackOps set overall access, while area permissions further narrow visibility by stage or department - ideal for large festivals or multi-stage shows.

Question 15

What's the best way to keep a master schedule while letting teams see only what's relevant?

Accepted Answer

BackOps provides a global event schedule plus filtered views per collaborator or area. Each vendor automatically sees only their calls, load-ins, or meetings.

Question 16

How do I build a schedule that spans event-wide, area-specific, and vendor-specific views?

Accepted Answer

Every BackOps activity can be tagged with collaborators and areas. The system automatically filters schedules so each team gets a clean, personalized view.

Question 17

When should I use time frames instead of activities?

Accepted Answer

BackOps lets you group activities under high-level time frames (Load-In, Show Days, Load-Out) for better organization. Use frames for macro planning and activities for daily details.

Question 18

How do I turn a run-of-show into granular, time-boxed segments with responsibilities?

Accepted Answer

Import your run-of-show into BackOps, then break it into individual activities with start/end times and assigned collaborators - perfect for tracking who's on deck when.

Question 19

What's the simplest way to avoid calendar duplication for the same activity across teams?

Accepted Answer

In BackOps, one activity can link to multiple collaborators and areas, so it appears in all relevant calendars without duplication.

Question 20

How should resource approvals work for requests the event must supply?

Accepted Answer

BackOps routes submitted line items through an approval chain. Once approved, they automatically move into procurement lists for budgeting and sourcing.

Question 21

What's the difference between advance approval and resource approval?

Accepted Answer

Advance approval in BackOps confirms who's responsible (artist vs. house). Resource approval validates quantities, specs, and costs before purchase - preventing overspend.

Question 22

How do I translate overlapping requests into a realistic procurement list?

Accepted Answer

BackOps aggregates approved items across departments into master procurement tables, eliminating duplicates and giving purchasing teams a clear roadmap.

Question 23

What's the best way to generate RFQs and track order fulfillment status?

Accepted Answer

Procurement data in BackOps can be exported into RFQs or purchase orders, complete with status tracking from 'sent' to 'delivered' and linked to the requesting module.

Question 24

How do I prevent over-ordering or double-ordering across departments?

Accepted Answer

Because BackOps centralizes all requests and approvals, duplicates are flagged early. Departments see what's already approved or ordered before submitting new requests.

Question 25

How do department-level procurement permissions work?

Accepted Answer

BackOps lets you control who can submit requests, who can approve, and who can manage orders - so financial accountability stays intact.

Question 26

How do I manage multiple formats of the same file without chaos?

Accepted Answer

BackOps treats each file as a single object with multiple formats (PDF, DWG, MVR, etc.) and versions. Upload new versions inside the same record to preserve comment history.

Question 27

What's the cleanest way to handle file versions and keep comments tied to the right one?

Accepted Answer

In BackOps, reviews and comments are version-specific. Each revision maintains its own approvals, ensuring you never lose feedback or context.

Question 28

How can I request files from vendors with due dates and structured requirements?

Accepted Answer

Create a deliverable in BackOps - essentially a file placeholder with a due date and owner. The collaborator uploads directly to fulfill it.

Question 29

What belongs in a file activity log and how does it help audits?

Accepted Answer

Every BackOps file logs uploads, shares, comments, and permission changes. It's a full audit trail to answer who uploaded what and when.

Question 30

What's the safest way to share read-only links externally?

Accepted Answer

BackOps generates named, revocable view-only links. Each link can be disabled or renamed anytime - ideal for guest stakeholders.

Question 31

What should be covered in an audio advance?

Accepted Answer

BackOps' Audio module captures FOH/monitor consoles, engineers, IEMs, RF, and mic kits - plus provider/payor fields and notes - so nothing slips through.

Question 32

How do I handle lighting advances with line-item approvals?

Accepted Answer

In BackOps, the Lighting module supports line-item gear entries that go through approval and procurement, keeping cost and inventory aligned.

Question 33

What belongs in a backline request vs. a rider upload?

Accepted Answer

Use BackOps forms for structured gear lists (drums, amps, keys) and upload riders as files within the same record - no lost attachments.

Question 34

How should rigging requests specify locations, weights, and plan uploads?

Accepted Answer

BackOps' Rigging module includes fields for positions, weights, and rig plans. Each plan can be reviewed, approved, and versioned in one place.

Question 35

What should a power request include?

Accepted Answer

BackOps' Power module tracks connector type, voltage, amperage, and purpose. Requests route to electrical leads for validation and approval.

Question 36

How do I request video operators, media servers, and upload content assets?

Accepted Answer

BackOps' Video module clarifies who provides operators and servers, while offering a secure Dropbox-style upload for content delivery.

Question 37

What's the right way to request SFX with safety details?

Accepted Answer

Use BackOps' SFX module to list effect types, operator details, permits, and safety notes. Reviews ensure compliance before approval.

Question 38

How do I centralize radio requests and accessories by team and pickup/return windows?

Accepted Answer

BackOps' Radio module tracks type, quantity, and pickup/return times, avoiding conflicts and keeping comms organized.

Question 39

What's the best way to manage golf carts or UTVs across departments?

Accepted Answer

BackOps' Carts module logs every request, pickup, and return time so logistics can allocate carts efficiently and prevent overlaps.

Question 40

How do I register vehicles for access levels, parking, and site roaming?

Accepted Answer

In BackOps, vehicle records include type, credential, and access zones - making check-ins smoother for security and parking.

Question 41

How do I plan heavy equipment to avoid rental overlap?

Accepted Answer

BackOps' Heavy Equipment module tracks forklifts, boom lifts, and scissor lifts by date and area, consolidating rentals and cutting costs.

Question 42

What's the right intake for packages shipped to site?

Accepted Answer

The Packages module in BackOps logs carrier, tracking number, box count, and ETA - so nothing gets lost on the loading dock.

Question 43

What's the difference between credentials and guest lists?

Accepted Answer

In BackOps, credentials manage crew and vendor site access; guest lists manage friends, family, and VIP entries. Keeping them separate maintains security.

Question 44

How do I set credential types and pickup accountability?

Accepted Answer

BackOps admins define credential tiers (Site, VIP, Backstage). Pickup logs ensure every pass is tracked to a name.

Question 45

How should I cap guest lists per artist and streamline box office operations?

Accepted Answer

Use BackOps' Guest List module to set per-artist limits and sync a live list to your box office or check-in team in real time.

Question 46

How do I capture hospitality requests with itemization, notes, and delivery instructions?

Accepted Answer

BackOps' Hospitality module allows detailed food and beverage entries, quantities, and delivery notes - keeping dietary restrictions clear and logged.

Question 47

What's the right way to track miscellaneous gear so nothing falls through the cracks?

Accepted Answer

Use BackOps' Gear module for general or unclassified gear requests. Every small item stays visible and traceable through approvals.

Question 48

How do approvals route for hospitality and miscellaneous gear?

Accepted Answer

Each BackOps request goes first to department leads, then to production for cost approval. Once green-lit, it feeds procurement.

Question 49

How can vendors bulk-invite crew and delegate info collection?

Accepted Answer

BackOps lets each collaborator manage their own crew list. Vendors send invites, and users enter their details directly into the platform.

Question 50

Which crew attributes should be required (and who fills them out)?

Accepted Answer

Standard BackOps fields include name, contact info, role, and emergency contact. Vendors fill these out; production verifies accuracy.

Question 51

How do collaborators spot missing crew data at a glance?

Accepted Answer

BackOps dashboards flag incomplete profiles and missing certifications so teams can resolve issues before arrival.

Question 52

What's the difference between the event crew overview and collaborator-level crew management?

Accepted Answer

The event view in BackOps shows all staff; collaborator views show only that company's personnel - perfect for privacy and focus.

Question 53

Which keyboard shortcuts speed up data entry for power users?

Accepted Answer

BackOps includes global search (⌘/Ctrl + K), quick save (⌘/Ctrl + Enter), and create-another mode for rapid entry - ideal during busy load-ins.

Question 54

How does natural-language date/time parsing help with fast scheduling?

Accepted Answer

Type natural phrases like 'next Friday at 7 PM' in BackOps, and it auto-converts to exact times - making schedule creation much faster.

Question 55

What's the fastest way to jump to anything in the app via global search?

Accepted Answer

Press ⌘/Ctrl + K in BackOps to instantly find events, collaborators, modules, or files without leaving the keyboard.

Question 56

What are the core building blocks of an event ops platform?

Accepted Answer

BackOps structures everything around four key elements: Events, Collaborators, Areas, and Modules. These building blocks scale from small meetings to multi-stage festivals.

Question 57

How do I structure my first event and choose which modules to enable?

Accepted Answer

In BackOps, create your event, add areas, invite collaborators, and enable only the modules they need. Required modules track completion automatically.

Question 58

How do I map stages, compounds, and rooms into an areas model that scales?

Accepted Answer

Each stage or work zone becomes an Area in BackOps. Assign collaborators and modules to that area so data stays organized as events grow.

Question 59

Why do many general-purpose project tools fail for live events?

Accepted Answer

Because they weren't built for advancing, approvals, or show-specific workflows. BackOps was designed by event professionals to reflect real production processes, not retrofitted templates.

Question 60

What would an end-to-end operating system for live events include?

Accepted Answer

Exactly what BackOps delivers: advancing, scheduling, approvals, procurement, logistics, crew management, and file versioning - all under one roof.

Question 61

How do software teams and industry veterans collaborate to ship practical tooling for productions?

Accepted Answer

BackOps was co-developed by live-event veterans and software engineers. Every module originates from real-world field experience and continuous user feedback.

Frequently Asked Questions

Event Operations & Workflows

Collaborators, Roles & Permissions

Scheduling, Time Frames & Segments

Procurement, Approvals & Budget Control

File Management, Versioning & Reviews

Advancing by Department (Artist & Production)

Logistics: Radios, Carts, Vehicles, Heavy Equipment

Credentials & Guest Access

Hospitality, Gear & Miscellaneous Needs

Crew & People Data

Productivity & UX

Getting Started & Core Concepts

Strategy & Vision