Assembly
Build a deliberate file and page sequence before pressing Merge
Start with a cover, index, or primary document when the packet requires one. Move files up or down, search large queues by name, and apply page ranges to omit duplicate covers or appendices. Quick sorting is reliable only when filenames were designed for sequence; inspect the visible order instead of assuming alphabetical order matches the reader's workflow.
Normalization
Rotation can be corrected, but page sizes and margins remain part of each source
A merged PDF can contain A4, Letter, landscape, receipt-sized, and scanned pages. Apply rotation per source or across the queue where appropriate, then check the transitions in a normal viewer. Merging does not automatically crop, scale, compress, or redesign inconsistent pages, so use organize or compression tools separately when those changes are needed.
Document features
Treat forms, bookmarks, signatures, attachments, and links as features that need testing
Basic page content usually merges cleanly, but document-level behavior can change when files are rewritten. Signature validity may be broken, duplicate form-field names can conflict, bookmarks may not become a unified outline, and attachments may not carry over. Preserve originals and use a full PDF editor when these features are contractually or operationally important.