AMS Workflow Configuration Before Outsourcing: What Matters
AMS workflow configuration is what separates agencies that outsource smoothly from agencies that spend their first 90 days managing an outsourced team instead of being managed by one. Most AMS platforms support workflow automation — activity creation, task assignment, follow-up triggers, and renewal queues — but most independent P&C agencies have never configured it. Before outsourcing insurance back office operations, this is the configuration work that matters most.
What workflow configuration means in an insurance AMS
Workflow configuration in an insurance agency management system means building the rules that determine what task is created, when it is created, who it is assigned to, and what happens if it isn’t completed by a defined deadline. In Applied Epic, this is suspense configuration. In AMS360 and Vertafore products, it is activity and diary setup. In HawkSoft, it is the tag and workflow automation system. In EZLynx, it is the pipeline and task management tools.
The goal is the same across all platforms: the outsourced team should arrive each day to a task queue that was generated automatically by the AMS, not by the agency owner sending a morning email.
The three workflow configurations that matter most before outsourcing
Renewal workflow. A renewal activity should be automatically created X days before policy expiration — typically 90 days for commercial lines and 60 days for personal lines — assigned to the outsourced team role, and linked to the policy record. Without this, the outsourced team is working from a manually generated list that requires daily owner input.
COI request workflow. Incoming COI requests need a defined intake path — a dedicated email inbox monitored by the outsourced team, an AMS activity created upon request receipt, a turnaround standard, and a completion confirmation step. Without this intake workflow, COI requests arriving through multiple channels create a version control problem before the certificate is even issued.
Endorsement tracking workflow. Each endorsement request should generate an AMS activity with a submission deadline, a carrier confirmation step, and an AMS record update step. Endorsements processed without an activity record leave no audit trail and create discrepancy risk between the AMS and carrier records.
How to configure workflows before handing off
Start with one workflow — usually the highest-volume task type — and build it completely before moving to the next. Document each workflow in a one-page SOP that the outsourced team can reference. Test the workflow with the outsourced team before go-live: create a test activity, assign it, complete it, and verify the AMS record reflects the completion correctly. Fix what doesn’t work before adding volume.
Frequently asked questions
What if my AMS doesn’t support workflow automation?
All major insurance AMS platforms — Applied Epic, AMS360, HawkSoft, EZLynx, QQCatalyst — support some form of workflow automation. The variation is in how it is configured, not whether it exists. If you believe your AMS doesn’t support workflow automation, the more likely explanation is that the feature exists but hasn’t been set up.
Can COVU help configure our AMS workflows before starting?
Yes. COVU’s onboarding process includes AMS workflow review and configuration support for the task types being outsourced. Agencies do not need to complete workflow configuration independently before engaging COVU; the configuration work is part of the implementation process.
For the full AMS readiness overview: Insurance Agency Management System: What to Fix Before You Outsource
Talk to COVU about AMS workflow setup and back office outsourcing for your agency
Based on COVU’s operational experience managing back office operations across 50+ independent P&C agencies and $200M+ in premium.