Versions, feedback & approval
One current version, one set of feedback, and an explicit approval before handoff.
One current version
Keep the request brief, current files, and latest review link together in our agreed channel. I will identify the version ready for review. Refer to that version in your feedback so an old screenshot or attachment does not become the working direction.
Consolidate before sending
Collect stakeholder comments, resolve conflicting instructions, and send one numbered set of notes from the agreed decision-maker. Point to the page, frame, slide, or element and explain what is not working and why. Separate required corrections from optional preferences.
Review the right stage
Structure is reviewed before detailed polish where practical. Design approval and implementation review are different decisions. A Figma approval does not confirm that a live website has been tested, and a digital preview does not replace a printer proof.
Approve explicitly
Confirm the version and deliverable in writing through the agreed channel, for example: “Approved: brochure, version 3, for production export.” Before approving, check copy, spelling, prices, dates, contact details, links, dimensions, and any approvals required by your business. Silence is not approval.
After approval
I prepare the agreed final files or move to the next confirmed stage. Keep final exports separate from previews and obsolete drafts. The handoff identifies the files, versions, formats, and any remaining setup steps.
Changes after sign-off
A new offer, changed copy, another size, or a different printer template can affect the approved layout and timing. Tell me what changed before production or launch. We will decide whether it is a correction, a revision, or a new request, and confirm the effect on the queue.