Production Calendars, Proofing, and File Handover

What this covers

This service covers the production side of a recurring agency publication: the annual calendar that sets every deadline, the proof and approval rounds for each issue, and the packaged source files the agency receives when an issue is accepted. It applies to activity guides, newsletters, program catalogs, and annual reports on a fixed cycle, including publications produced by parks and recreation, communications, library, and public works departments, often with several contributing to one issue.

Most of the dates are set by others. A recreation guide must reach households before program registration opens, the printer needs files by a fixed date, and the mail drop has its own window. When several reviewers comment at once, when nobody records who approved what, or when final files exist only on a designer's computer, issues slip, errors reach print, and the next designer rebuilds the publication from PDFs.

How we do it

• Work the calendar backward from fixed dates. We start with what the agency cannot move: distribution, the opening of program registration, board or council approvals, and office closures. From those we set mail and printer dates, proof rounds, and content deadlines in one annual calendar.
• Set content deadlines per department. Each department gets its own due date and a named contact, so missing content shows up before it compresses the proof schedule.
• Plan each issue and review it afterward. A planning session with agency staff before each issue confirms page allocation, priorities, and changes to programs or fees. A production review after distribution records what slowed the schedule.
• Proof at defined stages. PDF proofs go out at set points. The first layout checks page allocation and structure, the corrected proof checks text, fees, dates, and contact details, and the final proof before printing confirms every logged correction.
• Take consolidated comments from one reviewer. The agency names one reviewer who gathers department comments and resolves conflicts before returning them, which prevents contradictory edits.
• Track every change. We log each request, the proof it came from, and its resolution, make the revisions, and mark them on the next proof so the reviewer can confirm them without rereading the issue.
• Record sign-off at each stage. Approval is recorded with the reviewer's name, the date, and the proof version. Files do not go to the printer without a recorded final approval, and the printer's proof is checked and approved before the press run.
• Package the issue on acceptance. We run InDesign's Package command, add an IDML export, and assemble the linked graphics, fonts where the license allows, and stock image license records. Package does not copy fonts activated through Adobe Fonts, so we list them.

What you receive

• The annual production calendar, with distribution, printer, mail, proof, and department content dates, reissued whenever a date changes.
• PDF proofs for each stage, with a change log showing each request and its resolution.
• A sign-off record for each issue, listing each stage's approver, date, and proof version.
• A packaged source folder for each issue: InDesign files, an IDML export, linked graphics, fonts where licensing permits, a font list identifying any Adobe Fonts that require separate access, and the print PDF as sent to the printer.
• Stock image license records matched to the images used in that issue.
• A handover note describing the file structure, the styles in use, and anything a successor designer should know.

Considerations for public agencies

• Ownership of work product. The contract should assign copyright in the final designs and source files to the agency on acceptance and payment, and should list source files as a required deliverable. Without that language, an agency may hold only PDFs when it changes designers. Counsel should review the wording.
• Licenses do not transfer with ownership. Owning a design does not mean owning its fonts or stock photographs. Desktop font licenses vary on whether fonts may be shared with a printer or handed to a client. The contract should require stock images to be licensed in the agency's name or on terms that allow transfer to the agency, and the license records kept with each issue show what it may reuse.
• Public records and retention. Proofs, approvals, and final files are often public records. The agency's records schedule should determine what is kept and for how long. Confirm retention periods with the agency's records officer.
• Accessibility starts in the source file. Posted PDFs fall under the ADA Title II web rule, covered on the digital editions and accessible PDFs page. Reading order, export tagging, and alternative text are set in the InDesign file, so keeping it lets an agency correct most problems at the source and export again, though the exported PDF still needs testing.
• Approval records. The sign-off record and change log show who approved each proof and what was changed, which answers questions about a published fee, date, or program description.
• Procurement and transition. A solicitation and contract that specify the calendar, proof stages, sign-off method, and packaged deliverables let the agency compare proposals on equal terms and transition the work when a term ends.

Starting an engagement

An engagement begins with a review of the agency's current publication files, brand standards, production schedule, and fixed dates for the coming year. HQT then drafts the annual production calendar and a proof and sign-off procedure for agency approval, and inventories prior source files and license records so gaps are found before production starts.

Frequently asked questions