Mortgage file automation with decision boundaries.
ConditionRail handles the operational work of moving conditions and evidence through a loan file. Credit, compliance, and underwriting decisions remain with your team.
- · Collecting borrower documents on a checklist cadence.
- · Matching evidence to open conditions and citing the source.
- · Flagging inconsistencies as exceptions for human review.
- · Assembling the underwriter packet and audit trail.
- · Writing condition status back to your LOS.
- · Recording every action with actor, channel, timestamp.
- · Approving, suspending, or denying loan applications.
- · Clearing or waiving conditions to close.
- · Adverse action and fair-lending decisions.
- · Pricing, program eligibility, exception approvals.
- · Final underwriter sign-off on every packet.
- · Communication outside the documented audit channels.
ConditionRail organizes and tracks mortgage conditions. It does not underwrite, approve, or deny loans. Underwriter decisions stay with your team.
AI may classify, match, draft, and flag. It may not approve, deny, waive, or communicate a credit decision.
Prepared by ConditionRail for lender review. Final credit, compliance, underwriting, and adverse-action decisions remain with authorized lending staff.
Security posture
Stated precisely, in the same language we use with lender security reviewers.
- Security reviewDocumentation for reviewers
Security documentation is available to lender security reviewers during procurement.
- GLBA supportCustomer-controlled workflows
ConditionRail supports customer-controlled mortgage data workflows with access control, encryption, audit logging, and documented Safeguards Rule control mapping. Your institution remains responsible for its own GLBA compliance program.
- Deployment optionsCloud · self-hosted
Lenders can run ConditionRail in our cloud or self-host inside their own environment. Self-hosted deployments can be configured with no third-party subprocessors beyond customer-selected integrations.
- Borrower dataNot used for model training
Borrower documents and submission content are not used to train machine learning models. Document parsing happens against scoped operator instances.
- Audit logsDocument · message · LOS · override
Every document action, outbound message, LOS sync, and operator override writes an immutable audit entry with actor, channel, and timestamp.
- Data retentionConfigurable · default 7 years
Default retention is 7 years to align with common mortgage record-keeping practice. Retention windows are configurable per account.
Careful language is part of the product.
- · We do not say "fully compliant." Compliance status belongs to your institution, evidenced by your own audits.
- · We do not claim "no subprocessors" universally. Self-hosted deployments can be configured with no third-party subprocessors beyond customer-selected integrations; cloud deployments use disclosed infrastructure providers.
- · We do not claim autonomous underwriting. ConditionRail does not approve, deny, or risk-score loan applications.
- · We do not publish customer logos or proof without written consent. See proof.