Design Proofing Process: A Freelance Checklist

You open an email at 3:12 a.m. A client attached a 2MB flattened PDF with MS Paint red arrows and wrote 'make it pop'. You can feel your weekend evaporate.

This moment is about the design proofing process. It decides whether you lose time on vague feedback or gain a clean, paid approval and move on. The process isn't glamorous. It's repeatable. It's written down. It keeps you sane.

What should a reliable design proofing process do?

It must do three things: make client feedback precise, protect your scope, and capture sign-off. If it does those, you get predictable timelines and fewer re-dos.

Here’s a checklist you can copy, paste, and actually use. Apply it every single time someone asks for a 'final review'.

The checklist (step-by-step proofing process you can use today)

1. Prepare the files like you mean it

• Export a high-quality PDF for print or a 2x retina PNG/JPEG for screens. Name files with version numbers: project-name_v02.pdf.
• Include a PDF with guides/measurements or a Figma link with a read-only view and comments enabled.
• Embed fonts or list them in a small README if the file requires font checks.

Why: The single worst feedback is 'image looks blurry' when you sent a 72ppi export instead of 2x. Prevent that by shipping appropriate specs.

2. Create one obvious place for feedback

Send a single link — a Figma file, a shared PDF with comment enabled, or a ClientMarkup link — and say 'All feedback in this link only.'

If feedback arrives scattered across email, Slack, and handwritten screenshots, you'll miss things. A single link is your ticket to clarity.

If you use Figma, invite the client as a viewer and instruct them to use pins. If they prefer PDFs, use a shared proofing tool that accepts pinned annotations and screen recordings (hint: ClientMarkup handles both).

3. Tell them exactly how to give feedback

Clients don't know your mental model. Tell them.

• 'Pin to the exact spot, add a one-line note (what and why), or record a 30s screen walkthrough.'
• Provide one example image with a correct pin + note.
• Say explicitly: no vague comments like "too busy" or "make it pop" — show the pixel or tell you what to change.

A 20-second script reduces ten minutes of clarification emails.

4. Set a hard review window and approval criteria

Tell them: 'Please review within 48 hours. If we don't hear back, we'll assume approval and proceed.'

Also define what 'approved' means. Example: 'Approved' = you sign off on the final PNG/JPEG and accept deliverables as listed. If they need source files, that’s a separate line item.

5. Limit free rounds and price extras clearly

Put this in the proposal and repeat in the review instructions: 'Includes 2 rounds of revisions. Additional rounds are $X per hour or a fixed fee.'

Concrete numbers keep clients honest. If you want to be nicer, offer a one-time grace revision for small issues.

6. Capture final sign-off and date

Get them to sign. A typed signature with a date and a short acceptance line ('I approve files and accept deliverables listed') is all you need for invoicing and dispute protection.

Use a proofing tool that captures that signature directly on the proof or log the approval with a screenshot and timestamp. That stops scope creep.

7. Keep a versioned change log

Maintain a simple text file or spreadsheet: version, date, changed by, summary. Paste the change log in your delivery email.

This saves time when a client asks 'When did we change the hero image?'

8. Invoice on approval, not before

Trigger the final invoice the day they sign. If they delay payment but demand more changes, apply your revision-fee rule.

Cashflow respect is a quality-of-life move.

A short email template you can steal

Subject: Review: Project Name — v02 (please use this link)

Hi [Client],

Attached is v02. Please review using this link: [single link].

How to review:

• Pin to the exact spot and add one short note, or record a 30s screen walk-through.
• Deadline: please respond within 48 hours.
• Included: 2 rounds of revisions. Extra rounds billed at $75/hr.

When you approve, please sign the approval line on the proof or reply 'Approved' with the timestamp.

Thanks — I’ll make requested changes within 24 hours of receipt.

This short script reduces three back-and-forths into one actionable pass.

Real-world tradeoffs and rules of thumb

• If a client insists on email-only feedback, require annotated screenshots attached to the message. No embedded 'just fix it' lines.
• For very small gigs (logo tweaks under $200), you can be looser. For brand systems or websites, be strict and document everything.
• If a client gives contradictory feedback (e.g., 'make it brighter' + 'preserve brand colors'), ask for a priority. You need a tie-breaker.

Tools that make this work

Figma for collaborative edits and pinned comments. PDFs with comment tools for print proofs. And a lightweight proofing tool that accepts pins, drawings, and screen recordings for clients who hate Figma — ClientMarkup does this without forcing accounts.

Choose one workflow and stick to it. Mixing five tools guarantees miscommunication.

Final thought

The proofing process is not bureaucratic padding. It's insurance for your time, sanity, and bank balance. Ship clear files, demand focused comments, sign the approval, and invoice. Do it enough times and your weekends stop being proofing zones.