> ## Documentation Index
> Fetch the complete documentation index at: https://docs.amlok.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow Guide

> How data supports Verify, Underwrite, Fund, Monitor, Investigate, and Re-underwrite.

## Verify

| Property | Definition |
| - | - |
| Trigger | Application or applicant onboarding |
| Inputs | business; person; consent; document |
| Work performed | Registry, ownership, identity, screening and evidence checks. |
| Outputs | verification; verification\_check; screening\_match; requirement |
| Decision boundary | Unresolved checks and missing documents remain explicit. |

## Underwrite

| Property | Definition |
| - | - |
| Trigger | Separately requested full underwriting |
| Inputs | application; bank records; financial statements; liabilities; collateral |
| Work performed | Compute supported attributes and apply the institution policy. |
| Outputs | attribute; risk\_snapshot; decision |
| Decision boundary | Separate recommendation from the institution decision; preserve evidence snapshot. |

## Fund

| Property | Definition |
| - | - |
| Trigger | Institution approves and executes funding |
| Inputs | Approved application, conditions and executed documents |
| Work performed | Record resulting contract, facility, collateral and repayment schedule from lender system. |
| Outputs | loan; credit\_facility; installment; guarantee |
| Decision boundary | Funding execution is outside the read/assessment API. |

## Monitor

| Property | Definition |
| - | - |
| Trigger | Funded borrower or active exposure |
| Inputs | Baseline snapshot; active connections; consent; monitor rules |
| Work performed | Refresh permitted evidence and compare comparable windows. |
| Outputs | attribute; risk\_snapshot; alert |
| Decision boundary | Alerts identify changes that may require institution review. Data outages generate coverage/freshness issues, not an assumed improvement. |

## Investigate

| Property | Definition |
| - | - |
| Trigger | Suspicious evidence, screening match or related-party signal |
| Inputs | screening\_match; relationship; document; transactions; alerts |
| Work performed | Analyze permitted evidence, compare candidate matches and explain risk findings. |
| Outputs | Risk findings; supporting evidence; reviewed relationship or screening conclusions |
| Decision boundary | A possible match is not a confirmed match. The institution reviews the evidence and owns any intervention or borrower outreach. |

## Re-underwrite

| Property | Definition |
| - | - |
| Trigger | Monitor identifies a policy-defined material change |
| Inputs | Current and baseline snapshots plus updated borrower evidence |
| Work performed | Signal reassesses risk using the existing baseline and new evidence, preserving the original assessment. This is included in Signal and does not trigger or charge another Insights underwriting. |
| Outputs | workflow\_run; decision; new risk\_snapshot |
| Decision boundary | Never overwrite the original assessment; credit-limit action remains institution controlled. |

## Institution intervention

AMLOK provides assessments, alerts, and supporting evidence to help your institution decide when to intervene. Webhooks deliver these signals to your registered systems. Your institution handles borrower communications and follow-up in its own systems.

## Product scope

Verification, lien searches, calculations and investigations are included stages of Insights or Signal. Stage requests require an authorized `processing_context`; they are not independently priced products. A Signal change-driven reassessment stays within its paid monthly period. Read [products and endpoint scope](https://docs.amlok.io/api-reference/products-and-endpoints.md) for the complete mapping.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.