Change of Circumstance
How the Change of Circumstance request behaves — the reason categories, what submission writes to MeridianLink versus what it only documents, and the manual-for-now review model.
The Change of Circumstance (COC) request lets a broker document any change to a loan — fee changes, rate changes, occupancy, compensation, borrower changes — and file that request to MeridianLink. It lives on the loan's Requests tab.
What submitting does
Submitting a COC request has three effects, in order:
- Writes two fields to MeridianLink — the Disclosure Request date
(
sU3LStatD, set to today) and a comment (sU3LStatN, set to "COC Requested"). - Files a PDF to MeridianLink Documents — the request form is rendered to a
PDF and uploaded as the CIC/COC Change of Circumstance Request, with the
upload date in the description and the COC marker (
custLoan593) stamped on the loan. - Records a request in local history — a
loan_requestsrow capturing every current→new value, so the request is auditable in the portal.
Documentation-only, by design
The per-field new values (rate, amount, occupancy, compensation, fees…) are captured in the PDF and the history record — they are not pushed to MeridianLink as field edits. Only the two disclosure fields above and the uploaded document are written. Applying the changes is a manual, in-MeridianLink step today.
Reason categories
The Reason for Request options mirror MeridianLink's ComplianceCOCCategory:
| Reason |
|---|
| Construction Loan Delayed Settlement |
| Customer Requested |
| Eligibility Affected |
| Extraordinary or Unexpected Event |
| Inaccurate or Changed Information |
| Loan Estimate Expiration |
| New Information |
| Rate Dependent |
What can be documented
A request can flag any combination of these change categories:
- Rate, Base Loan Amount, Appraised Value / Purchase Price, Escrow / Impounds, Lender Fee Buyout — free-form current→new values.
- Loan Purpose, Occupancy, Property Type — dropdowns whose new-value options exclude the current value.
- Product / Program / Term / Doc Type — including Interest-Only and Temporary Buydown. Program and doc-type options come from the same loan-program catalog the pricer uses.
- Compensation — the current BPC/LPC source and amounts, with a new percent / flat entry and a live-computed total.
- Credit Scores — a new score per borrower, with a reminder to upload the new credit report.
- Fees — every current fee over $0, plus free-form additional fees for charges that don't exist on the loan yet.
The review model (today and tomorrow)
Today the request is manual: it captures and files the change, and an
internal user reconciles it in MeridianLink. The underlying request has a full
lifecycle (draft → submitted → in_review → approved → completed, with reject /
cancel), so a future iteration can add the request → approve/deny → apply
workflow — including role-gated underwriter review — without re-modelling the
request.
Reused by the Initial Closing Disclosure request
The Initial Closing Disclosure (ICD) request is built on this same form and contract, so the two stay consistent.
Disclosures
How the disclosure workflow behaves — packages and plan codes, audit severities, archive status, the loan-only eSign timeline, and what differs for leads.
Initial Closing Disclosure
How the Initial Closing Disclosure request behaves — the five-precondition eligibility gate, the business-purpose block, what submission writes to MeridianLink versus what it only documents, and the contacts and non-obligor collections it syncs.