Compare stage bids by normalizing the missing work

A bid is a scope hypothesis

Two stage quotes can name the same wall dimensions and still describe different jobs. One may include a prelight, a technician, content ingest, tracking integration, color support, and teardown. Another may include only a room and powered panels. Comparing the totals rewards ambiguity. The practical job is to convert both proposals into the same production assumptions before deciding which is cheaper.

This is not a demand that every vendor use one template. It is a request for enough detail to identify who has accepted each responsibility. Epic’s ICVFX guidance is explicit that art and stage teams must collaborate and that stage performance should be tested rather than assumed. That supports a procurement question: is the quoted stage time actually available for the content and configuration test the job requires?

Build a normalized day model

Put each proposal into columns that do not depend on a vendor’s product names: access, build or configuration, engineering, calibration, content ingest, camera/tracking support, rehearsal, shooting, changes during shooting, strike, restore, and data delivery. Mark each cell included, excluded, allowance, or unclear. Do the same for people: stage operator, render operator, playback, color or imaging support, tracking technician, and after-hours contact.

Separate capacity from promised outcome

Request the configuration that will be used for the quoted test: camera count, tracking route, render arrangement, image pipeline, and any assumptions about content readiness. Epic’s Level Snapshots documentation is a helpful technical boundary: snapshots can restore actor state but do not track asset changes, which must be handled independently. In a bid comparison, that translates to a simple question: who owns the change history for content, configuration, and on-stage decisions? A restore promise is not the same thing as an asset-management service.

Atlas proposed comparison rule

Do not add an invented contingency percentage to make proposals look comparable. Instead, price or flag each unmatched requirement. If Bid A includes a six-hour technical rehearsal and Bid B does not, show Bid B’s missing rehearsal as “unpriced exposure” until its provider states how it will be handled. Keep a separate assumptions register with the request date and answer. That prevents an oral clarification from disappearing into a spreadsheet total.

Illustrative: one bid includes a 10-hour shoot day after a prior “prep day.” The other includes a 12-hour “stage day” but no defined technical time. The normalized sheet finds that the first bid includes tracking alignment and a content playback check; the second calls them client responsibilities. The decision may still favor the second provider, but only after the client assigns and schedules those responsibilities.

• Compare usable time by task, not only by calendar day.
• Ask what is excluded, conditional, or billed after a trigger.
• Name the person who may approve a change on set.
• Keep safety, insurance, permitting, and local requirements as separate production checks; this worksheet does not determine them.