Publication Layout and Typesetting for Public Agencies

What this covers

Publication layout and typesetting turns approved text, tables, and images into pages people can read and that the agency can produce again next time. It covers page layout, type selection and setting, formatting of editorial and program content, and the template behind it. Recreation departments use it for program descriptions and schedules, finance offices for budget documents, planning departments for comprehensive and strategic plans, and most departments for annual and program reports.

The hard part is usually a later edition: copy arrives long, a fee table gains a column, a translated edition is due, and the original designer has moved on. Long and recurring documents need a structure that survives those conditions, reads well for a public audience including older residents, and exports to an accessible PDF without being rebuilt by hand.

How we do it

Build the template before the first edition. We build an InDesign template: a column and baseline grid, parent pages for each recurring page type, and paragraph, character, object, table, and cell styles for every repeating element. A later edition is then assembled, not redesigned, and another designer can follow the file.
Set hierarchy for the actual audience. Body type is sized for residents reading without magnification. Line length stays moderate, leading is generous, text contrast meets at least the WCAG 2.1 AA ratio of 4.5:1 (3:1 for large text), and body text is not set over photos. Heading levels are few and clearly distinct.
Build tables as structure. Schedules, fees, and listings are real InDesign tables with table and cell styles, repeating header rows, and consistent alignment for dates, times, and amounts. When content comes from a registration system or database, we agree on a fixed export format so data is placed or merged, not retyped.
Map styles to export tags. Each paragraph style carries export tagging, so the tagged PDF inherits its structure from the source. Images get alternative text through object export options, and the Articles panel sets reading order. The exported PDF then needs checking and finishing, not rebuilding.
Copyfit by rule. The template defines what may flex when copy runs long: a sidebar can drop, a photo can shrink, a section can continue later. Type size and tracking are not squeezed to force a fit. If copy still runs over, the content owner gets a specific cut request.
Plan multilingual editions from the start. Translated text usually runs longer, so the grid leaves room for it. Before the template is final, we confirm the fonts include every accented character the agency's languages need, and choose matched companion fonts for any non-Latin script. Each language gets styles with the correct language setting so hyphenation and spell checking work.
Separate content ownership from setting. The agency owns content accuracy: names, dates, fees, legal language, and translations. We own faithful setting: the layout matches the approved copy, nothing was dropped in a reflow, and styles were applied correctly. We proofread against the approved source and flag apparent errors, and the agency decides corrections.

What you receive

The InDesign template with grid, parent pages, and full style set, plus an IDML export for opening in earlier InDesign versions.
A template guide explaining each style, its export tag, each parent page, and the copyfitting rules.
PDF proofs for each round, with changes marked.
Packaged final files, with font files included only where each license allows it and a list of any fonts recipients must license or activate themselves.
A tagged PDF for posting, checked with an automated checker and a screen reader and finished to WCAG 2.1 Level AA as described on the digital editions and accessible PDFs page, and a separate print PDF to the printer's specification, such as PDF/X-4 or PDF/X-1a.
A record of the font and image licenses used.

Considerations for public agencies

Accessibility law. Posted documents fall under the ADA Title II web rule, which adopts WCAG 2.1 Level AA, and the duty to provide effective communication applies regardless; the digital editions and accessible PDFs page covers the rule, its exceptions, and compliance dates.
Public records. The published document, and depending on state law some working material, becomes a public record subject to a retention schedule. Confirm with the records officer what must be kept, and store the approved copy with the final files.
Ownership of the template. So the agency can change designers or bring work in house, confirm the contract assigns the agency ownership of the template, guide, and source files, not only the final PDFs.
Font licensing. Desktop font licenses vary on whether fonts may go to a printer or a client. Choose fonts the agency can license for its own staff so the template stays usable after a contract ends.
Language access. Title VI of the Civil Rights Act of 1964 prohibits national origin discrimination by recipients of federal financial assistance, and many states and localities have their own language access laws or policies. Confirm which documents and languages apply with counsel or the language access coordinator before the template is built.
Fixed calendars. Budget documents are tied to adoption hearings and program guides to registration openings. Set copy, approval, and printer deadlines backward from those dates. Defined copyfitting rules help late changes fit without moving them.

Starting an engagement

An engagement starts with a review of the agency's current documents and source files, brand standards, content systems, languages, and fixed dates. HQT then proposes a template structure and style list for agency approval before the first document is set.

Frequently asked questions

Can our own staff produce later editions from the template?

Yes, if they have InDesign and licensed access to the fonts the template uses. The template guide explains which style applies to each element, how the parent pages are used, and what may flex when copy runs long. Confirm font licensing for each staff machine before handover.

Who is responsible if a fee or date is wrong in the published document?

The agency owns the accuracy of its content, including fees, dates, names, legal language, and translations. HQT is responsible for setting the approved copy faithfully and checks the layout against that copy. Apparent errors in the source are flagged to the content owner, who decides the correction.

Does a good template make the PDF accessible on its own?

No. Styles mapped to export tags, alternative text, and a defined reading order build most of the structure into the source file. The exported PDF still has to be checked against WCAG 2.1 Level AA and fixed where needed, with particular attention to tables and reading order.

Can the layout pull schedules directly from our registration system?

Not as a live connection, but usually from an export, if the system can produce a consistent structured file such as a delimited text file. That export can be placed into styled tables or brought in with InDesign data merge, which avoids retyping. The export format needs to stay the same between editions, so changes to the system report should be coordinated with whoever maintains the layout.

How are translated editions handled in the same template?

The grid leaves room for longer translated text, each language has styles with the correct language setting, and each edition's PDF is exported with its document language set. Right-to-left scripts such as Arabic need right-to-left text direction and often a reversed page order, so they are planned as a separate layout. The agency or its translator owns translation accuracy, and a fluent reviewer should check the typeset proof.

Publication Layout and Typesetting