Skip to content

Keeping track of what the customer approved · 3 min read

How do you make sure customers approve the right version?

When several versions of a preview are in circulation, give the customer and the people doing the work a clear way to identify which one is approved.

Start here.

Tie the approval to the exact version the customer reviewed. Record who gave the go-ahead and make that version easy for staff to find. Agree how to handle replies to old previews and what to do if a customer requests a change after work begins.

  • Say what approval allows your team to do.
  • Keep the approval with the file it covers.
  • Test what happens when a reply refers to an earlier version.

Start with the decision that lets work begin

Imagine a shop making window decals for a café. The customer asks for a different opening time on the artwork. The shop sends a corrected preview. A day later the customer replies “looks good” to the first email, and the person cutting the decals has both files in front of them.

Before changing software, ask what the customer is agreeing to and who can give the go-ahead. The shop might ask one named contact to check the text, size and layout in the preview before cutting begins. Make it clear whether a reply is a request for edits or approval to start.

Put the version where people can see it

Give each preview a version label and show it with the order. If customers approve by email, ask them to include the version in their reply. Record who approved, when they did it and which file they approved. Put the approved file and decision together where the person doing the work will look.

When you send a new preview, say that it replaces the earlier one. Decide what staff do with a reply to an old email. In the decal example, the safest next step is to point the customer to the corrected preview and wait for a clear answer on that version.

Agree what happens if something changes after approval

Suppose the café approves the corrected preview, then calls to move the opening time again. If work has not started, the shop can put the order back on hold while it prepares the next preview. If cutting has started, a person needs to check what can still change and tell the customer what happens next.

Make the handoff clear on both sides. The person doing the work should be able to see whether to proceed, wait or ask a colleague. The customer should know what they are being asked to check again. Keep the earlier decision visible as history, alongside the current decision.

Test the awkward replies before buying software

Try these cases using sample orders. Ask one person to play the customer and another to find the job and decide whether to start. Include the tools you already use in the comparison. The supplier should show the customer’s view as well as the record staff see.

Three approval tests for the hypothetical decal shop
TestCustomer should seeStaff should see
Customer asks for a correctionThe request was received and a new preview will follow.Work is waiting for a decision on the revision.
Customer approves an old previewWhich version needs their review now.The old reply and the current preview still waiting for approval.
Customer asks for a change after sign-offSomeone will confirm what can still change.The last approved file, the new request and a clear instruction about whether to pause.

Keep the lightest process that holds up

If a clear email subject, a named approver and one shared order record pass the test, try that routine first. If staff keep searching message threads or cannot tell when work is on hold, ask a supplier to show one review link per version and a clear record of the latest decision.

Pick a few orders where revisions are common and review them with the people doing the work. Count cases where someone had to check which file was approved or contact a colleague before starting. If the same question keeps coming back, bring the exact case to your next supplier conversation.

Take one revised order into your supplier demo

Ask the supplier to walk through the customer’s side and the staff side.

The current version
How do people recognise the file they should review or work from?
The go-ahead
Who can approve, and what information shows they approved this file?
A later change
Who can pause the work, and how will the next person see that it is on hold?

Planning something with a similar workflow?

Discuss your project with us

A couple of common questions.

Can a customer approve a proof by email?

For a simple process, email can work if you can identify who replied, which file they reviewed and what they agreed to. Put that record where staff will see it before starting.

What if two people need to approve the same preview?

Decide who checks each part and whether both must reply before work starts. Show which replies are still missing and ask each person to review the same version.

What if we receive approval for an old version?

Check whether the version was replaced. If it was, send the current preview and ask the customer to confirm that version before staff proceed.

Have something in mind?

Tell us what you want to build or improve. We’ll work out a useful first step together.

Discuss a project