> 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/commercial-lending/getting-started/loan-stages.md).
# Loan stages
Learn the portfolio stages a deal moves through and the per-deal workflow inside them.
Every deal moves through two structures at once: a **portfolio stage** that shows where it stands in the bank's pipeline, and a **per-deal workflow** that runs inside Pre-Screening. This page explains both, from intake to post-close monitoring.
## Portfolio stage and deal workflow
```mermaid
flowchart LR
DRAFT["Draft"] --> APP["Application"] --> PRE["Pre-Screening"] --> LOI["LOI"] --> MEMO["Credit Memo"] --> CLOSING["Closing"] --> CLOSED["Closed"]
PRE -.-> NE["Not Eligible"]
PRE ==> STEP1["1. Extraction"] --> STEP2["2. Financial Review"] --> STEP3["3. Underwriting"] --> STEP4["4. Projections"]
STEP4 ==> LOI
STEP3 -. CRE only .-> CRE["Property Review"]
classDef portfolio fill:#F6F8FB,stroke:#5B6B83,color:#1F2937,stroke-width:1px;
classDef workflow fill:#E8F1FF,stroke:#2563EB,color:#0F172A,stroke-width:1px;
classDef outcome fill:#ECFDF3,stroke:#16A34A,color:#14532D,stroke-width:1px;
classDef negative fill:#FEF2F2,stroke:#DC2626,color:#7F1D1D,stroke-width:1px;
classDef optional fill:#FFF7ED,stroke:#EA580C,color:#7C2D12,stroke-width:1px,stroke-dasharray: 5 3;
class DRAFT,APP,PRE,LOI,MEMO,CLOSING portfolio;
class STEP1,STEP2,STEP3,STEP4 workflow;
class CLOSED outcome;
class NE negative;
class CRE optional;
```
{% columns %}
{% column width="50%" %}
**Portfolio stage** (top row)
The deal's high-level status in the bank's pipeline. The C\&I and CRE flow is **Draft → Application → Pre-Screening → LOI → Credit Memo → Closing → Closed**. A deal stays in a stage until an explicit action moves it. On the Dashboard tiles and the Applications stage chips the first portfolio stage reads **Draft**. A product's stage bar shows the label the product gives that stage, **Intake** by default, whose key is **Draft**.
{% endcolumn %}
{% column width="50%" %}
**Per-deal workflow** (blue lane)
Runs inside Pre-Screening: Document Extraction, Financial Review, Underwriting Review, and Projections & Stress Review. CRE can also include Property Review. Once the deal advances, the configured credit package takes over.
{% endcolumn %}
{% endcolumns %}
ICRE products follow a different stage sequence: Intake, Application, Pre-Screening, Greenlight, Term Sheet, Closed, and Not Eligible. See [ICRE](broken://pages/rdFLinf6NmyjsZIfmOsB#deal-process), [Compare categories](broken://pages/KZtd26gqoveY1SuHcP7A) and [ICRE deals](broken://pages/ee7k5ErjqGtpPOk0yzfo).
## Stage reference
Stages advance in order. The stepper shows completed stages for reference; only the current stage's actions can advance the deal.
| Stage | What happens | Where you work it |
| ----------------- | -------------------------------------------------------------------- | ------------------------------------------------------------ |
| **Draft** | The borrower or loan officer completes intake. | [Intake drafts](broken://pages/1ZhErIET6VASIpnIg0cL) |
| **Application** | The submitted application awaits assignment. | [Applications](broken://pages/HlkkNFhKVf67h4lJZGgG) |
| **Pre-Screening** | The loan team reviews documents, data, and underwriting assumptions. | [Underwriting](broken://pages/59c2zdmqn6QJYkgp3fAd) |
| **LOI** | The borrower reviews proposed terms. | [Loan summary](broken://pages/8d0rtGLJAIbB2RHDsMfl) |
| **Credit Memo** | The team prepares and approves the credit package. | [Credit memorandum](broken://pages/ZUFSQDiPM4ZEzh3CxukR) |
| **Closing** | The team completes legal documents, execution, and funding. | [Loan summary](broken://pages/8d0rtGLJAIbB2RHDsMfl) |
| **Closed** | The booked loan moves to covenant and servicing monitoring. | [Post-close monitoring](broken://pages/hejMRBtfQTFqqMCJeqTO) |
{% hint style="info" %}
The UI can say **deal**, **application**, or **loan account** for the same record. Use **application** before servicing and **loan account** after booking.
{% endhint %}
## Workflows by product
The C\&I and CRE path is the reference flow. Product configuration can rename, omit, or replace stages.
| Product | Workflow after Pre-Screening |
| -------------------- | ------------------------------------ |
| **C\&I** and **CRE** | LOI → Credit Memo → Closing → Closed |
| **ICRE** | Greenlight → Term Sheet → Closed |
ICRE replaces LOI and Credit Memo with Greenlight and Term Sheet.
{% hint style="info" %}
Workflow configuration controls the stepper. Your tenant can show additional or renamed stages, and product configuration controls each stage's views, checklists, and transition rules.
{% endhint %}
## End states
{% columns %}
{% column width="50%" %}
**Closed**
Ends origination. A new-money deal creates a loan account; monitor its covenants and servicing in [Post-close monitoring](broken://pages/hejMRBtfQTFqqMCJeqTO).
{% endcolumn %}
{% column width="50%" %}
**Not Eligible, Rejected, Withdrawn**
End an application without booking a loan.
{% endcolumn %}
{% endcolumns %}
{% hint style="warning" %}
**Not Eligible**, **Rejected**, and **Withdrawn** applications can't be reopened in place. Create a new application to continue with the borrower.
{% endhint %}
### Related
| | |
|---|
| Move a deal to the next stage | Advance a deal and resolve what blocks it. | Broken link |
| FI Staff | Every bank-side screen, by stage. | Broken link |
| Partner portal | Where a deal starts before the bank picks it up. | Broken link |
| Spreading and covenants | Where covenant rules are configured. | Broken link |
***
{% 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/commercial-lending/getting-started/loan-stages.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.
