Orchestration

What orchestration manages

• State: where the case is in the lifecycle (intake, readiness, rework, valuation, final offer, signing, disbursement).
• Tasks: what is required next, who owns it, due dates, and dependencies.
• Evidence: document slots, verification status, and version history (no silent overwrites).
• Sharing: permissioned exports to authorised parties with recorded receipts.
• Audit trail: key actions and changes recorded for accountability.

Rework handling (the part that usually breaks)

Rework requests are treated as structured tasks. Each rework item includes: what is requested, why it is requested, what evidence satisfies it, who must provide it, due dates, and a versioned response history. This reduces repeated back-and-forth and keeps outcomes defensible.

What operators and partners can see

• Case object: lifecycle status, milestones, and task queues.
• Consent receipts: what was authorised, when, and for which party.
• Evidence pack artifacts: controlled exports with versions.
• Event history: a traceable timeline of actions without leaking sensitive content.

Why it matters

• Fewer broken submissions and fewer last-minute surprises.
• Faster time-to-decision through higher first-time-right packaging.
• Lower operational cost per case through predictable workflows.
• Cleaner partner experience for banks, valuers, and other participants.