Applying headers and footers to every page of every document

The specification is one line: every page of every submitted document carries the document number, the project reference and the page numbering, in the customer’s format. One line to write, and a running cost for the whole project, because “every page of every document” includes the 300-page manual, the locked datasheet and the drawing whose title block sits exactly where the footer wants to go.

Here’s the manual approach and its limits.

The manual approach

Acrobat’s header and footer tool does this well for one document: set the text, the font, the margins, apply to all pages. The problem is the data. The header isn’t the same text on every document; it carries that document’s number and tag. Acrobat’s batch tools can stamp what’s common (a project reference, page numbers, a date) across many files in one run, but anything document-specific means one run per document, or a scripted approach driven from your register.

The workable manual version looks like this: batch-stamp the common elements across the whole set, then make a per-document pass for the variable fields, working from a checklist so nothing is skipped. Keep the customer’s font and margin requirements written down next to the tool settings, because “close enough” formatting is a thing reviewers reject.

Then the limits arrive.

Placement. Drawings have title blocks, manuals have their own running footers, and the customer’s margin spec doesn’t know that. Some documents need the header moved, which is another per-document decision.

Page x of y. If the numbering restarts per document, batch runs across files get it wrong, and if the customer wants numbering across a compiled set, nothing short of assembling the set first gets it right.

Locked files. The stamped file has to be a new file, produced the slow way.

Revisions. A revised document arrives clean and goes through the whole routine again, and the person doing it has to remember that the routine exists. A document that ships without its footers is a compliance return you did to yourself.

Where DocBoss comes in

DocBoss applies headers and footers across every page of every document, carrying the data your customer specified, in their font size and margins, laid out in one column or three. File names follow patterns you define, per target, with conditional rules for the cases one pattern doesn’t fit, so the customer’s convention and your sub-supplier’s can both be right at the same time. Locked and malformed files are handled rather than skipped. And because it happens as the submittal is built, a revised document can’t go out without its markings.

If your current process involves a checklist taped to a monitor, this part of the demo will feel familiar.