How to brief a 3D environment artist
A useful brief gives an artist enough context to make good visual decisions. It describes what the environment needs to communicate, where the finished work will appear and which constraints matter from the start. You do not need to solve the scene before getting in touch.
Start with the result and the audience
Describe the scene in a sentence, then explain what the viewer should feel or understand. Is this a quiet still image, a cinematic sequence, a product setting or an environment that needs to work inside a game? Name the audience and the place they will see it.
The Hideout is a personal Blender environment about nature reclaiming an abandoned building in the woods. Its damp ground, moss, cracked brick and filtered light support that quiet atmosphere. A comparable brief could explain which of those qualities matter to your project, rather than asking for an exact copy of the scene.
Show what each reference is for
Share a small set of references and add a note to each one: lighting, composition, materials, scale, color or atmosphere. Say what you want to avoid as well. A photograph may explain the light better than another 3D render; a sketch may make the camera position clearer than a long paragraph.
For a woodland environment, separate references for the building, vegetation and light. If The Hideout is a reference, say whether you mean the abandoned structure, the damp surfaces or the way light breaks through the trees. That leaves room for an original visual direction.
Define deliverables and how they will be used
List the outputs you need: still images, a short animation, individual assets or an editable scene. Include image dimensions and aspect ratios; for animation, include duration, frame rate and any required versions. Explain whether the work is for a website, social post, presentation, print piece or interactive project.
Keep the use visible in the brief. In the Dear Youth Volunteer Fair poster series, layout and typography had to keep event information legible in print and digital formats. A 3D project also needs that context: a wide website image and a vertical social crop may call for different framing. Discuss editable files and usage permissions explicitly rather than assuming they come with every output.
List supplied assets and permissions
Tell the artist what already exists: models, textures, scans, CAD files, logos, typefaces, copy or brand guidelines. Share previews or a file list, the relevant formats and any known problems. Identify which files are final and which are placeholders.
Explain who owns supplied material and what permission you have to use it. Flag third-party assets and license restrictions, including limits on redistribution in editable scenes. If the project needs new assets or licensed resources, make that part of the scope discussion. Agree on credit and portfolio display with the artist when those matter to the project.
Set technical constraints early
For rendered work, name any required software or version, file formats, transparency, color settings and delivery specifications. Explain whether the scene must remain editable and whether another person will take over the files. Share the requirements you know; mark the rest as open questions.
For a game or real-time environment, include the engine and version, target device, scale, performance goals, texture limits and any collision or level-of-detail requirements. A finished still render does not establish that the same scene is ready for a game engine. State that intended use before production begins.
Share timing, budget and decision points
Give the final deadline, any launch or review dates, and the date when supplied material will be ready. Name the person who can approve the visual direction and explain how feedback will be collected. If timing is flexible, say so.
Share a working budget or range and identify the priorities if the scope needs to change. Discuss milestones, feedback rounds and what counts as an additional request with the artist. The useful first conversation is about a scope that fits the project; this guide does not set a price or promise a production schedule.
Send a brief that starts the conversation
A concise first inquiry can cover the essentials below. It is fine to leave an item open and ask for help deciding it.
- The desired result, intended audience and mood of the scene.
- A few annotated references and anything to avoid.
- Required deliverables, formats, dimensions and intended uses.
- Supplied assets, ownership and known license restrictions.
- Software, engine or performance constraints that affect the work.
- Timing, review milestones, decision maker and working budget.