Federato RiskOps: A Practical Underwriting Workflow

The portfolio dashboard has been genuinely useful since Federato went live six months ago. The concentration map tells you things about your book that the old monthly report never surfaced. The individual submission scoring catches some risks that probably would have been written incorrectly. But walk the underwriting floor and you see two things happening: the senior underwriters who engaged with the implementation are using the triage view to prioritize their queue. The junior and mid-level underwriters are opening Federato, looking at the score, and then opening a different system to actually work the submission — because nobody explained how the score connects to their decision.

This guide covers the workflow from submission entry through underwriter decision, with specific attention to the triage view that is being underused.

Note: Federato RiskOps is a carrier and MGA platform. It is not a retail agency tool. Pricing is quote-based.

What Federato RiskOps Does

Federato RiskOps is a portfolio-level underwriting management platform. Its three primary functions are:

Submission triage and scoring: Individual submissions receive an AI-generated risk score and an appetite assessment — is this risk within the carrier's stated appetite, marginal, or outside appetite? The score draws on submission data, third-party enrichment, and the carrier's historical loss patterns.

Appetite operationalization: Underwriting managers encode appetite guidelines as rules within Federato. Instead of a PDF appetite guide that underwriters may or may not reference, appetite becomes an operational parameter that the platform applies to every incoming submission.

Portfolio monitoring: Real-time views of concentration by geography, industry, class, and line. Loss ratio tracking. The ability to see how the book is accumulating before the monthly report cycle.

Federato is distinct from pure predictive underwriting scoring tools like Gradient AI, Cytora, or Planck. Those tools generate a score; Federato is the platform that operationalizes the score within the underwriting workflow. Some carriers deploy both in combination. For a direct comparison, see our Gradient AI review and the Planck vs. Sixfold comparison for the broader underwriting technology landscape.

The Submission Intake Workflow

Before an underwriter sees a submission in Federato, it has to enter the platform. How submissions arrive depends on your specific integration setup — there is no single universal answer:

API intake: Submissions from your distribution system or submission portal can arrive via API, creating structured Federato records automatically. This is the cleanest path and produces the most complete data for scoring. If your wholesale or MGA distribution runs through a digital submission platform, this is typically the integration to build.

Email parsing: For carriers who still receive a meaningful volume of submissions via email, Federato can parse incoming emails and extract structured data. The parsing quality depends on how consistently formatted the submissions are. Set up email parsing during implementation and review the first two weeks of parsed records for accuracy before relying on it as a primary intake channel.

Manual entry: For submissions that arrive via phone, broker conversation, or formats that do not parse cleanly, manual entry is the fallback. This should be the minority path — it is slower and introduces data entry errors that affect scoring quality.

Whatever intake channel is used, the submission data feeds directly into the triage scoring engine. Incomplete submissions produce lower-confidence scores. Build intake completeness expectations into your submission requirements for brokers and agents from day one.

The Triage View: Reading the Submission Score

This is the view that is being underused, and it is the highest-value part of Federato for daily underwriting work.

When an underwriter opens their queue, each submission displays:

• Appetite indicator: In bounds, Out of Bounds, or Review Required. This reflects how the submission's characteristics map against the appetite parameters configured by your underwriting management team.
• AI risk score: A numerical or tiered indicator of projected loss probability relative to your book. Higher-risk scores do not mean automatic decline — they flag submissions that require more scrutiny.
• Contributing factors: The specific data points that most influenced the score. This is the explainable AI component that addresses the "black box" objection. If a landscaping contractor is scoring high-risk, the contributing factors might show: high payroll concentration in a hail-prone geography, prior losses exceeding book average for the class, and thin account history.

The reason underwriters route around this view is typically one of three things:

1. They do not understand what the score means in terms of their decision — they see a number but do not know how to act on it.
2. The contributing factors are not presenting in a way that maps to the underwriting rationale they already use.
3. The scores have been wrong enough times that they do not trust them.

All three are addressable. The first two are training and configuration issues. The third is a calibration issue that requires surfacing the data on score accuracy.

For context on how predictive underwriting tools fit into the broader workflow, see that glossary entry.

Setting Appetite Parameters

This is the underwriting manager's job in Federato, and it is what makes the triage view meaningful or meaningless for the underwriters using it.

Appetite parameters are encoded as rules that map to your underwriting guidelines. To configure them, navigate to Appetite Settings or Underwriting Rules in the management interface (label varies by version):

1. By line of business: Define the primary appetite parameters for each line you write. For a commercial property book, this might include: maximum TIV per location, preferred construction types, prohibited occupancy classes, geographic restrictions by county or zip code.
2. By class of business: Override or refine parameters for specific classes. A hospitality-focused carrier might have broader appetite for restaurants but stricter parameters on bars and nightclubs.
3. Hard stops vs. soft flags: Federato allows you to configure some parameters as hard stops (automatic Out of Bounds regardless of other factors) and others as soft flags (Review Required, meaning the underwriter sees it flagged but can proceed). Over-using hard stops reduces flexibility and frustrates underwriters. Under-using them means the triage view does not catch what it should.
4. Threshold values: Numeric thresholds for factors like TIV concentration by geography, maximum payroll per class code, or minimum years in business for certain classes.

After any change to appetite parameters, test the configuration by running 20–30 recent submissions through the new rules and confirming the triage output matches your intent before the change goes live for the team.

The Underwriter's Decision Workflow

Once a submission is in the triage view with a score and appetite indicator, the underwriter's workflow in Federato follows this sequence:

1. Review the triage summary: Check the appetite indicator, score, and contributing factors. For in-appetite submissions with clean scores, this review takes two to three minutes.
2. Open the submission detail: Review the full submission data — risk information, loss history, account structure.
3. Request additional information if needed: Federato allows you to log an information request, which can trigger an outbound communication to the submitting broker. Track these in the system rather than in email — otherwise the follow-up activity is invisible to supervisors and the audit trail is incomplete.
4. Make the decision: Approve (with or without conditions), decline, or request review.
   • For approvals, Federato connects to your policy admin system to initiate policy issuance (see the next section on integration).
   • For declines, log the decline reason in Federato. This data feeds portfolio analytics and trains the triage model over time.
   • For conditional approvals, Federato allows you to attach conditions to the decision record — specific endorsements required, sublimits to be applied, inspection requirements.
5. Log the rationale: For any submission that required underwriter judgment — particularly ones where the score and the decision diverged — log a brief rationale note. This is the institutional knowledge that otherwise lives only in the underwriter's head, and it is what makes supervisor review and audit meaningful.

Portfolio Monitoring: The Management Dashboard

For underwriting managers, the portfolio monitoring dashboard is where Federato's value is most immediate. The key views to configure and review regularly:

Concentration analysis: How is the book distributed by geography, class, industry, and TIV? Where are you accumulating exposure that approaches internal concentration limits or catastrophe modeling constraints? This view should be checked weekly, not monthly.

New business flow: Volume of submissions received, triaged, approved, and declined by time period. Conversion rates by line and class. This tells you whether your appetite settings are producing the right flow — too many declines may indicate over-restrictive appetite parameters; too many approvals on high-risk classes may indicate under-restrictive ones.

Loss ratio tracking: For carriers with sufficient loss data flowing into Federato, the dashboard can show real-time loss ratio trends by segment. This is one of the more operationally significant features — it turns loss ratio from a lagging monthly metric into something you can act on during the quarter.

Submission quality metrics: Are brokers submitting complete data? Which distribution sources are submitting the highest proportion of in-appetite risks? Use this to manage your distribution relationships with data rather than intuition.

Integration with Your Policy Administration System

The handoff from Federato decision to policy issuance is the integration that determines whether Federato becomes an additional data entry step or a net time saver.

Federato integrates with major policy administration systems. The specific integration varies by PAS vendor. The general workflow:

1. When an underwriter approves a submission in Federato, the decision and risk data are pushed to the PAS via API.
2. The PAS creates the policy record, runs premium calculations based on its own rating engine, and generates policy documents.
3. Status updates from the PAS (policy issued, bound, endorsed) flow back to Federato to keep the portfolio data current.

If this integration is not functioning correctly, underwriters end up re-entering data in the PAS that they already entered in Federato. This is the friction point that drives abandonment of the Federato workflow. Confirm the integration is working for your most common policy scenarios in the first week after go-live — not just for the test cases used during implementation.

Getting Underwriter Buy-In: Adoption and Explainability

The adoption challenge with Federato is not unique to Federato — it applies to any AI-assisted underwriting tool. Underwriters with years of experience have developed judgment they trust. A platform that generates scores without explaining them will be perceived as a check on that judgment rather than a support for it.

Federato's explainable AI component — the contributing factors view — is the primary tool for addressing this. To make it effective:

1. Calibration sessions: Run a monthly session for the first three months where the team reviews 10–15 submissions where the Federato score and the underwriter's decision diverged. Was the divergence justified? Was the score wrong, or was the underwriter's intuition overriding data that should have influenced the decision? These sessions build trust in the model where it is right and surface calibration issues where it is wrong.
2. Score accuracy tracking: Report to the underwriting team monthly on how well recent Federato scores predicted actual outcomes on closed accounts. Underwriters who see evidence that the score is predictive will use it. Underwriters who only hear "trust the AI" will not.
3. Manager use of the data: If supervisors are reviewing work without referencing the Federato record — using email threads and phone calls to discuss submissions instead of the platform's activity log — they signal to the team that the platform is optional. Supervisors need to use Federato as the primary context for any submission review discussion.

For more on AI adoption in underwriting, see our how AI underwriting works guide and the Cytora vs. Federato comparison.

Transparency

InsurAItools has no commercial relationship with Federato. This guide is based on independent research and review of the platform as of June 2026. Interface design, feature availability, and integration capabilities may have changed. For corrections or updates, contact editors@insuraitools.com.

Editorial verdict:

Federato RiskOps delivers measurable value when the triage rules are calibrated, the PAS integration is functioning, and underwriting managers reinforce the workflow through their own use of the platform. Agencies and carriers that deploy it as a scoring overlay and leave the rest of the workflow unchanged will see limited return. The work is in the configuration and adoption — both of which are ongoing, not one-time, efforts.

---

Daniel Cho writes about agency operations and workflow automation. He has advised more than 40 independent agencies on technology selection and implementation.

---

Frequently Asked Questions

How is Federato different from Gradient AI?

Federato RiskOps and Gradient AI both apply data and modeling to underwriting decisions, but at different levels of the workflow. Gradient AI is primarily a predictive scoring layer that assesses individual submission risk and estimated loss probability — it produces a score. Federato is a portfolio management and workflow platform: it handles submission intake, triage and routing, appetite operationalization, and portfolio-level monitoring. In practice, some carriers use both — a predictive scoring tool for the loss probability assessment and Federato for operationalizing those signals within a full underwriting workflow. See our Gradient AI review and the Cytora vs. Federato comparison for more detail.

Does Federato replace my underwriting system?

No. Federato RiskOps sits alongside your policy administration system, not in place of it. Federato handles the front end of the underwriting process: submission intake, triage, scoring, and decision support. Policy issuance, premium calculation, and forms generation remain in your policy admin system. The integration between Federato's decision output and your PAS is a required configuration step — it is what determines whether the workflow creates efficiency or just adds another screen. Carriers who deploy Federato without configuring the PAS integration typically see limited adoption from underwriters.

What data does Federato need to function?

Federato requires submission data — the risk information provided in an application or ACORD forms — to generate triage scores and appetite assessments. Score quality depends directly on data completeness. Federato also integrates with third-party data enrichment sources to supplement sparse submissions with external information about the risk. For portfolio monitoring, Federato needs historical policy and loss data. The specific data requirements depend on your lines of business, the depth of appetite configuration, and whether you are using Federato's loss ratio tracking features. Your Federato implementation team will define data requirements as part of the scoping process.