Working Out Cut and Stack Blocks (With the Arithmetic)
What is the formula?
Block size equals total pages divided by the number of positions on the sheet, and that same number is the sheet count. Position one covers pages 1 to the block size; each later position starts one past where the previous ended. For position p counting from one, the first page is block size multiplied by p minus one, plus one, and the last page is block size multiplied by p.
It is worth writing the boundaries down rather than trusting the layout, because an off-by-one at a boundary produces two piles that overlap by a page or leave one out, and neither is visible on any single printed sheet.
What does a worked example look like?
Take a 1,000-page job at 5-up. Dividing gives blocks of 200 and a run of 200 sheets. The piles then read 1 to 200, 201 to 400, 401 to 600, 601 to 800 and 801 to 1000, and the first printed sheet carries pages 1, 201, 401, 601 and 801 in its five positions.
That first sheet is the quickest check available. If its positions carry widely separated numbers matching the block boundaries, the imposition is cut and stack. If they carry consecutive numbers, or the same number repeated, the file has been imposed some other way and the piles will not come off the cutter in order.
What if the count does not divide evenly?
Uneven division leaves at least one pile short and moves the boundaries of every pile after the first, which is the situation that produces a job that looks right until it is cut. The straightforward answer is to pad the total with blank or duplicate pages until it divides by the number of positions.
Padding is cheap relative to the alternative. A 998-page job at 4-up needs two extra pages to reach 1,000, whereas discovering the mismatch after the stack has been cut usually means reprinting, because the ordering cannot be recovered by hand once the piles exist.
How do I verify before committing the run?
Print and cut a short test stack rather than a single sheet. The ordering in cut and stack lives in the depth of the stack, so a single sheet cannot demonstrate that the piles will count upward correctly, and only a stack several sheets deep shows what happens at the pile boundaries.
Check two things on the test: that each pile counts upward continuously with no repeats, and that the last number in one pile and the first in the next do not overlap. Those two checks catch the great majority of imposition faults in numbered work.
| Total pages | Positions | Block size | Sheets | First pile |
|---|---|---|---|---|
| 400 | 4 | 100 | 100 | 1 to 100 |
| 1,000 | 5 | 200 | 200 | 1 to 200 |
| 1,200 | 6 | 200 | 200 | 1 to 200 |
| 960 | 8 | 120 | 120 | 1 to 120 |
| 998 | 4 | uneven | pad to 1,000 | pad first |
Common questions
Is the block size the same as the sheet count?
Yes, for a straightforward cut and stack job. Every sheet contributes exactly one page to each pile, so the number of sheets equals the number of pages in each pile. That equivalence is a useful sanity check: if the two numbers differ, the arithmetic has gone wrong somewhere.
How do I check the imposition from one sheet?
Read the numbers in each position on the first sheet. Widely separated values matching your block boundaries mean cut and stack. Consecutive values mean the file is in reading order, and repeated values mean collated N-up. It is the fastest check available before printing.
Can I add pages after imposing?
Not without redoing the arithmetic. Adding pages changes the block size, which moves every pile boundary, so the imposition has to be regenerated from the new total. This is why the page count should be final, including any padding, before the file is imposed.
Where should padding pages go?
At the end is simplest, because it leaves every existing page in position and only extends the final pile. Padding inserted mid-document shifts everything after it into a different pile, which is exactly the kind of change that is hard to spot before cutting.
Does duplex change the calculation?
It changes what a sheet holds, so work in pages rather than in sides and confirm how your imposition treats the back of the sheet. The block logic itself is unchanged, but the sheet count halves when both sides carry positions, so verify against a test stack rather than assuming.