How an Assignment operates from intake through archive

Assignment created from lender input; validation workflow starts and missing or conflicted evidence parks the file for information.

GateUnchanged input must not loop the file back into validation.

Identity, duplicate and lender-configuration gates pass, then the dispatch-readiness checklist runs.

GateNo blocking hold or critical exception may be open.

Eligibility hard gates filter before ranking; the offer is delivered and acceptance is bound to a valid dispatch attempt.

GateSelected vendor must be eligible at the point of dispatch, not merely at shortlist time.

A qualifying First Action opens active work; check-ins, work sessions and stagnation detection keep the file moving.

GateTimers are durable and re-check current state before any side effect.

Location is a meaningful activity distinct from recovery; the recovery package must pass identity and verification gates.

GateConfigured evidence must pass before verification is recorded.

Current custodian and storage location are established and personal property handling is documented.

GateCritical custody issues must be resolved before lender direction is requested.

Verified, authorized lender direction drives transport or disposition; handoff is verified on completion.

GateNo conflicting hold may be active when direction is executed.

Operational outcome and evidence complete, then the ledger is reconciled against fee rules and exception controls.

GateBilling, payment and exception controls must all be satisfied.

Certification runs against operational and financial prerequisites; deficiencies route to a hold until remediated or formally excepted.

GateRequired certifications and Trial human review must pass.

Closure is requested, human-reviewed, and archived; authorized reopen requires a reason and a target workflow.

GateA human closes the file after final guards re-run. AI cannot.