Prepress and Print-Ready Files for Public Agencies

What this covers

Prepress is the step between an approved design and a press run. It turns layout files into production files a printer can image without guessing: pages checked against the printer's specification, images at usable resolution, color converted to the printer's output conditions, fonts embedded, and bleed and trim set correctly.

Parks and recreation departments use it for activity guides and community magazines. Communications offices use it for annual reports, newsletters, and mailers. Utilities and libraries use it for bill inserts, notices, and posters.

The problems are often invisible until press. A file can look correct on screen and still print with white slivers at the trim, muddy photos, black text that knocks out instead of overprinting, or a large black area that reads as gray. Agency printing also runs against dates that cannot move, such as a registration opening or a mail drop, so a rejected file costs time the calendar does not have.

How we do it

Get the printer's specification in writing before the first issue. We hold a specification conversation with the agency's print vendor and record trim size, bleed, PDF/X variant, output color profile, total ink limit, rich black build, minimum image resolution, and how creep is handled.
Build a preflight profile from that specification. We set up an InDesign Preflight panel profile matching the printer's rules, so missing links, low resolution, RGB images, and missing fonts show up during layout, not at export.
Set bleed, trim, and safety margins at the document level. Bleed goes on each trimmed edge at the printer's measurement, and live content stays inside the safety margin. For saddle-stitched books, we confirm the page count is a multiple of four, and for thicker books we either apply the printer's creep allowance or confirm the printer applies it in imposition.
Check effective resolution, not file resolution. Effective resolution drops as an image is enlarged in the layout. We flag images below the printer's minimum at their placed size, common with photos exported from a registration system or copied from a website or text message.
Convert color to the printer's profile. We convert to the output profile the printer names, use their rich black build for large black areas while keeping small text in single-ink black, and keep total ink coverage within their limit. Brand spot colors are kept or converted as the printer and job require.
Review overprint and transparency. Overprint Preview and Separations Preview show black text that should overprint and white objects wrongly set to overprint, and the Flattener Preview panel shows where transparency will be flattened. This matters most for PDF/X-1a, which does not support live transparency.
Export to the PDF/X variant the printer asks for. PDF/X-1a and PDF/X-4 handle color and transparency differently. We use the one in the specification, embed all fonts, and preflight the exported PDF again.
Deliver the way the printer works. We use the printer's upload method and file naming convention, then review the report from the printer's own preflight.
Settle proofing and sign-off in advance. We agree with the agency whether a job needs a hard proof, such as a contract proof or press proof, or a soft proof reviewed on screen, and who at the agency signs the printer's proof before the run is released.

What you receive

A written print specification summary for each printer and product.
A preflight profile matched to that specification, usable by agency staff or a later vendor.
Print-ready PDF/X files named to the printer's convention.
A completed written QA checklist for each job covering bleed, resolution, color, ink limit, overprint, fonts, and export settings.
The printer's preflight report and the signed proof approval, filed with the job.
A packaged source folder with layouts and links, plus a note listing any fonts that could not be included under their license.

Considerations for public agencies

Fonts and licensing. PDF/X files embed their fonts, so the printer can output the job without the font files. Source files are different: font licenses limit what can be handed over, as described on the production calendars, proofing, and file handover page, so confirm terms before source files change hands.
Print files are usually not accessible files. A PDF/X file is built for the press, while documents posted online generally must meet WCAG 2.1 Level AA under the ADA Title II web rule. Post an accessible version instead of the print file, often a PDF built to PDF/UA; the digital editions and accessible PDFs page covers the rule and its compliance dates.
Records and retention. Final print files, proofs, and sign-offs may be public records. Check the agency's retention schedule and keep the approved proof with the job file.
Sign-off authority. Approving a proof releases the job to press and generally makes the agency responsible for any error the proof shows. Name who may sign before the job starts, and record any change made after a proof.
Procurement and contract terms. Printing is often bought under a separate contract from design. That contract may set file standards, proof requirements, and who pays for a reprint caused by a file error, so prepress should follow its terms.

Starting an engagement

An engagement begins with a review of the agency's current print files, recent printer rejections, brand color standards, and the print calendar. HQT then contacts the agency's print vendor for the specification and builds the preflight profile and QA checklist before the next issue enters production.

Frequently asked questions

Our printer already runs preflight. Why prepare files separately?

A printer's preflight finds problems after the agency has approved the design, and any fix the printer makes may not be visible until the proof. Preparing files to the printer's specification first keeps the approved design and the printed piece the same. The printer's preflight then works as a second check, not the first one.

Do we need a hard proof for every job?

Not always. A soft proof reviewed on screen is often enough for a repeat job on a known paper stock with the same printer. A hard proof is worth the time for covers, brand colors, a new stock, or a new printer. The choice and the approver should be agreed before the job starts, not at the proof stage.

Which PDF/X version should our files use?

Use the version your printer specifies. PDF/X-1a requires transparency to be flattened and color to be in CMYK or spot inks, while PDF/X-4 keeps live transparency and supports color-managed workflows. If the printer has no stated preference, ask which one their workflow handles best and record the answer.

Can we post the print PDF on our website?

Generally not, because print PDFs are built for the press and usually lack the tags, reading order, and alternative text needed to meet WCAG 2.1 Level AA, which the ADA Title II rule adopts for posted documents. Post an accessible version instead. The rule allows an inaccessible file to sit beside an accessible alternate only in limited cases, so confirm with your ADA coordinator or counsel before posting both.

What happens if we change print vendors?

The first job with a new vendor starts with a new specification conversation, because bleed, color profile, ink limit, and PDF/X variant can all differ. The preflight profile and QA checklist are updated to match. The source layouts stay usable, subject to the font license terms noted in the package.

Prepress and Print-Ready Files