Know what a case or portfolio is worth before you commit capital.
Lifecycle · Stage 03 of 05

Deploy

Deployment is the act of committing capital under the terms underwriting produced, and the point where the first two stages either hold up against a live position or reveal that they did not.

01 Predict02 Underwrite03 Deploy04 Monitor05 Resolve

The Mechanism

Deployment looks operationally simple: a wire, a docket entry confirming the funding relationship where required, a servicing record establishing repayment terms. Operationally simple does not mean analytically simple. Deployment is the moment a hypothetical, priced position becomes a live exposure with an actual counterparty, an actual procedural posture, and an actual set of downstream events that will begin diverging from the median case the underlying models were trained on the moment the matter proceeds. The mechanism itself is a handoff: underwriting's priced terms become servicing's operating instructions, and the passport-style record established for the asset becomes the canonical reference point every subsequent stage checks against.

The handoff is where a well-run lifecycle and a poorly run one become visibly different, even though both produce the same wire transfer. In a well-run handoff, every term underwriting finalized is captured in a structured record before funds move; in a poorly run one, terms live in an email thread or a memo that servicing interprets after the fact, and any ambiguity in that interpretation becomes a dispute waiting to surface at resolution.

Inputs and Outputs

Inputs are the finalized underwriting terms and the fully resolved integrity record established before deployment. Outputs are the funded position itself, plus the baseline record, the passport, that captures the asset's state at the moment capital committed: the prediction it was priced against, the terms it was funded under, and the evidence that supported both. That baseline is what monitoring checks every subsequent update against, which is why an incomplete or unverified baseline at deployment corrupts every later comparison, not just the deployment decision itself.

The passport's minimum schema is deliberately comprehensive at this stage: identity, economic rights, case evidence, medical and provider data where applicable, servicing status, governance flags, and current scoring all populate together, rather than being assembled piecemeal after the fact when a question arises.

What Can Go Wrong

The primary risk at deployment is treating it as the end of diligence rather than the start of exposure. A position that was correctly priced at underwriting can still be poorly deployed if the baseline record is incomplete, if payment or servicing instructions are not independently verified, or if the passport record is not established with the completeness the standard's minimum schema requires. A second risk is specific to structures involving multiple parties or lien positions: deployment is where a payoff chain that looked clean on paper either holds or reveals a gap, and a funder that has not independently verified payment instructions at this stage is exposed to exactly the kind of settlement diversion and payoff fraud the standard's hard-stop framework is built to catch.

A third, easily overlooked risk is treating the passport as a one-time form rather than a living record. A baseline captured accurately on day one but never designed to accept updates is only marginally better than no baseline at all, since the entire value of the record depends on monitoring being able to write to it as the matter evolves.

A fourth risk applies specifically to multi-party structures: where a portfolio facility or a syndicated position spans several capital sources, deployment has to establish not just the asset's own baseline but the priority and allocation among the participating capital providers, and an ambiguity left unresolved at this stage tends to surface only when a dispute over proceeds makes it unavoidable.

How Criterica Implements This Stage

When an independent partner proceeds, the terms it sets are executed against what Criterica Intelligence's models supported, with independent verification of payment instructions and lien payoff chains built into the deployment process itself rather than treated as a post-funding cleanup step. Criterica Group's Legal Asset Passport schema is instantiated at this stage for every position that proceeds, capturing identity, economic rights, evidence, and scoring data in the standardized form the rest of the lifecycle depends on, so that monitoring in the next stage has a complete and trustworthy baseline to compare against.

This is the stage where the lifecycle's separation of functions becomes concrete rather than conceptual: the passport records which function produced each fact, the prediction from Intelligence, the terms from the independent capital partner, the verification from the execution process, so that accountability for each piece of the record is traceable to its source.

← UnderwriteLifecycle OverviewMonitor →

Discuss the Deploy Stage

Institutional buyers and capital partners evaluating the Regulated Outcome Lifecycle.

I am a

By sending, you agree to our privacy notice.