Numbered raffle tickets need two things a plain document doesn't: a matching number printed on both the ticket and its tear-off stub, and a page order that keeps sequential numbers together after cutting. Both come from a numbering merge plus a cut-and-stack imposition step, not from manually retyping 500 numbers.
What do you need to make numbered raffle tickets?
Three things, in this order: a one-ticket template with the stub attached, a numbering sequence (prefix, start number, digit padding, quantity), and an imposition step that arranges the numbered tickets onto sheets for cutting. Skip the imposition step and you'll still get 500 correctly numbered tickets — just not in an order that keeps them sequential once they're cut apart.
The template itself is simple: a ticket panel and a stub panel, usually separated by a perforation guide, each with a number field in the same position. Everything else — event name, date, prize description — stays static across the whole run.
Two decisions worth making before you set up the template: how many tickets fit per sheet at your chosen trim size, and whether the stub needs a barcode in addition to the printed number. A 4-up layout on a standard letter or A4 sheet is common for a compact ticket; a barcode adds a field to the merge but otherwise follows the same matching-number logic as the printed digits.
How does ticket-stub number matching work?
A numbering merge places the same generated value into two fields on one page: the ticket number and the stub number. Because both fields pull from the same counter for that record, they're guaranteed to match — there's no scenario where the ticket says 0247 and the stub says 0248, which is the exact failure a manual numbering stamp is prone to.
This matters for the drawing itself. Whoever draws a winning stub needs to hold a number that corresponds to exactly one ticket in circulation. A one-digit mismatch between ticket and stub either invalidates a draw or forces a manual cross-check against every ticket sold.
How should you set up padding and prefixes?
Digit padding keeps every number the same width by filling with leading zeros — 1 becomes 0001 in a four-digit scheme. A prefix is optional text before the number, useful when running multiple ticket types or events through the same numbering scheme (RAF-0001 vs VIP-0001).
| Run size | Minimum digits | Recommended digits | Example |
|---|---|---|---|
| Up to 99 | 2 | 3 | 001 |
| 100 – 999 | 3 | 4 | 0500 |
| 1,000 – 9,999 | 4 | 5 | 05000 |
| 10,000+ | 5 | 6 | 010000 |
Padding one digit past the minimum is cheap insurance — if a 500-ticket raffle grows to 650 tickets after the template is already set, 4-digit padding (0001–0650) still works, while 3-digit padding (001–650) would have broken at 999 anyway but reads inconsistently below 100.
Where does the perforation line go?
The perforation sits between the ticket panel and the stub panel, and it needs to be marked as a guide, not printed as visible ink. Most shops expect either a dashed line on a clearly labeled spot-color layer, or a position specified separately in the job ticket rather than drawn on the artwork at all.
Leave enough margin on both sides of the perforation guide for the stub to remain legible after tearing — a number set too close to the perf line risks being clipped by an imprecise cut or a slightly crooked tear.
A safe working margin is 3-4mm of clear space between any text or number and the perforation itself, on both the ticket and the stub side. That buffer absorbs the small positional drift that's normal for mechanical perforation, whether it's done on a digital press finishing unit or a separate perforating blade pass after printing.
How do you keep cut-and-stack piles sequential?
Printing four or six tickets per sheet is efficient, but naive imposition scatters numbers across sheets — sheet 1 might carry tickets 1, 126, 251, and 376 if numbers are assigned reading order across a standard grid. Once sheets are stacked and guillotine-cut through the whole block at once, you get four piles of tickets, but each pile mixes numbers from across the entire range instead of running sequentially.
Cut-and-stack imposition solves this by assigning numbers so that each position on the sheet lands in its own contiguous block once cut. Sheet 1 position 1 carries ticket 1, sheet 2 position 1 carries ticket 2, and so on — so after cutting, pile 1 is tickets 1 through 125 in order, pile 2 is 126 through 250, and so forth, depending on sheet count and grid size. For the imposition math and a step-by-step layout tool, see Cut & Stack PDF, which handles this specific grid-to-sequence mapping for numbered stacks.
Worked example: 500 raffle tickets start to finish
Say you're printing 500 tickets, 4-up per sheet (125 sheets), with a prefix of RAF- and 4-digit padding. The numbering merge generates RAF-0001 through RAF-0500, placing each value into both the ticket and stub fields on its page.
| Step | Setting | Result |
|---|---|---|
| Numbering | Prefix RAF-, start 1, pad 4 | RAF-0001 … RAF-0500 |
| Sheet layout | 4-up, 125 sheets | 500 tickets / 4 = 125 |
| Cut-and-stack grouping | 4 piles of 125 | Pile A: 0001–0125, Pile B: 0126–0250, Pile C: 0251–0375, Pile D: 0376–0500 |
| Sanity check | First 3 / last 2 per pile | 0001,0002,0003 … 0124,0125 |
Before sending the file to press, spot-check the first three and last two numbers in the sequence against the expected range — that single check catches most off-by-one errors from a miscounted start number or a padding width set too narrow for the run.
It's also worth confirming the pile boundaries land where you expect before cutting. If the 500-ticket, 4-up example above were run at 6-up instead, 500 doesn't divide evenly by 6 — the last sheet would carry only two tickets instead of six, which is fine to print but worth knowing in advance so the person cutting the stack isn't surprised by an odd-sized final pile.
Build the numbered ticket PDF here, then lay it out for cutting with Cut & Stack PDF.
FAQ
Do the ticket and stub need the exact same number?
Yes. The stub is the half a buyer keeps or the half dropped in a drum for the drawing, and it has to match the ticket exactly so a winning stub can be verified against a specific ticket. A numbering merge should place the same value in both fields on every page.
How many digits of padding should I use?
Pad to at least one digit more than your run size requires — a 500-ticket run needs 3 digits minimum, but 4 digits (0001–0500) reads more consistently and leaves room if the run grows before printing.
What line weight should the perforation guide use?
Use a dashed guide around 0.5pt in a spot color or clearly labeled layer, not a solid black line meant to print — most digital and offset shops perforate along a supplied guide line or a position you specify in the job ticket, and a heavy black rule can be mistaken for design content.
Can I number tickets without buying dedicated numbering software?
Yes. A numbering merge that accepts a prefix, start number, and digit padding covers standard sequential ticket numbering without a dedicated press-side numbering unit, which is typically only needed for on-press variable numbering at very high volumes.
1. Wikipedia, "Numbering machine," for background on mechanical sequential numbering that VDP replaced for most runs.