Your Loan Origination Data Template

ICE Mortgage Technology
Your Loan Origination Data Template

Your Loan Origination Data Template

This template helps you gather the right data for process analysis. It outlines essential attributes to collect and key activities to track within your loan origination process. We also provide guidance on extracting this data from ICE Mortgage Technology.
  • Recommended attributes to collect
  • Key activities to track
  • Extraction guidance for ICE Mortgage Technology
New to event logs? Learn how to create a process mining event log.

Loan Origination Attributes

These are the recommended data fields to include in your event log for comprehensive loan origination analysis.
3 Required 6 Recommended 13 Optional
Name Description
Activity Name
ActivityName
The name of a specific business event or step that occurred within the loan origination process, such as 'Credit Check Completed' or 'Underwriting Commenced'.
Description

The Activity Name describes a distinct task or milestone in the loan origination lifecycle. These events are recorded chronologically to build a sequence of actions for each loan application. The collection of these activities forms the basis of the process map.

In analysis, the Activity Name is used to visualize the process flow, identify bottlenecks between steps, and analyze the frequency and sequence of events. It is fundamental for understanding what happens during the process, measuring transition times, and detecting rework loops where activities are repeated.

Why it matters

This attribute defines the steps in the process, allowing for the visualization of the process map, analysis of process flow, and identification of bottlenecks or deviations.

Where to get

Typically derived from event logs, status change records, or milestone data within the loan file in ICE Mortgage Technology.

Examples
Initial Disclosures SentUnderwriting Decision RenderedFunds DisbursedApplication Withdrawn
Event Timestamp
EventTimestamp
The precise date and time when a specific activity or event was recorded in the system.
Description

The Event Timestamp marks the point in time that a process step occurred. It provides the chronological order necessary to reconstruct the process flow and is essential for all time-based analysis. For most activities, this represents the start time of the event.

This attribute is crucial for calculating durations and cycle times, such as the time between 'Underwriting Commenced' and 'Underwriting Completed'. It enables the analysis of process performance, the identification of delays and bottlenecks, and the monitoring of adherence to service level agreements (SLAs).

Why it matters

This timestamp provides the chronological sequencing for all activities and is the foundation for all duration, cycle time, and performance calculations.

Where to get

Each milestone or event record in ICE Mortgage Technology should have an associated timestamp indicating when it was completed or logged.

Examples
2023-04-15T10:22:15Z2023-04-18T14:05:00Z2023-05-01T09:30:45Z
Loan Application ID
LoanApplicationId
A unique identifier assigned to each loan application, serving as the primary key for tracking the entire origination process from submission to completion.
Description

The Loan Application ID uniquely identifies each individual loan request throughout its entire lifecycle. It serves as the central entity to group all associated activities and data, allowing for a complete trace of the origination journey for a specific loan.

In process mining analysis, this ID functions as the Case ID. It links all related events, such as 'Application Submitted', 'Underwriting Commenced', and 'Funds Disbursed', into a single coherent process instance. This enables the reconstruction and analysis of the end-to-end journey for every loan, which is essential for calculating cycle times, identifying variants, and understanding process flows.

Why it matters

This is the essential Case ID that connects all related activities into a single process instance, making it possible to analyze the end-to-end loan origination journey.

Where to get

This is the primary loan identifier in ICE Mortgage Technology, often referred to as the Loan Number or Loan ID within the system.

Examples
300185624530029947123004512388
Application Channel
ApplicationChannel
The channel or method through which the loan application was initially submitted.
Description

This attribute indicates the origin of the loan application, for example, 'Online Portal', 'Broker', or 'In-Branch'. Different channels may have different data quality, completeness, and customer profiles, which can impact the downstream process.

Application Channel is a valuable dimension for comparing process performance. Analysis can reveal which channels are most efficient, have the lowest rework rates, or lead to the highest approval rates. These insights can help the business optimize its channel strategy and allocate resources effectively.

Why it matters

Helps compare the performance and efficiency of different submission channels to identify which ones are most effective or require process improvements.

Where to get

Consult ICE Mortgage Technology documentation. This may be stored as a 'Source of Business' or similar field.

Examples
BrokerOnline PortalIn-BranchMobile App
Assigned Loan Officer
AssignedLoanOfficer
The name or ID of the loan officer or underwriter responsible for performing or owning a specific activity.
Description

This attribute identifies the human resource involved in a process step. It can represent the person who completed the task, the current owner of the loan file, or the primary contact for the application.

Analyzing the process by Assigned Loan Officer helps in understanding workload distribution, comparing performance across individuals or teams, and identifying coaching opportunities. It is essential for dashboards related to resource performance, such as 'Loan Officer Activity Distribution' and 'Underwriting SLA Performance'.

Why it matters

This attribute is key to resource-based analysis, allowing you to measure performance, balance workloads, and compare efficiency across different loan officers and teams.

Where to get

Consult ICE Mortgage Technology documentation. User information is typically associated with milestone completion records or loan ownership fields.

Examples
j.doer.browns.smithm.jones
Decision Outcome
DecisionOutcome
The final result of a decision-making activity, most notably the underwriting decision.
Description

This attribute records the outcome of key decision points in the process, such as 'Approved', 'Denied', 'Withdrawn', or 'Approved with Conditions'. It represents the terminal state of a loan application or the result of an interim review.

Analyzing Decision Outcome is critical for understanding process effectiveness. It helps quantify approval and denial rates and is often analyzed alongside the 'Reason for Decision' to identify the primary drivers of negative outcomes. Understanding these outcomes is key to improving application quality and process efficiency.

Why it matters

This attribute is essential for measuring process effectiveness, such as approval rates, and for analyzing the reasons behind loan denials or withdrawals.

Where to get

Consult ICE Mortgage Technology documentation. This information is typically tied to the underwriting decision milestone or the final loan status.

Examples
ApprovedDeniedWithdrawn by ApplicantApproved with Conditions
Event End Time
EventEndTime
The date and time when an activity was completed. This is used with the start time to calculate the active processing time of an event.
Description

The Event End Time marks the completion of a specific task. For events that are considered instantaneous, the end time may be the same as the start time. For activities with a measurable duration, like 'Underwriting Review', this timestamp is distinct.

This attribute allows for a more precise analysis of process performance by differentiating between waiting time (time between activities) and processing time (duration of an activity). It is essential for calculating the 'ProcessingTime' metric and for resource utilization analysis.

Why it matters

Enables the calculation of true processing time for activities, helping to distinguish active work time from idle waiting time for more accurate bottleneck analysis.

Where to get

Consult ICE Mortgage Technology documentation. This may be available for certain logged events or can be the same as the StartTime for milestone events.

Examples
2023-04-15T11:45:10Z2023-04-18T17:30:00Z2023-05-01T09:30:45Z
Loan Amount
LoanAmount
The total monetary value of the loan being requested by the applicant.
Description

The Loan Amount represents the principal amount of the loan application. This value can significantly influence the process, as larger or non-conforming loans may require additional scrutiny, different approval levels, or more extensive documentation, leading to longer cycle times.

This attribute is used as a key dimension for filtering and analysis. By creating value bands (e.g., <$250k, $250k-$500k, >$500k), analysts can compare process performance for different loan sizes. It is also a fundamental component for financial calculations, such as estimating the 'Cost per Loan Origination'.

Why it matters

Helps in segmenting the process to see if loan value impacts processing time, rework, or approval rates, providing valuable context for performance analysis.

Where to get

This is a fundamental field in the loan application data within ICE Mortgage Technology.

Examples
350000.00750000.00215500.50
Loan Product Type
LoanProductType
The specific type of loan product being applied for, such as '30-Year Fixed' or 'FHA Loan'.
Description

This attribute categorizes each loan application based on the financial product offered. Different loan products often have distinct process requirements, complexities, and regulatory constraints, leading to variations in the origination process.

In analysis, Loan Product Type is a critical dimension for segmentation. It allows analysts to compare cycle times, rework rates, and process paths across different products to see if certain products are less efficient. This insight is crucial for tailoring process improvement efforts and setting realistic performance targets.

Why it matters

Allows for performance comparison across different types of loans, helping to identify if specific products have more complex or inefficient processes.

Where to get

This information is a core data point for any loan and should be available in the main loan details section within ICE Mortgage Technology.

Examples
30-Year Fixed Conventional15-Year Fixed Conventional5/1 ARMFHA LoanVA Loan
Credit Score
CreditScore
The credit score of the primary applicant at the time of the credit check.
Description

The applicant's credit score is a key factor in the lending decision and can influence the complexity of the underwriting process. Applications with lower credit scores may require more rigorous review and documentation.

This attribute provides a valuable dimension for risk-based analysis. By segmenting applications into credit score bands, analysts can investigate whether there is a correlation between credit score and processing times, rework rates, or final decision outcomes. This can help in refining risk assessment processes and managing resources more effectively.

Why it matters

Provides a risk dimension for analysis, helping to determine if credit risk correlates with process complexity, cycle time, or decision outcomes.

Where to get

This data is typically sourced from a credit reporting agency and stored within the borrower's information in ICE Mortgage Technology.

Examples
785692740810
Customer Type
CustomerType
A classification of the loan applicant, such as 'First-Time Homebuyer' or 'Refinance'.
Description

This attribute segments customers based on their profile or relationship with the lender. The needs and required documentation for a first-time homebuyer can be very different from those of an investor or someone refinancing a loan, potentially leading to different process paths.

Analyzing the process by Customer Type can uncover variations in customer experience and process efficiency. It helps answer questions like, 'Do first-time homebuyers experience longer cycle times?' or 'Are refinance applications processed more quickly?'. These insights can inform customer service strategies and process adjustments.

Why it matters

Allows for customer-centric process analysis to understand if different types of customers experience different process efficiencies or challenges.

Where to get

Consult ICE Mortgage Technology documentation. This may be derived from the loan purpose or other applicant data.

Examples
First-Time HomebuyerRefinanceInvestorExisting Customer
Is Automated
IsAutomated
A boolean flag indicating whether an activity was performed automatically by a system or manually by a user.
Description

This attribute distinguishes between tasks executed by software, such as an automated credit check or sending system-generated disclosures, and tasks requiring human intervention. This information is key for automation initiatives.

Analyzing the process with this attribute helps quantify the level of automation and identify opportunities for further improvement. It is used to calculate KPIs like 'Manual Activity Frequency' and can highlight manual bottlenecks that are prime candidates for automation, ultimately aiming to reduce costs and improve speed.

Why it matters

Helps quantify the extent of automation in the process and identify manual activities that are bottlenecks, providing a basis for future automation initiatives.

Where to get

This is often derived by mapping activity names or user IDs (e.g., 'System') to an automation status. It is unlikely to be a direct field in the source system.

Examples
truefalse
Is Rework
IsRework
A calculated boolean flag that identifies if an activity is a repeated step within the same case.
Description

A boolean flag that indicates if an activity is being performed for a second or subsequent time within the same loan application. This is typically identified when an activity follows a later step in the standard process, such as 'Supporting Documents Requested' occurring after 'Underwriting Decision Rendered'.

Analyzing rework is fundamental to understanding process inefficiency. By filtering for activities where IsRework is true, analysts can quantify the frequency and impact of rework loops. This helps identify the root causes, such as incomplete initial documentation or unclear requirements, and is crucial for calculating the Application Rework Rate KPI and driving process simplification efforts.

Why it matters

Directly quantifies process inefficiency by flagging repeated work, making it easy to measure the frequency of rework and investigate its root causes.

Where to get

This attribute is not in the source system. It is calculated by process mining software by detecting repeated activities or backward loops in the process flow for a case.

Examples
truefalse
Last Data Update
LastDataUpdate
The timestamp indicating the last time the data for this record was refreshed or extracted from the source system.
Description

This attribute provides the date and time of the most recent data pull. It is essential for understanding the freshness of the data being analyzed and for managing data refresh schedules.

While not typically used for analyzing the process itself, it is vital for dashboard reporting and data governance. It informs users about how current the analysis is and helps diagnose issues related to outdated information.

Why it matters

Informs users of the data's freshness, which is critical for ensuring that analyses and dashboards are based on up-to-date information.

Where to get

This timestamp is typically generated and added to the dataset during the data extraction and loading (ETL) process.

Examples
2023-10-27T02:00:00Z2023-10-28T02:00:00Z
Loan Cycle Time
LoanCycleTime
The total calculated time from the first event to the last event for a loan application.
Description

The total time elapsed from the beginning to the end of a loan application case. It is calculated as the difference between the timestamp of the first event, e.g., 'Loan Application Created', and the last event, e.g., 'Funds Disbursed' or 'Loan Denied'.

This attribute is a primary key performance indicator for measuring overall process efficiency. It provides a high-level view of how long it takes to process a loan from start to finish. Analysts use this metric to track performance over time, benchmark against industry standards, and identify the impact of process improvement initiatives. Breaking down the average cycle time by dimensions like Loan Product Type or Application Channel reveals which process variants are more or less efficient.

Why it matters

This KPI directly measures the end-to-end efficiency of the loan origination process, providing a critical metric for performance tracking and accelerating service delivery.

Where to get

Calculated by subtracting the timestamp of the first event from the timestamp of the last event for each Loan Application ID.

Examples
259200038880004752000
Processing Time
ProcessingTime
The calculated duration of an activity, measured from its start time to its end time.
Description

The duration of an activity, calculated as the difference between its EventEndTime and EventTimestamp. This metric is essential for identifying which specific steps in the loan origination process are consuming the most active work time.

In analysis, ProcessingTime helps pinpoint bottlenecks at the activity level. By aggregating this metric, analysts can compare the efficiency of different activities, loan officers, or departments. For instance, a high average processing time for 'Underwriting Commenced' could indicate resource constraints or process complexities that need investigation. It is a fundamental building block for performance monitoring and continuous improvement initiatives.

Why it matters

Measures the active work time of individual process steps, helping to identify the most time-consuming activities and distinguish them from idle time.

Where to get

This attribute is not in the source system. It is calculated during data transformation using the formula: EventEndTime - EventTimestamp.

Examples
36008640012320
Property State
PropertyState
The U.S. state where the property associated with the loan application is located.
Description

This attribute provides the geographical location of the property. Lending regulations, market conditions, and processing requirements can vary significantly by state, which may influence the loan origination process.

Property State is a useful dimension for geographical analysis. It allows for comparing process performance, such as cycle times and approval rates, across different regions. This can help identify regional bottlenecks or highlight the impact of state-specific regulations on the process.

Why it matters

Enables geographical analysis of the process, helping to identify regional performance differences that may be caused by market conditions or state-specific regulations.

Where to get

This is a standard field in the property information section of the loan application data in ICE Mortgage Technology.

Examples
CATXFLNYIL
Reason For Decision
ReasonForDecision
A code or text description explaining the reason behind a specific decision outcome, such as a loan denial.
Description

This attribute provides context for the 'DecisionOutcome'. When a loan is denied or requires rework, this field specifies why, for example, 'High debt-to-income ratio' or 'Incomplete documentation'.

This information is invaluable for root cause analysis. By analyzing the most frequent reasons for denials or rework, the organization can identify systemic issues in the process or problems with application quality. These insights can lead to targeted improvements, such as clearer instructions for applicants or additional training for loan officers.

Why it matters

Provides the 'why' behind loan denials or rework, enabling root cause analysis to address systemic issues and improve first-pass yield.

Where to get

Consult ICE Mortgage Technology documentation. This information is often captured in reason code fields or notes associated with a decision milestone.

Examples
Credit score below thresholdIncomplete application documentsHigh DTI RatioAppraisal value too low
SLA State
SLAState
A calculated status indicating if an activity or case met its Service Level Agreement (SLA).
Description

Indicates whether an activity or the entire case is completed within its service level agreement target. It is typically derived by comparing the actual cycle time against a predefined SLA target, such as the UnderwritingSlaTarget.

This attribute is critical for performance and compliance monitoring. Dashboards often use SLAState to visualize the percentage of loans meeting their targets, allowing managers to track performance against key objectives. Segmenting SLA performance by loan officer, product type, or channel can reveal areas of excellence or opportunities for improvement, ensuring the organization meets its service commitments.

Why it matters

Provides a clear, at-a-glance indicator of performance against key time-based targets, making it easy to monitor and report on SLA compliance.

Where to get

This attribute is not in the source system. It is calculated by comparing the actual duration of a process segment with its corresponding SLA target.

Examples
On TimeAt RiskLate
Source System
SourceSystem
Identifies the originating system or platform from which the data was extracted.
Description

This attribute specifies the software or application that generated the process data, such as 'ICE Mortgage Technology Encompass' or a connected CRM. It is particularly useful in environments where data is aggregated from multiple sources.

In analysis, SourceSystem helps in data validation and provides context about the origin of an event. It can be used to filter analysis for specific systems or to investigate data quality issues that may be unique to one source.

Why it matters

Provides crucial context about data origin, which is important for data validation, troubleshooting, and understanding process variations across different systems.

Where to get

This value can be manually added during data extraction or may be available in data headers if the export originates from a data warehouse.

Examples
ICE Mortgage Technology EncompassICE Mortgage Technology VelocifyInternal CRM
Underwriting Department
UnderwritingDepartment
The specific underwriting team or department that is handling the loan application.
Description

This attribute identifies the organizational unit responsible for the underwriting phase of the loan. In large organizations, departments might be specialized by region, loan type, or risk level.

Similar to the Assigned Loan Officer, this attribute allows for performance analysis at a team or department level. It can be used to compare workloads, efficiency, and SLA adherence across different underwriting groups, helping management to identify high-performing teams and share best practices.

Why it matters

Enables performance analysis and comparison at the team or department level, which is useful for resource management and identifying systemic issues within specific groups.

Where to get

Consult ICE Mortgage Technology documentation. This may be part of the user data associated with the underwriter or a separate routing field.

Examples
UW-EastUW-WestJumbo Loans UWGovernment Loans UW
Underwriting SLA Target
UnderwritingSlaTarget
The predefined service level agreement (SLA) target duration for the underwriting stage.
Description

This attribute defines the expected maximum time for completing the underwriting process, from 'Underwriting Commenced' to 'Underwriting Completed'. It serves as the benchmark against which actual performance is measured.

This is a critical input for calculating SLA adherence. It allows for the creation of an 'SLAState' attribute to flag underwriting tasks as 'On Time' or 'Late'. Dashboards tracking SLA performance rely on this target to provide managers with a clear view of whether service commitments are being met.

Why it matters

Provides the benchmark needed to objectively measure and monitor underwriting performance against service level agreements.

Where to get

This may not be a field in the source system and could be business knowledge that is joined with the data during transformation. It might vary by loan type or region.

Examples
259200432000
Required Recommended Optional

Loan Origination Activities

These are the key process steps and milestones to capture in your event log for accurate process discovery.
5 Recommended 11 Optional
Activity Description
Clear To Close Issued
A formal notification that all conditions have been met and the lender is ready to schedule the closing and fund the loan. This is a critical milestone indicating the loan is ready for the final phase.
Why it matters

This is a key gate in the process, signaling the end of underwriting and processing activities. It allows for measurement of the time from application to final approval.

Where to get

Captured from the completion date of the 'Clear to Close' (CTC) milestone in Encompass. This is a standard and well-defined stage in the workflow.

Capture

Inferred from the population of the 'Clear to Close' date field within the loan's milestone tracking.

Event type inferred
Funds Disbursed
Marks the successful completion and end of the loan origination process, where the loan amount is paid out. This event concludes the loan's journey from application to funding.
Why it matters

As the primary success-state end event, this is critical for calculating the end-to-end cycle time of successfully originated loans. It is also used to measure application throughput rates.

Where to get

This is captured by the 'Funding Date' or 'Disbursement Date' field in Encompass. This date is populated once the wire transfer is confirmed.

Capture

Inferred from the population of the 'Funding Date' field in the loan data.

Event type inferred
Loan Application Created
This activity marks the official start of the loan origination process when a loan officer creates a new loan file in the system. This event is captured when the loan case is first saved, establishing the unique Loan Application ID.
Why it matters

As the primary start event, this activity is essential for calculating the overall loan cycle time and analyzing application intake volumes. It provides the baseline for all subsequent process measurements and throughput analysis.

Where to get

This is typically an explicit event recorded in the loan history or audit log. It can also be inferred from the creation timestamp of the loan record associated with the Loan Application ID.

Capture

Captured from the creation date of the loan file or the first entry in the loan's audit trail.

Event type explicit
Underwriting Commenced
Marks the official start of the underwriting process, where an underwriter begins their formal review of the loan application and all supporting documents. The file is formally submitted to the underwriting queue or assigned to an underwriter.
Why it matters

This is the start-point for measuring underwriting cycle time, a critical KPI for operational efficiency. It helps in analyzing underwriter workload and identifying pre-underwriting bottlenecks.

Where to get

This is typically inferred from the timestamp when the loan file is assigned to the 'Underwriting' milestone or when its status changes to 'In Underwriting'.

Capture

Inferred from the 'Submitted to Underwriting' date field or a status change to 'Underwriting in Progress'.

Event type inferred
Underwriting Decision Rendered
This activity represents the completion of the initial underwriting review, resulting in a decision such as approved, suspended, or denied. It marks a major milestone in the loan lifecycle.
Why it matters

This event concludes the underwriting cycle time measurement and is a critical decision point. Analyzing outcomes and time taken helps evaluate underwriting performance and identify drivers for rework.

Where to get

This is a key milestone in Encompass, captured by the completion date of the underwriting stage. The decision itself is stored in a separate field.

Capture

Inferred from the completion timestamp of the 'Underwriting' milestone or a status change to 'Approved', 'Suspended', or 'Denied'.

Event type inferred
Application Withdrawn
Represents an unsuccessful end to the process where the applicant chooses to withdraw their application. This is another terminal status for the loan file.
Why it matters

This is a failure-state end event initiated by the customer. Analyzing when and why applications are withdrawn can provide insights into customer satisfaction, competition, and process friction.

Where to get

This is captured when the final loan status is set to 'Withdrawn'. The date of this status change is recorded in the system's logs or a milestone date field.

Capture

Inferred from a final status of 'Withdrawn' and the timestamp of that status change.

Event type inferred
Appraisal Received
Represents the moment the property appraisal report is received from the appraiser and added to the loan file. This step is critical for property valuation and is a key dependency for the final loan approval.
Why it matters

The appraisal process is often a source of significant delays. Tracking when the appraisal is ordered and received helps to monitor and manage this external dependency effectively.

Where to get

This event is typically captured when the appraisal document is uploaded and the corresponding 'Appraisal Received' milestone date field in Encompass is populated.

Capture

Inferred from the population of the 'Appraisal Received Date' field or a related status change.

Event type inferred
Closing Disclosures Sent
Represents the point at which the final Closing Disclosure (CD) is sent to the applicant for review. This is a mandatory compliance step that must occur a set number of days before closing.
Why it matters

Tracking this activity is essential for ensuring TRID compliance, as it starts a mandatory waiting period. Delays here can directly impact the scheduled closing date.

Where to get

Captured from the completion date of the 'Closing Disclosure Sent' milestone or a specific date field within the compliance section of the loan file in Encompass.

Capture

Inferred from the timestamp associated with the 'CD Sent' or equivalent milestone.

Event type inferred
Conditions Cleared
This event signifies that all underwriting conditions have been satisfied, reviewed, and signed off by the underwriting team. The loan is now ready for the final closing steps.
Why it matters

This marks the end of any post-underwriting rework. The time between 'Loan Approved with Conditions' and this event highlights efficiency in resolving outstanding items.

Where to get

Inferred from the timestamp when the loan status is updated to reflect all conditions are met, often as part of the 'Final Approval' milestone in Encompass.

Capture

Inferred from the completion date of a 'Conditions Cleared' or 'Final Approval' milestone.

Event type inferred
Credit Check Completed
This activity signifies that a credit report has been successfully pulled and reviewed for the applicant. The results of this check are a critical input for the underwriting decision.
Why it matters

The credit check is a key dependency for underwriting. Delays in completing this step can stall the entire process, while the outcome directly influences the loan decision.

Where to get

This is usually captured via an integration with a credit reporting agency. A timestamp is typically recorded in the loan file when the credit report is received and attached.

Capture

Captured from the 'Credit Report Ordered' or 'Credit Report Received' date field within the loan file.

Event type explicit
Initial Disclosures Sent
Represents the point at which the initial set of compliance disclosures, such as the Loan Estimate, is sent to the applicant. This is a critical regulatory step that must occur within a specific timeframe after application.
Why it matters

Tracking this activity is crucial for monitoring compliance with regulations like TRID. The time lag between application creation and this step can indicate early-stage processing delays.

Where to get

Captured from the completion date of the 'Initial Disclosures' milestone in Encompass. This is typically a date field that is populated when the documents are generated and sent.

Capture

Inferred from the timestamp associated with the completion of the 'Initial Disclosures Sent' milestone or status.

Event type inferred
Loan Approved with Conditions
Occurs when the underwriter approves the loan, but with specific conditions that must be met before closing. This is a common outcome of the initial underwriting review.
Why it matters

This activity triggers the 'conditions clearing' phase of the process. Tracking this allows for analysis of rework and delays between initial approval and the final 'Clear to Close'.

Where to get

This is typically captured by the underwriting decision status changing to 'Approved with Conditions' or 'Suspended'. A timestamp for this status change can be found in the loan audit trail.

Capture

Inferred from the status change to 'Approved with Conditions' and its corresponding timestamp in the milestone log.

Event type inferred
Loan Denied
This activity represents an unsuccessful end to the process where the lender formally denies the loan application. This is a terminal status for the loan file.
Why it matters

This is a key failure-state end event. Analyzing loans that end with this activity, along with associated reason codes, helps identify opportunities for improving application quality or underwriting criteria.

Where to get

This is captured when the final loan status is set to 'Denied'. The date of this status change is recorded in the loan's audit log or a specific milestone date field.

Capture

Inferred from a final status of 'Denied' and the timestamp of that status change.

Event type inferred
Loan Documents Signed
This activity occurs when the borrower signs the final loan documents at the closing. This event confirms the borrower's agreement to the loan terms and precedes the funding of the loan.
Why it matters

This is the final major step involving the borrower before funding. It is a key confirmation that the loan is proceeding and allows for measurement of the 'closing' phase of the process.

Where to get

This is captured by the 'Documents Signed' or 'Closing Date' field within the Encompass loan file. This date is entered by the closing agent or loan officer.

Capture

Inferred from the population of the 'Signing Date' or 'Closing Date' field in the loan data.

Event type inferred
Supporting Documents Received
Indicates that all initially requested supporting documents have been received from the applicant and uploaded to the loan file. This event is a prerequisite for moving the application to underwriting.
Why it matters

This activity concludes the document collection phase. The duration between 'Supporting Documents Requested' and this event is a key KPI for measuring applicant and processor efficiency.

Where to get

Typically inferred from the completion of a 'Documents Received' or 'Ready for Underwriting' milestone. This can also be derived from the timestamp of the last required document being uploaded.

Capture

Inferred from the timestamp when the loan status changes to 'Processing' or 'Ready for Underwriting'.

Event type inferred
Supporting Documents Requested
This activity occurs when the loan processor or officer formally requests necessary documentation from the applicant, such as pay stubs or bank statements. This is often triggered after the initial review is complete.
Why it matters

This marks the beginning of the document collection phase. Analyzing the time from this request to document receipt helps identify bottlenecks caused by applicant delays or unclear communication.

Where to get

This event can be inferred from status changes in the loan file, a specific milestone completion date, or communication logs within the Encompass system.

Capture

Inferred from a status change to 'Pending Documents' or a timestamp on a document request template.

Event type inferred
Recommended Optional

Extraction Guides

How to get your data from ICE Mortgage Technology