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.
Worked example: a 1,000-ticket run
Take a 1,000-ticket job printed 5-up. Pages per stack is 1,000 ÷ 5 = 200, so the press run is 200 sheets. Position 1 carries tickets 1–200, position 2 carries 201–400, position 3 carries 401–600, position 4 carries 601–800, and position 5 carries 801–1,000. Cut the 200-sheet stack once along both grid lines, and you lift five piles, each already numbered in order.
| Position | Sheet range printed | Ticket numbers in this pile |
|---|---|---|
| 1 | sheets 1–200 | 0001–0200 |
| 2 | sheets 1–200 | 0201–0400 |
| 3 | sheets 1–200 | 0401–0600 |
| 4 | sheets 1–200 | 0601–0800 |
| 5 | sheets 1–200 | 0801–1000 |
Each of the 200 sheets prints one ticket from every one of the five ranges — sheet 1 carries tickets 1, 201, 401, 601, and 801; sheet 200 carries tickets 200, 400, 600, 800, and 1,000. That's normal and expected: the sequence lives down the stack (sheet to sheet), not across a single sheet.
Where does perforation fit into the workflow?
Most numbered tickets carry a tear-off stub, and the stub needs to show the same number as the main ticket body. Handle that at the template stage, before numbering: design the stub and the ticket body on the same page, side by side, so a single numbering pass stamps both halves with the identical value. The perforation line itself is a print mark, not a cut — it gets printed at a fixed offset inside the ticket template and doesn't move as part of the imposition step.
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.
Impose your already-numbered ticket file into ordered cut and stack piles.
Open the free toolFAQ
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.