Remote approval works when every comment points to an identifiable product, frame and decision. It becomes slow and error-prone when the buyer, supplier and regional team send separate messages such as “make it warmer” or “use the other blue” without naming the sample or image.
For a textile shoot in Nantong, set the review method before the samples are prepared for camera. Decide which proof establishes the visual direction, who consolidates feedback, what information accompanies each frame and how the agreed scope distinguishes a correction from a new scene, deliverable or product change.
Agree the review map before the first proof
List the review stages in the brief and state what decision belongs to each one. An arrival reference can confirm sample identity and visible condition for the shoot. A test frame can establish a composition or lighting direction. A first proof set can check planned views. A delivery review checks the agreed retouched outputs, filenames and crops. These stages are not interchangeable.
Name one buyer-side feedback owner and one final visual approver. They may be the same person, but the responsibility should be explicit. Record the time zone and planned review window as project inputs, then agree actual timing in the quotation or schedule. Do not describe a requested date as guaranteed.
Make every proof self-identifying
Each proof should carry or accompany the project reference, SKU or sample ID, shot ID, product state, version and requested decision. Keep proof marks or watermarks outside the final customer-facing file set. If one frame shows several pieces, state which are sale contents and which are supporting props.
Approval of one status should not silently grant another. In particular, visual-direction approval does not approve product specifications, production or customer-facing release when a product-accuracy gate remains open.
- FOR IDENTITY CHECK — confirm the sample or component named in the record.
- FOR DIRECTION REVIEW — decide composition, arrangement or another stated visual choice.
- REVISION REQUESTED — changes are listed and a new version is expected.
- VISUAL DIRECTION APPROVED — the stated setup may extend to the agreed items.
- FINAL FILE APPROVED — the named delivered version passed the agreed visual review.
- HELD FOR PRODUCT DECISION — image work is waiting for a sample or product decision outside visual approval.
Write feedback as an executable change request
Use one consolidated, versioned response tied to an observable issue. The filled example below is hypothetical: DEMO-R is not a client SKU and proof-v2 is not an actual delivered file. It shows why a hidden border can require different work from a wrong export. The buyer-side feedback owner resolves conflicting comments; the studio confirms the proposed correction route and any scope change before creating another proof.
| Recorded item | Illustrative request | Route / owner | Close only when |
|---|---|---|---|
| File and issue | DEMO-R / shot03 / proof-v2: reverse border hidden at right edge | Buyer feedback owner confirms the actual required detail | One authoritative request identifies the same sample and view |
| Crop/export decision | Check whether the existing source contains the complete border outside this export | Studio checks source coverage; agency confirms the required slot | Proposed export-v3 retains the border in the actual placement preview |
| Retouch boundary | If visible border needs agreed cleanup, preserve its real stitching and pattern | Studio compares source and protected-detail notes | Cleanup does not invent a hidden edge or alter the sale product |
| New capture decision | If the fold hides the border in the source, rearrange the identified sample for another view | Studio confirms capture scope; buyer authorizes sample handling | New proof shows the actual border and the agreed composition |
| Protected facts | Keep the approved sample identity and sale contents; color or quantity change is not this request | Brand product owner resolves any inconsistent facts | Proof notes and image refer to the same approved record |
| Version closure | Record the selected correction, next proof ID, approver and affected placements | Named visual approver reviews the new proof; agency rechecks its slot | New version accepted explicitly; proof-v2 is not reused as final |
Separate revision, new scope and product change
A revision adjusts an agreed deliverable within the boundaries recorded for the project. A new background, additional setup, extra output ratio, unplanned product or newly requested source file can require additional scope. A changed sample, print, component or package is a product change that may make previous frames inaccurate even when the creative direction remains approved.
The quotation or agreement determines included revisions, fees and schedule effects. This guide supplies a classification method; it does not promise that a particular change is included or can be completed by a particular time.
- Does the request identify the SKU, file and observable issue?
- Does it correct the agreed brief, or add a task that was not in it?
- Has the physical product or approved product information changed?
- Can the request be resolved in the existing frame without inventing product detail?
- Which other SKUs or delivered files would be affected by the same decision?
- Who can approve the change in scope or product representation?
Approve a representative setup without skipping product differences
A representative proof can establish lighting, background, bed arrangement, camera angle, crop space and a general styling rule before that setup extends across a range. Choose a product that actually exposes the important decisions. A plain white pillow may not test the pattern direction required for a printed duvet set.
Record which decisions carry forward and which still require SKU-specific review. Color, pattern placement, border, closure, label, component count and packaging may differ even when the setup stays the same. Do not treat one approved sample as evidence that every variant is identical.
Close approval with a versioned decision record
The final record should name the project, SKU or range, proof or delivery version, approved items, remaining holds, approver and date. If approval is limited to visual direction or selected files, say so. Store the record with the delivery manifest so later users do not mistake an earlier proof for the current asset.
Before customer-facing release, confirm that the photographed sample still represents the sale product and that the intended channel version uses the correct crop, text and language layer. File approval does not guarantee marketplace acceptance or commercial results; current publishing requirements remain a separate check.
The remote review should end with a documented release decision: confirm the product record, visible contents, surrounding copy and final crop against the approved file version. See pre-publication textile image audit.
