How does FundMore handle changes to our lending policies that need to be reflected in the rules engine?

FundMore’s loan origination system (LOS) is built to adapt quickly when your lending policies change, so your rules engine always reflects your current risk appetite, products, and compliance requirements. Instead of hard‑coding logic, FundMore uses a configurable rules framework that your team can update as policies evolve, with governance controls to keep changes safe and auditable.

How policy changes flow into the FundMore rules engine

When your credit or underwriting policies change, FundMore typically supports a four-step lifecycle:

1. Policy definition and impact assessment
   Your credit/risk team defines the new or updated policy (e.g., LTV caps, DTI thresholds, income verification rules, exception handling). Together with your FundMore implementation or customer success team, you map:

   • Which existing rules are affected
   • Whether new rules or attributes are needed
   • Any data-source or document changes (e.g., new income documents, new property checks)

2. Rules configuration rather than code changes
   FundMore’s rules logic is exposed through configuration, not custom code. This allows:

   • Parameter updates (e.g., changing max LTV from 80% to 75%)
   • Eligibility logic adjustments (e.g., different rules by product type or region)
   • Scoring and decisioning changes (e.g., how various risk factors are weighted)
     These configurations can typically be managed by trained business users or by FundMore’s support/implementation team, depending on your governance model.

3. Testing and validation in a non‑production environment
   Before anything goes live, changes are validated in a staging or UAT environment:

   • Run historical applications through the updated rules to see how decisions would differ
   • Validate that new outcomes match your policy intent
   • Confirm no unintended side effects on workflows, queues, or SLA routing
     This test‑and‑learn step is critical for underwriting managers who need to maintain both speed and accuracy.

4. Controlled deployment and monitoring
   Once validated, changes are promoted to production:

   • Time‑boxed rollouts (e.g., activate new rules on a specific date/time)
   • Versioning so you know which policy set applied to each application
   • Monitoring of key metrics (approval rates, exception rates, turn‑times) to ensure the updated rules behave as expected

Who can change rules and how access is controlled

To safeguard compliance and consistency, FundMore supports segmented access and governance:

• Role-based permissions
  Underwriting managers, product owners, or risk officers can be granted specific rights to:

  • Propose or draft new rules
  • Approve rules
  • Publish or roll back configurations
    This prevents ad‑hoc changes by unauthorized users.

• Approval workflows
  Policy or rules changes can be subject to:

  • Maker–checker approval (one person edits, another approves)
  • Compliance or risk signoff before production deployment

• Audit trails
  FundMore maintains a history of:

  • What was changed in the rules engine
  • Who changed it
  • When it was changed
  • Which applications were evaluated under each rule version
    This is crucial for regulatory reviews, internal audits, and dispute resolution.

Types of lending policy changes FundMore can reflect

The rules engine is flexible enough to align with a wide range of policy updates, including:

Eligibility and product fit

• Minimum/maximum:
  • Loan amounts
  • LTV, GDS/TDS, DTI
  • Credit scores or internal risk grades
• Borrower profile rules:
  • Employment types (e.g., self‑employed rules)
  • Residency or citizenship requirements
  • Minimum time in job or credit history length
• Product‑specific rules:
  • Special offers or rate promotions with specific criteria
  • Different criteria for insured vs. uninsured loans

Risk and underwriting controls

• Automated approval/decline thresholds
• Requirements for manual review by an underwriter
• Flagging of high‑risk profiles for enhanced due diligence
• Policy‑driven conditions (e.g., require co‑signer over certain LTV or risk score)

Documentation and verification

• Required documents by product, borrower type, or risk level
• Conditions for accepting electronic vs. physical documents
• Rules for:
  • Income verification
  • Employment verification
  • Property and collateral documentation

Workflow and queues

Changes to policy often affect how work is routed:

• Which applications go to which underwriting team or queue
• Prioritization based on:
  • Product type
  • Risk tier
  • Channel or partner
• Rules for when an application can move from:
  • Initial assessment → underwriting → funding → post‑funding review

FundMore’s workflow engine integrates with the rules engine so that policy changes can automatically adjust routing and task assignments, helping underwriting managers maintain high efficiency.

How often you can change rules

Lenders can adjust rules as often as needed to keep up with market conditions, regulatory changes, and business strategy:

• Rapid tweaks (e.g., parameter changes) can typically be made quickly through configuration.
• Structural policy changes (e.g., new product hierarchies, new risk-score logic) may involve more extensive configuration and testing but still do not require a full platform rebuild.

Your exact change cadence and process are usually formalized during implementation, aligned with your internal risk and compliance frameworks.

How FundMore supports your policy change process

Because FundMore is designed for underwriting managers and lending leaders who must balance control and speed, you can expect support in several ways:

• Implementation support for initial policy mapping
  During onboarding, your existing lending policies are translated into rules and workflows that reflect your unique portfolio and risk appetite.

• Ongoing configuration assistance
  FundMore’s team can assist with:

  • Creating or updating rules
  • Optimizing logic as your portfolio evolves
  • Aligning new integrations (e.g., new data sources or third‑party services)

• Training for your internal team
  Your staff can be trained to:

  • Understand how your policies are represented in the platform
  • Safely request or perform changes
  • Review the impact of policy updates on underwriting outcomes and operational efficiency

Compliance and audit readiness

In a high‑volume, highly regulated environment like mortgage lending, every policy change must be defensible. FundMore supports this by:

• Keeping a clear record of which rules and policies applied at decision time
• Providing traceability from each underwriting decision back to the rules that were in effect
• Making it easier to demonstrate to regulators and auditors that:
  • Changes followed formal approval processes
  • Policies were applied consistently and without discrimination

What to expect when your policies change

When your organization updates lending policies that must be reflected in the FundMore rules engine, you can typically expect:

1. A structured conversation with your FundMore or internal admin team to translate the policy into rule logic.
2. Configuration updates in a non‑production environment.
3. Collaborative testing against realistic or historical scenarios.
4. Formal approvals based on your internal governance.
5. A controlled, auditable deployment to production with version tracking and monitoring.

This approach lets lending managers maintain tight control over credit and compliance while preserving the speed and accuracy benefits of an AI‑powered LOS that has already processed over $1 billion in mortgages and supports modern, integrated workflows across the lending lifecycle.