Architecture definition

Control Plane Architecture

A control plane governs how lending operations are executed: policies, workflows, evidence, and integrity controls. Modules deliver execution. The control plane standardizes decisions and governance across the lifecycle.

Control planes make change governable at enterprise scale

Enterprise lenders need to update rules, workflows, and controls without rebuilding every execution module or weakening accountability.

LL uses control planes to coordinate policy, workflow, evidence, and financial integrity across origination, servicing, recovery, and legal enforcement.

What a control plane does

Defines and enforces the operating rules of a domain, independent from UI channels and execution modules.

Governance responsibilities

  • Policy definition and versioning
  • Workflow orchestration and exception management
  • Evidence capture: who did what, when, and why
  • Integrity controls: reconciliation and posting rules

Operational outcomes

  • Consistent execution across teams and channels
  • Reduced manual handling and operational variance
  • Audit-ready visibility for compliance review
  • Controlled change management for regulated environments
Module-to-control-plane map

See which control responsibility sits above each module

A premium architecture view that links execution modules to their governing plane, control evidence, and stakeholder review path.

Module
Primary control plane
Control evidence
Primary review path
LOS

Intake, eligibility, approval routing, documentation.

Origination control plane
PolicyDecisioning
Approval evidence

Rule version, approval path, consent, and document trace.

Executive + architecture

Review policy ownership and onboarding controls before scale.

LMS

Schedules, interest, fees, allocation, payoff.

Servicing control plane
LifecycleIntegrity
Financial evidence

Reconciliation outcomes, posting health, and adjustment lineage.

Finance + operations

Assess servicing integrity and reporting confidence.

Collections

Queues, contact strategies, promises, agency execution.

Recovery operations plane
WorkflowStrategy
Action evidence

Case movement, next-best-action logic, and collector discipline.

Operations + compliance

Monitor queue health and treatment consistency.

Litigation

Case intake, court calendars, judgments, enforcement.

Legal enforcement plane
WorkflowEvidence
Legal evidence

Case chronology, approvals, orders, and cost traceability.

Legal + executive

Review exposure, timeline discipline, and recovery path.

How it connects to modules

Control plane governs. Modules execute. Data integrity validates. The control tower monitors.

Control-plane map (conceptual)
Policy + Workflow Control Plane Versioned rules · orchestration · evidence Control Planes Origination Servicing Recovery Legal Enforcement Execution Modules LOS · LMS · Collections · Litigation Channels: portal · partner APIs · back office Integrity + Oversight Reconciliation · GL posting integrity Audit trails · monitoring · compliance
Practical evaluation: assess policy versioning, audit evidence, reconciliation automation, and controlled change management.

Architecture and governance entities that connect this page to the broader control plane.

Why it matters

  • Clarifies platform boundaries for architecture, procurement, and governance review
  • Connects policy, execution, and accounting evidence across related pages
  • Helps executives and implementation teams navigate the operating model with less friction
Choose the next review path
Move from page-level detail to executive visibility, architecture fit, or module-by-module evaluation.