What does the combined numbering and imposition workflow look like?
The two jobs are separate tools solving separate problems, and mixing up the order causes most of the mistakes people run into with numbered ticket runs. Variable data numbering changes the content of each page — it prints "0001", "0002", "0003" onto an otherwise identical ticket template, one number per page, in page order. Imposition then rearranges those already-numbered pages onto a press sheet.
Run numbering first. If you impose an unnumbered template and try to number the imposed sheet afterward, you either have to place four or eight numbering fields per sheet with different starting offsets, or you end up numbering by position instead of by final stack order — which produces four separate sequences instead of one continuous one. Numbering the flat, single-ticket file first means the imposition step only has to preserve an order that's already correct.
How are the lifts taken off the pile?
A guillotine cuts to a fixed depth, so a long run is separated in lifts taken from the top of the delivery downward. Each lift is cut, and its resulting piles are placed onto the piles from the lift before it rather than beside them, which is what preserves the running sequence through the whole job.
Lift boundaries are where sequence is most often lost, because they are the moments when material is physically handled. A lift set down out of order, or piles combined side by side instead of on top, produces output that looks orderly and counts wrongly.
Heavier stock reduces how many sheets fit in a lift, so the same quantity on a thicker sheet needs more handling operations and carries proportionally more risk. That is a scheduling consideration as much as a technical one.
What does the delivery need to look like?
The delivery is the press output stacked in the order it was produced, unjogged in the direction that would disturb the sequence and kept as one body of work. Anything that reorders it, including riffling to check registration, has to be undone exactly before the job moves on.
Interleaved marker sheets are a common precaution on long runs. Placing a slip every few hundred sheets gives the operator a reference for reassembling the pile if it is disturbed, and costs almost nothing compared with the alternative.
Waste is handled at the front rather than in the middle. Because a replacement cannot be inserted into an ordered pile, spoilage is covered by running additional sheets at the start of the job and accepting them as consumed.
How do you check the order is correct before printing the full run?
Print a short proof run first — enough sheets to cover at least one full block boundary, such as sheets 1 through 5 for a 5-up job. Cut the proof by hand and confirm each pile reads consecutively with no repeats or gaps at the boundary between position ranges. This catches the most common setup mistake: numbering applied to the imposed sheet instead of the flat file, which produces four or five interleaved short sequences instead of one continuous one.
For the numbering step itself — generating the sequential values, handling leading zeros, and applying prefixes or skip patterns — see our sibling site on variable data PDF numbering, which covers that half of the workflow in detail. Variable data printing in general refers to a print method that allows elements such as text and images to change from one printed piece to the next without stopping the press, which is exactly the mechanism a numbering pass relies on. (Wikipedia: Variable data printing)
Should you print extra sheets to cover spoilage?
Digital and offset presses both produce the occasional spoiled sheet — a mis-feed, a smudge, a registration slip on an offset run. On a sequentially numbered job, a spoiled sheet doesn't just cost one ticket, it costs one ticket from every position on that sheet, which breaks the sequence at that point in five different piles instead of one. Planning a small run of extra numbered sheets at the end of the sequence (continuing the numbering past the target quantity rather than repeating numbers) gives the bindery operator sheets to substitute for any that come out damaged, without ever having to duplicate a number that's already in circulation.
Confirm with your print provider how they prefer to handle this before the file goes out, since some shops number to a fixed end value and simply accept a slightly short final stack if spoilage occurs, while others expect a numbered overage built into the file from the start. Either approach works; what matters is deciding before printing rather than discovering the gap after the piles are already cut and boxed.
Does the numbering software need to match the imposition tool?
No — the two steps only need to agree on file format and page order, not on being the same product. A numbering tool that outputs a standard multi-page PDF, one ticket per page in ascending order, hands off cleanly to any imposition tool that reads standard PDFs and preserves page order during layout. Keep the intermediate file as a checkpoint: open the numbered PDF before imposing it and confirm the first and last few pages show the numbers you expect, since it's far faster to fix a numbering error in a flat file than after it has been split across multiple sheet positions.
Bring an already numbered or merged PDF into PDFImpose, configure cut-and-stack order, and verify a small cut sample before the full run.
Common questions
Should I number the tickets before or after imposition?
Number first, then impose. Variable data numbering works on the single-page source file, one ticket per page, in the exact order you want them to end up. Imposing an already-numbered file preserves that order across each stack position.
What if I need to skip certain numbers, like 4 or 13?
Handle skips in the numbering step, not the imposition step. Generate the numbering sequence with the excluded numbers removed or replaced, then impose the resulting file — the stack layout doesn't need to know about the gap, it just follows the page order it's given.
How do I number a stub and a main ticket with the same number?
Keep the stub and the main ticket on the same page in the source file so they share one numbering pass and one position in the imposition. That guarantees ticket #42 and stub #42 are always adjacent in the printed sheet and separated only by the perforation, not by cutting.
Can this same workflow print numbered raffle tickets in duplicate?
Yes. Print the numbered source twice per ticket (once for the stub, once for the retained half, or as a duplicate page) before imposition, or design the ticket with both halves showing the same number on one page. Either way, keep the duplication in the source file so the cut and stack layout only has to handle ordering, not duplication.
What does a mis-imposed numbered job look like?
Each individual sheet looks correct, and the error only appears across the stack: the piles jump in increments rather than counting upward, or numbers repeat at pile boundaries. Because nothing on a single sheet is wrong, the fault survives ordinary proofing and is usually found only after cutting.
How do I test a numbered run cheaply?
Print and cut a short test stack rather than a single sheet. Check that each pile counts upward continuously and that the last number of one pile and the first of the next do not overlap. A test of a few sheets catches ordering faults that no amount of on-screen checking will.