Category: Encompass® Notes, Updates, and Best Practices

  • Your Workflow Sets the Pace

    Strong technology doesn’t automatically create strong operations, no matter how many AI features are added to the conversation. Encompass® is a powerful platform across both desktop and web environments, but technology alone does not determine performance.

    Your workflow sets the pace. Encompass simply follows it.

    Across Encompass desktop and web, workflow decisions shape how efficiently teams function, how reliably data moves, and how confident users feel day to day. When nothing is clearly defined, even experienced teams end up relying on workarounds, manual checks, and inconsistent processes. The system may technically function, but it doesn’t operate with clarity or consistency.

    The people closest to the work usually see process problems first. Processors notice when a file requires extra steps that no one can explain. Ops leaders see delays that repeat but never quite get resolved. LOS managers recognize when settings conflict or when users stop trusting automation. When teams rely on manual workarounds, outdated steps, or inconsistent Encompass setups, daily tasks take longer and errors become harder to avoid.

    High loan volume combined with limited support only adds pressure. Processors are asked to move faster. Administrators are asked to adjust configurations quickly. Operations leaders are expected to maintain accuracy and throughput at the same time. Without a clear structure, that pressure compounds and frustration increases.

    Over time, small inefficiencies become cultural norms. Teams adapt instead of improving. New hires are trained on how to work around the system instead of how to work within it. Automation exists, but users don’t fully trust it. Reporting exists, but leadership questions whether it reflects reality. And all of this is not a technology issue.

    When we work with teams, Mortgage Workflow Partners starts by understanding how your teams actually work from initial contact through final accounting. We don’t begin with assumptions about how the platform should function. We begin with the lived experience of your users. By documenting how work is truly done, we translate that reality into practical, usable workflows that support accuracy, consistency, and scale.

    The focus stays on clarity, repeatability, and support that helps teams work more confidently inside the platform. When expectations are clearly defined and steps are aligned across roles, users stop relying on memory and manual checks. Administrators gain confidence in making changes. Leadership gains better visibility into performance and capacity.

    For internal champions driving improvement, this transparency matters. You know where it breaks. You see the bottlenecks. You understand which steps slow the team down. But advocating for change is difficult without structure and documentation to support it. Clear workflows and reliable guidance make it easier to move conversations from frustration to solution.

    Whether you’re addressing backlog, preparing for growth, or relieving overwhelmed admins and users, the right workflow gives Encompass the structure it needs to perform. It allows automation to function as intended. It allows data to move consistently. It allows teams to operate with confidence instead of caution.

    When workflow is intentional, time is used more productively. Errors become easier to prevent. Scaling becomes more controlled. And performance becomes more predictable.

    Technology will continue to evolve. Volume will fluctuate. Platform updates will continue. Those variables will always exist. But what determines how well your organization handles them is the structure underneath.

    Your workflow sets the pace. Make sure it’s setting the right one. Contact us and bring clarity back to your Encompass workflow.

  • 2026 Is a Workflow Year

    As 2026 begins, mortgage teams are already under pressure from several fronts. Resources are tight. Encompass® Web is becoming a larger part of platform planning. Automation expectations are rising. Operational decisions are receiving more scrutiny.

    And none of these pressures operate independently.

    In this environment, the way work moves through Encompass has a direct impact on consistency, throughput, and control. Workflows aren’t just an operational detail. It determines how predictable your outcomes are. When processes are unclear or outdated, small inefficiencies compound quickly across teams and pipelines. What feels manageable at the individual level becomes measurable at scale.

    A processor adds a manual check because trust in a rule is low. An underwriter waits for clarification because task ownership is unclear. An administrator hesitates to update a setting because no one remembers why it was built that way in the first place.

    Over time, these moments create drag.

    For your team to take a more deliberate approach in 2026, you need to be reviewing how loans flow from intake through closing. That means documenting what actually happens day to day, not what was originally designed during implementation. It means identifying where handoffs create delay, where automation is layered onto inconsistent processes, and where web and desktop workflows may not align.

    You may assume your workflow is stable because loans are still closing. But surviving to the next day and optimizing to make things more productive are not the same thing. If team members rely on workarounds, historical knowledge, or repetitive manual steps to get the job done, the system is functioning, but not operating at its full potential.

    Deliberate workflow evaluation brings clarity to:

    – Where time and effort are being lost and where you can be more productive

    – Where compliance exposure may be increasing and controls are inconsistent

    – Where automation will truly create lift and where it may amplify confusion

    – How Encompass Web fits into long-term platform planning

    Mortgage Workflow Partners helps teams examine their workflows at this level. We work directly with the people inside the process to capture how work is actually performed. From there, we identify friction points and design processes that support stability and growth without adding unnecessary tools or complexity.

    The objective is not to introduce more technology. It’s to strengthen how Encompass scales with your business.

    When workflow is intentional, automation becomes safer to implement. Administrative decisions become clearer. Leadership gains confidence in operational reporting. And teams spend less time compensating for process gaps.

    2026 will continue to bring platform updates, compliance changes, and market shifts. Those variables are outside your control. How work moves through your system is not.

    Make 2026 your workflow year. Contact us and start building a stronger, more intentional workflow strategy.

  • Preparing Encompass® for What’s Next

    Encompass® continues to evolve rapidly, from infrastructure migrations to deeper automation and API-driven workflows. These changes create opportunities for efficiency, but they also introduce risk if teams are not clear on how their environment is configured and how their data is controlled.

    In a recent Ask Me Anything Encompass® | Admins & Users workshop, several critical themes surfaced that apply broadly across organizations: preparing for AWS migration, understanding connectivity behavior, protecting automation-driven data, and redefining when key compliance milestones truly begin.

    Here’s what matters most.


    Preparing for the AWS Migration

    Many Encompass® environments are transitioning from legacy data centers to AWS infrastructure. While the migration is designed to improve scalability and performance, it also introduces new dependencies that teams must plan for.

    Understanding where your Encompass® instance is hosted is the first step. Using tools like traceroute and ping allows admins to identify whether their instance resides in a traditional data center or an AWS environment. This information becomes essential when troubleshooting connectivity issues or validating performance changes after migration.

    More importantly, migration affects integrations. EPC connections, third-party services, and allow-listed domains may require updates. Integration partners often rely on instance-specific identifiers, which can change during migration.

    The takeaway is simple: migration itself is not the risk. Lack of preparation is.


    Connectivity Issues Are Often Local, Not Platform-Wide

    When users experience disconnects or slow performance, the instinct is to blame the platform. In reality, connectivity issues frequently originate from local network infrastructure.

    Traceroute and ping diagnostics help determine whether packets are reaching Encompass® reliably. If there is no packet loss and responses remain consistent, the issue is rarely the Encompass® server.

    Instead, focus on:

    • Wireless hubs and network switches
    • VPN routing configurations
    • Hardware interface cards
    • Local network congestion

    Identifying whether issues are isolated to a location or user group provides clarity and prevents unnecessary escalation.

    Understanding how to validate connectivity empowers admins to distinguish between platform issues and infrastructure issues.


    Automation Requires Clear Data Ownership

    As Encompass® continues expanding its automation capabilities, especially through APIs and third-party integrations, data ownership becomes critical.

    Automation can populate values such as income, assets, appraised values, and employment data directly into loan files. Without clear workflow controls, users can overwrite that data unintentionally.

    This creates two risks:

    1. Loss of reliable automation output
    2. Paying for third-party data services that are never actually used

    Organizations that operate efficiently define ownership at the field level. When trusted automation populates a value, business rules prevent unnecessary manual edits. Underwriters review decisions rather than re-entering data.

    Automation only creates value when workflows protect its integrity.


    Automation Should Replace Work, Not Create Duplicate Work

    Many organizations invest heavily in verification tools, income analysis platforms, and asset validation services. However, those same organizations often continue reviewing and overriding the automated results.

    This creates a paradox. The organization pays for automation but continues operating manually.

    Efficient workflows treat trusted automation as the primary source of truth. Once data is validated through trusted providers and underwriting logic, the workflow progresses forward without redundant verification.

    The result is faster processing, lower operational cost, and greater consistency.

    Workflow clarity determines whether automation reduces effort or simply adds expense.


    Redefining Application Timing in Wholesale Workflows

    Wholesale lending introduces unique workflow timing challenges. Brokers can upload loan files into TPO Connect before the lender formally accepts responsibility for the loan.

    From a compliance and workflow perspective, the critical milestone is not when the broker uploads the file. It is when the lender accepts the file.

    Many organizations establish an internal “Accepted” milestone or field that marks when the lender takes ownership. This milestone becomes the trigger for disclosure timing, workflow automation, and reporting timelines.

    This distinction protects compliance accuracy while ensuring workflows align with operational reality.


    Security and Authentication Behavior Can Affect User Experience

    Features like Single Sign-On and one-time passcodes improve security, but they also introduce testing and usability considerations.

    SSO mappings connect directly to specific user identities, making testing difficult without alternative login methods. Similarly, mobile browser privacy protections, especially on iOS devices, can block cross-site tracking required for certain Encompass® features.

    In these cases, guiding borrowers toward secure mobile apps or configuring alternative login methods improves reliability.

    Security controls must be implemented alongside workflow design that supports real users.


    Workflow Before Technology®

    The most efficient Encompass® environments do not rely on more tools. They rely on clearer workflows.

    Successful organizations:

    • Define ownership of critical data fields
    • Lock automated values when appropriate
    • Align milestones with operational responsibility
    • Prepare proactively for infrastructure changes
    • Treat automation as part of workflow, not a separate layer

    Technology amplifies workflow. It does not replace it.


    Join Us Live

    This article was inspired by our February 17 Ask Me Anything Encompass® | Admins & Users workshop, where AWS migration, automation, and workflow integrity questions surfaced across teams.

    🎥 Watch the replay or join a live workshop at MasteringEncompass.com

    Mortgage Workflow Partners Inc. Helping lenders simplify, standardize, and scale their Encompass® workflows.

  • Optimizing Encompass®: Conditions, Fields, and TPO

    Encompass® configuration decisions compound over time. What starts as a small workaround in TPO Connect, a complex Word merge, or an unclear condition setting can quietly create friction across underwriting, disclosures, and funding.

    When workflows feel inconsistent, the issue is rarely the platform itself. More often, it comes down to structure, clarity, and understanding how Encompass® separates roles, documents, conditions, and automation.

    In a recent Ask Me Anything Encompass® | Admins & Users workshop, several recurring themes surfaced that are worth unpacking more broadly: TPO notification limitations, smarter custom field strategies, enhanced condition configuration, and the difference between document tracking and condition tracking.

    Here’s what matters most.


    TPO Connect Notifications and Role Limitations

    One of the first questions focused on sending notification templates to a delegated TPO contact.

    The challenge: internal notification templates do not easily fetch email addresses from externally mapped TPO contacts unless they are hard-coded in the original configuration. While standard TPO Loan Officer and Loan Processor roles work as expected, newly created delegated roles may not behave the same way.

    The core takeaway is this: Encompass® distinguishes between internal and external users at the database level. Assigning a role in TPO Connect does not guarantee that notification templates can retrieve that email address.

    When native functionality does not support the use case, lenders often rely on:

    • Updating mapped email fields dynamically through business rules
    • Using external automation tools
    • Submitting enhancement requests directly to ICE

    Understanding the boundary between what Encompass® was designed to do and what it can be extended to do saves hours of troubleshooting.


    Custom Fields vs Word Merge Logic

    Another discussion revisited Word merge complexity and how to simplify conditional language in custom print forms.

    Instead of embedding complicated merge code inside Word documents, the recommended approach is to:

    1. Create a custom field
    2. Use a nested IF statement inside the field calculation
    3. Output the final formatted string
    4. Merge that single field into the document

    This method improves:

    • Testing
    • Debugging
    • Visibility on input forms
    • Long-term maintainability

    For example, combining borrower and co-borrower names conditionally can be handled entirely in a custom field calculation rather than layered merge code.

    When working with numeric values, remember:

    • Use Integer field types when you do not want decimals
    • Decimal format settings only limit display, they do not change field behavior

    Small structural decisions make long-term document management significantly easier.


    Enhanced Conditions: Clearing, Roles, and UI Confusion

    Enhanced Conditions sparked several important clarifications.

    First, condition status behavior:

    • If the Cleared box is checked in settings, that role is allowed to mark conditions as cleared
    • If it is unchecked, they cannot
    • Roles are controlled at the condition type level, not within the individual condition

    Second, a reminder about role-based behavior: Condition permissions are tied to job roles, not specific users. If a role does not exist in the milestone template, the system can still apply its settings depending on configuration.

    Third, troubleshooting status issues: If a condition appears cleared but the UI does not update properly, test the behavior in Encompass® Web and export a HAR file. This captures the backend activity and gives ICE support concrete data to review.


    Moving from Standard to Enhanced Conditions

    A major theme was migration hesitation.

    The Condition Migration Tool allows lenders to move from Standard Conditions to Enhanced Conditions quickly. The most common mistake is trying to clean up and reorganize every condition before migrating.

    Do not over-engineer the move.

    Instead:

    • Migrate first
    • Activate only what you need
    • Refine condition types afterward

    Trying to perfect your taxonomy before transitioning often delays projects indefinitely.


    Condition Workflow vs Document Workflow

    One of the most important distinctions of the workshop was this:

    Documents are not conditions. Conditions are not documents.

    Documents represent files received. Conditions represent underwriting requirements.

    An optimized workflow looks like this:

    • Documents are marked received in eFolder
    • Corresponding conditions are marked fulfilled
    • Underwriters review from the Conditions tab using filtered views

    This prevents underwriters from digging through File Manager unnecessarily and keeps reviews structured and intentional.

    Using clear terminology such as Fulfilled instead of Received reduces confusion between document tracking and condition tracking.


    Web Behavior and Custom Field Calculations

    A final reminder covered Encompass® Web behavior.

    Custom field calculations in Web do not refresh dynamically while moving between fields. They update on Save. This is working as currently designed.

    If behavior seems inconsistent:

    • Confirm in Web
    • Capture a HAR file
    • Submit through support with backend evidence

    Understanding the platform’s intended behavior prevents chasing problems that are not actually defects.


    Join Us Live

    This article was inspired by our February 3 Ask Me Anything Encompass | Admins & Users workshop.

    Each workshop is open to anyone using Encompass®, whether you manage personas, build rules, configure TPO, or support operations.

    🎥 Watch the replay or join a live workshop at MasteringEncompass.com

    Mortgage Workflow Partners Inc. Helping lenders simplify, standardize, and scale their Encompass® workflows.

  • Ask Me Anything Encompass®: Troubleshooting Forms, Rules, and Readiness

    The latest Ask Me Anything Encompass® workshop brought another round of real screens, real questions, and real solutions. Designed for anyone using Encompass®, these sessions create space to troubleshoot live, share best practices, and strengthen workflows that keep lenders moving.

    This week’s discussion covered everything from Microsoft Word printing errors and EDS configuration to enhanced conditions, workflow rules, and web readiness. Each topic reminded admins why “workflow before technology” continues to drive lasting efficiency.


    When Word and Encompass® Don’t Agree

    The call began with troubleshooting custom print forms that suddenly stopped working after a Microsoft Word update. The takeaway was simple but critical: if printing works in Test but not Production, the environment setup is likely misaligned. Running “remove UAC” and reinstalling DLLs often resolves the issue.

    Even when technical errors seem isolated, updates to Word or local permissions can ripple through multiple users, especially when Encompass® was open during the update. Always start by comparing Word versions and testing the same form in both environments.


    Removing Signature Lines the Smart Way

    Another question focused on removing an underwriter’s signature line from the Statement of Denial form. The quick fix: leave the Denial.X70 field blank before printing. This prevents the signature line from generating, eliminating the need for an EDS request.

    Small details like this highlight why understanding merge codes and field relationships can prevent unnecessary support cases.


    Enhanced Conditions and Workflow Rules

    Enhanced Conditions were a major focus again, especially how to apply, waive, or automate them through workflow rules. The key reminder:

    • To remove conditions, do not delete them. Waive them instead.
    • Deleting conditions removes traceability, while waiving maintains audit and compliance integrity.

    Admins also explored how to build workflow rules that apply Enhanced Conditions based on triggers like loan type changes or program updates. Each trigger should match a single, clear outcome; separate complex logic into multiple smaller rules for easier tracking and debugging.


    Automation and Logging Best Practices

    Discussions around automation emphasized balance. Workflow automation should clarify actions, not hide them. When conditions update automatically, document why. Adding a log note or workflow task (“Loan Type Changed – Conditions Updated”) helps future users understand what happened without sifting through rules.

    Notification Templates also came up. They can’t include conditional logic inside the email itself, but conditional delivery can be controlled through workflow rules. Keep calculations and merge logic in custom fields, then pull those fields into the template.


    Keeping Homepages and Whiteboards Clean

    Some users reported gray or frozen login screens in Encompass® Desktop. The culprit was often HTML formatting inside the Admin Whiteboard or too many homepage modules. The solution:

    • Keep Admin Whiteboard content as plain text.
    • Disable unnecessary homepage modules in Personas.
    • Verify that users meet minimum system requirements (at least 16 GB RAM).

    Simple cleanups like this can dramatically reduce crashes or blank screens.


    Looking Ahead

    This Ask Me Anything Encompass® workshop reinforced why collaboration matters most, because no two lenders use Encompass® exactly the same way. Every shared challenge helps others strengthen their workflows, and every question creates space for smarter automation and better user experiences.


    Join Us Live

    This article was inspired by our January 20 Mastering Encompass®: Ask Me Anything Encompass® Workshop.

    ✅ Join the next session live and bring your toughest Encompass® questions to the screen. 👉 Watch replays and upcoming workshops at MasteringEncompass.com

    Mortgage Workflow Partners Inc. Helping lenders simplify, standardize, and scale their Encompass® workflows.

  • Ask Me Anything Encompass®: Kicking Off 2026

    The first Ask Me Anything workshop of 2026 kicked off the year with real screens, real questions, and real solutions. This session covered everything from milestone automation and HMDA logic to disclosure timing, New Doc Viewer, and funding readiness.

    It was the perfect reminder that no matter how the platform evolves, the foundation stays the same: workflow before technology.


    Rethinking Milestones and HMDA Automation

    Many lenders still rely on milestone completion rules to trigger HMDA updates, especially for withdrawn or denied files. The issue is that field 1393, the HMDA action taken field, should only be updated when ownership of the loan is clear.

    Instead of automating from a milestone alone, consider tying the update to a workflow event or creating a task that requires underwriter review. This ensures accuracy and keeps control in the right hands while preventing compliance issues caused by premature automation.


    Building Confidence in Workflow Logic

    Workflow uncertainty often starts with missing documentation. Teams know what they think happens but not what actually happens. Defining each step, who triggers what, when, and why, creates a blueprint for consistency.

    Whether it is a loan denial or funding readiness, the fix is the same: document your process. If no one can explain how a file moves from one milestone to another, the workflow isn’t ready for automation.


    Making the Move to Enhanced Conditions and New Doc Viewer

    As more lenders migrate to Encompass® Web, New Doc Viewer continues to be a turning point. Admins reported faster processing, better document control, and fewer versioning issues once teams learned the right way to edit and search documents.

    The biggest adjustment? Users must select a single document to edit or rearrange thumbnails, not multiple at once. It sounds small, but this simple detail is the difference between frustration and efficiency.

    New Doc Viewer also introduces searchable PDFs across Encompass Web and Desktop. For underwriters, that means instantly finding “subject to” in an appraisal or spotting hidden transactions like “Affirm” or “Afterpay” within bank statements.


    Compliance and the 3-Day Disclosure Rule

    Disclosure timing remains one of the most common compliance questions. The rule isn’t just about sending the Loan Estimate. It is about confirming borrower receipt within three business days, and that starts with eConsent.

    If eConsent isn’t completed before disclosures are sent, the file isn’t compliant until receipt is confirmed. The fix is simple: use scheduler-based workflow tasks. When an initial disclosure event occurs, create a two-day reminder task. If the borrower hasn’t viewed or signed by day three, the system can alert the disclosure desk to mail the package manually.

    It’s a practical way to track compliance without relying on manual follow-up or endless reports.


    Improving Funding Readiness

    Funding errors, like loans funded before they are ready, often come down to incomplete readiness checks. Rebuilding the funding process begins with clarity: what fields, documents, and approvals define a “ready to fund” loan?

    Creating a Funding Readiness form inside Encompass® lets teams confirm every field is complete before funding approval. Adding scheduler-driven workflow tasks can automatically alert funders and managers when a loan is due for review, keeping visibility across the pipeline and preventing last-minute surprises.


    Tracking and Prioritizing Tasks That Matter

    Workflow Tasks and Schedulers are more than reminders. When used together, they create structure across departments, from appraisal follow-ups to re-submissions and funding approvals.

    Dynamic due dates and priority rules let Encompass® automatically reorder what needs attention first. For example, an appraisal task due in ten days can automatically move up in priority as the closing date approaches. The result is a live, organized view of your true daily workload.


    Join Us Live

    This article was inspired by our January 6 Ask Me Anything Encompass® Workshop

    Join future sessions to see how admins and users are solving real Encompass issues in real time.

    ✅ Watch past and upcoming workshops at MasteringEncompass.com

    Mortgage Workflow Partners Inc. Helping lenders simplify, standardize, and scale their Encompass® workflows. MortgageWorkflowPartners.com

  • What Questions Are Coming Up in Encompass®?

    The final Ask Me Anything workshop of 2025 wrapped up with an hour of real screens, real questions, and real solutions, covering everything from SSO confusion to workflow task design and reporting.

    Each session reminds us how much power Encompass® admins have when the tools are configured for clarity, not chaos. This one was packed with insights that hit across setup, security, and workflow management.


    Connecting Systems with Single Sign-On

    One of the first questions centered around using Single Sign-On (SSO) for Encompass Consumer Connect®. Lenders wanted to know how to connect their online banking systems so borrowers don’t need separate credentials.

    The answer: integration depends on your online banking provider. For many, vendors like Q2 can bridge systems through Encompass Consumer Connect, allowing borrowers to log in once and move seamlessly into their loan application. The result is a cleaner borrower experience and one less password to manage.


    Understanding Conditional Workflow Tasks

    Another major discussion focused on conditional workflow tasks and how to make them dynamic instead of static checklists.

    Tasks can now be fired by workflow rules and adjusted automatically based on loan type, milestone, or other field criteria. That means instead of managing hundreds of static checklists, you can use templates that adapt automatically.

    It’s one of the most powerful native Encompass features for tracking actions, not just documents. As Larry noted, “A workflow task captures intent, what needs to be done, who needs to do it, and when.”


    From Checklists to True Workflow Management

    Admins discussed moving away from static desktop checklists to the web-based workflow task system. While the transition can feel unfamiliar, it’s where visibility and accountability improve.

    Each workflow task can include subtasks, comments, and conditional due dates, all visible in the web interface. Once the “View All Tasks” feature becomes available, teams will be able to track task status across the entire pipeline. That shift turns Encompass into a living workflow tool instead of just a record-keeping system.


    Enhanced Conditions and Post-Closing Visibility

    The group revisited Enhanced Conditions, with admins sharing strategies for combining them with workflow tasks to manage post-closing and funding milestones. Pairing these two systems gives lenders real-time visibility into what’s missing, what’s waiting, and what’s complete without switching between spreadsheets and Outlook reminders.


    Reporting and Future Analytics

    Several admins asked when workflow task data will become reportable. ICE has confirmed that Encompass Analytics will eventually support these metrics, allowing visibility into open tasks, due dates, and user activity directly through dashboards.

    Until then, teams can use the task view inside Encompass Web to monitor activity and progress at the loan level.


    Practical Advice for Change Management

    A key takeaway: adoption starts small. Introduce workflow tasks to one team or one pain point first. When others see how much it simplifies their day, the momentum grows naturally.

    As Larry put it, “There’s always one person in your company who’s in enough pain that this is a godsend. Let them use it first, then watch everyone else follow.”


    Looking Ahead

    This session wrapped up the final Mastering Encompass®: Ask Me Anything workshop of the year, closing out a full calendar of live, interactive problem-solving sessions across the platform.

    Thank you to everyone who joined us throughout 2025.
    Have a wonderful holiday season, and we’ll see you in the new year for more Ask Me Anything sessions in 2026.

    Watch this and all previous workshops anytime at MasteringEncompass.com.

    Mortgage Workflow Partners Inc.
    Helping lenders simplify, standardize, and scale their Encompass® workflows.
    MortgageWorkflowPartners.com

  • Ask Me Anything: Real Encompass® Questions, Real Admin Solutions

    Every Encompass® admin has moments of feeling stuck, alone with a screen full of error codes, unclear communication, and constant updates that never seem to stop. That’s exactly why the Ask Me Anything workshops were created.

    During these live sessions, admins bring their toughest real-world challenges and get answers that go beyond theory. It’s not about rehearsed demos or polished slides. It’s about solving problems in real time, on real screens, with real people who face the same daily hurdles.

    This session covered a wide range of topics, from EPC credential confusion and AUS setup to workflow tasks, enhanced conditions, and how to move forward when test environments feel impossible to maintain.


    Clearing Up the EPC Confusion

    A recurring theme was credential management inside EPC versus Services Password Management. Many admins are still unclear about where to store credentials and when to use which system.

    The key takeaway: every lender should now be creating vendor services directly within EPC. Credentials stored in both systems can conflict, and leaving old configurations active in Services Password Management can cause unexpected breakage.

    It’s not just about following rules. It’s about avoiding downtime. As Encompass transitions away from SDK connections, keeping credentials current inside EPC ensures smoother integrations and fewer login failures across the board.


    Understanding Dual AUS and the “Both” Problem

    Dual AUS setup remains one of the most misunderstood areas. Many users still rely on hybrid configurations that use both EPC and the older password management paths. For now, running both remains the most reliable option, but it’s temporary.

    When in doubt, confirm that credentials are stored consistently for both DU and LPA, and verify persona or user assignments inside EPC. Small misalignments here often create large workflow interruptions later.


    Moving from Conditions to Tasks

    Several admins discussed how to bridge the gap between conditions, documents, and workflow tasks, especially in post-closing. The message was simple: start where the most repetition exists.

    Post-closing is one of the best areas to pilot workflow tasks because every missing document or trailing item can be tracked dynamically. Subtasks can be tied to milestone requirements, giving teams visibility into what’s done, what’s missing, and what’s waiting for review, all without manual checklists or spreadsheets.

    Workflow tasks create accountability and automation at the same time. They surface only what needs attention when it needs attention, reducing clutter and preventing duplicate work.


    Enhanced Conditions and Document Management

    Enhanced Conditions continue to offer better tracking and automation compared to standard setups, but many lenders hesitate to make the leap. The biggest barrier is complexity, deciding which conditions belong to which type.

    A practical way forward is to export all standard conditions and have underwriting identify which ones can only be cleared by them. Those become your underwriting condition types. Repeat the process for closing, funding, and QC. Start simple and expand over time.

    Pairing Enhanced Conditions with New Doc Viewer can dramatically improve document control, allowing teams to split, rename, and prepare closing packages without duplicate uploads.


    Personas, Testing, and Change Control

    Testing environments often fall out of sync with production, making admins reluctant to use them. ICE is working on a web-based settings comparison tool to help identify mismatches between environments, but until then, cautious development in production is often necessary.

    For persona management, remember that a persona represents a job function, not a department. Use settings reports to validate what each role should access, and review them with the business for confirmation. If your personas have drifted, start small with one role at a time and reestablish boundaries before new workflows roll out.


    Why Workflow Tasks Matter

    Workflow tasks are not just another checklist. They’re a way to capture intent: what needs to be done, who needs to do it, and when. Unlike static checklists, workflow tasks only appear when relevant and disappear when complete.

    That visibility drives accountability and helps every team member focus on what matters most. The goal is to stop managing lists and start managing action.


    Join Us Live

    This article was inspired by our December 2 Mastering Encompass® Community Call, “Ask Me Anything – Admin Workshop.”

    Have an Encompass® question you want solved? Be there for the next AMA on December 16 @ 4 pm ET.

    👉 Join the community and watch replays at MasteringEncompass.com

    Mortgage Workflow Partners Inc. Helping lenders simplify, standardize, and scale their Encompass® workflows. MortgageWorkflowPartners.com

  • Dollars & Data: Loan-Level Profitability & Analytics

    Every lender knows the importance of generating revenue, but few have a clear picture of what it truly costs to produce each loan.
    Loan-level profitability isn’t just about the bottom line; it’s about understanding where your money is going and why.

    Tracking those numbers accurately reveals how decisions, inefficiencies, and unmeasured costs impact your company’s overall performance. The key is to build workflows that capture not just loan revenue, but the real cost of producing it.


    1. Know What to Measure

    Most lenders can calculate total company profit, but few can calculate profit per loan.
    That’s because accounting systems often track payments and revenue but not how those dollars tie back to individual files.

    Loan-level accounting starts by associating every invoice, fee, and payout with a loan number. Without that reference point, your reporting will always fall short.
    If your vendors don’t include loan numbers on invoices, make that a requirement. It’s one of the simplest ways to uncover where money leaks are happening.


    2. Count the True Cost of a Loan

    It’s not enough to know how much you earned on a file. You need to know what you spent.

    That includes:

    • Service and verification fees
    • Loan officer commissions
    • Extensions, cures, and refunds
    • Human time spent touching the file

    Few lenders track the human cost of production, including salaries, touches, and delays that add up quickly.
    Without that, you’re missing one of the largest drivers of profitability loss.


    3. Eliminate Invisible Expenses

    One of the biggest money drains in mortgage operations is hidden in plain sight: inefficient vendor workflows.

    A single invoice without a loan number, a delayed trailing doc, or an unnecessary overnight delivery can quietly drain thousands every month.
    Even automated systems come with a price. For instance, mailing initial disclosures through fulfillment might seem like a fixed $10 per package, but when you factor in review time, return postage, and processing, the actual cost can triple.

    Audit those small processes. They’re often the difference between profit and loss.


    4. Track Concessions and Credits Separately

    Concessions, lender credits, and pricing adjustments are real dollars leaving your bottom line.
    If they’re not tracked correctly, they disappear from view and distort profitability reporting.

    Distinguish between:

    • Pricing concessions given to stay competitive
    • Operational mistakes that required a cure
    • Sales credits issued to retain a borrower

    Each one affects your accounting differently. Remove or combine them, and you lose visibility into why money left the file in the first place.


    5. Map the Cost of Time

    Every extra touch adds up.

    If an underwriter reviews a file five times instead of two, or a processor reworks conditions three times before submission, that time has a cost.
    You don’t need to calculate down to the minute, but you do need to understand the relationship between touches and expense.

    Start by tracking the number of times each role interacts with a file. Over time, you’ll identify patterns and opportunities to reduce unnecessary touches.


    6. Use Workflow Tasks to Prevent Revenue Loss

    Workflow tasks aren’t just operational tools; they’re financial safeguards.

    In post-closing, for example, missing a trailing document can trigger investor penalties.
    A recurring task schedule (30-day email, 45-day call, 60-day reminder) ensures those items don’t slip through the cracks.
    The fewer fines, delays, and overnight shipments you incur, the more profit you keep.


    7. Integrate Analytics into Everyday Operations

    Profitability isn’t just a finance department metric; it’s an operational one.

    Modern Encompass® tools like Enhanced Conditions, New Doc Viewer, and Workflow Tasks can automatically track activity and performance data across roles.
    That data reveals where time, money, and focus are being spent, giving you the ability to refine processes and invest in what actually drives ROI.


    8. Train, Support, and Reinforce

    Even the best workflow design fails without consistent adoption.
    Teams need ongoing training, visual documentation, and quick-access answers to keep up with process updates and new Encompass® features.

    Invest in short, engaging resources such as screen recordings, internal guides, or AI-powered search tools that make answers easy to find.
    When teams know exactly what to do and why it matters, you eliminate confusion and increase consistency.


    9. Start with What You Can Track

    If your current systems can’t calculate every cost, start small.
    Measure what you can: services, vendor fees, concessions, and loan officer commissions, and build from there.
    Even partial visibility will help you identify where profit is leaking and guide where to improve next.


    Join Us Live

    This article was inspired by our November 18 Mastering Encompass® Community Call, “Dollars & Data: Loan-Level Profitability & Analytics.”
    This session marked the final installment in our 12-part series, “From First Click to Final Docs.”

    Thank you to everyone who joined throughout the series. Together, we’ve explored how to design, measure, and master every step of the mortgage workflow, proving that workflow really does come before technology.

    👉 Join the community at MasteringEncompass.com

    Mortgage Workflow Partners Inc.
    We help lenders simplify, standardize, and scale their Encompass® workflows.
    MortgageWorkflowPartners.com

  • The Workflow-First Imperative

    Bridging the Gap Between Mortgage Technology and Operational Excellence

    The mortgage industry has invested millions in technology — but the data is clear: lenders are still struggling with manual work, inconsistent workflows, and a lack of true operational governance.

    Our new whitepaper, The Workflow-First Imperative, draws on findings from the 2025 State of Mortgage Workflow Report and reveals a critical trend across banks, credit unions, and IMBs: technology is amplifying broken processes rather than fixing them.

    This report uncovers why fewer than 30 percent of lenders are familiar with their documented workflows, why most organizations operate without a formal review or change-management framework, and how manual processes continue to drain efficiency across the loan lifecycle.

    More importantly, it lays out a clear path forward. The whitepaper introduces the Workflow Before Technology philosophy, a four-stage maturity model, and the role consultative partners play in helping lenders move from reactive chaos to strategic operational excellence.

    If your organization is wrestling with manual work, documentation gaps, or workflows that haven’t kept pace with your LOS investment, this report will give you the clarity and structure needed to reset your operating model.

    Download the full whitepaper to see what lenders across the industry are experiencing and how a workflow-first strategy changes outcomes.