ACORD Cancellation Form—How to Fill ACORD 35
Use this ACORD 35 field map to verify 4 essentials before submission: policy, effective date, reason, and authorized signature.
Key Takeaways
- ✓ACORD 35 documents an insured’s cancellation request; it is not a substitute for licensed coverage advice.
- ✓The 4 essentials to verify before submission are policy, effective date, reason, and authorized signature.
- ✓In many agencies, a CSR or account manager prepares the form after a licensed person confirms the servicing context.
- ✓Use your licensed ACORD source, agency management system, or carrier workflow instead of random public fillable PDFs.
- ✓Removing one vehicle from a multi-vehicle policy is usually an endorsement workflow, not necessarily a full-policy cancellation.
- ✓Sera can help collect cancellation intake after hours or during lunch, but licensed staff still decide what to send and update the agency management system.
Connect Twig with Gmail
Autonomous AI support for email via Gmail.
An ACORD cancellation form is usually ACORD 35, the Cancellation Request and Policy Release used to document an insured’s request to cancel a policy on a requested effective date. Use this ACORD 35 field map to verify 4 essentials before submission: policy, effective date, reason, and authorized signature.
ACORD editions, carrier procedures, premium-finance rules, and state requirements vary. Use the current licensed form instructions and the carrier’s workflow. I’m writing this as an operator’s reference for agency owners, principals, CSRs, and producers, not as legal advice or a substitute for your carrier’s instructions.
If you run an independent P&C agency, this is the kind of form that looks simple until Tuesday at 4:47 p.m., when the insured says they sold the only vehicle last week, the lienholder is still listed, and the producer is asking whether there is replacement coverage. The form is only half the work. The real work is clean intake.
TL;DR: The ACORD cancellation form most agencies are looking for is ACORD 35, used when the insured requests policy cancellation and releases the carrier as of a stated effective date. Verify the policy, effective date, reason, and authorized signature before submission. Do not rely on random public ACORD 35 fillable PDFs; use your licensed ACORD source, agency management system, or carrier workflow.
Key takeaways:
- ACORD 35 documents the insured’s cancellation request; it is not a substitute for licensed coverage advice.
- The 4 essentials to verify are policy, effective date, reason, and authorized signature.
- In many agencies, a CSR or account manager prepares the form after a licensed person confirms the servicing context.
- Replacement coverage, lender or lienholder interests, return premium expectations, and timing should be clarified before sending.
- Removing one vehicle while the policy stays active is usually an endorsement workflow, not a full ACORD 35 cancellation.
- An AI front desk can collect intake and route the request, but a licensed person should decide the next action.
What is the ACORD cancellation form used for?
The ACORD cancellation form is used to document that the insured requested cancellation and to send that request to the carrier with the policy details, requested date, reason, and signature.
In agency shorthand, “ACORD cancellation form” usually refers to ACORD 35. You may also hear staff say “ACORD cancellation,” “cancel ACORD,” or “ACORD 35 fillable” when they are trying to find the same cancellation request form.
The form is commonly part of the workflow when an insured:
- Sold the only insured vehicle and requests cancellation of the auto policy. If other vehicles or coverages remain, use the carrier’s endorsement workflow instead of treating the request as a full-policy cancellation.
- Sold a home or property and no longer needs that policy.
- Moved coverage to another carrier.
- Closed a business location or ended operations.
- No longer needs a specific policy.
- Requests flat cancellation, if allowed by carrier procedure and applicable state rules.
- Wants cancellation on a future date.
A good agency treats this as a servicing workflow, not a clerical errand. Before the form goes out, the CSR should understand what is being canceled, when, why, and whether anyone else has an interest in the policy.
Who fills out ACORD 35 and who signs it?
In many agencies, a CSR, account manager, or producer prepares ACORD 35, while the named insured or authorized signer signs the cancellation request according to the carrier’s requirements.
In a small agency, the principal may still review certain cancellations: commercial accounts, high-premium accounts, policies with open claims, financed premiums, or accounts with a history of disputes. In a larger agency, the front desk gathers the request, the CSR prepares the form, and a licensed account manager reviews it before it goes to the carrier.
A workable division of responsibility is:
| Step | Usually handled by | What to confirm | Why it matters |
|---|---|---|---|
| Intake call or email | Front desk, CSR, or producer | Caller identity, policy, requested date, reason | Prevents sending the wrong policy or date |
| Coverage context | Licensed CSR, account manager, or producer | Replacement coverage, sale date, lender, claim status | Helps avoid uninsured gaps and file disputes |
| Form preparation | CSR or account manager | Insured name, carrier, policy number, effective date | Reduces carrier follow-up |
| Signature collection | CSR or account manager | Signer authority and date signed | Carrier procedures may require specific authority |
| Submission and diary | CSR or account manager | Carrier receipt, cancellation confirmation, return premium communication | Keeps the file defensible |
My firm recommendation: do not let a general receptionist promise that a cancellation is “done.” They can say, “I’ll get this to the service team today,” but cancellation is not complete until the agency follows its carrier workflow and documents the file.
How do you fill out ACORD 35?
To fill out ACORD 35, capture the agency and policy identifiers first, then the requested cancellation date and reason, then the insured’s signature using the current licensed form instructions.
The exact layout can vary by edition and system, so use this as an operator field map rather than a replacement for ACORD instructions or carrier guidance.
| ACORD 35 area | What to enter | Operator note |
|---|---|---|
| Date | Date the form is prepared | This is not automatically the cancellation effective date |
| Producer or agency | Agency name, address, contact details | Should match your agency record |
| Company | Carrier name | Use the writing company required by your workflow |
| Named insured | Exact named insured on the policy | Do not casually shorten LLCs, trusts, or DBA names |
| Policy number | Full policy number | Include prefixes and suffixes if shown in the AMS or carrier portal |
| Line of business | Auto, homeowners, BOP, GL, workers comp, or other line | Make clear what policy is being canceled |
| Requested cancellation effective date | Date requested by insured | If time is required, follow the carrier’s standard |
| Reason for cancellation | Rewritten, sold, no longer needed, duplicate, request of insured, or other factual reason | Keep it brief and accurate |
| Release or request wording | Follow the wording on the current licensed form | Make sure the insured understands they are requesting cancellation |
| Lienholder, mortgagee, or other interest | Any listed party, if applicable | Check the dec page and carrier workflow for notice requirements |
| Signature | Named insured or authorized signer | Match authority to the policyholder type and carrier procedure |
| Remarks | Supporting context | Use for sale date, replacement policy reference, or special instructions when appropriate |
Before the CSR sends the form, use this four-question check:
- Are we canceling the correct policy, not just one vehicle or one coverage part that should be endorsed?
- Is the effective date what the insured actually requested?
- Is the reason factual and documented?
- Does the signer have authority under your agency and carrier workflow?
If the answer to any of those is unclear, pause and call the insured.
ACORD 35 filled example for a typical agency file
A filled ACORD 35 should read like a clean audit trail: who asked, what policy, what date, what reason, and who signed.
Here is a fictional example you can compare against your workflow. Do not copy it as legal language; use your licensed form, current instructions, and carrier rules.
| Field | Example entry |
|---|---|
| Date prepared | 03/12/2026 |
| Agency | [Agency Name], 214 Market Street, Columbus, OH 43215 |
| Carrier | Example Mutual Insurance Company |
| Named insured | Jordan Lee |
| Mailing address | 18 Cedar Lane, Columbus, OH 43215 |
| Policy number | PAP 1234567 02 |
| Line of business | Personal Auto |
| Requested cancellation effective date | 03/15/2026, time per carrier workflow |
| Reason | Insured reports the only covered vehicle was sold on 03/10/2026 and requests cancellation of the auto policy |
| Replacement coverage | Not applicable; insured reports that the only covered vehicle was sold. Licensed staff to confirm the appropriate policy action. |
| Lienholder | None listed on agency record |
| Remarks | Insured called on 03/12/2026 and confirmed no remaining vehicles on policy. Identity verified using agency procedure. |
| Signature | Jordan Lee |
| Signature date | 03/12/2026 |
Notice the distinction: this example is a full-policy cancellation request because the insured reports that the only covered vehicle was sold. If Jordan had two vehicles on the policy and sold one, I would not treat that as an ACORD 35 cancellation by default. I would route it through the carrier’s endorsement workflow.
For a small commercial account, I would add more context in the file note, not necessarily all on the form: who requested the cancellation, signer title, whether operations ceased or coverage moved, and whether certificates of insurance had been issued to third parties.
If your team handles commercial intake often, pair this with our related field map for the ACORD Commercial Insurance Application 125. Different form, same discipline: clean fields beat heroic back-and-forth.
What should staff say when a client asks to cancel a policy?
Staff should acknowledge the request, avoid off-the-cuff coverage advice, and collect the facts a licensed person needs to process the cancellation correctly.
Here is a simple script I would be comfortable giving to a front desk or newer CSR:
“Absolutely, I can help get the cancellation request started. I’ll need to confirm the policy, the date you want cancellation to take effect, and the reason for the request. A licensed member of our service team will review it before anything is sent to the carrier, because cancellation can affect coverage, lenders, certificates, and refunds.”
Then collect:
- Caller name and relationship to the policyholder
- Best callback number and email
- Named insured
- Policy number, if they have it
- Policy type
- Requested cancellation date
- Reason for cancellation
- Whether property or the only insured vehicle was sold
- Whether replacement coverage is in place, if applicable
- Whether there is a lender, mortgagee, lessor, certificate holder, or premium finance company
- Whether there is an open claim
- Whether they need proof of cancellation
I prefer that agencies avoid phrases like:
- “You’re canceled.”
- “Coverage ends today.”
- “You’ll definitely get a refund.”
- “You don’t need that policy anymore.”
Those sentences create unnecessary risk. Safer wording is: “We’ve received your cancellation request and our service team will confirm the next step with the carrier.”
Common ACORD cancellation mistakes and safer fillable workflow
ACORD cancellation delays often start with bad intake: wrong date, missing signature, unclear authority, or a mismatch between the form and carrier requirements.
Here are the mistakes I would train against first:
| Mistake | What can happen | Better process |
|---|---|---|
| Using the date prepared as the cancellation date | Carrier or staff may process the wrong requested effective date | Ask the insured for the requested cancellation effective date every time |
| Missing insured signature | The carrier workflow may require follow-up before processing | Collect the required signature before submission, unless the carrier workflow says otherwise |
| Wrong named insured | Entity policies and personal names get mixed | Copy the named insured exactly from the policy declarations |
| Treating a vehicle removal as policy cancellation | The agency may send the wrong request | If the policy remains active, use the endorsement workflow |
| Vague reason | Accounting or underwriting may ask follow-up questions | Use a factual reason: rewritten, sold, duplicate, request of insured, operations ceased |
| Ignoring mortgagee, lienholder, or premium finance context | Notice or documentation requirements may be missed | Check the dec page, finance status, and carrier requirements before sending |
| Assuming return premium | Client expects money the carrier may not owe | Say the carrier will determine any return premium |
| No file note | Future dispute has no timeline | Save call notes, email, signed form, submission proof, and carrier confirmation |
| Random PDF from search | Outdated or unofficial form creates cleanup work | Use licensed ACORD forms, AMS output, or carrier-approved forms |
The “random PDF” point matters. Some current search results for ACORD cancellation or ACORD 35 fillable pages look like generic download farms. Even if a PDF opens, that does not make it the right version, a licensed copy, or acceptable to your carrier. A public PDF may be outdated, unofficial, or outside your agency’s approved document-handling process.
A safer fillable workflow is:
- Staff receives the cancellation request.
- Staff verifies identity using your agency’s normal process.
- Staff gathers policy, requested effective date, reason, signer, and replacement coverage context.
- Licensed staff reviews whether any coverage, lender, claim, certificate, or premium-finance issue needs attention.
- CSR prepares ACORD 35 from an approved source.
- Insured signs using your accepted signature process.
- CSR sends to the carrier through the required channel.
- CSR diaries the file for carrier confirmation.
- Staff saves the signed form, submission proof, confirmation, and any return premium communication.
That is slower than grabbing the first PDF from Google, but it is faster than fixing a disputed cancellation six months later.
For broader service workflow cleanup, I wrote about the interruption problem in Insurance CSR Workflow—6 Steps That Cut Interruptions. Cancellation requests are a perfect example: one missing fact can turn a short task into three callbacks.
Where Sera fits in an ACORD cancellation workflow, and where she does not
Sera can help with cancellation intake, missed calls, and routing, but she should not decide whether a client should cancel coverage or submit ACORD 35 to a carrier.
Twig makes Sera. Sera is an AI front desk for local businesses: she answers every phone call, text, web chat, email and WhatsApp message, 24/7. Appointment booking is included on Growth and above. For an independent insurance agency, the practical use case is not “AI completes ACORD forms.” It is that Sera can reduce the chance that a cancellation request sits in voicemail at lunch, after hours, or while the CSR is on another call.
Where Sera can help:
| Cancellation workflow task | Sera can help? | Notes |
|---|---|---|
| Answer after-hours cancellation calls | Yes | She can capture the request and contact details |
| Ask intake questions from your script | Yes | Policy number, requested date, reason, callback info |
| Send the transcript to staff | Yes | Every conversation is logged with a full transcript |
| Escalate urgent or licensed questions | Yes | Your agency sets escalation rules; Sera escalates with the conversation attached |
| Update EZLynx, HawkSoft, Applied Epic, AMS360, or QQCatalyst | No | Sera has no direct integration with agency management systems |
| Bind coverage or quote premium | No | Licensed questions go to agency staff |
| Give coverage advice | No | She should route those questions to a person |
| File claims with carriers | No | She does not file claims with carriers |
| Submit ACORD 35 to the carrier | No | Your licensed workflow should control submission |
If your agency gets cancellation calls after hours, the biggest win is often a cleaner handoff: transcript, requested date, policy clues, reason, and callback information in one place. Sera can send intake to supported destinations including Gmail, HubSpot, Salesforce, and Slack. Most businesses are live in under 30 minutes by forwarding the phone line or adding website chat.
You can read more on our AI receptionist for independent insurance agencies page. If you are comparing cost to an answering service or missed-call process, Sera pricing starts at $49 per month, with a 15-day free trial, voice included, and no credit card.
Limits matter here. Twig is SOC 2 Type II certified, but Twig is not HIPAA compliant and does not sign BAAs. Appointment booking, missed-call text-back, live transfers, and multi-language conversations are included on the Growth plan and above, not on Starter.
Next step: turn ACORD 35 into a checklist, not a scavenger hunt
If your team handles more than a few cancellations a week, make ACORD 35 a checklist in your service process.
Start with one shared intake script, one approved form source, and one rule: no cancellation request gets submitted without the policy number, requested effective date, reason, and authorized signature path. Then decide what your front desk can collect and what must go to a licensed CSR.
If missed calls are where cancellation requests fall through, try calling Sera’s live demo line at (650) 795-7838 or review what an AI front desk is before you change your phone workflow.
Get your own AI Receptionist now
Free 15-day trial · From $49/mo · No credit card
Frequently Asked Questions
How do you fill out an ACORD 35 cancellation form?
Start with the agency, carrier, named insured, policy number, line of business, and requested cancellation effective date. Then enter the cancellation reason, follow the current licensed ACORD 35 instructions for the release and signature areas, and submit through the carrier’s required workflow. A licensed CSR, account manager, or producer should review the request before it goes out.
What is an ACORD 35 form used for?
ACORD 35 is the Cancellation Request and Policy Release form. Agencies use it to document that an insured requested cancellation of a policy and to communicate the requested effective date and reason to the carrier. Carrier, state, premium-finance, and form-edition requirements can vary.
Is there an ACORD 35 fillable PDF?
You may see public search results for an ACORD 35 fillable PDF, but an agency should use a licensed ACORD source, agency management system, or carrier-approved workflow. A public PDF may be outdated, unofficial, or outside your agency’s approved document-handling process. Treat the form as controlled insurance documentation, not a generic download.
What is an ACORD 37?
ACORD 37 is the Statement of No Loss. It is generally used to document that no loss occurred during a stated period, often in connection with reinstatement or a lapse in coverage. It is not the standard form for an insured’s policy-cancellation request; that is ACORD 35.
Does submitting ACORD 35 cancel a policy immediately?
Submitting ACORD 35 documents and transmits the insured’s cancellation request, but the agency should still track carrier processing and confirmation. Do not tell the insured the policy is canceled until your workflow and the carrier’s response support that statement. Save the signed request, submission proof, and carrier confirmation in the file.
Related Pages
Weekly AI CX insights
How leading support teams deploy autonomous AI. One short email a week.
Related Articles
ACORD Commercial Insurance Application 125—Field Map
Map 7 ACORD 125 sections, see a worked contractor example, and use an 8-question intake script to reduce CSR and producer rework.
18 min readACORD 25 Field Map—Example and 8 Mistakes
Map every ACORD 25 section, review a filled subcontractor example, and catch 8 errors before a certificate leaves the agency.
18 min readInsurance CSR Workflow—6 Steps That Cut Interruptions
Use this 6-step insurance CSR workflow to separate intake from licensed work and route COIs, ID cards, endorsements, and FNOLs clearly.
16 min read