Drive proofs and status updates from the job record. AI drafts the proof email and each status message from the job's fields, a person checks the job number, version and specification, and the customer's reply is logged against that exact version. Six status messages, from received to ready for collection, mean customers hear from you before they have to ask.
The AI never decides what has been approved. The log does, and an approval belongs to a version ("proof 2 of job 10482"), never to "the artwork". Checking the artwork itself and pricing the job are separate problems, covered in our print shop tutorial on pricing jobs and checking artwork. Everything below starts once a proof exists.
What a proof email must carry
A proof is the version of the job you ask the customer to approve before anything is printed. It is usually a PDF sent by email (a soft proof) and sometimes a printed sample (a hard-copy proof). An approval protects both sides only if it is specific, so every proof email should carry the same fields in the same order.
- Job number and version. "Job 10482, proof 2", plus the file name, which should also appear on the job ticket.
- The job as the customer knows it. A short title they will recognise.
- A specification summary. Quantity, size, stock, colours and finishing, copied from the job ticket.
- What to check. Spelling of names, phone numbers and web addresses, prices, dates, image placement, and fold or page order.
- What the proof cannot show. Screen colours are approximate; ask for a printed proof when colour matters.
- The approval instruction. The exact words to reply with.
- A deadline tied to the date it protects. "Approve by Thursday, 3 pm, to keep Tuesday's delivery."
- Who may approve. The named contact on the order.
Here is a filled-in example, illustrative like every job in this tutorial.
Subject: Proof 2 for job 10482: 500 trifold leaflets, please approve by Thursday, 3 pm
Hi [first name],
Attached is proof 2 (10482_leaflet_v2.pdf) for your trifold leaflets. It changes your phone number and moves the logo to the back panel, as you asked.
Job: 500 trifold leaflets, 150 gsm silk, full colour both sides, folded.
Please check: the spelling of names, your phone number and web address, the dates and prices, and that the panels read in the right order when folded.
Colour: colours on a screen are approximate. If colour matching matters, ask me for a printed proof before approving.
To approve: reply with "APPROVED proof 2, job 10482". Printing does not start until we have that. Approve by Thursday, 3 pm, to keep delivery on Tuesday. After that, delivery moves to the next free press slot and I will tell you the new date.
If you want changes, reply with a list and I will send proof 3.
[your name]
Drafting the proof email without letting the AI touch the facts
The safest design is a template written once, with the job's fields merged in, and the AI used for the one sentence that changes each time: what is different from the last proof. That sentence comes from the customer's change request and the designer's note, and it is where a model saves real time. Everything else is copied.
Write ONE sentence, plain and friendly, telling the customer what changed between proof 1 and proof 2 of this job. Use only the CHANGE REQUEST and DESIGNER NOTE below. Do not mention anything that is not in them. Do not describe the quality of the work.
CHANGE REQUEST (customer, Monday 14:30): "Phone number should end 4471 not 4417. Can the logo go on the back panel? Everything else is fine."
DESIGNER NOTE: "Phone corrected. Logo moved to back panel, centred above the address."A good answer is the sentence in the example above: "It changes your phone number and moves the logo to the back panel, as you asked." Left to write the whole email, the model makes five predictable mistakes.
- It rewrites the specification. "500 high-quality leaflets" is not what is on the ticket. The spec line must match the job ticket word for word.
- It drops the version number or writes "our latest proof", which means nothing a week later.
- It promises what you cannot. "Colours will match exactly" and "guaranteed delivery" appear unprompted.
- It softens the approval wording. "Let us know if you're happy" is not an approval instruction.
- It invents a deadline, usually "by end of day". The deadline comes from the production schedule.
The approval log: one row per proof version
The log is a spreadsheet, or a table in your job software, with one row for every version sent. It is short on purpose, because it has to be filled in by someone busy, every time. This is what it looks like after one job with a change and one job still waiting (illustrative).
| Job | Version | Sent | To | Response | Approved by and when | Status |
|---|---|---|---|---|---|---|
| 10482 | 1 | Mon 10:05 | [first name], buyer | Changes: phone number, logo to back panel (Mon 14:30) | n/a | Superseded |
| 10482 | 2 | Mon 16:20 | [first name], buyer | "APPROVED proof 2, job 10482" (Tue 09:12) | [first name], Tue 09:12 | Approved |
| 10483 | 1 | Tue 11:00 | [first name], accounts | None yet; reminder 1 sent Wed 11:00 | n/a | Awaiting |
A few rules make the log worth keeping.
- A new version is a new row. Never overwrite an earlier one.
- An approval names its version. An approval of proof 1 does not cover proof 2.
- Only the named contact approves. If someone else replies, confirm with the person who placed the order.
- Keep the evidence. Save the reply as a PDF in the job folder, or keep it in a log mailbox, so you can find it in seconds.
- The file that goes to press is the approved file. The job ticket shows its name, and the press operator checks it against the log.
AI earns its place at the intake end, sorting customer replies. Paste in the proof's details and the reply, and ask it to label the reply Approved, Changes requested, Question or Unclear, and to say why. Approval counts only if the reply is from the named contact, refers to the current version and contains a clear yes. Four replies show how it behaves (illustrative).
| Customer reply | Label | What you do |
|---|---|---|
| "Approved, thanks!" in the proof 2 thread | Approved | Log it, save the reply, send the "in production" message |
| "Looks great. Can you make the logo a bit bigger?" | Changes requested | Not an approval; make proof 3 |
| "Fine" from a colleague who is not the named contact | Unclear | Ask the named contact to confirm |
| "OK go ahead", replying to proof 1 after proof 2 was sent | Unclear: refers to a superseded version | Ask them to confirm proof 2 by number |
How strict to be is your decision, and it should track the cost of a wrong print. On a $60 flyer job, a clear yes in the same thread is reasonable. On a $2,400 packaging run, ask for the exact wording and the version number every time. Our tutorial on packaging artwork approval goes deeper on the high-value end.
Chasing a proof nobody has answered
A proof waiting for an answer is a job waiting in the queue, and the delay is usually silence rather than refusal. The chase works best when it is tied to the production slot, because that is the thing the customer can feel: approve by Thursday and delivery stays on Tuesday; approve on Friday and it moves.
- Reminder 1, the next working morning. Friendly, restating the deadline and the date it protects.
- Reminder 2, a day later, by phone or text. States the consequence: the earliest new delivery date if approval misses the deadline.
- At the deadline. Call, set the job to "on hold, awaiting approval" and release the slot. Tell the customer what you have done.
Silence is never approval. Printing on silence is the one shortcut that turns a late job into a disputed one, unless your written terms say otherwise and an adviser has checked them.
Here is reminder 2 in full. The new delivery date comes from your production schedule, because the AI cannot know your next free press slot (see production scheduling and where AI helps).
Subject: Job 10483 is waiting for your approval
Hi [first name],
Proof 1 for job 10483 (250 business cards) is still waiting for your approval. To keep delivery on Monday we need your reply by 3 pm today. If it arrives after that, the earliest delivery we can offer is Thursday.
Reply "APPROVED proof 1, job 10483" or send me your changes, and I will turn it round the same day.
[your name]
Each morning, ask the AI to do the boring part: paste in the log export and a prompt such as "list every row with status Awaiting and a sent time more than one working day ago, show the delivery date each one endangers, and draft reminder 1 for each". The list is a draft for you to check against the schedule, not a mailing.
Six job-status messages, from received to ready
Status messages answer the call before it is made. Six cover most jobs, and one of them is the proof email you already have.
| Status | Moves when | The message says |
|---|---|---|
| 1. Received | Order accepted, deposit logged if you take one | Job number, what you have understood, when the proof will arrive |
| 2. Proof sent | Proof goes out | The proof email itself, so no extra message |
| 3. In production | Approval logged | Approved version, promised date, what happens next |
| 4. Delayed | A person decides the date will slip | True reason in one clause, new date, what you are doing about it |
| 5. Ready or dispatched | Quality check passed | Where, when and how to collect, or the carrier and tracking details |
| 6. Closed | Collected or delivered | Thanks and one line asking whether anything is wrong |
Message 5 is the one customers value most, and it needs the most facts. Here is a ready-for-collection message with the shop's own details left as placeholders (illustrative).
Subject: Job 10482 is ready to collect
Hi [first name],
Your 500 trifold leaflets (job 10482) are ready, packed in 2 boxes.
Collect from: [address], [opening hours]. Please bring the job number. The balance of $[amount] is due on collection.
We will hold the job for [number] days. After that, please call us so we can arrange storage or delivery.
Please check the boxes before you leave and tell us the same day if anything is wrong.
[your name]
The AI may write the wording but may not change the box count, the balance or the hold period, because each comes from the job record. It also must not say "paid in full" when a balance is outstanding. For a delay, a person sets the new date and the AI writes around it: a true reason, the new date, one sentence on what you are doing, and any offer the owner has approved. Never let the model decide to offer a discount.
Wiring it up: your job software, a sheet or a Zap
Start with what you already own. Check whether your print management system already sends status emails and offers online proofing. Printavo's features page, for example, lists customer approvals for quotes and artwork and workflow rules that "send updates", though it does not say who receives those updates. Ask your vendor to show you the template editor, then use AI to rewrite the templates once. If you sell through an online storefront, ask whether your web-to-print software includes proofing too.
A sheet plus a form, for small volumes. The approval log is a sheet. For approvals, a form with the job number and version pre-filled stops customers approving the wrong version, and each response arrives with a timestamp. Google Forms, for instance, can build one: open the form's More menu, choose "Pre-fill form", type the job number and version, then click "Get link". If you would like alerts when a status changes, our tutorial on AppSheet job-status email alerts shows one way.
A Zap, only for exceptions. Zapier's pricing page lists the Free plan at 100 tasks a month, with two-step Zaps only, and the Professional plan at 750 tasks for $19.99 a month on annual billing ($29.99 monthly). Each successful action counts as a task. A shop doing 25 jobs a day, about 550 a month, would need 1,650 tasks to send just three messages per job, more than Professional includes. So the routine messages belong in your job software, and a Zap is for the odd case, such as one alert when an approval has been outstanding too long. Check Zapier's page for today's figures.
Six checks before a proof or status message is sent
Most errors in this flow are small and avoidable: a wrong attachment, a stale date. Build the checks into whoever presses send.
| Check | What goes wrong | How to catch it |
|---|---|---|
| Job number and version | Proof 1 attached to an email that says proof 2 | Open the attachment and match its file name to the log |
| Specification | Quantity, stock or finish reworded by the AI | Compare the spec line with the job ticket, word for word |
| Dates | Delivery date taken from the last job, or invented | Copy it from the production schedule |
| Recipient | Sent to the wrong contact at a customer with several | Check against the named contact on the order |
| Approval wording | Softened or missing | Keep it as fixed template text that the AI cannot edit |
| Balance and collection details | Says paid when a balance is due; wrong hours | Read the amount and hours from the job record and the shop's settings |
Approval disputes that need a person, not a template
Some situations are not for a template. The log gives you the facts quickly, and a person makes the call.
| Situation | What the log shows | What to do |
|---|---|---|
| Customer asks for a change ten minutes after approving | Approved proof 2 at 09:12; the job is not on press until 10:00 | A person decides whether it can still be stopped, issues proof 3 and states any cost or delay before re-approval |
| "I never approved that" | The row, the saved reply and the file name on the ticket | Show the evidence politely and follow your terms on what happens next |
| Approval with extra changes in the same email | "Approved, but change the headline" | Treat it as not approved; issue a new version |
| Two people at the customer disagree | Different replies from different addresses | The named contact decides; log both replies |
| Error found after delivery | Whether the error is in the approved file or was introduced at print | Compare the delivered job with the approved version, then apply your terms |
Your terms should say what approval means and what happens when an approved proof contains an error. Have a qualified adviser review that wording, and do not let a model draft it unsupervised.
A six-person print shop's monthly hours, before and after
Illustrative figures throughout. A six-person shop runs about 12 jobs a day, around 260 a month. Roughly 60% need a proof, and a third of those need a second version, so the shop sends about 210 proof emails a month.
Proof emails. Written from scratch (retyping the spec, finding the file, wording the request), each takes about 5 minutes: 17.5 hours a month. With a template, merged fields and an AI sentence on what changed, each takes about 2 minutes: 7 hours. That saves 10.5 hours.
The log. It adds roughly a minute per proof, to save the reply and update the row: 3.5 hours a month. The net saving on proofs is 7 hours.
Status enquiries. Say customers ring or email 30 times a week asking where a job is, at 4 minutes each, about 8.7 hours a month. If the in-production and ready messages halve that, it saves about 4 hours.
Errors. Suppose one job every two months is printed from a version the customer never approved, and the reprint costs $180 in stock, press time and rush delivery. That is $90 a month in expected cost, which the log and the file-name check aim to bring close to zero.
Together that is about 11 hours a month, which at $24 an hour of staff time is $264, plus $90 of avoided reprints: roughly $354 a month against an AI assistant plan at $20. Replace the 60%, the minutes and the hourly cost with your own figures. If the result is small, the sensible response is to start with the ready-for-collection message alone, and see how many calls disappear.
Questions print shops ask about proofs and status messages
Can AI approve a proof or check it against the order?
Approval is a human step, and the customer's, not yours or the AI's. AI can compare text you paste, such as the order specification against the wording in the proof email, but it cannot be trusted to judge artwork by eye. Treat any comparison as a prompt to look again, and keep the customer's own reply as the evidence.
Should approvals come by email reply, a form or an online proofing tool?
Match the evidence to the cost of a wrong print. A clear reply in the proof's own email thread is fine for a low-value job. A form with the job number and version pre-filled, or an online proofing tool that records who clicked and when, suits expensive runs because the version and the time are captured for you.
Should status updates go by text or by email?
Send proofs by email, because the attachment and the reply thread are your approval record. Short status updates, such as in production, delayed and ready to collect, suit a text if the customer gave a mobile number for the job and agreed to texts. Put the job number in every message, and follow your texting tool's rules on consent and opt-outs.
What if a customer replies 'looks good' without saying approved?
Decide the rule in advance and apply it every time. For low-value jobs, a clear yes in the same thread can count. For high-value jobs, reply asking them to confirm with your approval wording and the version number. Whatever you choose, put it in your terms, and have a qualified adviser review what approval means there.
Further reads
- How to Add Human Approval Steps to AI Automations — Where a person must stay in any AI-drafted flow.
- AI in Sports Business: Team Kit Orders With Sizes, Names and Numbers — One club, 30 players, three squads: an order form, a duplicate-number check, a supplier order sheet and parent reminders, with sums and sample prompts.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Printavo features page (customer approvals, workflow rules), Zapier pricing page (task limits, plan prices) and Google's Docs Editors Help page on sending a form with pre-filled answers, all checked October 2026. Job numbers, times and money in the examples are illustrative.