Loss Planner Easy

Setting Up Loss Planner Easy Without Losing Your Mind

I've been working with loss planning tools across commercial insurance and risk management for years, and most of them are overcomplicated junk. Loss Planner Easy is different mostly because it's not. It's a streamlined claims and loss control planning platform designed for adjusters and risk analysts who need to get through a file without wrestling with enterprise software that wasn't built for humans. The basic workflow is straightforward. You log in, create a new case file, and start entering loss details. The system walks you through the key data points: incident date, exposure type, estimated reserve, applicable coverage limits, and subrogation potential. That's it. No 40-field intake form. No mandatory certifications before you can save a draft.

Loss Planner Easy for Small Teams

Here's where it gets useful. If you're running a boutique claims shop or handling loss control for a mid-market portfolio, this tool actually fits. The interface doesn't assume you have a dedicated IT department. You import loss runs through CSV, the predictive reserve engine does what it's supposed to do, and you can generate adjustment summaries without jumping through three permission gates. One thing most reviews won't tell you: the export function respects your state formatting requirements out of the box. I spent a Tuesday afternoon pulling together 14 reserve reports for a regulatory audit, and every single one matched what our compliance team needed. Took about 20 minutes total. A comparable process on our old system would have eaten half the day. The interface loads fast because there isn't a lot happening visually. That's intentional. Some people find it plain, but when you're processing files back-to-back, plain is what you want. Cluttered dashboards with animated charts don't help you close a claim. They help nobody.

Real Workflows and Where It Actually Falters

The core strength here is speed on straightforward commercial property and liability claims. For a standard fire claim at a retail location, you're looking at probably 15 to 20 minutes from file creation to a complete estimate package, assuming your documentation is already assembled. That's not hype. That's what I measured over about six months of actual use across roughly 80 files. There are honest limitations. The subrogation tracking module is basic. If you're handling complex construction defect cases with multiple potentially responsible parties, you'll outgrow this quickly. The subrogation feature basically tracks dates and contacts. It won't map out contribution apportionment or handle the kind of multi-party coordination that real-world construction litigation demands. For that, you'd need something like Xactimate with a dedicated subrogation add-on, or a full enterprise platform like Guidewire ClaimsCenter. Another issue I ran into personally: the automated reserve recommendations lean conservative on first-party property claims involving business interruption. The algorithm weights direct physical damage heavily and tends to under-predict BI exposure. I found that setting my own manual override on the BI portion early in the process prevents reserve adequacy issues down the line. Don't rely on the default suggestions for anything longer than a two-week business interruption window. I learned that the hard way on a restaurant claim where the initial reserve was roughly 30% too low, and we had to amend it after the adjuster had already communicated an expectation to the insured.

The mobile app works fine for field inspections. Photo capture, GPS tagging, and quick notes sync properly. But the offline mode is unreliable if you spend significant time in areas with spotty service. I've had cases where notes saved locally didn't upload for hours, and there's no conflict resolution if you edited the same file from two different devices. Stick to the web version for anything that matters.

Getting Started and Staying Organized

You'll need a business email address and a carrier or MGA affiliation to sign up. The registration process checks your credentials against the NAIC database, which takes a day or two. There's no instant activation, and that's actually a good thing from a security standpoint. Don't expect to start filing claims the same hour you submit paperwork. Once you're in, set up your template library immediately. Default templates are generic and not particularly useful for specialized lines. I built custom templates for restaurant operations, light manufacturing, and general liability with slip-and-fall scenarios. Each one pre-populates the relevant questions and reserve ranges based on historical data from our own books. This cuts average handling time by another five to seven minutes per file. Use the tagging system religiously. The search function is functional but not intelligent. If you don't tag files consistently, you'll spend more time looking for old cases than working new ones. I use a simple system: line code, claim type, and assigned adjuster. Three tags per file. That's all it took to make the search actually work after six months of accumulated cases.

The reporting dashboard gives you basic metrics: closed claims, average days to settlement, reserve development, and referral rates. It's adequate for monthly management reviews. Don't expect advanced analytics. If you need trend analysis by vendor performance or predictive modeling on reserve leakage, you'll need to export the data and run it through something else. CSV export is clean and complete, so that part works fine. Pricing is per-seat with tiered discounts starting at five users. The entry tier covers core claims functionality. The advanced tier adds the subrogation module and priority support. For a small team handling straightforward commercial lines, the basic tier is usually sufficient. I'd skip the advanced tier unless subrogation recovery is a major revenue driver for your operation. The upgrade cost doesn't justify itself for teams doing fewer than twenty subrogation-focused claims per year. Data retention runs indefinitely by default. You can configure auto-archiving after a set number of years, but I'd leave it alone unless your storage costs are a real concern. Having historical files readily available pays for itself whenever a reinsurer or auditor asks for a prior claim detail.

The support channel is ticket-based with a stated four-hour response time during business hours. In practice, I've seen responses come back in under an hour for straightforward questions and sometimes 12 to 18 hours for technical issues involving integrations. Their documentation is sparse but accurate. They don't pad it with filler content. That's refreshing and slightly frustrating at the same time because you'll sometimes hit a wall without a tutorial to fall back on. If you're considering whether this replaces your current setup, test it on five actual open files before committing. Run them in parallel for a month. Compare handling times, reserve accuracy, and how much time you actually save on administrative tasks versus how much time you spend navigating the tool itself. The answer varies enough by line of business and case complexity that a trial period is the only way to know whether it's worth the migration effort for your specific operation.