A post-production brief must give a studio three things before any pixel gets touched: the final deliverable set with usage rights attached, the exact color profile and file specs for output, and a timeline with a single named approver. Skip any one of these and you get revision loops, mismatched files, or a print job that comes back the wrong color. Get them right, and the studio can quote, schedule, and deliver without a single clarifying email.
TL;DR:
- Precise deliverables including exact counts, file formats, and crop variants are essential for accurate quoting and scheduling.
- Color profiles must specify both working and output settings, with a request for hard proofs when printing to ensure color accuracy within Delta E2000 of 3 or lower.
- A clear timeline with scheduled review windows and a confirmed manifest are necessary to prevent delays caused by batching issues or miscommunication.
- Confirmed source files, a designated approver, and explicit product-truth boundaries are crucial to avoid project stalls and unnecessary revisions.
- Stating revision limits and feedback procedures upfront helps streamline the process and prevents scope creep during approval cycles.
Table of Contents
- What to include: the post-production brief checklist
- Technical specs and color management: profiles, proofing and export requirements
- Workflow, timeline and handoff: sequencing, workback schedules and manifests
- Feedback, revisions and approvals: how to give consolidated, actionable notes
- Practical brief template and annotated example
- Budget and cost estimates for post-production work
- Communication protocols and points of contact during the project
- Legal considerations: rights, usage licenses, and confidentiality
- Quality control standards and acceptance criteria
- Typical challenges and how to pre-emptively address them in the brief
- Studio perspective: how 35milimetre avoids common briefing failures
- If you want a studio to run this brief: how 35milimetre works
- Sources
- FAQ
What to include: the post-production brief checklist
A brief that lets a studio price and schedule on the first read covers five areas. Miss one, and you're trading emails instead of moving files.
Deliverables need to be counted, not described in general terms. "A hero shot and some lifestyle images" tells a retoucher nothing about scope; "6 hero shots, 3 crop variants each, delivered as layered PSD and flattened JPG" tells them exactly what to price. Scope defines what can change and what can't: which surfaces are up for compositing, whether label text must stay pixel-accurate, and where product-truth boundaries sit. Reference material, meaning approved selects, a style guide, and shot-row IDs tied to raw files, removes guesswork about tone and framing. Usage rights determine how far the retouching can go, since a print campaign running across multiple territories for two years calls for different color rigor than a single social post running for a week. Finally, access to source files, including RAW captures, PSD layers, 3D scene files, LUTs, and embedded metadata, is what actually lets the studio start.
- Deliverables: exact counts, crop variants, and final file format for each asset, not a general description.
- Scope: which elements can be composited or retouched and which must remain factually accurate, such as label copy or product geometry.
- References: approved selects, a style guide link, and shot-row or select IDs tied to raw files.
- Usage: territories, duration, and media types, since these affect how much retouching and licensing clearance a job needs.
- Access: RAW or PSD source files, 3D scene files, LUTs, and metadata the studio needs on day one.
A retouching checklist built for studios covers this same ground from the production side: product truth, global correction, geometry, edges, shadows and reflections, composites, and cross-view consistency all need to be named upfront rather than discovered mid-project.
Technical specs and color management: profiles, proofing and export requirements
Color management is a translation problem between the device that captured the image and the device that will display or print it, and Adobe's own documentation makes clear that the right profile depends on the output, not a default assumption. A brief that just says "sRGB" for a piece heading to a commercial press, or assumes CMYK for a digital banner, sets the studio up to guess wrong.
State both the working profile and the output profile by name. If the piece is going to print, say so and request a hard proof, since a soft proof on a monitor won't catch every shift a press introduces. For color-critical print work, a ΔE2000 threshold of 3 or lower is a workable target for how close the final print should sit to the approved reference, a standard the studio's own print color management guidance walks through in more detail.
- Layered PSD or TIFF for anything that might need further edits down the line.
- Flattened JPG for web and social placements where file weight matters.
- PNG with alpha channel for any asset that needs a transparent background.
Statistic Callout: Adobe's color management guidance notes that rendering intent should be chosen per element rather than applied uniformly, meaning a single blanket profile setting across an entire campaign can introduce inconsistent color shifts between assets.
Separate pixel dimensions from DPI in the brief. Pixel dimensions determine what the file can be used for; DPI only matters once a print size is fixed. Name both, along with a file naming convention, so nothing gets lost in a folder of forty near-identical exports.
Workflow, timeline and handoff: sequencing, workback schedules and manifests
A workback schedule works backward from the delivery date: final delivery, then the review window before it, then the first-pass date, each with padding for the unexpected. A producer's guide to working with retouchers recommends pencilling these dates rather than treating them as fixed, since retouchers typically work in staged batches rather than moving through files one at a time.
That batching matters for how you plan feedback. Masking gets done across the full set before color grading starts, and color gets graded across the full set before composites go in. Reviewing one finished image while the rest sit in an earlier stage produces feedback that doesn't apply evenly, so review rounds should align with batch completion, not with individual file readiness.
- Set the first-pass date with enough padding that a batching delay doesn't cascade into the final deadline.
- Build a review window that matches when a full batch, not a single image, will be ready.
- Confirm the manifest format before final delivery, listing every filename, version, and intended output.
- Lock the delivery date last, once the two review rounds above it are realistic.
Pro Tip: Send your shot-row list and manifest template in the same email as the brief, not after the first round of files arrives.
A studio-published handoff checklist covers manifest structure and naming conventions in more depth, useful for teams setting up automated ingest on their end.
Feedback, revisions and approvals: how to give consolidated, actionable notes
Consolidated feedback, meaning one annotated proof with every note attached, moves faster than five separate emails sent over three days. Practitioner guides for producers and retouchers point to this as one of the clearest efficiency gains available in a revision cycle, since batched notes let a retoucher fix everything in one pass instead of reopening a file repeatedly.
State the revision policy in the brief itself: how many rounds are included, what turnaround each round gets, and how extra changes get priced. Photography quote templates recommend separating basic editing from advanced retouching in this clause specifically, since the two carry different time costs and blending them into one vague line invites scope creep.
- Name one approver in the brief. "Marketing team" is not an approver; a person with a title is.
- Write feedback against the reference, not in isolation: "match the shadow density in the approved select" beats "make it darker."
- Flag anything outside the agreed scope as a new line item, not a free addition to the current round.
Practical brief template and annotated example
A brief that a studio can act on immediately fits into six fields: job summary, deliverables, technical specs, timeline, revision policy, and approver. Fill each one specifically and most clarifying calls disappear before they start.
- Job summary: the product, the campaign, and where the final images will run.
- Deliverables: exact count, variants, and file format per asset.
- Technical specs: working and output color profile, pixel dimensions, and file types.
- Timeline: first-pass date, review windows, and final delivery date.
- Revision policy: included rounds, turnaround per round, and pricing for extra changes.
- Approver: one named person with authority to sign off.
| Field | Vague version | Actionable version |
|---|---|---|
| Deliverables | "Product shots for the site" | "8 SKUs, 2 angles each, flattened JPG at 2000px, plus layered PSD" |
| Scope | "Make it look premium" | "Composite onto white background, retain label text exactly as photographed" |
| Timeline | "ASAP" | "First pass October 10, review window October 10 to 13, final delivery October 17" |
For a packaging variant paired with a product composite, the studio would read the deliverables line first to confirm count and format, then the scope line to confirm whether the label art is fixed or open to placement adjustment, since that single distinction changes the quote. The studio's own briefing guide walks through more annotated examples like this one.
Budget and cost estimates for post-production work
Post-production pricing tends to run per deliverable or per project rather than per hour, which is why a brief with exact deliverable counts is what lets a studio quote at all. 35milimetre publishes per-image pricing for some categories: Amazon Photo Retouching - Compositing runs $125 one-off per image, 3D Modeling starts from $175 one-off, and 3D Render falls between $80 and $175 one-off depending on complexity. Other services, including image manipulation, color grading, packaging design, and AI compositing, are priced on request once the studio sees the brief, since scope varies too much for a flat rate to make sense.
A brief that separates basic editing from advanced retouching, as photography quote templates recommend, gives a studio a clean way to line-item the quote instead of bundling everything into a single guess. If your budget is fixed before the brief goes out, say so; a studio can often suggest where to trim scope, such as fewer crop variants or a shorter revision window, to hit a number rather than quietly cutting quality to compensate.
Communication protocols and points of contact during the project
One point of contact on each side prevents the same note from arriving twice in different forms. Name who at the studio owns the project and who on the client side can approve changes, and state which channel carries which kind of message: email for anything that needs a paper trail, like scope changes or sign-offs, and a faster channel for quick clarifications that don't change the brief.
Set an expected response window for both sides in the brief itself, since a studio waiting three days for feedback on a two-week project loses proportionally more time than one waiting three days on a two-month project. If the work touches multiple stakeholders, such as a brand team and an agency creative director, decide in advance whose feedback is final when the two disagree, rather than letting the studio referee that during a live review round.
Legal considerations: rights, usage licenses, and confidentiality
Usage rights belong in the brief, not in a separate contract negotiated later, because they change what the retouching needs to accomplish. A composite cleared for one social post carries different risk than one cleared for a multi-year print campaign across several territories, and the studio should know which one it's building before the first file gets opened.
State whether reference material, unreleased packaging, or pre-launch product designs require a nondisclosure agreement, and flag that requirement at the brief stage rather than after files have already changed hands. If any element in the shot, such as a licensed background, a third-party prop, or a model's likeness, carries its own usage restriction, name it explicitly so the studio doesn't build a composite around something that can't legally run.
Quality control standards and acceptance criteria
Acceptance criteria answer one question before a single review round starts: what does "done" actually look like for this asset. A retouching checklist for studios frames this around product truth, cross-view consistency, and output preparation, meaning the final files match the reference in geometry and color, look consistent across every angle of the same product, and export at the correct pixel dimensions, profile, and compression for their destination.
Internal QC at the studio level catches most of this before a client ever sees a proof, but the brief should still state the acceptance bar in writing: does every SKU need to match a master reference within a stated color tolerance, and does every crop variant need to preserve the same framing logic. Naming this upfront gives both sides a shared definition of finished, rather than leaving "looks right" to be settled during the review round.
Typical challenges and how to pre-emptively address them in the brief
Missing source files stall a project before it starts. A brief that requests final JPGs but forgets to attach the RAW captures or 3D scene files leaves the studio unable to do anything but wait, so list every source file the studio needs alongside the brief itself, not after a follow-up request.
An undefined approver causes the second most common delay, since feedback from three people with different opinions takes longer to resolve than feedback from one. Name the approver in the brief, not during the first review round. Unclear product-truth boundaries cause the third: a studio that doesn't know whether label text can shift slightly to fit a new composite will either guess wrong or send a clarifying email that costs a day. State explicitly what must stay accurate and what's open to adjustment, and most of the back-and-forth that stretches a project past its workback schedule disappears before it begins.
Studio perspective: how 35milimetre avoids common briefing failures
The briefs that run smoothly are the ones where someone senior reads them before they're sent, catching the missing source file or the undefined approver before it becomes a delay. A small, senior-led team keeps that consistency across retouching, compositing, and CGI, since the same eyes see the brief and the output. For readers who want the operational detail behind this, the studio's collaboration process covers it further.
— 35mm
If you want a studio to run this brief: how 35milimetre works
Once the brief is written, the fastest next step is sending it to a studio that already works this way. The studio handles retouching, compositing, CGI, and packaging design with a small, senior-led team, which supports close oversight of projects. On first contact, send the deliverable list, any reference images, and your target timeline.
- Packaging and label projects fall under Packaging Design.
- AI-assisted compositing requests go through AI Product Compositing.
Send your brief and source files to start a quote at 35milimetre.
Sources
- Understand Photoshop color management
- Verybusy
- Photography Quote Template: Packages, Usage Rights, Deposits, and Retouching Scope - Ququ Blog
- Product Photo Retouching Checklist for Studios | Lenso
FAQ
What should a post-production brief always include?
A post-production brief should always name the exact deliverables and file formats, state the working and output color profile, and set a timeline with one named approver. Without these three, a studio can't quote or schedule the work accurately.
How many revision rounds are standard for retouching work?
There's no single universal number, and it varies by studio and project scope, so the brief should state the included rounds explicitly rather than assume a default. Photography quote templates recommend writing this figure directly into the brief along with pricing for any rounds beyond it.
What file format should I request for print versus web?
Request layered PSD or TIFF files for anything headed to print or further editing, since these preserve the ability to make changes later. For web and social, a flattened JPG at the correct pixel dimensions is the standard, and any asset needing a transparent background should come as a PNG with an alpha channel.
Who should approve revisions on a post-production project?
One named person should hold approval authority, stated in the brief itself rather than decided mid-project. Naming a single approver prevents conflicting feedback from different stakeholders, which is one of the most common causes of delay in retouching and compositing work.