> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lendflow.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Manage a Deal in Workflow Live
## Manage a Deal in Workflow Live
Use Workflow Live to process one deal through the stages configured in its workflow. In the Lendflow Dashboard, open the **Deals** tab in the left-side menu, select a deal, then select **Deal Progress**.
**Deal Progress** is the dashboard page where users work in Workflow Live. The [Workflow Builder](/lendflow-external/docs/what-is-the-workflow-builder) defines the stage order, tabs, blocks, statuses, responsibilities, and available actions that appear there.
Stage names, stage order, and available actions depend on the Workflow Builder template applied to the deal. Follow the stages shown on the deal instead of assuming every workflow uses the same sequence.
## Typical deal journey
The following sequence represents a common workflow:
| Stage | What users commonly do |
| - | - |
| **Application** | Review application data, collect documents, and complete configured application blocks. |
| **Underwriting** | Review underwriting data and run Data Orchestration. |
| **Scorecards** | Run individual scorecards or scorecard groups and review their results. |
| **Placement** | Submit the deal to funders and manage placement responses. |
| **Offer** | Create, review, share, and update offers. |
| **Closing** | Complete stipulations, review checkout progress, and confirm final funding terms. |
| **Funded** | Review funded details and record supported funding transactions. |
Workflow Builder templates can add, remove, rename, or reorder stages. Data Orchestration belongs in an **Underwriting** stage, while Scorecards use their own separate **Scorecards** stage.
## Navigate and advance workflow stages
The workflow stages appear across the top of **Deal Progress**. Current and previous stages have a blue background, while future stages have a gray background.
* Select a stage name to view its configured tabs and blocks. Viewing a stage does not move the deal.
* Complete the work required by the current stage.
* Select **Submit to \[next stage]** in the deal header to advance the deal through its configured workflow.
The button uses the next stage's configured name. Stage responsibilities, permissions, required fields, and workflow configuration can determine whether a user can advance the deal.
## Work through the Application stage
The **Application** stage displays the tabs and blocks saved on the deal's workflow. Names and required information vary by template, but commonly include business information, individual information, prequalification details, bank data, discovery questions, and signed applications.
1. Open each Application tab in **Deal Progress**.
2. Review the information already saved on the deal.
3. Complete or correct the available fields.
4. Confirm that required blocks contain the information needed for the next stage.
### Upload application documents
Open **Documents** from the deal menu to upload and review files. This page shows required documents and the **Uploaded Documents** table.
### Collect signed applications
When the Application stage includes a **Signed Application** block:
1. Open the block and select the applicable owner.
2. To request a signature, optionally select a consent or contract template, then select **Generate New Link**.
3. To upload an existing signed application, select **Add Applications**, choose or drop the file, associate it with an owner and optional product, then select **Upload**.
4. Review completed documents in preview or list view.
Every owner must have a completed signed application before the Signed Application block is complete.
## Run Data Orchestration in Underwriting
Open the configured **Underwriting** stage. Workflow Live displays **Orchestration Outcome** separately from the provider or service tabs configured for the stage.
1. Select **Run Orchestration**.
2. Select an available published template.
3. Start the run.
4. Review the master status, service outcomes, errors, evaluated attributes, and run history in **Orchestration Outcome**.
5. Resolve any review or service-error outcome before continuing according to your organization's process.
After a run, the **Orchestration** control can provide actions such as **Pass-resume**, **Fail-resume**, **Re-run Last Condition**, **Restart Orchestration**, and **Run New Orchestration**.
The control can be unavailable while a run is processing or when the user, client, or stage lacks the required Data Orchestration access. See [Run Data Orchestration on a Deal](/lendflow-external/docs/manual-trigger-to-run-orchestration-within-a-deal) for result interpretation and recovery actions.
## Run Scorecards
Scorecards use a separate **Scorecards** stage. They evaluate information already stored on the deal and do not run Data Orchestration or retrieve new provider data.
1. Advance the deal to its **Scorecards** stage.
2. Open **Scorecards** or **Scorecard Groups**.
3. Select **Run All**, **Run Specific Scorecards**, or **Run Specific Scorecard Groups**. You can also use the run or rerun action on one row.
4. Review the points, status, risk tier, knockout result, and primary designation.
5. Select a result to review its detailed calculation.
The workflow must make finished scorecards or groups available on the stage, and the user must have permission to run them. See [Run Scorecards on a Deal](/lendflow-external/docs/how-to-run-a-scorecard-in-a-deal).
## Create and manage placements
Open the **Placement** stage. Its Workflow Builder configuration and the organization's [Lender Network](/lendflow-external/docs/lender-network) determine which funders, products, and submission methods are available.
### Create a placement
1. Under **Available Funders For Placement**, expand a funder.
2. Select one or more product rows.
3. Review the **Product**, **Submission**, **Workflow Builder Template**, and **Funder Product** selections.
4. Select **Submit**.
The destination Workflow Builder template and funder product must be available before submission. The supported submission method—Email, API, Manual, or Lendflow—depends on the funder configuration.
### Manage submitted placements
Use **Submitted Placements** to:
* Review and update the placement status.
* Add a decline reason, optional decline sub-reason, and description when declining.
* Resubmit application data when the restart action is available.
* Send additional documents when supported.
* Review the destination workflow status, sub-status, URL, and associated offers.
A placement must be **Approved** before an offer can be created from it. Select **Create Offer** on an approved placement. After an offer exists, use the **+** action to add another offer or open **Offer Details**.
## Create and manage offers
Open the **Offer** stage. The product's offer template determines the available offer fields, closing fields, and stipulations.
### Create an offer
* For a placement workflow, create the offer from an approved placement in **Submitted Placements**.
* For an eligible self-funded workflow without a Placement stage, select **Create Offer** in the Offer stage.
Then:
1. Select the offer product or template.
2. Complete **Offer Details**.
3. Select **Set Stips** and configure **Required Stips** when applicable.
4. Select **Save**.
### Manage offers
Use the Offer stage to:
* Select an offer row to review or edit its terms.
* Show or hide offers in the Borrower Platform.
* Change an offer's status individually or in bulk.
* Edit snapshot details, duplicate an offer, set a manual status, or delete an offer from its action menu.
* Drag funder cards to change their display order.
The applicant can select **Accept Offer** in the Borrower Platform, or an authorized internal user can update the offer status to **Accepted** in Workflow Live. See [Borrower Platform](/lendflow-external/docs/borrower-platform) for the applicant experience.
## Close the deal and confirm funding terms
Advance the deal to **Closing** after an offer is accepted. Only accepted offers appear in the Closing offers block.
1. Complete any remaining stipulations.
2. Select the accepted offer row.
3. Open the **Funding Details** tab.
4. Review or edit the final fields defined by the offer template.
5. Select **Confirm**.
Confirming Funding Details records the final closing terms. It does not accept the offer or move the deal to Funded.
When the workflow includes Checkout, use **Checkout Progress** to review completion and edit the deal-specific snapshot when permitted. See [Online Checkout](/lendflow-external/docs/online-checkout) for setup and applicant checkout behavior.
After closing work is complete, select **Submit to Funded** when Funded is the next configured stage. At least one offer must be accepted before Workflow Live allows this transition.
## Manage a funded deal
The **Funded** stage can display:
* **Offer Details**, containing the original accepted offer information.
* **Funding Details**, containing the final confirmed terms.
* **Funding Summary**, containing high-level funded information.
### Add funding transactions
Funding transactions are available under **Funding Summary** for funded **Line of Credit** and **ARLOC** offers.
1. Locate **Transaction History**.
2. Select **Add Transaction**.
3. For a Line of Credit, enter the draw amount, draw date, and any optional commission or accounting code.
4. For ARLOC, complete **Upload Invoice** with the invoice amount, dates, payment terms, optional commission or accounting code, and optional invoice file.
5. Select **Save**.
Creating a funding transaction records a draw or invoice after funding. It does not fund the deal or move it to another stage.
## Statuses and sub-statuses
Stages show the major steps in the workflow. Statuses and sub-statuses provide more detail about the deal's current state:
| Item | What it communicates |
| - | - |
| **Stage** | The major workflow step, such as Application or Underwriting. |
| **Status** | The current state of the deal within the configured workflow. |
| **Sub-status** | Optional additional detail for the selected status. |
The available statuses and sub-statuses come from the Workflow Builder template applied to the deal.
1. Open the deal and locate the status selectors beside the deal name in the header.
2. Select the workflow status.
3. If the selected status has sub-statuses, select the appropriate sub-status.
Changing the workflow status clears the previously selected sub-status. Select a new sub-status if one applies to the new status. Changing a status does not move the deal to another workflow stage.
**API alternative:** Use [Get Workflow Status](/api-reference/workflow-management/get-workflow-status) to retrieve the deal's configured choices, then [Update Workflow Status](/api-reference/workflow-management/update-workflow-status) to set its status and optional sub-status.
## Mark a deal as dead
Mark a deal as dead when it should no longer continue through Workflow Live. This is different from declining one placement or offer. The available Dead Statuses and Dead Sub-Statuses are configured for the current stage in Workflow Builder.
1. Open the deal and select **Mark As Dead** in the upper-right corner.
2. Select a **Dead Status**.
3. If the selected status has sub-statuses, select a **Dead Sub-Status**.
4. Optionally enter a note, then save the change.
After the deal is marked as dead, its selected Dead Status and Dead Sub-Status describe why it stopped. Users with the appropriate permission can select **Restore** to return the deal to the live workflow.
**API alternative:** Use [Decline Application](/api-reference/workflow-management/decline-application) to mark the deal as dead and [Revive Application](/api-reference/workflow-management/revive-application) to restore it.
## Assign users to a deal
Assign Onboarding, Processor, and Analyst users when a deal needs a clear owner for each responsibility.
1. In the Lendflow Dashboard, open the **Deals** tab in the left-side menu.
2. Select a deal.
3. Locate the user assignment selectors beside the deal name in the header.
4. Select the **Onboarding**, **Processor**, or **Analyst** assignment you want to update.
5. Search for and select the user. Select **None** when you need to remove an assignment.
The available assignment types and users depend on your role and organization configuration. Lendflow assignments are identified separately from your organization's assignments.
**API alternative:** Use [Update the Application's Assigned Users](/api-reference/workflow-management/update-the-applications-assigned-users-underwriter-analyst-etc). Send only the assignments you want to change. Use a user ID to assign a role or `null` to clear it.
## Deal Notes
Use deal notes to record information and action items on a deal. You can associate a note with a workflow stage and control who can see it.
### Create a deal note
1. Select the **Deal Notes** button in the deal header.
2. Enter the note.
3. Optionally select a workflow stage to associate the note with that stage.
4. Review the visibility setting, then submit the note.
**API alternative:** Use [Create Application Note](/api-reference/workflow-management/create-application-note) with `notable_type` set to `application`, the application ID in `notable_id`, and the note in `comment`.
### Control who can see a note
Before submitting a note, select its visibility:
* **Everyone** makes the note available to users who can access the deal.
* **Only Me** makes the note private to you.
* **Other Groups** lets you select an available audience. The groups shown depend on your role and organization.
## FAQ
Workflow Builder defines reusable workflow templates. Workflow Live is the configured experience on one deal under **Deal Progress**, where users review data, run available actions, and advance that deal.
No. The applied Workflow Builder template determines the stage names and order. Follow the stages shown on the deal.
Complete the current stage's required work, then select **Submit to \[next stage]** in the deal header. The action requires the appropriate permission and stage responsibility.
No. A stage determines the deal's position in the workflow. A status and optional sub-status describe its state without changing its stage.
Current and previous stages have a blue background. Future stages have a gray background.
Yes. Select any stage name across the top of **Deal Progress**. Viewing a stage does not advance the deal.
Confirm that the appropriate Underwriting or Scorecards stage exists, a published template is available there, no run is currently processing, and your user has the required permission.
The placement must be Approved before Workflow Live enables offer creation.
No. Confirmation records final closing terms. Advance the deal separately with **Submit to Funded** after the closing work is complete and an offer is Accepted.
The deal stops progressing through Workflow Live and records the selected Dead Status and optional Dead Sub-Status. Users with the appropriate permission can restore it.
Open the deal and use the assignment selectors beside the deal name. Select the Onboarding, Processor, or Analyst assignment, then search for and select the user.
No. A user must already have permission to access the deal before they can see a note on it.
## Next steps
Search deals and expand offer or placement details.
Configure the stages, tabs, blocks, and responsibilities used in Workflow Live.
Run an orchestration and respond to its outcome.
Run scorecards or groups and review their results.
Configure and review the applicant's closing checkout.
Follow the same deal lifecycle programmatically.