By the time a file reaches submission, every number inside GDS and TDS should be traceable to a document: a pay stub or Notice of Assessment for income, a tax bill or written estimate methodology for property tax, an actual utility record or a stated estimate basis for heat, a condo fee statement, and a bureau printout for every debt included or excluded. An underwriter who has to ask where a number came from is an underwriter whose decision just got slower — and on a tight file, slower often means more scrutiny, not less.
This is especially true for any number that required judgement rather than a simple lookup — an estimated heat cost, a co-signed debt you excluded based on payment history, a rental offset you calculated using a particular method. Write down the reasoning at the time you calculate it, while it is fresh, rather than trying to reconstruct it later if a question comes back.
A tight file invites scrutiny by definition — the underwriter's job is to be more skeptical the closer a file sits to the ceiling. The most useful thing a broker can do is read their own file the way the underwriter will and answer the obvious follow-up question before it is asked: why is this heat estimate what it is, why was this debt excluded, why does the down payment allocation look the way it does.
This is the same discipline Course 01 frames as the core of what a broker adds to a file — arriving with nothing left to discover. A ratio calculation that is technically correct but unexplained still generates a request for clarification; the same calculation with a one-line rationale attached often does not.
A short, plain paragraph at the top of the submission — stating the calculated GDS and TDS, which ceiling applies given the borrower's credit band, and which lever (if any) was applied to get there — turns a wall of numbers into a narrative an underwriter can follow in one read. Something like: 'GDS 36.2%, TDS 43.1% against a 39/44 ceiling supported by a 705 credit score; borrower is applying $8,000 of available cash to retire a line of credit prior to closing, reflected in the TDS figure above.'
Course 20, Submission Notes & Lender Relationships, develops this skill in full across every part of a file, not just the ratios — worth taking alongside or after this course if submission quality is a gap for you.
Before sending a tight file, confirm: the qualifying rate used matches the correct rule for this transaction type (Module 04); every debt on the bureau is either included or excluded with a documented reason (Module 03); heat and tax figures are based on real records or a stated, defensible estimate method (Module 02); the applicable ceiling reflects the borrower's actual credit band, not an assumed one (Module 05); and any lever applied — paydown, amortization, guarantor — is reflected consistently in both the numbers and the cover note.
Why does a well-documented tight file typically move faster through underwriting than an undocumented one with the same numbers?
Tight files draw more scrutiny by nature, and every unanswered question becomes a request for clarification that adds a round trip to the timeline. Pre-empting those questions with documentation and a clear rationale is what actually saves time — it does not mean the underwriter skips verification, which is the tempting but wrong idea in one of the distractor answers. Documentation is not merely a formality either; on a marginal file it can be the difference in how much scrutiny the rest of the file receives.
Lender policies change without notice. Confirm current guidelines directly with the lender or insurer before relying on them for a live file.
The intro and first module are free to read. Add your name and email once and the rest of this course opens — along with every other course on the site. No card, no trial.
Already unlocked on another device?
