Phase 1: Eliminating "Not-Verified" Policy Statuses

A plan for franchisors to get every franchisee's insurance on file in the RMS, using the Not Verified filter on the Franchisees list.

Written By Wade Millward (Super Administrator)

Updated at October 27th, 2026

Expected outcome

This plan helps you, as a franchisor, make sure every franchisee has at least uploaded their insurance documentation (moving them out of "Not Verified"), and then work on improving compliance for those who are "Non-Compliant." It outlines a clear pathway using the RMS, along with potential consequences for non-compliance, drawing on what has worked for other brands.

The fastest results come from brands that run the full launch sequence: announcement email, Rikor reminders, a mandatory all-owners meeting, a deadline and a one-on-one call with every owner. AdvantaClean, a Homefront Brands company, went from no visibility to 100% of locations with insurance on file and an 80% average compliance score in six weeks this way. See Initiating Franchisee Insurance Compliance.

Phase 1: Eliminating "Not Verified" policy statuses

1. Set clear goals for verification

  • Monitoring: Use the RMS to see which franchisees have not uploaded their insurance documentation. They show a Policy Status of Not Verified: no required policy is on file for them yet.
  • Open Franchisees, click the Policy Status filter and choose Not Verified. The number next to the option tells you how many locations match. On Analytics, the Not Verified tile opens the same list.
  • Goal setting: Reach 0 "Not Verified" franchisees within six weeks of launch.
    • Example: "By (date), every location must have its insurance documentation uploaded for verification."

2. Communication strategy for "Not Verified" franchisees

  • Automated outreach: When your brand has policy reminders turned on, the RMS sends Not Verified franchisees automatic reminder emails with a button to upload their certificate. Ask Rikor if you're not sure they are on. Reinforce this by telling franchisees why uploading their documentation matters: until they do, the brand can't confirm they are insured.
  • All-owners meeting: Cover the program at a meeting every owner is required to attend, while the reminders are running. Explain why, show the email they will receive and state the deadline.
  • One-on-one calls with every owner: Have a brand leader who owns the franchisee relationship (brand president, field business coach or similar) call each owner. Do this for every owner, not only the ones who are behind. Owners act on something new when someone they know asks them directly.
  • Weekly check-ins: Each week, check the Not Verified list and follow up by phone or email with anyone still on it until it reaches 0.

3. Educational support

  • Training materials: Give franchisees guides or videos on how to upload their documents to the RMS, such as the How to Upload a COI article.
  • Compliance reminders: Remind franchisees that a "Not Verified" policy status means the brand has no proof of their coverage, which can harm their business and their relationship with the franchisor.

4. Target completion date

  • Completion deadline: Set a hard deadline for franchisees to move out of "Not Verified" and announce it in the email, the all-owners meeting and the one-on-one calls.
  • Incentives: Depending on the needs of your organization, you may need incentives to reach the adoption goals you set by the completion date.

How this protects your brand

Monitoring shows you where a franchisee's insurance falls short. The way to close those gaps for good is to have franchisees insured right from the start. Franchisees insured through Rikor get coverage built to your brand's requirements by a dedicated Rikor consultant, and with monitoring on they're 93.3% compliant, against 48% for franchisees insured elsewhere. Make sure your brand's Rikor link is in your franchisee onboarding: Add Rikor to your franchisee onboarding.

Related: Phase 2: Addressing non-compliance · How do I know what's wrong with a franchisee's insurance? · Statuses explained