Skip to main content
C-Suite Summit 2027. Where Credit Union Leaders Come Together. Learn More →

What Should a Credit Union LOS RFP Include?

November 18, 2026
Back to Press Releases

A request for proposal (RFP) for a loan origination system (LOS) is one of the few moments in a technology decision when every vendor answers the same questions, in writing, before anyone signs a contract. The quality of those answers depends on the quality of the questions. An RFP built from a long list of features tends to produce responses that all say yes, which leaves the selection team exactly where it started. This guide covers what a credit union LOS RFP should include, how to write requirements that produce comparable answers, and how to carry the RFP into the demo stage.

The short answer: a credit union LOS RFP should include an objectives statement, current lending data and systems, scenario-based functional requirements, integration and data requirements, decisioning and compliance requirements, security and continuity evidence, an implementation and conversion plan, support terms, vendor background, itemized pricing, contract terms drawn from NCUA due diligence guidance, and a published scoring method.

What is an LOS RFP, and why does it matter?

A loan origination system is the software a credit union uses to take a loan application, pull credit, decision the loan, gather documents and disclosures, and hand the funded loan to the core system. An LOS RFP is the formal document that describes the credit union's needs and asks vendors to respond in a consistent format.

The RFP does more than collect proposals. NCUA expects credit unions to plan, perform due diligence on, and then monitor significant third-party relationships, and its examiners use a standard framework built around risk assessment and planning, due diligence, and risk measurement, monitoring and control [1][2]. A well-built RFP gives the credit union a written record of that due diligence, and it gives the board a clear basis for the decision. NCUA's guidance does not prescribe an RFP format, so the structure below is a practical approach rather than a regulatory template.

What should a credit union decide before writing the RFP?

The work before the RFP shapes everything after it. A widely cited piece from c. myers recommends three steps before an RFP goes out: write a clear objectives statement tied to strategy and measurable results, map how the ideal process should work before seeing any vendor demos, and have stakeholders agree on the top five to 10 decision drivers [3]. Mapping the process first keeps the team from rebuilding today's workarounds inside new software.

Two more preparation steps make vendor responses far more useful. Gather your own lending data, such as application volume by channel and loan type, current decision times, and the share of applications that close, so vendors can size their proposals to your credit union instead of a generic one. Then name the evaluation team early, including lending, lending operations, IT and information security, compliance, finance, and digital or member experience leads, plus at least one front-line lender or loan processor who will use the system every day.

What sections should a credit union LOS RFP include?

A complete LOS RFP usually covers the following 12 sections. Each one should ask for evidence, not just a statement.

  1. Credit union profile and objectives. Asset size, membership, loan products, branches and channels, and the objectives statement and decision drivers agreed above.
  1. Current environment. An inventory of the systems the LOS must work with: core processor, digital and mobile banking, credit bureaus, decisioning or scoring tools, document preparation, e-signature, indirect or dealer channels, fraud tools and reporting.
  1. Functional requirements written as scenarios. Real lending situations the system must handle, from application through funding, for each loan type you offer (more on this below).
  1. Integrations, APIs and data. Which connections exist today and are in production, which are real-time versus batch, who builds and maintains new integrations, and how the credit union can export its data, including at contract end. An API (application programming interface) is the standard way two systems exchange data.
  1. Decisioning, credit services and compliance support. Who can change decision rules and how quickly, what the audit trail captures, and how the system produces adverse action reasons. Regulation B requires that adverse action reasons be specific and state the principal reasons; saying an applicant failed the credit union's internal standards or did not reach a qualifying score is not enough [4]. Ask each vendor to show how its system supports that requirement for automated decisions.
  1. Security, resilience and incident notification. Independent control reports (such as a SOC report), business continuity and disaster recovery testing results, and data security practices. NCUA requires federally insured credit unions to notify it of a reportable cyber incident within 72 hours, and that clock can start when a third party notifies the credit union [5]. The RFP should ask how quickly, and through what process, the vendor will notify you of an incident.
  1. Implementation and conversion. A sample project plan, the assumptions behind the timeline, the staff hours the credit union must contribute, which data migrates from the current system, how testing works, and what training is included.
  1. Support, service levels and roadmap. Support hours and channels, service level agreements (SLAs) with performance measures, how performance is reported, how often releases happen, and how clients influence the product roadmap.
  1. Vendor background and financial condition. Experience with credit unions of your size, client references, any material legal proceedings, and financial statements. NCUA's questionnaire asks whether a credit union reviewed a third party's financial statements for reasonable assurance it can meet its commitments, checked references and reviewed lawsuits involving the third party [2].
  1. Pricing. Every fee over the full contract term: implementation, licensing or per-application and per-loan charges, integration fees, third-party pass-through costs, change orders, renewal increases, and termination or deconversion fees.
  1. Contract terms. The terms the credit union expects the final agreement to include (see the next section).
  1. Response instructions and scoring method. Deadlines, a single question-and-answer process for all vendors, the required response format, and the weighting the team will use to score responses.

Which contract terms belong in an LOS RFP?

Putting expected contract terms in the RFP surfaces deal-breakers before the credit union invests weeks in demos. NCUA's own third-party questionnaire is a practical starting list. It asks whether a credit union's contracts address the scope of services; responsibilities of all parties, including oversight of subcontractors; service level agreements, performance reports and penalties for lack of performance; ownership and access to records; audit rights; data security and member confidentiality; business resumption planning; evidence of insurance; member complaints; compliance with regulatory requirements such as GLBA privacy rules; dispute resolution; and default, termination and escape clauses [2].

For an LOS, pay special attention to data ownership and exit terms. The RFP should ask what format your loan data will be returned in at contract end, how long the vendor will support a deconversion, and what it will cost. Your legal counsel should review the final agreement; this article is informational and is no substitute for counsel or your compliance team.

How do you write LOS requirements vendors cannot answer with a simple yes?

Checklist requirements such as "supports mobile applications" invite a yes from every vendor. Scenario requirements describe a real situation and ask the vendor to explain or show how the system handles it. For example: a member starts an auto loan application on a phone, stops after entering income, and finishes it with a loan officer in a branch two days later. Explain how the application, uploaded documents and credit pull carry over, and what the member and the loan officer each see.

Pair scenarios with a required answer label so responses can be compared line by line. Ask vendors to tag every requirement with one of four labels:

  • Available today: in production with current clients and included in the proposed price.
  • Available with configuration: possible without custom code, with an estimate of who does the configuration and how long it takes.
  • Requires custom development: quoted separately, with an estimated timeline.
  • On the roadmap: not yet available, with a target release date.

This one change turns a stack of glossy responses into something the team can score, and it makes later contract negotiations easier because each answer is already in writing.

How should a credit union score LOS RFP responses?

Publish the scoring weights in the RFP and tie them to your decision drivers. A worked example for a credit union focused on member experience and growth might weight functional fit at 25%, integrations and data at 20%, implementation and support at 20%, security and vendor stability at 15%, and total cost over the full contract term at 20%. Your weights should reflect your own objectives.

Two habits improve scoring. Have each evaluator score independently before the group discusses, so the most senior voice in the room does not set the result. Compare total cost over the full term, including integrations and renewal increases, rather than first-year cost, since fee structures differ widely between vendors.

What should a credit union ask during an LOS vendor demo?

The strongest demos are scripted from the RFP. Send each finalist your top five to eight scenarios ahead of time and ask them to run those scenarios live in their system, in the same order, so the team compares the same work across vendors. Useful questions during the demo include:

  • Can you change this decision rule now, and who at the credit union would normally make that change?
  • What adverse action reasons does the system produce for this declined application, and where do they come from?
  • What happens when an integration with the core or a credit bureau fails partway through an application, and who is alerted?
  • Which parts of what you just showed are configured for us, and which require your team or a change order?
  • What reports would our lending manager use every morning, and can we build our own?
  • Can we speak with a client of similar size that converted in the last two years?

What are common LOS RFP mistakes?

A few patterns weaken LOS RFPs. Copying an old RFP carries forward requirements that reflect the last system rather than current goals. Asking hundreds of yes-or-no questions buries the requirements that matter. Leaving pricing open-ended makes cost comparisons unreliable, and skipping exit terms leaves the credit union with little leverage years later when it is time to renew or move on. Giving vendors too little time to respond also tends to produce generic answers, so build enough time into the schedule for thoughtful, specific responses.

Conclusion

A strong credit union LOS RFP states what success looks like, describes real lending scenarios, asks for evidence on integrations, decisioning, security, implementation and cost, sets out expected contract terms, and explains how responses will be scored. Built that way, it helps the team choose with confidence and doubles as a clear record of the credit union's due diligence.

Sync1 Systems builds lending technology for credit unions, anchored by our cloud-based loan origination system and supported by the services, integrations, and emerging capabilities that help credit unions lend more effectively and grow. As a CUSO, we welcome credit unions that bring a scenario-based RFP to the conversation. Contact the Sync1 Systems team to start that conversation.

Frequently asked questions

Does NCUA require credit unions to issue an RFP for an LOS?

NCUA's third-party guidance does not require a specific RFP format. It expects credit unions to perform planning, due diligence and ongoing monitoring that fit the significance of the relationship [1][2]. An RFP is a common and practical way to document that work for a system as central as an LOS.

Should an LOS RFP ask for pricing?

Yes. Ask for itemized pricing covering every fee over the full contract term, including implementation, per-application or per-loan charges, integrations, third-party pass-through costs, renewal increases and deconversion fees, so proposals can be compared on total cost.

Who should be on a credit union LOS RFP team?

Include lending leadership, lending operations, IT and information security, compliance, finance, and digital or member experience, plus at least one front-line lender or processor. A single project owner should manage vendor communication so every vendor receives the same information.

How many vendors should receive an LOS RFP?

A short list keeps scoring manageable and lets each vendor give a thoughtful response. Initial research and conversations can narrow the field to a small group, often three to five vendors, before the RFP goes out.

What is the difference between an RFP and an RFI?

A request for information (RFI) gathers general information about vendors and the market and is often used to build the short list. An RFP asks short-listed vendors for a specific proposal, including how they will meet the stated requirements and what it will cost.

Sources

  1. National Credit Union Administration, Letter to Credit Unions 07-CU-13 and enclosed Supervisory Letter 07-01, "Evaluating Third Party Relationships," December 2007: ncua.gov
  1. National Credit Union Administration, Letter to Credit Unions 08-CU-09, "Evaluating Third Party Relationships Questionnaire," April 2008, status Active, with enclosed questionnaire: letter; questionnaire
  1. c. myers corporation, "Don't Touch That RFP," reprinted on CUmanagement.com, April 27, 2018: cumanagement.com
  1. Consumer Financial Protection Bureau, Regulation B, 12 CFR 1002.9, Notifications, eCFR current as of October 23, 2026: ecfr.gov
  1. National Credit Union Administration, "Cyber Incident Notification Requirements for Federally Insured Credit Unions," final rule amending 12 CFR 748.1(c), 88 FR 12811, March 1, 2023, effective September 1, 2023: govinfo.gov

Want to Turn Lending Insights Into Action?