Guide to Applied Epic Optimization: What It Actually Means and Where to Start

An agency with well-configured events and activity codes still underperforms if staff isn’t properly trained and is aware of management expectations for utilizing Epic to manage their clients. Training people on a suboptimal configuration, or skipping training entirely, just encourages staff to find workarounds to what the system should be doing for them and the agency.

What Applied Epic Optimization Actually Means

The word “optimization” means two very specific things.

First: are there tools in Epic you aren’t using that would genuinely help your agency? Not every feature is worth turning on. The question isn’t what’s available. It’s whether a given feature would actually serve your operation.

Second: are there things you are already using that are making your people’s work harder than necessary? Configuration that made sense at go-live may be creating friction today. Your system has grown. Workflows have changed. Nobody checked whether Epic kept up.

Optimization is reviewing everything you’re currently doing and asking how you can improve it. What can you use out of Epic that you’re not already using? And then, what ancillary tools will serve your agency best?

Turning on a feature is not implementation. Any meaningful change requires updating your written workflows, training your staff, and following up in 30 days to check whether it’s actually being used.

The Most Impactful Optimizations: Where to Start

Not every optimization is worth the same effort, and trying to change everything at once is one of the most reliable ways to guarantee nothing actually changes. Start with low-cost, high-impact items so you have real wins before the harder work begins.

Carrier Downloads

Download is the single highest-leverage switch for most agencies. Many agencies that had painful download experiences years ago turned it off and never turned it back on. If your staff are manually processing policy changes that carriers are already sending electronically, that’s recoverable time being lost every day. The savings on policy updates, issuance, and commission matching compound across every renewal cycle.

Office 365 Integration and Email Templates

The Office 365 integration removes a step your staff are almost certainly performing separately right now. Applied Epic integrates with Outlook so that emails can be composed from within Epic and attached to activities automatically in the same step. If your staff drag and drop emails separately, log communications as a second manual step, or don’t log them at all, you’re losing both time and your E&O trail.

Email Templates live inside the same integration and are included in Epic at no additional cost. A new employee shouldn’t need to read through old email threads to figure out what language your agency uses for a coverage change notice. If your staff write individual endorsement transmittal emails from scratch every time, they’re spending more time than necessary on something that also needs to be consistent for E&O purposes.

E-Signature

E-signature is relatively simple to adopt and immediately reduces paper handling and client back-and-forth on applications and acknowledgments. For most small and mid-size agencies, this is the third highest-impact change after Download and the Office 365 integration. There are third party apps that integrate with Epic such as DocuSign and RightSignature.

Real-Time Carrier Connections

Real-time carrier connections are one of the most underused features in Applied Epic. Epic supports direct policy inquiry on carrier websites and, for many carriers, real-time quoting from within the system, without a separate browser login and with rates that come directly from the carrier. Most staff don’t know this exists and default to going to the carrier website directly.

The time saved on policy inquiries and renewal prep adds up quickly. The barrier is correct configuration and training. Your staff default to what’s familiar, and real-time connections take deliberate reinforcement before they become a habit.

Ongoing Training

At larger agencies, ongoing training is the optimization with the broadest reach. The impact of poor training compounds at scale in a way it doesn’t at a smaller agency. Your people bring in assumptions from previous systems. Acquired staff bring different habits.

Features added in the last three upgrade cycles are turned off or unknown because nobody reviewed the release notes and updated security groups accordingly. You need to stay current on new features and refresher training for high-frequency tasks.

Training — while it may not be a direct revenue driver – is in fact a lever for efficient use of time and your safety net. The outcomes of structured training reflect directly in the results of your audits.

Freeing Up Your Account Managers

Freeing up your account managers is a different category of optimization, and in many agencies it’s the most significant one. Your licensed account managers may be spending meaningful time on work that doesn’t require their skills: checking that endorsements came in as ordered, ordering loss runs from carrier websites for upcoming renewals, gathering information for summaries of insurance before renewal meetings.

These are real tasks. They are also entry-level tasks. The question is whether a licensed professional with client relationships should be doing them, or whether they can be handled by entry-level staff, a third-party service, or automation.

Having highly paid account managers checking policies is a waste. You want them dealing with their clients, selling other lines of business. If the policy check finds an issue, then we want them handling that. But that initial check doesn’t need them.

Optimizing Applied Epic’s Enterprise Admin Layer

The optimizations above are largely switches you can flip without touching Epic’s deeper Enterprise Admin workflows. But how much runway you have, and how clean the results are, depends on what’s underneath. The sections below cover the configuration layer that either supports your operation or quietly works against it.

The Foundation: Getting Your Structures Right

Before optimization can happen, your underlying Structure has to make sense. If you set structure up quickly at go-live and never revisited it, you may discover years later that your reporting is wrong, your income statements don’t reflect reality, or that a structural decision you made in year one is now costing you weeks of manual work to undo.

The Hierarchy of Structures

Epic’s core structural hierarchy is Agency, Branch, Department, and Profit Center. What each structural level does matters, especially when you think about how policies, accounting entries, and reports get tagged.

Agency is a legal entity and the only level at which a balance sheet can be generated. Branch maps to a physical location or major division. Department is your line-of-business grouping: Commercial, Personal, Benefits. Profit Center is the flexible sub-segment beneath the department level, such as small business within commercial, a VIP client tier within personal, or a particular program or book.

Correct agency structure decides how accurately you can understand your revenue and business efficiency.

The Mid-Term Constraint in Structures

Here is the critical constraint that catches agencies off guard. Branch, and Department can only be changed on a policy through a renewal or remarketing process. They cannot be easily changed mid-term.

If your structure needs to change mid-term and you have active policies, you’re facing a copy-and-cancel operation per account. One branch consolidation across 131 accounts can run to roughly 99 clicks per account, around six hours of unbroken manual work for what was, on paper, a simple structural decision. Poor structure also compounds significantly during any agency acquisition, where incoming data has to be fit into your hierarchy under deadline pressure.

Profit Center: The Flexible Exception

Profit Center, by contrast, can be changed on a line at any time. That flexibility is exactly why Profit Center is the right tool for segmenting business below the department level. If you skip Profit Centers entirely, you miss the one flexible reporting layer Epic gives you without structural lock-in. Using “all lines” as a catch-all across your entire book, cross-segment reporting becomes meaningless.

Decisions made in the structure layer echo through your reporting and your accounting for the life of the agency. Getting someone with real Epic experience involved before you build or rebuild structure is worth the cost.

Events and Activity Codes: The Workflow Engine

Your Events and Activity Code setup is where most agencies are either over-configured or under-configured. Both outcomes are expensive.

Events fire when something happens in the system: a policy is added, an endorsement is ordered, a policy is issued, an attachment is added. Each event can be configured to generate a visible activity for the user to act on, a background activity for audit and reporting purposes that doesn’t surface as a task, or nothing at all.

Out of the box, every event is turned on. Every stage of every workflow generates an activity. Your users click “finish” repeatedly before anything real is done. They can’t see what actually needs attention, they protest, they work around the system, and they lose confidence in it.

The opposite failure is just as damaging. You disable most events because the click-through was overwhelming. Now there’s no audit trail, no visibility into who did what, and no reliable E&O defense.

If you leave every single Event as generating a required activity, your end users are going to complain. But if you turn them all off, you’re basically paying a lot of money for an address book.

The right position sits between these extremes, and reaching it requires working through each workflow deliberately. Wherever an endorsement is ordered, a cancellation processed, or a coverage change made, a visible activity should tie to that action and hold the record. Where the system just needs to know something happened without interrupting your user’s workday, a background activity is enough.

The question for every event is: at which stage of this workflow do you need documentation, and at which stage is the activity just noise?

Activity Codes are the labels your agency attaches to activities, the way you categorize and report on work. Without governance, they accumulate over years. Codes created in 2013 are still in the system. New admins add codes that overlap with existing ones. Your staff don’t know which to use.

Stale codes can be inactivated in Epic, which removes them from selection dropdowns without deleting historical records. But codes tied to system events cannot be inactivated without first removing them from the Event they are associated with.

Without a regular review process, the list keeps growing, and your activity reports become unreliable, your open backlog looks larger than it is, and your managers can’t distinguish genuine outstanding work from activities nobody has touched in three years.

Policy Types: Configuration That Shapes Everything Downstream

Policy Types are not labels. They control which ACORD application or Custom Form attaches to a policy, which department it routes to, and how it shows up in every report you run. Getting this wrong at setup has consequences that pile up for years.

Common Failure Modes

The most common failure is using one generic “Commercial Lines” type for everything because the right type didn’t exist when you needed it. Reporting becomes useless. You can’t distinguish auto from GL from workers’ comp from umbrella. Cert issuance from structured data doesn’t work and proposals can’t be generated correctly.

The inverse problem is just as common. “GL,” “General Liability,” “CGL,” and “Comm GL” all exist because different people added records at different times, or an acquisition brought in different naming conventions. Your production reports split the same business across multiple codes. Cleanup means picking a canonical type and manually reclassifying every affected policy, which is not a small project.

A Policy Type without an ACORD application or Custom Form attached is a shell. Epic has nowhere to hold limits, deductibles, conditions, or exposures. Your staff discover that certain policy types don’t properly work in Epic and can start managing those policies outside the system. Once that habit forms, it’s hard to reverse.

The form choice, once made, is effectively permanent until you do the cleanup work. A Policy Type can be linked to either an ACORD Application or a Custom form, not both. Changing it later requires creating a new type and migrating policies manually.

What Well-Structured Policy Types Enable

When your Policy Types are specific and correctly formed, Epic can do something genuinely useful: run queries across your book to find clients who hold some lines but not others. Which commercial clients don’t have an umbrella? Which personal lines clients have auto but no home? Epic can run those queries natively and trigger marketing campaigns against the result without any add on products. Most agencies never use this because the underlying policy type data isn’t clean enough to trust the output. Getting types right is what makes that analysis possible.

Transaction Codes work alongside Policy Types to make your production reporting meaningful. Every transaction in Epic should represent whether a transaction is new business, a renewal, a rewrite, an endorsement, a cancellation, or an audit.

If those codes aren’t accurate, your production figures are wrong. An endorsement coded as new business inflates your new business numbers. A rewrite coded as a renewal distorts carrier-level reporting.

One distinction most agencies miss entirely: Epic can separately track a new line written on an existing client from a true new client acquisition. Cross-sell book of business looks identical to new business in most agencies’ reports because nobody configured the distinction. You can’t measure organic growth on your existing book, and the correct commission rate may not even apply. This should be handled by having separate Line Status Codes for new business and lines won by cross-selling.

You can also build segmentation into your type structure intentionally. If you want to separate small commercial from standard commercial, you can create a distinct Policy Type for small business workers’ comp that automatically routes into the small business Profit Center. That means every policy written under that type is already tagged correctly for reporting without anyone needing to remember to apply it manually. The more deliberate your type structure, the more your reports reflect how your agency actually thinks about its book.

Custom Forms for Specialty Coverage

Standard coverages like GL, auto, property, and workers’ comp have standard ACORD Applications. Specialty coverages like professional liability, EPLI, pollution liability, D&O, and cyber do not. For these, Epic supports Custom Forms: configurable templates that hold the specific fields for that coverage type.

Most agencies don’t have the bandwidth or the IT person to build those Custom Forms. So a lot of times, those specialty coverages, their application detail does not exist in Epic. All they have is the policy attached.

Without a Custom Form, a specialty policy exists in Epic with no structured application detail such as limits, deductibles, exposures. Your account managers learn to manage those lines outside the system, which quietly signals that certain lines of business don’t belong there. No structured coverage detail means no cert issuance from Epic, no proposals, and no summary of insurance without manual entry. Manual entry can increase your E&O exposure.

There is another trap! Updating a Custom Form doesn’t apply to existing policies. The change only takes effect when a policy goes through Actions > Renew. If your admin doesn’t know this, they update a field, see nothing change on live policies, and either repeat the change or unknowingly create version inconsistency between renewed and non-renewed policies. There’s no native Epic tool to see which policies are on the current form version.

Carriers: The ICO/PPE Distinction and Why It’s Important

Carrier setup is one of the least visible and most consequential configuration areas in Epic. The consequences don’t appear in your daily operations. They show up when commission statements don’t reconcile, when reports look wrong, or when your E&O renewal application requires premium data by carrier and you can’t produce it cleanly.

ICO and PPE: Why They Must Be Separate

Every carrier in Epic requires two distinct record types. The ICO (Issuing Company) is the subsidiary whose name appears on the policy document. The PPE (Premium Payable Entity) is the billing entity: who you pay premiums to or who pays commissions out. A large carrier like Travelers may have dozens of ICO subsidiaries under a single PPE.

When insurance companies aren’t configured correctly, meaning: multiple PPEs for the same company, or issuing companies designated as billing companies, commission matching fails. The system tries to match an incoming commission statement from the PPE against a policy recorded under a different PPE, and they can’t be reconciled. Your accounting team ends up making corrections in order to reconcile statements under one PPE, one item/policy at a time.

Mixing ICOs and PPEs

The most common failure is using the same record as both ICO and PPE. This typically happens because whoever set up the carrier didn’t understand the distinction, or took a shortcut. As a result, your proofs of insurance may not accurately reflect the proper issuing company. This in turn becomes a failure to meet compliance requirements for issued proofs.

Duplicate PPEs

Duplicate PPEs are the other recurring issue. “Travelers,” “Travelers Ins,” and “Travelers Insurance Group” entered separately over time by different staff. Your commission reports fragment across multiple codes. Your production reports split the same carrier’s volume. Fixing it requires touching every affected policy. The problem is especially common after acquisitions, where the incoming agency had its own carrier naming conventions.

How to Implement Optimizations Without Failing

Every change in Epic has a ripple effect. A change to an event affects how activities are generated, which affects documentation discipline, which affects your E&O trail. Testing before rolling out is not optional. If a feature touches existing workflows, those workflows have to be updated before it goes live, and your staff need training before the update lands, not after.

Most optimization projects that fail do so for one of two reasons. They try to change too many things at once, or they underestimate what a single change actually requires.

Getting Internal Buy-In

Implementing optimizations is also a sales job internally. Your staff don’t like being asked to change habits they’ve built over years. The case has to be concrete: “this removes a dozen clicks from every endorsement you process.” Without such a concrete improvement, your people need to hear the reasoning behind a change. Otherwise resistance is the default response.

You need an internal advocate with credibility across management and staff. Without that person, even solid recommendations sit on a list. The same applies if you bring in a consultant, so ask explicitly whether they’ll guide implementation or just deliver a report, and get a scope of work for each phase separately. A consultant who disappears after the audit leaves you exactly where you started.

Some work requires Applied directly: Structure reconfiguration, General Ledger changes, platform-level integration issues. For everything else, the limiter is usually people.

You can’t fix people. If you have people who will not change, if you have people that are very set in their ways, all the optimization in the world doesn’t help with that. It’s mostly about people.

Where Bulk Operations Become the Bottleneck for Admins

Even with a clear picture of what needs to change, execution is often where progress stops. Epic is a powerful system designed for one-at-a-time human operation. That design serves your producers and account managers exceptionally well. For Enterprise Administrators working across hundreds or thousands of records, that same design creates a volume problem.

Every bulk operation requires opening each record individually in Epic’s native interface: normalizing a carrier PPE across hundreds of policies, fixing Policy Types after a configuration correction, moving Accounts between Branches, aligning an acquired agency’s records for data conversion.

The manual approach to Enterprise Administration can consume days or weeks of staff time depending on the scale of the problem. That cost repeats every time a similar operation comes up.

RecordLinker connects to Applied Epic and exposes bulk operations that Epic’s native interface isn’t designed for. The operations that Epic handles one record at a time, RecordLinker handles across groups of records in a fraction of the time: Employee Setups, flexible Workload Reassignments, Structure Group management, Carrier normalization, M&A data conversion, and data quality checks. What takes admins days of manual grind can easily take productive hours.

If you’re running an optimization or cleanup project where the decisions are clear but the execution volume is prohibitive, or if you’re working through an acquisition where data normalization is bleeding into your post-go-live operations, that’s where RecordLinker comes in.

Suggested Resources for Insurance Agencies

Visit these resources to learn more:

• [Solutions] Applied Epic Controls for Enterprise Admins
• [Blog] Data Governance in P&C Insurance for Applied Epic and Vertafore’s AMS360
• [Blog] Simple Data Analytics for Insurance Brokers
• [Podcast] Hidden Heroes of Insurance Data
• [Blog] Insurance Agency Acquisitions – AMS Data Migration
• [Solutions] Data Conversion to Applied Epic
• [Solutions] Book of Business Import to Applied Epic
• [Solutions] RecordLinker Cognition: AI-Assisted, Reusable Conversion Logic