Content Central · mortgage lending
Content Central gathers every document that carries a loan number into that loan's packet, checks it against the document types each stage requires, and tells processing, closing and post-closing which loans are complete.
Three desks, three checklists
A packet template is a list of document types, each marked required or optional, tied together by one key field: the loan number. Make one template per stage. A document joins every template that lists its type, the moment it is filed with the loan number, and a new template picks up the documents already on file.
Processor
“What do I still need from this borrower?”
Pay stubs, W-2s, bank statements and the verification of employment arrive by email, upload and the branch scanner. The packet shows the file as Complete, or Incomplete with the missing document types named.
Submit to underwriting
Closer
“Is anything holding up the closing date?”
Title commitment, insurance binder and the Loan Estimate on file. A scheduled rule can email you about every loan whose closing checklist is still incomplete.
Clear to close
Post-closing and shipping
“Which files are still waiting on trailing documents?”
The recorded deed of trust and the final title policy come back weeks after closing. A scheduled report lists every loan still incomplete, so nothing ships short.
Ship to investor
What goes wrong today
The employer returns the verification of employment to the processor who requested it. She is out on Friday, and underwriting sends the file back as incomplete.
The loan closed and shipped. The recorded deed of trust came back from the county two months later and went in a tray. The investor asks for it.
Each processor keeps a stare-and-compare list in Excel. It is right on the day it is updated, and nobody else can see it.
Getting the loan number onto every page
The application, the Loan Estimate and the Closing Disclosure print the loan number. CapturePoint 6, at the branch scanner, splits a mixed stack, recognizes each document and reads its fields on that PC, then sends each one to Content Central with its values matched to your fields.
Pay stubs, W-2s and bank statements know nothing about your loan. Scan a borrower's stack in Content Central behind a packet separator sheet and type the loan number once; every document in the stack carries it. Anything that arrives without one waits in the Coding Queue until someone types it.
Content Central can watch a processing mailbox on Microsoft 365, Gmail or IMAP, file the attachments, and read the loan number out of the subject with a pattern you set.
A CapturePoint 6 mortgage job, for example
Document types a loan job can sort, and the fields it reads from each.
Point it at a folder of your own loan documents and it works out the document types and fields by itself, then learns from every correction. The free trial starts the first time you open it, with a 2-minute tour on sample documents.
A worked example
Day 1
Processor
The signed application and the Loan Estimate are scanned at the branch. CapturePoint 6 recognizes both and reads the loan number, so they join loan 26-04187 on their own. Three checklists now exist for the loan, and all three say Incomplete.
Days 2 to 6
Processor
The borrower emails pay stubs and bank statements to the processing mailbox with the loan number in the subject. Content Central reads the number from the subject line and files each attachment to the loan. The W-2s come in on paper, scanned behind a packet sheet with the loan number typed once.
Day 7
Workflow
A scheduled rule finds the underwriting checklist still incomplete after five days and emails the processor. The packet shows why: the verification of employment.
Day 9
Underwriting
The VOE arrives and the checklist turns Complete. That fires a rule that starts the underwriting approval on the whole packet: the underwriter sees every document, approves with a PIN, and the decision is in the audit trail.
Day 12
Processor
One condition: a letter of explanation for a large deposit. It goes to the borrower as a signature request by email. When she signs, the signed PDF is saved as a new version and, carrying the loan number, sits in the file.
Day 31
Post-closing
Closed. The Closing Disclosure and the note are scanned; the shipping checklist is waiting only on the recorded deed of trust and the final title policy. Every Monday the Incomplete Packets report lists this loan with the others still waiting.
Day 64
Post-closing
The recorded deed of trust comes back from the county and the file turns Complete. The packet is merged into one PDF and exported to the folder your delivery process picks up from.
Signatures are requested per document; a packet is not signed in one session. Your loan origination system stays your system of record for the loan itself; Content Central keeps the documents.
The rules behind the file
Federal minimums for a few of the records in a consumer mortgage file. Investors, servicing agreements and state rules often ask for longer; set each document type's schedule to the period your counsel approves.
ECOA / Regulation B
Application records
Generally 25 months after you notify the applicant of action taken
TILA / Regulation Z
Evidence of Loan Estimate compliance
Three years after consummation
TILA / Regulation Z
The Closing Disclosure and related documents
Five years after consummation
Your investors and your state
Everything else in the file
The period you set, per document type, with a hold that overrides it
For non-bank lenders and brokers, the FTC's Safeguards Rule asks for access controls, multi-factor authentication for anyone reaching customer information, and a record of what authorized users do. Banks and credit unions follow their regulators' guidelines to the same end. Content Central runs in the cloud or on your own servers and gives you the controls; your information security program decides how they are used.
In a free live demo we set up a loan number field, your underwriting and shipping checklists, and file a sample loan into them so you can see Complete and Incomplete on your own document types.
Since 2002, more than 1,000 organizations have used Ademero software. Fortune 500 companies and government agencies review our security every year.