To build a correctly ordered PDF stack in PaperPort, establish the source order before stacking and inspect the resulting page sequence afterward. Folder display order, selection order and the final reading order should not be treated as interchangeable. A document can contain all the right pages in the wrong sequence.
Work on copies in a separate working folder. PaperPort's assembly operations can change the contributing items, so preserving the originals is more reliable than assuming they will remain available in their initial form. This guide follows the documented PaperPort 14 desktop workflow.
Write the intended sequence before combining
Create a short list of the source files in reading order. Include the expected page count for each file and identify any cover or separator pages. If several sources have similar names, give the working copies clear labels before selecting them.
For an illustrative packet containing a cover, report and appendix, the acceptance check is not simply that the output has the expected total. The report must follow the cover, and the appendix must begin after the report's last page. A page count alone cannot establish that order.
Select the appropriate assembly operation
Tungsten's stacking and combining guidance distinguishes stacking PDFs from other combining operations. It describes selecting files in the intended stack order. Check which operation you are about to use rather than relying on the fact that several commands all produce a PDF.
Keep source restrictions visible
Read-only or protected inputs can have restrictions in the documented stacking workflow. Ask the owner for an appropriate authorized working copy when necessary. Do not remove protections or substitute an unofficial conversion service merely to make the source join the queue.
Keep multi-page sources intact when appropriate
A source that already has several pages should be checked internally before joining the larger packet. If its own pages are reversed, arranging the file correctly among other files will not repair its internal order. Treat file order and within-file order as separate checks.
| Stage | Check |
|---|---|
| Source preparation | Correct files, names and individual page counts |
| Selection | Intended sequence of contributing files |
| Assembly | Correct stack or combine operation |
| Saved result | Total pages and every section boundary |
Test a small packet first
Use three harmless sample files with visible labels such as Cover, Report and Appendix. Build the proposed stack through the controls documented for your installed edition. Save or identify the output clearly, then inspect the actual page sequence.
This small exercise establishes how your selection and operation behave. It is not a performance benchmark or proof that every later production will be correct. Once the sequence is understood, repeat the process with the reviewed working copies of the intended documents.
Check insertion points when adding a missing page
If a page must be inserted afterward, use the page insertion instructions to understand where the selected page will place the new material. The documented workflow uses the current page as a reference. Confirm the intended insertion boundary on a copy rather than guessing from thumbnail position.
After insertion, inspect the page before and after the addition. A correct inserted page can still be placed on the wrong side of a divider. Update any manually written contents page or reference list affected by the change.
Review the final document as a recipient
Open the final saved packet and move through each section boundary. Check that the front and back of a two-sided original are adjacent where appropriate, that separator pages appear intentionally and that no source was included twice.
Also inspect orientation and readability. A page in the correct numeric position can still be upside down or belong to a different case. Use the document owner's source list rather than treating a tidy thumbnail grid as evidence of content accuracy.
Preserve a lightweight assembly record
Keep the final filename, source order, page count and responsible reviewer. If a corrected version is issued, name it distinctly and record the change. Do not silently replace an already distributed packet whose page references others may be using.
Our PDF workflow selection guide discusses combining requirements in a broader software decision. For an existing PaperPort workflow, the immediate goal is simpler: an intentional source sequence, a preserved original set and a saved stack whose boundaries have been checked against the intended reading order.
