Print and mail
Variable Data and Document Composition
Turning records from an agency system into documents that are correct, accessible, and ready for print or electronic delivery.
What this covers
Variable data and document composition is the engineering between an agency's system of record and the document a resident opens. A billing system holds meter reads, rate codes, and balances; a tax system holds parcels, assessed values, and exemptions. A bill or a notice is a rendering of those records under rules: which paragraphs apply, which legally required language appears, which insert goes in the envelope, and which accounts are not mailed at all.
The service spans the extract, the templates and composition engine, the rules, the proofs, the accessible electronic copy, and what happens to all of it when the source system is replaced.
The departments that buy it are the ones with mail they are required to send: utilities for bills and delinquency notices, tax and assessment offices for valuation notices, courts for hearing notices, and human services for eligibility determinations. The press run is the last and most visible step of a system. Most of the difficulty sits upstream, in the data, the rules, and the calendar.
Typical activities
- Extract design. Settling the interface between source system and composition: format, record structure, encoding, control totals, how the file declares itself complete, and naming that traces a document to its run.
- Document inventory and rules capture. Listing every document the system produces, who owns its language, and which passages are fixed by statute, ordinance, court rule, or consent decree rather than discretionary.
- Template development. Separating fixed design from variable content, so a rate change or an amended legal paragraph is a content edit rather than a redesign.
- Conditional logic. Implementing the selection rules: delinquency stage, exemption status, credit or zero balance, payment plan, language preference, and suppression.
- Proofing against real records. Proofs from a production extract with a deliberate edge case set: long names, multiple parcels on one bill, negative balances, detail that overflows to extra pages, and in-care-of addressing.
- Accessible output. A tagged PDF for the electronic copy with reading order, document language, heading structure, alternative text, and real table structure, generated as its own output rather than converted from the print file.
- Version control. Templates, rules, and the extract specification in source control with releases and approvals, so the template behind a document mailed on a given date can be reproduced.
- Reconciliation and mail handoff. Comparing record and page counts between extract and output, confirming suppression and reprint lists were honored, and passing output and addressing data to presort and barcoding. Postal requirements change, so confirm current United States Postal Service publications.
What you receive
- An extract specification written as an interface document, with field definitions, control totals, and failure handling, reusable when the source system is replaced.
- The template library in editable source form under version control, with release notes.
- A business rules catalog mapping each condition to the content it selects, citing the authority for any legally required passage.
- Proof sets from real records, including an edge case proof book, with the record of agency approval.
- Accessibility test results for the electronic output against a named standard, with the method used and open items.
- A run book and reconciliation reports written so agency staff or another vendor can run the process.
Considerations for public agencies
Deadlines are often set in law. Mail-by dates for tax bills, minimum notice periods before a penalty, lien, hearing, or shutoff, and election mailing windows are frequently fixed by statute. Build the schedule backward from those dates, with proof review inside the window and a recovery path for a failed run. Confirm current deadlines against the statute and with counsel.
The composed document is a record. Retention schedules generally require that an agency be able to produce what was sent: keep either the composed image or the data plus the exact template version behind it. Appeals and records requests ask for the notice mailed to one person on one date, so decide before the first run.
Accessibility applies to the electronic copy. Title II of the Americans with Disabilities Act covers state and local government services, and the Department of Justice rule implementing it adopts WCAG 2.1 Level AA, with dates that depend on entity size. Section 508 may apply where federal funding is involved; PDF/UA is the PDF-specific standard. Confirm which applies with counsel and name it in the solicitation.
Sensitive data travels in the extract. These files carry partial account numbers, bank details, addresses protected under state confidentiality programs, sealed or juvenile case information, and health or criminal justice data. Masking and suppression belong in the composition rules and should be tested like any other rule.
Keep the documents portable. Composition is often procured with printing and mailing, but the template source, rules catalog, and extract specification should be agency-owned deliverables, so the documents can move if the print work does.
Replacing the source system breaks the extract. Identifiers, consolidated accounts, and historical balances change with a new billing, tax, court, or permitting system. Treat the extract specification as an acceptance criterion for that system, and compare documents composed from old and new extracts before retirement.
Working with HQT on this
HQT works on the data and rules layer of document production: extract design, composition templates, conditional content, accessible output, and the version control and reconciliation around it. An engagement usually starts with a review of one document family, its extract, and the rules governing its language.
Frequently asked questions
Can we keep our existing bill templates when we replace our utility billing system?
Sometimes, if the templates exist in editable source form and the new extract can be mapped to the fields they expect. More often the extract changes shape, identifiers are renumbered, and some values no longer sit in the same place, so the templates need rework even when the visual design survives. Make the extract specification a requirement and an acceptance criterion for the new system, and plan a parallel period in which documents composed from the old and new extracts are compared record by record.
Is the PDF we archive from the print file accessible?
Usually not. A print stream is built for a press, so it generally carries no tags, reading order, language declaration, or table structure, and converting it afterward tends to produce a file that passes a shallow check but reads poorly with a screen reader. Generate the accessible copy as its own output from the same data and templates, then test it against the standard that applies to your agency and keep the test results.
Who should own the template files, the agency or the print vendor?
The agency should own the template source, the business rules catalog, and the extract specification, and the contract should say so rather than leave it to be assumed. Those assets are what allow the documents to move if the print work moves or the source system is replaced. It is also worth asking what it would take to reproduce the same documents in a different composition engine, since some output formats are tied to particular products.
How do we proof documents without putting production data at risk?
Masked or synthetic data is fine for early template development, but final proofing needs records that behave like production: unusual names, overflow detail, credit balances, consolidated accounts, and accounts that must be suppressed. A common approach is a controlled extract of real records held in an environment with the same access controls as production, with the approved proof set retained as a record. Confirm the approach with your privacy or records officer, particularly for court, health, or criminal justice information.
Our notices go out late almost every cycle. Is that a printing problem?
Usually not. Late mail is more often caused by the extract finishing late, rules questions resolved late, or proof review compressed into days the calendar does not have. Measure the actual elapsed time from the source system close through extract, composition, proof approval, and handoff to mail preparation. The step that needs to change is rarely the press.