Record what will be photographed, what will be delivered, who supplies resources, how revisions work, how images may be used and how schedule or sample issues are handled. A project name and total price leave these questions unresolved.
This is a project discussion checklist, not legal advice or a substitute for reviewing a specific agreement. Rights, permissions, liability and disputes depend on the actual terms and applicable law.
Connect the products, shots and deliverables
Identify SKUs, colors, components, quantities and priorities. Separate full views, lifestyle, details, white-background images, model scenes and video tasks. Then state file counts, ratios, formats and versions so each deliverable can be traced to a task.
Mark open choices and agree when they must be finalized. Keep a written record when products, colors, sets or channel versions are added during production.
| Area | Details to record | Avoid relying on |
|---|---|---|
| Products and shots | SKUs, colors, components and essential or optional views | A batch of products; several photos |
| Production resources | Responsibility for sets, props, models, styling and travel | Follow the reference |
| Reviews and revisions | Approver, feedback window, correction types and added work | A number of revisions |
| Delivery files | Counts, ratios, formats, versions and any raw or editable files | Delivered when complete |
| Image use | Channels, term, territory, attribution, public display and third-party permissions | For promotional use |
| Changes and exceptions | Delays, cancellation, samples, transport, file retention and written changes | To be discussed later |
- SKUs, colors and components
- Essential and optional shots
- Photo and video tasks
- Aspect ratios
- Editing scope
- File counts and formats
- First-delivery priorities
- How additional work is approved
Assign responsibility for production resources
Room sets, custom builds, locations, special props and models require different resources. State who provides and approves each, whether the cost is included and what happens if it is unavailable on time.
Where models are included, agree casting, wardrobe, styling, travel and permission responsibilities. Connect the model's appearance to specific shots and channels rather than treating it as a general style request.
Define approvals and revision scope
For test shots, specify what is being approved, by whom and within which window. Separate direction approval from image selection and final retouching, and agree how later direction changes are handled.
Define the type of revision as well as the number of rounds. Basic corrections, detailed retouching, composites, reshoots and additional exports involve different work. Assign one person to consolidate feedback.
Distinguish file delivery from permitted use
Separate raw captures, selection previews, finished photographs, layouts and video project files. Record what is delivered, how files are retained and any conditions on further editing or sharing with third parties.
Product pages, paid ads, catalogs and social platforms may need different permissions. Confirm attribution, portfolio display, confidentiality and model permissions separately rather than assuming one approval covers every use.
Plan for delays, sample issues and file retention
Delays may arise from samples, product information, sets, weather, people or feedback. Agree notification, rescheduling, already-incurred production costs and the responsibilities of both sides.
For samples sent to the studio, confirm receiving, handling, return arrangements, transport responsibilities and issue records. Also agree download deadlines and file-retention terms; a general guide does not establish those service terms.
- Delay notice and rescheduling
- Cancellation and incurred costs
- Sample condition records
- Sample handling and return
- Shipping costs and exceptions
- File download deadline
- Backup and retention scope
- Contacts and dispute arrangements
Turn a change request into a reviewable scope decision
Keep the original brief and approval record beside each request. Record the affected files, reason and proposed work so both sides can distinguish an agreed correction from new production or a new use; actual terms remain project-specific.
| Request type | Record first | Discuss the work | Close with |
|---|---|---|---|
| An agreed view was not delivered | Shot ID, promised output and missing file | Completion or correction against the agreed task | Accepted replacement file tied to that task |
| Direction changes after proof | Approved proof and new annotated reference | Affected styling, capture, editing and review work | Written scope decision and replacement proof |
| A physical product changed | Sample versions and the visible differences | Which views require capture rather than digital invention | New shot scope and sample-linked file list |
| A new party or use needs files | Recipient, placement and requested file types | Applicable usage, sharing and editable-file terms | Recorded permission decision and named release files |
Sources and further reading
These sources provide context for the claims or channel requirements discussed here. Review current requirements alongside your product information and project agreement.
- CAC: Civil Code of the People's Republic of China ↗China-law reference covering contracts and personality rights. Review the actual agreement and use case with appropriate professional advice.
- State Council website: Copyright Law of the People's Republic of China ↗China-law reference on copyright and licensing. Delivery of an image file should not be assumed to transfer every right or authorize every use.
