catchline
A temporary note at the top of a page or galley proof to identify it.
catchline: proof ID that stays only until print
A catchline is a brief identifying label printed or written at the head of a galley proof, page proof, or other intermediate printing stage. It serves as a temporary tracking mark, typically containing the job name, page number, date, or revision level, and disappears before the final printed product leaves the pressroom. Unlike a permanent header or footer, the catchline exists only in the proofing phase.
In traditional letterpress and offset workflows, the catchline allowed compositors and press operators to sort and sequence pages correctly when multiple proofs were in circulation. A catchline might read something like "SMITH ANNUAL 2024 / P12 / REV B / 14 JAN" at the top margin. This proved essential when a single job involved dozens of galleys moving between different stations: editor, art director, platemaker, and pressman. Without it, a single misplaced proof could collapse the sequence and force a costly rerun.
Placement and Format
The catchline typically appears in the top margin, outside the live image area, so it could be stripped away or hidden during final plate preparation. It was often set in a smaller font than body text, sometimes in a contrasting typeface for visibility. In digital workflows, catchlines function similarly on screen proofs and print-ready PDFs, though they may be embedded as metadata or printed in a crop margin rather than as physical type.
The catchline overlaps with similar tools: a running head identifies content within a finished book; a job ticket rides with physical materials through production; a proof mark signals corrections. But the catchline's sole purpose is temporary identification during manufacture, making it distinct from elements meant to remain visible or functional in the product itself.
Today, catchlines are less common in fully digital workflows where asset management systems and file naming conventions do much of the tracking work. However, they remain useful in hybrid environments where proofs are still printed to paper or where multiple versions of complex jobs circulate among stakeholders who may lack access to a shared database.