Websites and delivery
Make an album proof a sequence of specific decisions
Editorial team · Reviewed
Album feedback becomes difficult when comments are detached from the spread or version they refer to. Give the client a clear way to request a change, review the next proof and approve the final design.
A practical sequence
- Identify the proof version and show spread-level comments in context.
- Distinguish an image swap, layout change and product option.
- Resolve feedback explicitly rather than only hiding old comments.
- Separate design approval from cover, quantity and additional-cost approval.
Work through an example
The couple approves the layout but asks for a different cover and an extra copy. Those product choices may affect price and fulfillment without reopening every spread. The record keeps the approved design and commercial decisions distinct.
Where judgement matters
A proofing deadline should not silently turn unresolved comments into consent. Explain the revision policy and the action required for final approval. Preserve the approved version before sending files for production.
Make it usable
Open the working tool and work through the decision with your own inputs. Adapt the structured template to preserve the choices and responsibilities. Keep an original copy so later changes remain understandable.
Work the decision
A practice case
An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.
A couple approves album revision three, then asks to replace a photograph on one spread. The approval must stay attached to revision three; it cannot silently authorize the altered production file. Treat the new image, crop and layout as a new reviewable version before releasing anything to a lab.
| Decision | Why it matters |
|---|---|
| Distinguish comments from final approval. | A client can suggest a crop without accepting every spread or production option. |
| Freeze the approved visual and production inputs. | Size, cover, paper and image versions all affect what will be manufactured. |
| Validate against the actual supported product. | A plausible preview does not establish that a lab accepts the dimensions or file requirements. |
Make one usable artifact
Create an album decision record with revision, spread changes, unresolved comments, selected options, approver and production readiness. Keep the approved artifact recoverable.
Then test the difficult case
An original image is replaced after approval. Require a new review of the affected artifact and confirm that a retry cannot submit a different file under the old approval.
Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.