| Portfolio and Visual Quality |
Review work that matches the required industry, camera style, materials, lighting, and level of realism. |
Request relevant samples rather than relying only on general portfolio images. |
Use a paid or clearly defined test scene before assigning a large project. |
| Technical Compatibility |
Confirm support for the required 3D formats, texture maps, color profiles, render engines, and output resolutions. |
The provider should accept the project’s native files or offer a reliable conversion process without losing materials, cameras, or scale. |
Create a technical handoff sheet listing file versions, units, naming rules, plug-ins, and output specifications. |
| Image Resolution |
Check final pixel dimensions, aspect ratio, image format, transparency requirements, and intended use. |
Web images generally need fewer pixels than large-format print or high-resolution presentations; the final size should be agreed before rendering. |
Approve one low-resolution composition preview before producing full-size images. |
| Turnaround Time |
Evaluate modeling complexity, number of views, animation length, revision rounds, and approval speed. |
A credible schedule should separate asset preparation, preview rendering, revisions, and final delivery. |
Use milestone dates instead of relying on one final delivery date. |
| Pricing Structure |
Identify whether pricing is based on image, view, asset, animation duration, complexity, or working hours. |
The quotation should state inclusions, exclusions, revision limits, taxes, rush fees, and additional change costs. |
Compare total project cost, not only the initial rendering fee. |
| Revision Policy |
Clarify how many revision rounds are included and what counts as a minor or major change. |
The agreement should define feedback deadlines, approval stages, and charges for changes to the approved brief. |
Consolidate feedback into one annotated review document for each round. |
| Communication and Project Management |
Assess response times, project ownership, file-sharing methods, meeting routines, and escalation procedures. |
A single project contact and a documented communication channel reduce duplicated instructions. |
Record decisions, deadlines, and approvals in a shared project log. |
| Data Security and Confidentiality |
Review access controls, file retention, transfer methods, confidentiality terms, and subcontractor access. |
Sensitive source files should be shared through controlled access and removed or returned according to the agreement. |
Send only the files required for the current milestone and maintain versioned backups. |
| Rendering Capacity |
Ask how the provider handles batch rendering, peak workloads, failed jobs, and large animation sequences. |
The provider should explain queue management, backup procedures, and how interrupted jobs are recovered. |
Render a short representative sequence to test stability before committing to a long animation. |
| Quality Assurance |
Check geometry, textures, lighting, reflections, shadows, color consistency, image artifacts, and frame continuity. |
A documented quality checklist should be completed before final delivery. |
Approve a test frame and use it as the visual reference for the remaining views or frames. |
| Ownership and Deliverables |
Clarify ownership of final images, source models, textures, project files, and reusable assets. |
The contract should identify exactly which files are delivered and when usage or ownership rights transfer. |
Use a final delivery checklist with file names, formats, resolutions, and approval status. |
| Post-Delivery Support |
Determine whether the provider can make corrections, prepare alternate crops, update assets, or create additional views later. |
Support terms should specify the response window and whether corrections caused by production errors are included. |
Archive the approved scene, references, fonts, textures, and render settings for future updates. |
