2026-11-17 · StackFill
An Agency Print Template Handoff Checklist
Use this agency print template handoff checklist to send press-ready PDFs, specs, and approvals so the shop runs your job with zero questions.

A print job leaves your agency in good shape or it doesn't. When the handoff is clean, the shop runs the job, sends a proof, and ships. When it is sloppy, you get an email at 4 p.m. asking which black is the real black, why the logo looks soft at trim, and whether the client approved version 3 or version 3-final-USE-THIS.
That back-and-forth is a handoff problem, and the handoff is yours to own. This agency print template handoff checklist covers what an agency should settle before a job leaves the building. It points to our deeper references for each spec instead of repeating them. If you manage templates for many clients, read the agency print template portal guide alongside it.
Send what the shop needs, not what is convenient
Most stalls have one root cause. The agency sends what is easy to send. A folder of layered source files, a screenshot of the approval, and a note that says "high res, full bleed" asks the shop to finish your prepress for you.
Here is what that costs. The shop opens the file, finds a problem, and stops. The job sits while someone writes a question, waits for your answer, and requeues the file. Each round trip is about a day. Two or three rounds miss the client's deadline, and a rushed fix can bring its own mistake and a reprint.
The client does not see the shop in this chain. They see you. So the test is simple: the shop should be able to run the job with zero questions. If they have to ask you anything before they print, the package was incomplete.
Think about who reads your package on the other end. It is often a prepress operator with a queue of twenty jobs. They do not know your client, your brand, or your deadline pressure. They know the file, the spec sheet, and whatever you wrote in the email. A package that answers their questions before they form them gets pulled to the front of the line. A package that raises questions gets parked.
The core file package
Send the file the shop actually prints, not your working source. Send source files only if the shop asks and knows how to handle your fonts and links. The default is one PDF per piece, exported to a standard you both agreed on.
- The print-ready PDF, exported to an agreed standard. PDF/X-1a is a common default for CMYK work. It requires embedded fonts, no RGB, and trim and bleed boxes defined, and it does not allow live transparency. See PDF/X-1a compliant web-to-print.
- A proof PDF or reference image showing exactly what the client approved, so the shop can compare output to intent.
- A job spec sheet: flat size, finished size, page count, quantity, stock, coating, folds, and binding.
- Bleed and marks set correctly, not eyeballed. Ask the shop whether it wants marks in the file. The PDF crop marks reference shows what is normal.
- Every font embedded.
- A named contact who can answer the same day.
Name files so they explain themselves. ClientName_Postcard_5x7_v4.pdf tells the shop what it holds. postcard_FINAL_final2.pdf tells them versions are loose. If the job folds or binds, include a folding dummy or diagram so nobody guesses which panel is the cover. For booklets, check page order and spreads first. The binding file setup guide explains reader spreads versus printer spreads.
Write the cover note like a work order
The email that carries the files matters as much as the files. Keep it short and put the facts in a fixed order every time. A good note lists the job name, the quantity, the due date, the file names, and anything unusual. "Unusual" means a spot color, a special finish, a die cut, or a stock substitution you already cleared with the client.
Do not bury the one risky detail in paragraph four. If the job has a spot varnish layer, say so in the first line and name the layer or plate in the file. If the client supplied a logo that was weak and you did your best, say that too. Honest notes save the shop from guessing, and shops remember agencies that flag problems early.
Agree on the spec once, then reuse it
Most agencies work with the same two or three shops. Sit down once and write a one-page spec profile for each: the PDF standard, the bleed amount, whether marks go in the file, the ink limit, the color handling for spots, and the preferred file transfer method. After that, every handoff starts from that profile instead of from memory.
A shared profile also makes new hires safe. A junior producer who has never exported a press file can follow the profile and get it right. Without it, each person invents their own export settings and the shop sees a different file every week.
The pre-send spec pass
Most reprints come from four things: color, bleed, fonts, and resolution. Check each one, and use the linked reference when a check fails.
Color. Deliver CMYK, and convert it yourself where you can see and correct the result. A PDF/X-1a file cannot carry RGB at all. If you send RGB in a looser PDF, the shop's workflow converts it at output, and the blue the client approved can print purple. Brand spot colors should stay defined as spots, not rebuilt as CMYK mixes. See CMYK vs RGB for print and spot color preservation.
Be careful with promises here. The same CMYK file can look a little different on two presses, and a proof is the best tool you have for setting expectations. Tell the client what the proof is and what it is not before the job runs, not after the boxes arrive.
Blacks and overprint. Set small text, roughly under 12 pt and especially thin or reversed type, in single-ink 100% K, so four plates cannot misregister and fuzz the edges. Large solid areas can take a rich black build, but keep total ink within the shop's limit and watch registration. See rich black CMYK. Check overprint too. A stray overprint on white text can make it disappear. The overprint vs knockout guide covers it.
Bleed and trim. Anything that runs to the edge needs bleed, commonly 0.125 inch past trim. Keep live content inside a safe margin. A background that stops exactly at trim will show white slivers, because cutting has tolerance. See the bleed and trim reference.
Fonts. Embed every font, and confirm the embed in the exported PDF, not just in the export dialog. See PDF font embedding for print. Font license terms are your call to read. Check the license for your typeface.
Resolution. Images need enough pixels at final print size. 300 ppi is a starting point, not a law. A photo scaled up 200% in the layout is effectively 150 ppi, so check the effective resolution, not the original file. See PDF resolution for print.
Then run preflight before the file leaves. The preflight errors that cause reprints list is a good profile to check against. Open the exported PDF in a viewer one last time and zoom in on the edges, the small type, and any place a font could have swapped. Exports fail quietly, and your eyes catch what a profile misses.
Extra requirements for templated files
Templated work means you ship a design plus rules for how it changes: a business card for forty franchisees, a postcard where each store swaps its address, a rack card reordered each quarter with a new headline. A solid agency print template handoff covers both the artwork and the rules.
Handing the shop editable source files and a spreadsheet does not hold up. By the tenth card, someone has nudged a logo, swapped a font, or mistyped a phone number.
A templated handoff needs three more things:
- The data. A final spreadsheet with every field spelled and formatted as it should print. See variable data printing from a finished PDF.
- The edit rules. Which elements change and which are locked. Logo, brand colors, and legal line stay put. See brand template lockdown.
- A variant proof. A sample of filled variants, including long names and long addresses, since text overflow is where templated jobs break.
Test the edges of the data
Before you send, build the worst cases on purpose. Use the longest name in the list, a two-line job title, an address with a suite number, and a phone number in a different format. Look for text that runs past its box, wraps onto a logo, or shrinks below a readable size. Also test the shortest entries, because a one-word name can leave a gap that looks like a mistake.
Decide in advance what happens on overflow. Does the text shrink to a minimum size, wrap to a second line, or get rejected so someone shortens it? Write that rule into the handoff. If you leave it open, the shop will make the call, and it may not be the call the client wants.
Keep the legal and brand lines out of reach
Every franchise or multi-location template has a few lines nobody should touch: the license number, the disclaimer, the logo lockup, the brand colors. List them in the handoff as locked. If your process lets anyone retype them, you will eventually print a wrong license number on a thousand pieces. That is a client problem you own.
Approval and version control before you send
The costliest handoff mistake is shipping the wrong version. Make sure the file you send is the one the client approved, and that you can show it.
Get approval on the actual proof, not a screenshot, and record who approved it and when. A print template approval workflow beats an email thread where "looks good" is buried under twelve replies. If the client should check a live proof, see online PDF proofing with live preview.
Keep one canonical file with one clear name, and archive superseded versions so they are never sent by mistake. See print template version control. It pays off at reorder time, when the client wants the same card with a new name. The print shop reorder workflow shows the production side.
A simple rule helps: the approved file is read-only. If the client asks for a change after approval, make a new version, get a new approval, and only then send. Never patch an approved file and send it under the same name. That is how version 3 becomes two different files with one label.
Final pass: right file, right version, approval on record, specs confirmed, fonts embedded, CMYK confirmed, bleed present, proof included, contact named. It takes about ten minutes.
After the shop confirms
The handoff is not done when you hit send. Ask the shop to confirm receipt and to tell you if preflight flags anything. When the shop sends its proof, compare it against your approved reference before you forward it to the client. Check names, numbers, and the legal line, not just the look.
Once the job ships, file the exact package you sent: the PDF, the spec sheet, the approval, and the cover note. Store it with the job name and date. When the client calls in six months for a reorder, you open one folder and send the same package with the changes. That is the point of a repeatable handoff.
Use the file you already have
For templated jobs, the friction above comes from handing off editable source files and hoping every later edit stays inside the lines.
StackFill works from the finished print PDF you already approved. You mark which elements customers may edit and lock everything else. Nobody rebuilds the design in a new editor, so layout, brand colors, and the legal line stay as approved. You publish a hosted fill link or an embed, and the person filling it in works against a live proof.
The download is a press-ready CMYK PDF. The locked artwork in it is the same artwork you approved, not a re-created copy. CMYK and spot colors are kept as they are in your file, and the proof is rendered from the same file that goes to the shop. Final color on press still depends on the shop's process and proofs. See how it works.
StackFill does not design or redesign anything, and it does not replace your prepress judgment on a one-off job. It makes an existing, finished file fillable. For multi-client studios, see the agencies overview.
A clean agency print template handoff is ten minutes of checking before the file leaves. Do it every time, and the shop can run your job without questions.