> ## Documentation Index > Fetch the complete documentation index at: https://docs.useunderflow.com/llms.txt > Use this file to discover all available pages before exploring further. # Underwrite and quote > Apply program appetite, produce options, and send a proposal. Once a file has enough information, Aurora applies the selected program and decides whether to decline, refer, or quote. Every consequential step follows the autonomy policy for its action type. ## Turns Aurora works a file in turns. She takes one when something happens to the file: mail arrives, a collection link ends, a quote is accepted, a person answers her question or hands the file back, a held action is rejected or later runs, a reminder she set herself comes due, or someone asks from the rail. The renewal sweep can also open a file for an expiring policy and request its first turn. A turn ends with her next reminder, or with something named she is waiting on, and the Desk lists files with no wake scheduled. Each turn starts from a briefing built from the record: the application with its conflicts and sources, the open gaps, the correspondence and what is new in it since her last turn, any letter of hers waiting for approval, her memo on the file, her earlier turns, and the questions she has open with the team along with their replies. She writes back to the record: * **Gaps**: what the program still needs, what should be confirmed, and what the underwriter wants clarified. * **Risk assessment**: the overall risk level and complexity, key findings, exposures, positive factors, concerns, and a recommendation. It is rewritten as the file changes. * **Suggestions**: coverage the risk calls for that the file did not ask for. Each carries a rationale and a relevance, and the underwriter accepts it or sets it aside on the file page. A decided suggestion is not offered again. * **Memo**: her working notes on the file, rewritten as her picture of it changes, which the next turn reads first. The turn then takes the next permitted action, writes the letter the file is owed if one is, and sets its own reminder for when to look again. Every turn is listed under **Turns** on the file page with what woke it and what she did; the whole conversation is the file's thread. The underwriter works from the same record. A question asked in the rail on the file is a turn on that file, answered from the same briefing, and a gap, suggestion, or assessment written in conversation is what the next turn sees. A newer letter of hers to the same person replaces one still waiting for approval, so the queue never holds two of hers to one reader. When a turn needs the team, Aurora asks under **Decisions**. A reply by mail to that question reaches her whole on her next turn, and she closes the question herself with the guidance she took from it; a reply that asks something back gets an answer, not a closed question. ## Appetite and declines Each program defines the classes, limits, and states it writes, plus the conditions that require referral or declination. Business outside the box gets a proposed decline that states its reason, and the decline itself follows the approval policy before anything is sent. ## Rating Rating runs against the program's rate tables. A quote can carry several sibling options, such as different limits or retentions presented side by side. Each option itemizes: * Premium * Surplus lines tax * Stamping fee * Coverage terms * Required subjectivities See [Surplus lines](https://docs.useunderflow.com/controls/surplus-lines.md) for the state controls behind taxes and fees. ## External risk scanning Some programs require consented ONYPHE remote service and vulnerability checks. Aurora can request fresh scans after the application records consent and usable domains. The scan writes observed findings back as application answers, leaves unsupported findings unknown, and can affect the technical score, rating, subjectivities, referral, or declination. There is no operator scan button or dedicated scan-status screen. A completed report is best-effort and may be available to Aurora even when it is not linked on the file page. See [External risk scanning](https://docs.useunderflow.com/underwriting/external-risk-scanning.md). ## Subjectivities Subjectivities are conditions that must be satisfied before or shortly after binding, such as a signed application or current loss runs. Each subjectivity is tracked on the file. When a document satisfies it, that document can be attached as evidence. Blocking subjectivities prevent bind. Nonblocking subjectivities remain visible after bind until they are closed. ## Proposal The proposal action sends a document with the options, terms, and subjectivities. The file moves to Proposed and waits for the agency. If the agency goes quiet, Aurora follows up when she judges it right, in a letter she writes, and sets herself a reminder to look again; the file page lists the follow-ups sent. If the terms change, withdrawing the quote closes the old offer before a replacement is sent. When the agency accepts an option, the file moves to [bind and policy paper](https://docs.useunderflow.com/underwriting/bind-and-issue.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.