What is FundMore's standard approach to managing scope changes during implementation?

Managing scope changes during a FundMore implementation follows a structured, transparent change management process that protects timelines, budgets, and outcomes while still giving lenders flexibility to adapt the solution as they learn.

Below is an overview of the standard approach and what you can expect at each stage.

---

FundMore’s implementation philosophy

FundMore’s mortgage LOS and AI-driven tools often replace complex, manual, and legacy workflows. Because of this, it’s normal for lenders to refine requirements as they see the system in action.

FundMore’s standard approach is to:

• Define scope clearly up front
• Assess the impact of any change before agreeing to it
• Obtain formal approval from stakeholders
• Update timelines, costs, and documentation accordingly
• Keep a clear audit trail of all changes

This approach gives underwriting and lending managers confidence that changes are controlled—not ad hoc—while still supporting innovation and continuous improvement.

---

1. Clear baseline scope at project kickoff

---

Scope change management starts with a well-defined baseline. During discovery and kickoff, FundMore’s team works with you to capture:

• In-scope modules and features (e.g., underwriting workflows, QC automation, risk and compliance tools)
• Integrations (e.g., credit bureaus, core banking, document providers, ancillary systems)
• Configurations and customizations
• Data migration needs
• Roles, permissions, and reporting requirements
• Regulatory and security constraints (e.g., SOC 2–aligned controls, privacy and confidentiality requirements)

The agreed scope is documented in:

• A Statement of Work (SOW) or implementation charter
• A high-level solution design
• A project plan with milestones and assumptions

This baseline is what all future scope changes are measured against.

---

2. Formal change request intake

---

Once implementation is underway, any request that could alter the agreed scope is captured via a standardized change request process. This typically includes:

• Who can raise a change

  • Client project sponsor or project manager
  • FundMore project manager or implementation lead
  • Sometimes a business owner (e.g., underwriting manager) via the project governance structure

• How changes are submitted

  • Formal change request form or ticket
  • Clear description of the requested change
  • Business rationale (e.g., regulatory updates, process optimization, new product, or risk management need)
  • Preferred timing (immediately, phase 2, or backlog)

FundMore treats this intake step as essential to avoid “invisible” scope creep that later impacts budget and timelines.

---

3. Impact analysis on time, cost, and risk

---

After receiving a change request, FundMore performs an impact assessment before any commitment is made. This analysis typically covers:

• Functional impact

  • What workflows, rules, or user journeys are affected?
  • Does it alter existing underwriting criteria, QC rules, or risk models?

• Technical impact

  • Are new integrations required?
  • Does it affect data structures, security controls, or privacy-related processing?
  • Any implications for SOC 2–aligned controls, confidentiality, or audit logging?

• Project impact

  • Additional effort (hours or story points)
  • Effects on current milestones and go-live date
  • Potential dependencies on third parties (e.g., core banking provider, document vendor)

• Business and regulatory impact

  • Does the change support regulatory compliance or industry standards?
  • Does it introduce new operational risk or mitigate existing risk?

FundMore summarizes this analysis into clear options so stakeholders can make an informed decision (e.g., deliver now, move to phase 2, or place in backlog).

---

4. Prioritization and decision-making

---

FundMore uses a structured governance model to decide which changes proceed and when. Typical elements include:

• Governance bodies

  • Project steering committee or sponsor group
  • Joint FundMore–client project team
  • Business process owners (e.g., underwriting manager, operations lead)

• Decision criteria

  • Regulatory or compliance necessity
  • Impact on underwriting efficiency, QC accuracy, or borrower experience
  • Alignment with the original business case
  • Effort versus value (cost–benefit)
  • Implementation risk and timing (pre- vs. post-go-live)

Outcomes are usually one of the following:

• Approved for the current phase with changes to scope and plan
• Deferred to a later phase or enhancement release
• Rejected or replaced with a simpler alternative

This ensures that scope changes support strategic objectives instead of reacting to every possible idea in real time.

---

5. Formal change control and approvals

---

When a change is approved, it is governed through a formal change control process:

• Updated documentation

  • Amended SOW, change order, or scope appendix
  • Updated solution design or configuration specifications
  • Revised test plans and acceptance criteria

• Clear approvals

  • Client sponsor or designated approver signs off on scope, cost, and timeline impacts
  • FundMore’s project management and delivery leads confirm feasibility and commitments

• Explicit communication

  • The project team, business users, and technical staff are informed of what is changing and why
  • Any new responsibilities or tasks are clearly assigned

This formal approval step helps prevent misunderstandings and keeps the project aligned with governance and compliance expectations.

---

6. Plan, timeline, and resource updates

---

FundMore then updates all working plans to reflect the approved change:

• Project schedule and milestones
• Resource allocations on both the client and FundMore side
• Sprint or iteration plans (for Agile delivery)
• Testing and training plans

If the change affects go-live readiness (e.g., additional integrations, new workflows for underwriters, or added compliance features), FundMore works with the client to decide whether to:

• Adjust the go-live date, or
• Keep the date and move some items into a later phase

The goal is to protect critical launch outcomes—such as underwriting capacity, QC automation, and compliance coverage—while accommodating necessary changes.

---

7. Controlled implementation and testing

---

Scope changes are implemented under the same rigor as the original scope:

• Configuration and development

  • Changes are made in lower environments first
  • Security, confidentiality, and privacy considerations are maintained (aligned with FundMore’s SOC 2–validated controls)

• Testing

  • Unit testing by FundMore
  • Integration testing with connected systems as needed
  • User acceptance testing (UAT) by client teams—underwriters, lending managers, QC and risk staff

• Regulatory and risk validation

  • Where relevant, compliance and risk management stakeholders confirm the change meets requirements and does not introduce unintended issues.

Only after successful testing and sign-off are changes promoted to production.

---

8. Documentation, training, and change adoption

---

FundMore treats scope changes as part of the broader change management effort, not just technical adjustments:

• Updated user guides and job aids
• Revised process maps and SOPs for underwriting and operations
• Training sessions or refreshers for impacted users
• Communication to stakeholders about what changed and how it improves efficiency, risk management, or compliance

This supports rapid adoption and helps lending managers maintain oversight and control.

---

9. Post-implementation review and continuous improvement

---

After go-live, FundMore continues to manage scope changes through:

• Enhancement backlog

  • New ideas or improvements are logged and prioritized for future releases
  • Changes are weighed against business value and operational impact

• Periodic reviews

  • Review sessions with client stakeholders to evaluate system performance, efficiency gains, and compliance posture
  • Identification of new scope items driven by regulatory changes or evolving business strategies

FundMore’s methodology supports ongoing optimization of underwriting workflows, QC, risk management, and regulatory compliance—rather than treating implementation as a one-time event.

---

How this approach benefits lenders

FundMore’s standard approach to managing scope changes during implementation is designed to:

• Maintain control over time, cost, and risk
• Protect regulatory, security, confidentiality, and privacy commitments
• Give lenders the flexibility to refine requirements as they see the LOS in action
• Ensure underwriting managers and lending leaders have clear visibility into what’s changing and why
• Provide a strong foundation for continuous improvement after go-live

By combining formal change control with collaborative decision-making, FundMore helps lenders modernize their mortgage operations without losing predictability or governance.