The 1003, and every
document, in order.
A real URLA that knows what it’s missing, document requests that chase themselves, and uploads that are checked by their actual bytes — not just their file name.
A 1003 that knows what’s missing
All nine sections, co-borrower aware. Fields already on the loan are read through to one canonical home, so a borrower’s income is never stored in two places that can disagree.
- Live completeness % with the actual missing fields named
- Solo files never ask for co-borrower data
- Itemized liabilities feed DTI — one source of truth
A "yes" becomes a real to-do
Answer a declaration "yes" and Mars produces the follow-up — a bankruptcy asks for the discharge papers, a judgment for the payoff — and turns it into a condition on the file in one click.
- Follow-ups namespaced per borrower and co-borrower
- One click turns them into tracked conditions
- Nothing relies on someone remembering
Checked by their bytes, not their name
An executable renamed invoice.pdf is refused. Files are stored under random names — the borrower’s filename never touches the disk — and served back sandboxed so nothing runs in your browser.
- Type allowlist plus magic-byte sniffing
- Random stored names; 25 MB cap with a real error
- Downloads are attachment-only with a sandbox CSP
Send a title company two files, not the file
A read-only link that names only the documents you pick. The token lives in the URL fragment, so it never reaches a server log; it can carry an access code and an expiry, and you can revoke it.
- Only the documents you name are visible
- Outsiders see "Provided" / "Waiting on it", not your states
- Optional access code, expiry, and one-click revoke
See it on your own files this afternoon
Start free — no card. Import with MISMO 3.4, invite your team, send your first application link.