> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/retail-lending/implementation-guide.md). # Implementation Guide Plan and run a Retail LOS implementation in order, from foundation to go-live and beyond. Use this guide to take Retail LOS from lending strategy to day-to-day governance. It follows the order an FI usually works in. Each phase names who owns it, what done looks like, and where to read and what to do. {% hint style="info" %} [Start Here](/retail-lending/start-here.md) helps you find a page. [User Journeys](/retail-lending/user-journeys.md) show what each audience experiences. This guide shows what to do, and in what order, to launch and run Retail LOS. {% endhint %} ### The phases at a glance | Phase | Owner | Start with | | ---------------------------------- | -------------------------------------------- | ------------------------------------------------------------------ | | 1. Set the lending foundation | FI Administrator, with credit and compliance | [Overview](/retail-lending/retail-los-overview.md) | | 2. Design the product portfolio | FI Administrator, with credit | [Create a Product](broken://pages/opN1TXIhdJnuYiD71MWP) | | 3. Originate applications | FI Administrator | [Build an Application Flow](broken://pages/n1SdyLUnQZgbkOYajm7c) | | 4. Assess risk and make offers | FI Administrator, with credit | [Publish the Decision Matrix](broken://pages/n5eU7xEVylTz025Fvnzy) | | 5. Fulfil and manage applications | FI staff and FI Administrator | [Work an Application](broken://pages/lvXMbbnbRDUhZZqPPeJE) | | 6. Govern and integrate Retail LOS | FI Administrator and technical teams | [Technical Teams](broken://pages/tY9pGHMXFDw1rITeh3FI) | | 7. Test, go live and improve | FI Administrator, with credit and compliance | [Test Before Go-Live](broken://pages/SaOPfYcafTO6mGboNYJl) | ### 1. Set the lending foundation Establish shared context for your Retail LOS implementation. Confirm the Retail LOS model, available products and common terminology before configuration starts. **Done when** your team shares one view of what Retail LOS is, which sample products exist and the terms it uses. * [Overview](/retail-lending/retail-los-overview.md): what Retail LOS is and who uses it. * [Sample Products](/retail-lending/sample-products.md): the example products that show how a configuration fits together. * [Foundation: Key Concepts](broken://pages/VvAIBGMkKvOEbqSLjdvS): the layers and terms every configuration step uses. * [Glossary](/retail-lending/glossary.md): definitions, when a term needs clarifying. ### 2. Design the product portfolio Turn lending policy and commercial requirements into configurable products. Select the right product model, complete the configuration and validate it before launch. **Done when** each product has its type, category and core terms, and stays **Inactive** until it is ready. * [Product Configuration](broken://pages/h1BRHsVc3cwuzs0gW1IM): what the module covers and how its parts connect. * [Product Settings](broken://pages/Kw4nVkT343872n04UwP2): the settings and tabs on a product. * [Decide the Product Type](broken://pages/pUWg5cwsueJfptR9K75P) and [Ways to Create a Product](broken://pages/lyRRUoyPEbh52PzRRGZq). * **Guides:** [Create a Product](broken://pages/opN1TXIhdJnuYiD71MWP) and [Edit a Product's Details](broken://pages/PTjokj0RtdZloVebVwWv). * **If you're stuck:** [Product Configuration troubleshooting](broken://pages/iBNTtj2yY4SXOc3avYU9). ### 3. Originate applications Create a clear path from product selection to a submitted application. Design the applicant journey, then build, test and publish the supporting experience. **Done when** an applicant can complete the flow for each **Active** product and submit. * [User Journeys](/retail-lending/user-journeys.md) and the [Applicant Journey](/retail-lending/user-journeys/applicant-journey.md): what the applicant goes through. * [Building Applications](broken://pages/AHrYhOpoy0ldcUiuUa0S): the flow, its steps and its screens. * [Starting an Application](broken://pages/802GfCWuEgm8kc5qwK7F): how an application begins. * **Guides:** [Build an Application Flow](broken://pages/n1SdyLUnQZgbkOYajm7c) and [Set Up Documents and Eligibility](broken://pages/R3cqZGDPblK7WmHQ88Fl). ### 4. Assess risk and make offers Apply lending policy consistently at scale. Configure decision logic, pricing, offers and routing so each application receives the appropriate outcome. **Done when** the decision matrix or scorecard is published, approval authority is set, and the workflow is published and tested. * [Decisions, Pricing, Offers](broken://pages/jo3OJEsRNxMSgOW8D09V): the decision engines, pricing, offers and overrides. * [Workflows](broken://pages/HtrMw5Rb28SNfizcpoDI): the steps an application follows and where each outcome leads. * **Guides:** [Publish the Decision Matrix](broken://pages/n5eU7xEVylTz025Fvnzy), [Set Up a Scorecard](broken://pages/CdVet89Uo7n7MdHKWFnS), [Set Up Approval Authority](broken://pages/BOlHIgJWrxip1AUUfkNh) and [Build and Publish a Workflow](broken://pages/YpBznnpGXgIgnhL2fSdK). * **If you're stuck:** [Product Configuration FAQs](broken://pages/ulFlMWsMbHYlmiUQPoT2). ### 5. Fulfil and manage applications Take approved applications through fulfilment with the right controls. Manage documentation, queues, exceptions and lifecycle progress through completion. **Done when** queues cover every status your teams work, lifecycle names fit your process, and staff can work and decide applications. * [Documents](broken://pages/adDmjh1mCNrm4jqVOIY6): the registry, requirements and checklists. * [Lifecycle and Queues](broken://pages/R7nNPhUkV7PFpoQXu97h): stages, statuses and work queues. * [Application Record](broken://pages/JFF4ngUInPlRk5SpVF7A) and [Workflow Timeline](broken://pages/oH9buEhKL7c4OSqdWm2x). * **Guides:** [Work an Application](broken://pages/lvXMbbnbRDUhZZqPPeJE), [Claim, Assign and Transfer an Application](broken://pages/2vitIUvb87Dnf1kf0Og8), [Manage Work Queues](broken://pages/AcHGnKC5TVYfuZEeVRA0) and [Change a Product's Lifecycle](broken://pages/tFjYXGI3mCW7chYnbJih). * **If you're stuck:** [Applications troubleshooting](broken://pages/C9xWy15lVYd45Fyl4AMs). ### 6. Govern and integrate Retail LOS Maintain a controlled and connected lending solution. Configure external services, enforce appropriate access and review the audit trail. **Done when** your vendors are connected, API keys and agents are set up, and roles and module access match your policy. * [Integrations](broken://pages/HDQLTIGTmB72aE21K90r): which vendor handles which task. * [Roles](broken://pages/lwftzPHlwUChlhZeEB6T) and [Module Access](broken://pages/EebOasKPKQhWq9ggrFQL): what each role can do and open. * [Logs](broken://pages/EApi4HoQOVLOa74TzOwK): the audit trail, emails, API calls and errors. * **Guides:** [Connect Third-Party Integrations](broken://pages/bbbLMXrSOSk5LLhPCVdC), [Manage Users](broken://pages/f7gdPumh7eDJyAOWCy9G) and [Assign Roles and Access](broken://pages/RiRqM3F5kuH60sctM6xH). * **If you're stuck:** [Settings](broken://pages/JaIndk0bJgKYQ9HcCmvV), [User Management](broken://pages/V4PD6MqypWeS2OqiDSaK) and [Logs](broken://pages/3pK2Z7XjzKmjHGATtdbe) troubleshooting. ### 7. Test, go live and improve Prove the configuration end to end, activate it, and keep it healthy as policy changes. **Done when** each product has passed an end-to-end test, is set to **Active**, and changes are reviewed in **Version History**. * [Test Before Go-Live](broken://pages/SaOPfYcafTO6mGboNYJl) and [Common Mistakes](broken://pages/cFDwjWwjywK0MbNttGp4). * [The 14-Step Checklist](broken://pages/ZHcqhJqAfVimIkhsRuOr): every step, where it happens and how to know it is done. * [FI Staff Journey](/retail-lending/user-journeys/fi-staff-journey.md), whose **Set up Retail LOS** tab walks the same path with guides. * **If you're stuck:** [FAQs](broken://pages/NOJfP7yQ9ZNcrpfIWJNk) and [Troubleshooting](broken://pages/cznSqi25s8AMbDZABKSr). *** {% columns %} {% column width="83.33333333333334%" %}

Maintained by Abhishek Paul
AI-assisted, human-approved

{% endcolumn %} {% column width="16.666666666666664%" %}
{% endcolumn %} {% endcolumns %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.uptiq.ai/retail-lending/implementation-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.