Non-renewal notice
How do we send a non-renewal notice with the reasons the state requires, within the state's days before expiration, and prove delivery?
Generate the notice from the decision and run the state's clock on it. When underwriting decides not to renew, Callvu classifies the policy (the state, the line, the policy's age and the permitted grounds under the state's rule), checks the decision against the grounds and the restrictions (the moratoria after a catastrophe, the limits on non-renewal for claims history or age), generates the notice with the state's required content (the specific reasons, the effective date, the right to request the reasons or to appeal where the state gives one, the availability of other coverage), sends it by the method the state recognizes within the required days before expiration with proof of mailing or delivery, and writes the notice, the proof and the date to the policy system.
In scopeSimpleCallvu moves: classify, write back
Last updated November 7, 2026.
The problem today
The notice gave thirty days in a state that requires sixty, so the policy renewed by operation of law.
Underwriting decides not to renew a policy. A letter is produced from a template, mailed, and the policy expires. The state required sixty days of notice, the specific reason, and a statement of the insured's right to appeal; the letter gave thirty, said the company had elected not to renew, and was mailed without proof. The insured complains, the department finds the notice defective, and the carrier is on the risk for another term.
State non-renewal notice rules set, by line, the days of advance notice (thirty, forty-five, sixty or more before the expiration date), the method of delivery and the proof required, the content (the specific reasons in most states, the effective date, the insured's rights), the permitted grounds for personal auto and homeowners after the policy's first term, and the restrictions (no non-renewal for a single claim, for age, for a catastrophe loss during a moratorium). The rules vary enough that the notice must be generated for the policy's state, not from one template.
A non-renewal is a decision the carrier may make; the notice is the state's condition for making it.
How it runs
From the requestto the system of record.
Underwriting records a decision not to renew a policy (from the renewal underwriting process or an inspection follow-up). Callvu opens the notice case on the policy.
- Underwriter
- Records the decision and the reasons; decides exceptions in the Decision Desk.
- Policyholder
- Receives the notice with the reasons and their rights; may request the reasons or appeal where the state provides.
- Agent
- Receives the copy the state or the agreement requires.
- Callvu
- Classifies, checks the grounds, generates the notice, sends with proof on the clock and writes back.
Classify the policy and the rule
The policy's state, line (personal auto, homeowners, commercial), term and renewal count, the expiration date and any moratorium in force classify the rule: the days of notice required, the delivery method and proof, the required content, the permitted grounds and the restrictions.
Check the decision against the grounds
The underwriter's reasons are checked against the state's permitted grounds and restrictions (a claims-history limit, a prohibition on non-renewal for age or a single not-at-fault claim, a catastrophe moratorium, a required offer of alternative coverage); a decision outside the grounds or inside a moratorium stops here and goes to the underwriter in the Decision Desk with the rule.
Generate and send on the clock
The notice is generated for the state with the required content (the specific reasons in the words the state accepts, the effective date, the insured's right to request the reasons or to appeal to the carrier or the department where the state gives one, the availability of other coverage or the residual market, the agent copy) and sent by the recognized method (first-class mail with a certificate of mailing, certified mail, or electronic delivery where the state and the insured's consent allow) no later than the required days before expiration, with the proof captured.
Write back
The notice, the version, the sending date, the method and the proof of mailing or delivery are written to the policy system against the policy, the agent copy is recorded, the policy's expiration is set to not renew, and a late or defective notice is flagged before expiration so the carrier can renew or re-notice rather than discover it afterwards.
Where it ends: The non-renewal rested on a permitted ground, the notice carried the state's content, went out by the recognized method inside the state's days with proof, and the policy system holds all of it. The Decision Trace shows the classification, the grounds check and any exception; the Audit Trace shows the generation, the sending and the proof with their times. The Callvu moves in this process are classify and write back.
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.
The handoff
Between the front doorand the back office.
The front door
The policyholder receives the notice with the reasons and their rights; a request for the reasons or an appeal comes back through the complaint process.
The back office
The underwriter records a decision; the notice, the clock and the proof are the process's; the policy system shows it.
The Decision Desk
- A decision outside the state's permitted grounds, inside a moratorium, or on a consumer report without the adverse action content goes to the underwriter in the Decision Desk with the rule and only renew, revise the grounds, or confirm with the required content.
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.
How many days of notice are required?
It depends on the state and the line, commonly thirty to sixty days before expiration; the process classifies the policy and sets the clock for its state.
Must the notice give reasons?
In most states, the specific reasons, plus the effective date, the insured's rights and the availability of other coverage; the notice is generated with the state's content from the underwriter's decision.
What if the notice is late or defective?
The policy stays in force until proper notice is given; the process flags a late notice before expiration so the carrier can renew or re-notice.
Related 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.