Skip to main content
A submission usually starts as an email. If the risk fits the program and the agency accepts the terms, Underflow carries the same record through binding, policy documents, and invoicing.
1

Intake

Underflow opens the file, preserves the source material, and extracts what arrived.
2

Clearance

Check duplicates, counterparty readiness, and completeness before underwriting begins.
3

Collection

4

Underwriting

Apply appetite, guidelines, and rating to produce eligible options.
5

Screening

Run required external risk scans, then screen sanctions before a quote letter or bind.
6

Proposal

Send the options and wait for the agency’s response.

Automation

Aurora takes a turn on a submission when something happens to it:
  • A new email arrives
  • A collection link ends
  • A quote is accepted
  • A person answers her question, hands the file back, or asks for a turn
  • A held action is rejected, or runs after being held
  • A reminder she set herself comes due
  • The renewal sweep opens a file for an expiring policy
Each turn reads the file against the program requirements and takes the next permitted action. If information is missing, Aurora asks for it. If the risk falls outside appetite, Aurora prepares a decision. If the submission is complete and eligible, Aurora rates it. Along the way she keeps the file’s gaps, risk assessment, coverage suggestions, and her own memo current, and ends the turn with her next reminder.

Human review

Your team enters through moments, approvals, takeover, or the rail. A moment asks for judgment. An approval authorizes one proposed action. Takeover puts the entire submission in Manual and stops Aurora’s file turns until hand-back. The rail is a conversation with Aurora about the file, working from the same record. The core model explains the record behind this flow: lifecycle status, handling mode, and the program that defines what is eligible.