By ScoutMyTool Editorial Team · Last updated: 2026-05-27
Introduction
A broker I work with submits about 30 packages a month, and the difference between a package that clears underwriting in three days and one that bounces back for re-stacking is almost never the underlying file quality — it is the order, the bookmarks, the manifest, and the disclosure tracking. None of that is hard; all of it is easy to skip when an income document arrives twelve minutes before the lock expires. Here is the working PDF discipline I have seen survive a high-volume desk: standardized stacking, section bookmarks, a manifest cover page, and e-signed disclosures with intact audit trails. The goal is one first-submission package, every time.
Vocabulary, quickly
| Term | Meaning |
|---|---|
| Loan package | Single PDF combining borrower documents in underwriter-expected order |
| Stacking order | Lender-specific sequence of sections in the package |
| Disclosure | Regulatory document the borrower must receive within set deadlines |
| TRID / Loan Estimate | Three-day disclosure required at application; closes regulator gaps |
| eSign consent | Borrower opt-in to electronic signatures and records |
| Bookmark tree | Navigational sidebar that underwriters use to jump between sections |
| Manifest page | Cover page listing what is inside the package and where |
Step by step
- Pull the lender stacking order in writing. Most lenders publish it; if not, ask the AE. Follow it literally — same section names, same order.
- Collect documents into per-section folders. One folder per stacking section; one file per document. Easier to QC than a single bucket.
- Convert everything to PDF first. JPGs of pay stubs, screenshot bank statements — all become PDF before merge. Mixed formats break merge tools.
- Merge in stacking order. The merge tool should respect file-list order; double-check the first three pages of each section land where the underwriter expects.
- Build a manifest cover page. Loan number, borrower name, package version, table of contents with page ranges, disclosure deadline tracker.
- Add section-level bookmarks. One per stacking-order section, plus one per outstanding loan condition.
- Route disclosures through eSign separately. Disclosures sit in their own PDF that the borrower signs in the eSign platform; the signed file gets re-attached to the package as the final section.
- Submit via the LOS portal. Never email a loan package. Upload through the lender portal so the audit trail starts at submission.
Pre-submission checklist
- Manifest matches the actual section page ranges — slipping a document in or out without updating the manifest is the most common QC miss.
- Bookmarks open the expected section; click each one before submission.
- Disclosure dates on the manifest match the timestamps in the eSign audit certificate.
- File size is reasonable — a 600 MB package is usually an unflattened scan that should have been compressed. Flatten and re-compress before submission.
- The package opens in the underwriter\'s default reader (Adobe) without warnings about signatures or attachments.
- Loan number appears in the file name, the manifest, the metadata, and the LOS upload field — four places, all consistent.
Related reading and tools
FAQ
- What goes wrong most often in a first-submission package?
- Out-of-order documents. Underwriters work top-down, and a package that puts the borrower's 1003 application after the income docs gets bounced before review. Stick to the lender's stacking order exactly; if they publish one, follow it character-for-character even when it feels arbitrary. Their automation matches section headers.
- How do I bookmark a 200-page package quickly?
- Bookmark at the section level, not the page level. One bookmark per stacking-order section (application, credit, income, assets, property, disclosures), plus one bookmark per loan condition. Eight to twelve bookmarks total — that is what the underwriter clicks. Tools that auto-bookmark every page produce noise that nobody navigates.
- Can the borrower e-sign disclosures on a phone?
- Yes, and most lenders prefer it because it timestamps and audit-trails automatically. The borrower must first sign an eSign consent (E-SIGN Act in the US). Use an e-signature platform that issues a tamper-evident signed PDF; do not flatten the signed file because flattening can drop the audit certificate.
- How do I track disclosure deadlines?
- Use a manifest page at the front of the package that lists every disclosure with its required-delivery date and its actual-delivery date. The processor updates the manifest as disclosures clear. If a disclosure deadline gets missed, the manifest shows it on page 1 instead of buried in the package — much easier to catch in QC.
- What metadata should the package PDF carry?
- Loan number, borrower name, broker name, package version, and assembly timestamp. Set in the Info dictionary; mirror in a manifest page footer. The underwriter's LOS often indexes on loan number and version; consistent metadata cuts processing time.
- Can I send a package over email or does it have to go through the LOS portal?
- Always the LOS portal for active files. Email risks data exposure, missing acknowledgments, and version confusion. Use email only for clarifications referencing a package already in the portal, and never attach borrower documents to those emails.
Citations
- Wikipedia — “Mortgage underwriting in the United States.” en.wikipedia.org/wiki/Mortgage_underwriting_in_the_United_States
- Wikipedia — “TILA-RESPA Integrated Disclosure (TRID).” en.wikipedia.org/wiki/TILA-RESPA_Integrated_Disclosure
- Wikipedia — “Electronic Signatures in Global and National Commerce Act (E-SIGN).” en.wikipedia.org/wiki/Electronic_Signatures_in_Global_and_National_Commerce_Act
Assemble loan packages in your browser
Merge in stacking order, bookmark sections, build a manifest, and compress before upload — ScoutMyTool runs every step locally so borrower documents never cross a third-party server.
Open the PDF toolkit →