What previs and techvis artists do

Previsualization artists turn a script, storyboard, director's idea, or production problem into a moving plan before final photography or animation. Their sequences communicate staging, shot size, camera movement, timing, geography, character action, and visual-effects intent with enough clarity for creative and technical decisions. ScreenSkills describes previs as a 3D animatic process used to plan shots, scale, timing, movement, and the relationship between live action and VFX. The work is intentionally provisional: its value comes from making choices visible early. Techvis is closely related but asks whether a chosen shot can be executed. A techvis artist may model the stage, camera, lens, crane, vehicle, performer, sun path, LED volume, or safety clearance and produce diagrams or measurements for departments. Postvis happens later, combining rough effects with photographed plates to clarify an evolving cut. Studios use these labels differently, so applicants should judge the actual deliverables rather than the title alone.

Job titles and production contexts

Search for previs artist, previsualization artist, previs animator, previs generalist, previs editor, techvis artist, technical visualization artist, virtual production visualization artist, real-time cinematic artist, layout artist, virtual camera operator, postvis artist, or visualization lead. Smaller teams may ask one generalist to model, rig, animate, light, edit, and publish. Larger teams may separate assets, animation, camera, editorial, pipeline, and supervision. The work appears at visualization companies, VFX studios, animation studios, film and television productions, virtual-production teams, and sometimes game-cinematic departments. A live-action feature may emphasize camera and physical feasibility. Animation may use previs and layout to establish the movie before expensive shot production. Commercials and independent films may need rapid pitch or planning sequences. Read whether the role supports story exploration, technical planning, on-set operation, postvis, or all four.

Begin with the decision the sequence must support

A useful previs brief names the audience and the decision. A director may need to compare coverage. A cinematographer may need lens and movement options. Stunts may need timing and clearances. VFX may need screen direction and plate strategy. Production may need an estimate of locations, extras, vehicles, or stage days. An LED-volume team may need to know whether the camera frustum, wall, lens, and blocking can support the shot. Write down the script version, sequence scope, assumed assets, camera format, aspect ratio, frame rate, scale, delivery date, review owner, and uncertainties. Separate creative proposals from approved facts. A polished sequence built on the wrong stage dimensions can mislead the crew. Conversely, a simple blockout with traceable assumptions can save a costly setup. The artist's task is to answer the brief at the appropriate fidelity, not to make every object look final.

Story, geography, and cinematic blocking

Previs is visual storytelling. Establish where characters are, what they want, what changes, and what the audience must understand. Maintain screen direction and eyelines unless a deliberate break serves the scene. Use entrances, exits, foreground, depth, movement, and shot progression to reveal information. Camera movement should have a reason: follow action, expose geography, shift point of view, intensify scale, or connect beats. A complex move is not automatically better. Block broad action before refining animation. Test the sequence as an edit, because individual shots that look attractive may not cut together. Include representative sound or dialogue only when permitted and clearly temporary. Review at normal playback speed and also as still frames. A strong previs reel shows readable staging and choices, not merely expensive assets or a constantly moving virtual camera.

Camera, lenses, and physical plausibility

A previs camera should carry meaningful properties: sensor or filmback assumption, focal length, aperture when relevant, focus distance, aspect ratio, transform, frame rate, and timing. OpenUSD's camera schema represents optical properties including aperture, focal length, f-stop, focus distance, clipping, and transform. Unreal Engine's Cine Camera and Sequencer tools similarly expose film-oriented camera controls. These systems help an artist communicate, but values are useful only when units and assumptions match production. Techvis goes further by checking whether the camera can occupy the proposed position and complete the move. Model the floor, set, ceiling, wall, rig envelope, lens height, track, crane or robot limits, and safe working area at appropriate accuracy. Flag any dimensions that came from estimates. Never present a virtual move as physically approved; the camera, grip, stunt, locations, safety, and production teams own their domains.

Real-time workflows with Sequencer

Epic documents Sequencer as a multi-track cinematic editor built around Level Sequence assets and actors. Its tracks can hold cameras, keyframes, animation, audio, events, and other scene properties. Sequences, sub-sequences, shots, and takes let teams divide work and compare alternatives. For previs, this means an artist can block, cut, revise, and review in one real-time environment while still preserving shot organization. Production discipline matters more than button knowledge. Establish naming, frame ranges, handles, shot ownership, asset versions, level structure, playback settings, and render presets. Keep temporary assets visibly provisional. Confirm whether an object is spawnable, level-bound, or referenced from another package before handing off. A sequence that plays only on its creator's machine is not production-ready. Test it from a clean checkout or packaged review context and record the engine version and required plugins.

Assets, rigs, and the right level of fidelity

Previs assets should support the decision without slowing iteration. A character needs enough proportion and rigging to stage action. A vehicle needs correct scale and turning behavior if movement is being planned. A location needs accurate constraints where camera or safety depends on them, while distant decoration may stay crude. Use approved libraries and document licenses; do not copy online models merely because they are easy to download. Build replaceable assets with clear pivots, units, orientation, materials, and version names. Maintain a distinction between surveyed geometry, art-department models, concept approximations, and artist invention. If a final asset arrives, test whether swapping it changes bounds, performance, animation, or framing. The ability to work quickly comes from controlled simplification and reusable systems, not from hiding uncertain geometry behind polished lighting.

Techvis deliverables crews can use

A techvis package may include plan and elevation views, lens and camera tables, path diagrams, rig dimensions, stage boundaries, sun or shadow studies, performer and vehicle trajectories, timing charts, overheads, or annotated frames. Each page should identify production, sequence, shot, version, date, author, scale, units, coordinate reference, source dimensions, assumptions, and approval status. Use legible labels and show the exact endpoints of critical measurements. Design for the recipient. A grip team may need footprint and height; camera may need lens, sensor, focus, and movement; VFX may need camera and environment data; stunts may need timing and separation. Ask departments what is actionable instead of exporting every property in the scene. Techvis informs planning and review; it does not replace engineering, manufacturer limits, risk assessment, or a department head's approval.

How AI can assist responsibly

AI can help generate rough alternatives, retrieve approved assets, classify notes, propose camera coverage, estimate poses, create temporary motion, transcribe review sessions, or find continuity differences. A useful application is bounded: it names the input, output, reviewer, acceptance criteria, and fallback. It should make exploration faster without obscuring what is approved, measured, licensed, or generated. Do not upload unreleased scripts, concept art, actor scans, location plans, storyboards, or production files to an unapproved service. Generated cameras can violate geography, lens intent, stage constraints, or safety. Generated motion can misrepresent a performer's abilities or a stunt plan. Keep human authorship and review visible, preserve source versions, and record model and license details when required. NIST's AI Risk Management Framework provides a voluntary structure for governing, mapping, measuring, and managing risk; production policy determines the permitted tools.

Editorial, sound, and review discipline

Previs is judged as a sequence, so editing is a core skill. Maintain shot identifiers, handles, frame rate, timecode or sequence timing, version, and slate information. Use temporary dialogue, effects, and music only with permission and label them as temp. Keep a clean output for viewing and a burned-in version that identifies shot and version for notes. Ensure review files have the expected color and audio channels. Collect notes through the production's approved system. Convert broad reactions into actionable changes while preserving the director's intent. Do not silently revise a previously approved camera or duration because another department requested an asset change; surface the tradeoff to the owner. Archive key review versions so teams can compare decisions, but avoid retaining redundant confidential exports beyond policy.

Quality control before publishing a sequence

Visual QC includes story clarity, continuity, screen direction, eyelines, collisions, camera clipping, focus, animation readability, frame cadence, and distracting asset errors. Technical QC includes shot names, frame ranges, aspect ratio, resolution, frame rate, audio sync, missing references, units, asset versions, render completeness, and file readability. Techvis adds measurement sources, rig limits, coordinate orientation, and uncertainty. Automate objective checks where practical. A script can detect missing shots, duplicate names, frame-range gaps, unexpected resolution, absent cameras, or unversioned output. Automation cannot decide whether a cut lands emotionally or whether a move is worth the production cost. Keep a publish checklist and make failed checks visible. A predictable review package earns trust because recipients can focus on decisions instead of decoding files.

Build a portfolio project that resembles production

Choose a two- or three-page scene with clear geography and one technical constraint, such as a small stage, moving vehicle, complex stunt beat, or LED wall. Use assets you created, licensed, or have permission to show. Deliver a script breakdown, overhead, two different coverage strategies, edited previs, selected final approach, and a techvis page. Record camera assumptions and explain why one version better serves story and feasibility. Show work in progress alongside the final sequence: storyboard or beat map, blockout, camera pass, animation pass, notes, and revision. Include one failed approach and what you learned. If you use AI for a temporary asset or motion proposal, label it and show how you validated or replaced it. Hiring teams should see your choices and iteration, not just a finished video.

What a strong previs reel demonstrates

Lead with the clearest storytelling, not the biggest explosion. Use short sequences that show camera language, staging, timing, action clarity, editing, and response to constraints. Break down your contribution precisely, especially on team projects. State whether you handled layout, camera, animation, assets, editing, techvis, or supervision. Remove confidential identifiers and obtain permission before displaying production material. Avoid reels made entirely from tutorial scenes, unlicensed characters, or shots that mimic a finished movie without showing planning value. Do not hide weak geography under rapid cuts. Include slates and captions sparingly so the viewer can understand the brief. A supplementary PDF can show dimensions, assumptions, shot lists, and review changes. The best portfolio makes it easy to imagine the candidate helping a director and crew make decisions.

Resume and interview preparation

Use a specific headline such as Previs and Techvis Artist — Real-Time Cinematics and Camera Planning. For each project, describe the brief, your responsibility, production context, collaboration, tools, and result without revealing confidential numbers. Mention cinematography, editing, animation, camera and lens literacy, scale, Unreal Engine or Maya, scripting, file management, and communication only when supported by work samples. Practice explaining a sequence from script to delivery. Interview scenarios may include a late stage-size change, impossible crane move, new lens package, missing final assets, conflicting notes, frame-rate mismatch, or sequence that performs poorly. Explain how you isolate the issue, protect approved work, make uncertainty visible, and offer alternatives. Creative fluency and calm production communication carry equal weight.

Finding legitimate previs and techvis openings

Search official career pages for visualization companies, VFX studios, animation studios, virtual-production teams, and film-technology vendors. Combine title variants with previs, previsualization, techvis, postvis, layout, real-time cinematics, virtual camera, Sequencer, or camera planning. A listing should state the employer, duties, work arrangement, application destination, and enough pipeline context to evaluate fit. International applicants should verify location, contract type, work authorization, travel, time-zone overlap, and remote eligibility. For external AIMovieJobs listings, follow the link to the employer's original page and confirm it remains active. Never pay for an interview, test, equipment shipment, visa guarantee, or offer. Protect source project files and unreleased portfolio material during hiring tests, and clarify ownership before completing substantial speculative work.

A practical ninety-day learning plan

During the first month, study shot grammar, lenses, blocking, editing, scale, and one 3D or real-time tool. Recreate a short public-domain scene as simple shapes, then make two coverage alternatives. In the second month, add reliable naming, shots, takes, a virtual camera, review renders, and a techvis problem with measured constraints. Create a small validation script or checklist for frame ranges and missing assets. In the third month, complete an original, permission-safe portfolio sequence and a concise breakdown. Ask a filmmaker, animator, and technically minded reviewer for different kinds of feedback. Revise the story and the handoff, not only the lighting. Tailor applications to the responsibilities in real postings. The aim is not photorealism in ninety days; it is repeatable evidence that you can translate intent into a clear, testable production plan.

Sources and further reading