What Is a DFS (Documents for Signing) and How to Automate It

The most tedious step in closing - and the easiest to automate.

← Back to Blog

If you have worked in mortgage brokering for any amount of time, you have assembled a DFS package. DFS stands for documents for signing - the disclosure forms, commitment letters, consent documents, and authorization forms that need client signatures before a deal can close.

It is also, without contest, one of the most time-consuming administrative steps in the entire mortgage process. And it does not need to be.

What a DFS Package Actually Is

A DFS package is the set of documents requiring client signatures at various stages of the mortgage process. These are the forms that get routed through DocuSign or printed for wet signatures - the legal paperwork that authorizes the deal to move forward.

Think of it as the signing layer of a deal. While the broader submission package includes income verification, property details, and supporting documents for the lender, the DFS is specifically the documents the client needs to review and sign.

Not every brokerage uses the exact term "DFS." Some call it the signing package, the disclosure package, or just "the docs." What matters is the function: a complete, organized set of documents routed for client signatures at the right time in the right order.

What Goes Into a Typical DFS Package

While the exact documents vary by lender, deal type, and province, most DFS packages include the following:

Disclosure Forms

Provincial disclosure documents that inform the borrower about the broker's role, compensation, and the terms of the relationship. These are legally required in most provinces and must be signed before the brokerage can act on the client's behalf.

Commitment Letters

The lender's formal offer outlining the approved mortgage terms - rate, term, amortization, conditions, and any fees. The borrower signs to accept the commitment and authorize the deal to proceed.

Consent and Authorization Forms

Privacy consent (PIPEDA), credit check authorization, third-party information sharing agreements, and any other forms that give the brokerage permission to collect, use, and share the borrower's personal information.

Rate Lock Agreements

If applicable, the document confirming the rate hold terms, expiry date, and any conditions attached to maintaining the locked rate.

Brokerage-Specific Forms

Many brokerages have their own internal forms: fee agreements, service acknowledgments, conflict of interest disclosures, or dual agency disclosures when applicable.

Closing Documents

Depending on the deal stage, the DFS may also include mortgage direction documents, insurance confirmations, or final authorization forms required before funding.

The DFS package often gets assembled alongside the broader submission file (income docs, property details, supporting documents for the lender), but the DFS itself is specifically the documents that need signatures.

Why It Takes 30 to 45 Minutes

On paper, assembling a DFS package looks straightforward. In practice, it is slow because of what happens between the steps.

  • Identifying which forms are needed. Different lenders require different disclosure forms. Provincial requirements vary. Deal type matters - a refinance package looks different from a purchase. Before you start assembling, you need to figure out exactly which documents this particular deal requires.
  • Populating borrower details. Every form needs the borrower's name, address, SIN, and deal-specific information filled in. Most brokerages do this manually - copying from the CRM into Word templates or PDF forms, field by field, tabbing between windows.
  • Cross-checking for accuracy. The borrower name on the disclosure form needs to match the commitment letter. The rate on the rate lock agreement needs to match the lender's terms. Every inconsistency that slips through gets flagged and costs more time downstream.
  • DocuSign preparation. Creating the signing envelope, uploading the right forms, mapping the signature and initial fields, setting the signing order, and testing that everything routes correctly. This is repetitive work that follows the same pattern every time but requires careful attention. If your document collection process is already messy, organizing the supporting docs that accompany the DFS makes everything slower.
  • Tracking signing status. Once the envelope goes out, someone needs to monitor who has signed, who has not, and follow up with borrowers who let it sit in their inbox for three days.

As we have explored before, a single DFS package taking 45 minutes is expensive enough. Multiply that across 15 to 20 deals a month, and you are looking at 10 to 15 hours of assembly time per broker.

What Can Actually Be Automated (and What Can't)

Not every step of the DFS workflow can or should be fully automated. Your team still needs to pull the deal data from your LOS (Velocity, Lendesk, Mortgage Automator, or wherever your deals live), select the right documents, and organize them into a folder. That part requires judgment: knowing which forms this specific lender requires, catching edge cases, and making sure the file is complete.

Where automation makes a real difference is what happens after your team has the documents ready:

  1. DocuSign envelope creation. Instead of manually uploading forms, mapping every signature and initial field, setting the signing order, and configuring the routing, automation builds the envelope from your prepared documents. Fields are pre-mapped, signing order is set, and the envelope is ready for review in minutes instead of 15 to 20.
  2. Client email generation. When your team compiles the signing package with instructions, automation generates the client-facing email: a clear, professional message explaining what they are signing, why, and what to do next. No more rewriting the same explanatory email for every deal.
  3. Review and send. The broker or assistant reviews the DocuSign draft and the email, makes any adjustments, and hits send. The assembly is done. The writing is done. You are just checking the work.

The result is not a fully hands-off process. Your team still does the prep work. But the most tedious, repetitive parts - building the DocuSign envelope from scratch and writing the same client email every time - are handled. When even a single automation can save 15 minutes per deal, cutting the DocuSign and email steps alone can recover hours every week.

Why the DocuSign Step Is Worth Automating First

Most brokerage automations handle a single communication: an email, a notification, a reminder. DFS automation sits at the intersection of document handling and client communication, which makes it higher value but also more specific to your workflow.

What makes it work well:

  • Template reuse. Most brokerages use the same set of forms for 80 to 90% of their deals. Once the DocuSign templates are built with pre-mapped fields and signing order, every new deal reuses that structure. Your team swaps in the deal-specific documents and the envelope is ready.
  • Consistent client communication. The email that accompanies the signing package follows the same pattern every time. Automating the draft means every client gets a clear, professional message without someone rewriting it from scratch.
  • Human-in-the-loop review. Your team still reviews the envelope and the email before anything goes to the client. The goal is to eliminate the assembly and writing, not to remove the broker from the process.

The Prep Work Still Matters

The DFS workflow will always require someone who knows the deal to pull the right documents and organize the file. That is skilled work and it should stay with your team. What should not stay with your team is the 15 to 20 minutes of DocuSign envelope building and email drafting that follows the same pattern every single time.

Automate the repetitive tail end. Keep the judgment where it belongs.

Automate the DocuSign Step

LendFrame builds your DocuSign envelopes and drafts the client email from your prepared deal documents. Your team preps the file. We handle the rest.

See DFS Package Automation