A live LendingPad dashboard that pulls loan-stage data on a schedule, normalizes each record, and gives mortgage teams one reliable view of active pipeline movement.
The Mortgage Pipeline Tracker connects LendingPad to a reporting layer through Zapier Webhooks. It replaces repeated exports, hand-maintained status sheets, and dashboard figures that drift from the loan origination system. The finished tool retrieves authorized loan records, maps them into a consistent schema, updates the dashboard, and records every sync attempt for review.
What the Mortgage Pipeline Tracker Shows
A mortgage pipeline tracker is a read-focused operations dashboard that turns loan records from a loan origination system into stage counts, aging queues, ownership views, exception lists, and recent movement history. LendingPad remains the source of truth; the dashboard provides a faster way to review what changed, which files have stalled, and where follow-up is required.
The design reflects the reality that mortgage volume can change quickly. The Mortgage Bankers Association’s Q2 2025 performance report recorded originations rising 35% quarter over quarter and 24% year over year, while ICE reported the highest quarterly origination volume since 2022. A dashboard must therefore handle both quiet periods and sudden increases without producing duplicate loans or stale stage totals.
Mortgage Pipeline Tracking Across Systems Without Duplicate Rows
The workflow reads LendingPad data through approved API access, then treats the LendingPad loan identifier and last-modified timestamp as the deduplication key. According to LendingPad’s API terms, API access requires provisioning and current import/export windows can be within 30 minutes. The tracker accounts for that window rather than presenting delayed source data as real-time.
A scheduled Zap requests changed records, validates required fields, and passes only normalized values downstream. The Google Sheets API stores the reporting table because it supports controlled reads, writes, and batch updates. Looker Studio renders the operational dashboard with filters for loan officer, processor, stage, age band, and last activity.
Core Features
| Feature | Description |
|---|---|
| LendingPad Scheduled Data Pull | Teams lose time repeating exports and reconciling versions. The workflow requests newly created or modified records on a defined schedule and stores the source timestamp with every row. |
| Loan Stage Normalization | Inconsistent stage labels make totals unreliable. The mapping layer converts LendingPad statuses into a controlled dashboard taxonomy while preserving the original status for audit review. |
| Idempotent Loan Upserts | Repeated syncs can inflate counts or overwrite newer information. Each record is inserted or updated by loan ID and modification timestamp, preventing duplicate pipeline entries. |
| Aging and Stalled-File Queues | Managers cannot act quickly when files disappear inside broad stage totals. The dashboard calculates days in stage and surfaces records that cross configured aging thresholds. |
| Ownership and Workload Filters | Shared spreadsheets make it difficult to isolate responsibility. Users can filter pipeline views by assigned loan officer, processor, branch, stage, and recent activity. |
| Sync Audit and Exception Log | Silent failures create false confidence in dashboard numbers. Every run records start time, completion status, records received, records changed, rejected rows, and the reason for each rejection. |
Why This Stack Fits LendingPad Reporting
LendingPad API access keeps the LOS authoritative. Zapier handles scheduled retrieval, field routing, retries, and notifications without placing reporting logic inside the origination platform. Google Sheets provides a transparent normalized table that operations staff can inspect. Looker Studio separates presentation from data collection, so charts and filters can change without rewriting the sync workflow.
Credentials are stored outside exported workflow files, and logs exclude sensitive borrower fields that are not required for pipeline reporting. The project follows the OWASP Secrets Management guidance: restrict access, rotate credentials, and avoid placing secrets in source files or dashboard formulas.
Mortgage Pipeline Tracker Refresh and Reliability Targets
| Control | Target | Validation Method |
|---|---|---|
| Scheduled sync | Every 15 minutes | Confirm the Zap run history and source retrieval timestamp |
| Duplicate prevention | Zero duplicate loan IDs | Run the same fixture payload twice and compare row count |
| Dashboard propagation | Under 2 minutes after table update | Timestamp the normalized write and dashboard refresh |
| Reconciliation | Once daily | Compare LendingPad record counts with dashboard counts by mapped stage |
| Failure visibility | One logged result per run | Force an invalid payload and verify the exception record and notification |
These are operational targets, not assumptions about LendingPad delivery speed. When the source returns no changed records, the run is logged as successful with zero updates. When a request fails, the last verified dashboard snapshot remains visible and the sync status changes to delayed.
Use Cases
- Run a morning pipeline review from one screen. Branch managers open stage totals, aging bands, and yesterday’s movement without requesting a fresh spreadsheet from each team member.
- Find files that have stopped progressing. Processors filter loans that exceeded the configured time in a stage and work the exception queue instead of scanning every active record.
- Compare workload by owner. Operations leaders group active files by loan officer or processor to identify uneven assignments and missing ownership fields.
- Track movement between LendingPad and reporting systems. Administrators review the sync audit to confirm when a loan changed, how its stage was mapped, and whether the dashboard accepted the update.
How to Track Mortgage Pipelines Using Mortgage Pipeline Tracker
Download & Set Up the Project
Download, set up, and install Mortgage Pipeline Tracker to get the project running. If you hit any difficulty, contact us here.
Open the Dashboard
Open the dashboard and confirm the sync-status card shows the latest completed LendingPad retrieval, record count, and source timestamp.
Set the Pipeline View
Choose loan officer, processor, branch, stage, age band, and last-activity filters to define the operational view you need.
Refresh and Review
Select Run Sync, then review updated stage totals, stalled-file queues, movement history, and any rejected records in the audit panel.
Project Directory
mortgage-pipeline-tracker/
├── README.md
├── .env.example
├── config/
│ ├── field-map.json
│ ├── stage-map.json
│ └── aging-thresholds.json
├── workflows/
│ ├── lendingpad-polling-zap.json
│ ├── sync-failure-alert-zap.json
│ └── daily-reconciliation-zap.json
├── scripts/
│ ├── normalize-payload.js
│ ├── validate-record.js
│ ├── upsert-loan.js
│ ├── calculate-stage-age.js
│ └── write-audit-log.js
├── dashboard/
│ ├── data-source-schema.md
│ ├── calculated-fields.md
│ ├── filter-controls.md
│ └── report-layout.md
├── tests/
│ ├── fixtures/
│ │ ├── new-loan.json
│ │ ├── modified-loan.json
│ │ └── invalid-loan.json
│ ├── deduplication.test.js
│ ├── stage-mapping.test.js
│ └── reconciliation.test.js
└── docs/
├── deployment.md
├── field-dictionary.md
├── troubleshooting.md
└── security-notes.md
For customization, deployment, or additional integrations, CogworkLabs can extend mortgage pipeline tracking across systems while keeping LendingPad as the authoritative record.
FAQs
Can the dashboard update when a loan changes stage in LendingPad?
Yes. The tracker requests records on a scheduled interval and updates a loan when its LendingPad modification timestamp changes. The visible refresh timing depends on API delivery, the configured polling interval, and dashboard propagation.
What happens if LendingPad data is delayed or unavailable?
The dashboard keeps the last verified snapshot and marks the sync as delayed rather than replacing valid data with blanks. The audit log records the failed request, and the workflow can notify the designated operations contact.
Can the tracker combine LendingPad data with other systems?
Yes, when the additional system exposes a stable API, webhook, or structured export. Its records are mapped to the same controlled schema, with source-specific identifiers retained so duplicates and conflicting updates can be traced.
