Adverse underwriting decision notice

How do we send the right adverse underwriting notice, with the reasons the state and the FCRA require, every time an application is declined or rated up, and prove it was delivered?

Generate the notice from the decision instead of writing it afterwards. When an underwriting decision declines, rates up, reduces coverage or terminates, Callvu classifies the notice required by the state, the line and the decision basis (a consumer report, a medical record, an inspection, a rule), assembles the specific reasons in the words the state permits, adds the FCRA content where a consumer report contributed and the state's privacy act content where an adverse underwriting decision rule applies, delivers it in the applicant's chosen channel inside the state's period, records the delivery, and writes the notice and its reasons to the policy system.

In scopeSimpleCallvu moves: classify, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The declination letter said 'underwriting reasons' and the state's examiner asked for the specific ones in every file from the last three years.

Today, without Callvu

An underwriter declines or rates up an application and a letter goes out from a template. The template says the decision was based on underwriting guidelines. The reasons that would satisfy the state and the FCRA, and that the applicant could act on, are in the underwriter's notes. The letter is mailed to the address on the application that the applicant has since left; there is no delivery record.

Adverse underwriting notices are governed by several rules at once: the FCRA when a consumer report contributed, the state insurance information and privacy protection act in the states that adopted the NAIC model (which defines an adverse underwriting decision and requires the specific reasons in writing or the right to them), the state's declination and surcharge notice statutes by line, and the carrier's own timeliness standards. The content depends on the basis of the decision, which the decision record already holds.

A notice assembled from the decision is specific by construction.

How it runs

From the requestto the system of record.

An underwriting decision is recorded that declines, rates up, reduces or restricts coverage, or terminates an application or policy. Callvu opens the notice from the decision.

Applicant or policyholder: Receives the notice in their chosen channel with the reasons and their rights.
Underwriter: Confirms the reasons where the rules require a person to, in the Decision Desk.
Callvu: Classifies the notice, assembles the reasons and the required content, delivers, records and writes back.

Classify the notice
The decision type (declination, rate-up, reduced coverage, cancellation or non-renewal), the line, the state and the basis (consumer report, medical information, inspection, a rule) classify which notices apply: the FCRA adverse action content, the state's adverse underwriting decision notice under the privacy act, the line's declination or surcharge notice, and the period for delivery.
Assemble the reasons
The specific reasons are taken from the decision record (the report item, the condition, the finding, the rule) and rendered in the words the state permits; the FCRA content (the reporting agency's name and contact, that it did not make the decision, the right to a free report within sixty days and to dispute) is added where a report contributed; the state's privacy act content (the right to the specific reasons and to access and correct information) is added where it applies; a reason the rules require a person to confirm goes to the underwriter in the Decision Desk.
Deliver on the clock
The notice is delivered in the channel the applicant chose and consented to (electronic or mail), inside the state's period from the decision, and the delivery is recorded with the time and the method; a bounced or undeliverable notice is re-sent by the next method before the period ends.
Write back
The notice, its reasons, the delivery record and the FCRA and state content are written to the policy system as the system of record against the application or policy, so an inquiry, a complaint or an examination finds the notice with its proof.

Where it ends: Every adverse decision produced the notice the state and the FCRA require, with specific reasons taken from the decision, delivered inside the period with proof, and on the policy system. The Decision Trace shows the classification and the reasons; the Audit Trace shows the delivery and any re-send.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

FCRA adverse action (15 USC 1681m): An adverse action in connection with insurance underwriting based in whole or in part on a consumer report requires notice to the consumer with the name, address and telephone number of the consumer reporting agency, a statement that the agency did not make the decision and cannot explain it, and the consumer's right to a free copy of the report within sixty days and to dispute its accuracy; where a credit-based insurance score was used, the state's rules add the key factors.
State adverse underwriting notice rules (NAIC Insurance Information and Privacy Protection Model Act #670 as adopted, and state declination and surcharge notice statutes): In the adopting states, an adverse underwriting decision (declination, termination, placement with a residual market or a higher-rated company, a charge above the standard rate) requires written notice with the specific reasons or a statement of the right to them, the right to access and correct recorded personal information, and the summary of rights; line-specific statutes set the period (commonly fifteen to thirty days) and the content for auto and property declinations and surcharges.
State electronic delivery and e-signature rules: A notice may be delivered electronically only with the recipient's consent under the state's electronic transactions law, and the carrier must keep the delivery record; mail remains the default where consent is absent.

Company policies

The notice is generated from the decision record; a free-text letter is never sent.
Reasons are specific: the report item, the condition, the finding or the rule, in the words the state permits.
Delivery is in the consented channel inside the state's period, with a recorded time and method and a re-send on failure.
The policy system is the system of record for the notice and its proof.

Controls

Notice classification by decision, line, state and basis.
Reason assembly from the decision record.
FCRA and state content added by rule.
Decision Desk confirmation where a person must confirm.
Delivery in the consented channel with the record.
Policy system write.

Clocks and deadlines

Notice delivery: Inside the state's period from the decision by line, commonly fifteen to thirty days, tracked from the decision's time.
FCRA free report right: The consumer's sixty days from the notice, stated in it.
Re-send on failed delivery: By the next method before the state's period ends.

Documents and checks

The decision record and its basis
The notice classification
The notice with the specific reasons and the required content
The delivery record
The policy system entry

In the Decision Trace

The notices required and why.
The reasons and their source in the decision.
Any underwriter confirmation and the person.

In the Audit Trace

The notice generation with time.
The delivery and any re-send with method and time.
The write to the policy system.

The handoff

Between the front doorand the back office.

The front door

The applicant's chosen channel; the applicant can reply from the notice to request the specific reasons or the report.

The back office

Underwriters confirm reasons only where a rule requires it; compliance finds every notice with its proof on the policy system.

The Decision Desk

A reason the rules require a person to confirm, or a decision with no recorded basis, goes to the underwriter in the Decision Desk with the decision record and only confirm the reasons, correct the basis, or withdraw the decision.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

Phoenix put more than 100 processes live in under 3 months.

Across Callvu customers

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Questions

What buyers ask next,answered plainly.

What counts as an adverse underwriting decision?

A declination, a termination, a rate above the standard, placement with a residual market or a higher-rated company, or reduced coverage, under the state's privacy act and the FCRA where a report contributed; the classification applies the right notices.

Where do the reasons come from?

From the decision record itself: the report item, the condition, the finding or the rule, rendered in the words the state permits.

How is delivery proven?

The notice is delivered in the consented channel inside the state's period, the time and method are recorded, and the record is written to the policy system.

Related processes

Driving and loss history discrepancy review Non-renewal notice Life underwriting evidence collection Underwriting referral and approval Try it in the sandbox All insurance processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.