
A mood board cannot define a technical scope
Before a stage can assess an environment, it needs more than visual references. It needs to know what the camera must see, where the physical set stops, what changes within a take, what must illuminate performers, and which parts are still exploratory. A beautiful reference may say nothing about a required 270-degree move, a reflective floor, a sunrise transition, or an actor walking through an opening. Those omissions become expensive only after the room is booked.
Epic’s ICVFX guidance describes two linked requirements: assets must read realistically on the LED wall, and the environment must run in real time. It also stresses collaboration between art and stage teams. Treat those as constraints to brief, not as assurances that a vendor will solve every unstated scene problem.
Write three layers, separately
The story layer names the audience-facing purpose: “dawn on a coastal road, calm but exposed,” not a presumed lighting or rendering method. The camera layer gives the practical envelope: shots, lens range, framing extremes, focus behavior, movement, eyelines, and reflective or transparent foreground elements. The stage layer is a set of questions or stated assumptions: usable wall geometry, physical set footprint, tracking, render/playback mode, color pipeline, and who may adjust what on the day.
The following entries are illustrative briefing examples, not recommended distances or safety clearances. Validate all dimensions for the actual stage and shot.
| Brief field | Badly specified | Useful specification |
|---|---|---|
| Camera | “Handheld close-ups” | “35–65 mm, shoulder-height arc, 1.2 m subject-to-wall minimum” |
| World change | “Sunset feel” | “Two approved sky states; change only between takes” |
| Physical seam | “Road set” | “Physical asphalt to 4 m; digital continuation begins behind barrier” |
| Approval | “Director to tweak” | “Director approves story look; named operator applies preset changes” |
Ask for the uncertainty, too
Epic’s snapshot documentation warns that an actor-state snapshot does not record asset changes. That technical detail is an excellent briefing habit: distinguish a “stage state” from an “environment version.” The brief should identify the current asset revision, the expected state changes, and the unresolved choices. Otherwise a provider may be pricing a static scene while production expects live redesign.
Atlas proposed handoff
Send a one-page brief plus a short shot appendix. The one-page version contains intent, physical/virtual boundary, camera envelope, required in-camera interaction, change list, and decision owners. The appendix contains diagrams or frames for the riskiest setups. Add a small “not yet decided” box. It is more credible to say that the exact wall treatment is pending a camera test than to imply that a render is final.
Illustrative: an alley scene has rain on the ground, wet coats, and a moving neon sign. The brief marks the rain on the foreground as practical or post, the neon reflection as a camera test, and the distant traffic as a playback element. It does not ask a stage to infer all three from one concept image.
- Name the physical/virtual seam in camera terms.
- Give lens and movement extremes, not only hero frames.
- State which changes happen in take, between takes, or only after the shoot.
- Identify every unresolved assumption before it becomes an exclusion.
Sources & evidence
Primary documentation establishes tool behavior or a reported production. Checklists and illustrative examples are Atlas editorial guidance, not results of independent testing. Match documentation to your installed version.
States that ICVFX environments must both appear realistic on LED and perform in real time, requiring art/stage collaboration.
Source published: Not established · Retrieved 19 September 2026
Explains the boundary between restorable actor state and separately tracked asset changes.
Source published: Not established · Retrieved 19 September 2026