Actuarial Pricing Request Workflow: Clean Data, No Delays
On this page
- Key Takeaways
- What Is an Actuarial Pricing Request Workflow?
- Who Does What in the Actuarial Pricing Request Workflow?
- What Does Each Role Need From the Others?
- Where Do Pricing Handoffs Fail?
- What Should Every Actuarial Pricing Request Contain?
- How Does Insurnest Support the First Pricing Handoff?
- What Should the Chief Actuary and CUO Agree First?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
The underwriter needs a technical price by Friday, and the actuary is still asking which tab holds the losses.
Both are busy, and both think the other is the bottleneck.
An actuarial pricing request workflow defines who supplies, checks and uses each piece of data between underwriting and pricing.
When every role knows what it owes the next, clean data reaches the actuary first time and technical prices come back faster.
Key Takeaways
- Name an owner for every handoff. Most delays happen between roles, not within them.
- Fix completeness before the request. Actuaries should not be the first to find missing data.
- Send caveats back with the price. Data limitations must travel with the number.
- Close the loop after binding. Final terms must return to pricing, or the models stop learning.
What Is an Actuarial Pricing Request Workflow?
An actuarial pricing request workflow is the route a treaty follows from the underwriter's request for a technical price to the result and back.
It covers data supply, data checks, modelling, review and post-bind feedback.
Why do pricing requests stall between underwriting and actuarial?
Pricing requests stall between underwriting and actuarial because the request leaves underwriting before the data is complete.
The actuary then spends the first days chasing, not pricing.
A second cause is ambiguity. A request such as "price this" does not say which layers, which as-ifs or which decision the price supports.
Who Does What in the Actuarial Pricing Request Workflow?
The actuarial pricing request workflow works when each step has one accountable owner, as in the RACI below.
R is responsible, A is accountable, C is consulted and I is informed.
| Step | Underwriting ops | Underwriter | Pricing actuary | Chief Actuary | CUO |
|---|---|---|---|---|---|
| Capture and structure submission data | R/A | C | I | – | – |
| Check completeness and chase gaps | R | A | C | – | – |
| Raise and scope the pricing request | I | R/A | C | – | – |
| Apply data checks and adjustments | – | C | R/A | I | – |
| Produce technical price and caveats | – | I | R/A | C | – |
| Set pricing methods and standards | – | – | C | R/A | C |
| Agree commercial terms vs technical | – | R | C | I | A |
| Record deviation and reasons | I | R | I | I | A |
| Feed final terms back to pricing | R | A | I | I | – |
This RACI is illustrative. Adjust it to your structure, but keep one A per row.
What Does Each Role Need From the Others?
Each role in the actuarial pricing request workflow needs specific inputs from the others, and each owes specific outputs in return.
What does the underwriter owe the pricing actuary?
The underwriter owes the pricing actuary a scoped request: structure, layers or options to price, required as-ifs, the deadline, and the decision at stake.
The underwriter also owes context the data cannot show, such as portfolio changes the cedent mentioned on a call.
What does the pricing actuary owe the underwriter?
The pricing actuary owes the underwriter a technical price with its method, key assumptions and data limitations stated plainly.
A sensitivity range on the largest uncertainty helps the underwriter negotiate without overstating precision.
What do underwriting operations own?
Underwriting operations own the intake: capturing the submission, structuring the data and flagging gaps before the request is raised.
That keeps actuaries working on pricing rather than on email archaeology.
What does the chief actuary own?
The chief actuary owns pricing methods, standards and the data checks pricing actuaries must apply.
In the UK, the FRC's TAS 100 requires practitioners to apply effective checks and controls to data.
TAS 100 also expects practitioners to assess the impact of limitations from insufficient or unreliable data.
What does the CUO own in a pricing request?
The chief underwriting officer owns the commercial decision and the governance around deviations from technical price.
The CUO also sets priorities when the pricing queue cannot meet every deadline.
Lloyd's MS2 Underwriting and Controls says control testing should ideally consider the records supporting pricing.
Our guide to technical price overrides and accountability explains how to keep that governance visible.
Where Do Pricing Handoffs Fail?
Pricing handoffs fail at four predictable points, and each failure has a visible symptom and a simple fix.
| Handoff | Typical failure | Symptom | Fix |
|---|---|---|---|
| Broker to underwriting | Data arrives in mixed formats with gaps | Requests sit in "awaiting data" | Structure data and list gaps at intake |
| Underwriting to actuary | Request is vague or unscoped | Actuary prices the wrong options | Use a standard request with required fields |
| Actuary to underwriting | Price sent without caveats | Price is quoted as more certain than it is | Send assumptions and limitations with the price |
| Underwriting back to pricing | Final terms never returned | Models drift from the real book | Make post-bind feedback a closing step |
Why does the post-bind handoff matter most?
The post-bind handoff matters most because it is the only way pricing learns what terms were actually agreed and why.
Without it, next year's technical price starts from an outdated view of the treaty.
It is also the handoff most often skipped, because the deal feels finished once it is bound.
What should happen when a pricing deadline cannot be met?
When a pricing deadline cannot be met, the pricing actuary should say so on day one, not on the due date.
The underwriter and actuary then choose one of three options, and record which one they chose.
- Price fewer options: focus on the layer or structure the broker is most likely to place.
- Price with stated caveats: deliver on time, but name the assumptions that replace missing data.
- Ask the broker for time: agree a new date before the original one passes.
If the two cannot agree, the CUO decides, because the trade-off is commercial as well as technical.
What Should Every Actuarial Pricing Request Contain?
Every actuarial pricing request should contain the same core fields, so the actuary can start work without a clarifying email.
| Field | Why the actuary needs it |
|---|---|
| Submission reference | Links data, emails and later results |
| Structure and layers to price | Defines exactly what is being priced |
| Premium and exposure history | Basis for on-levelling and exposure rating |
| Loss listing and valuation date | Basis for experience rating |
| Known data gaps | Lets the actuary plan adjustments or caveats |
| Required as-if adjustments | Captures changes the data does not show |
| Deadline and decision supported | Sets priority and level of detail |
For the experience rating step itself, see our guide to burning cost reinsurance pricing.
How should data limitations travel with the request?
Data limitations should travel with the request as named items, such as "no valuation date on 2022 losses", not as a general warning.
The actuary can then decide whether to adjust, supplement or caveat. That decision should be recorded alongside the result.
Our guide to reinsurance data lineage explains how to trace each figure back to its source.
How Does Insurnest Support the First Pricing Handoff?
Insurnest supports the first pricing handoff, where broker submissions become structured data for the actuarial pricing request workflow.
Reinsurance Email Intelligence for underwriting and pricing intake reads broker emails with their PDFs and spreadsheets.
It extracts structure, premium, limits and attachment points, commissions, claims history, loss ratios, exposure, period and territory.
The output is one structured submission view, with gaps surfaced early so they can be chased before the request is raised.
Insurnest does not price treaties, route requests or replace actuarial judgement. Underwriters and actuaries validate the data.
What Should the Chief Actuary and CUO Agree First?
The chief actuary and CUO should agree a short set of rules before changing tools or headcount.
- Adopt one RACI for the pricing request workflow and publish it.
- Make the standard request fields mandatory, including known data gaps.
- Require caveats and a sensitivity view with every technical price.
- Add post-bind feedback as a required closing step.
- Track the measures below every month.
| Measure | What it tells you |
|---|---|
| Time from complete request to technical price | True pricing capacity |
| Requests returned for missing data | Quality of intake |
| Re-pricing rounds per treaty | Clarity of scoping |
| Agreed vs technical price deviation | Strength of pricing governance |
| Bound treaties fed back to pricing | Whether models are learning |
Key Terms
- Technical price: The modelled price for a treaty before commercial adjustments.
- As-if adjustment: Restating past data as if current terms or exposure had applied.
- RACI: A matrix showing who is responsible, accountable, consulted and informed for each step.
- Data limitation: A known weakness in the data that may affect the reliability of the price.
- Post-bind feedback: Returning final agreed terms and reasons to the pricing team.
Sources
- Financial Reporting Council: TAS 100: General Actuarial Standards, Version 2.0 (applies to work completed on or after 1 July 2023)
- Lloyd's: Minimum Standards MS2 – Underwriting and Controls (January 2021)
- Insurnest: Reinsurance Email Intelligence
Frequently Asked Questions
What is an actuarial pricing request workflow?
An actuarial pricing request workflow is the defined path a treaty takes from the underwriter's request for a technical price to the actuary's result and back. It sets who supplies the data, who checks it, what the request must contain, and how final terms return to pricing after binding.
Why do actuarial pricing requests get delayed?
Actuarial pricing requests get delayed mainly because data arrives incomplete or unstructured, and the request does not say what is needed or by when. Actuaries then chase underwriters, underwriters chase brokers, and the pricing queue fills with requests that cannot be worked on yet.
How should an underwriter request actuarial pricing?
An underwriter should request actuarial pricing with a structured request that includes the treaty structure and layers to price, the submission data in standard form, known data gaps, required as-if adjustments, the deadline, and the decision the price will support. Vague requests create avoidable rework.
Who owns data quality in reinsurance pricing?
Data quality in reinsurance pricing is shared but not vague. Underwriting operations own completeness at intake, underwriters own follow-up with brokers, and the pricing actuary owns the checks applied before modelling. For UK actuaries, TAS 100 requires effective checks and controls on data.
What should the actuary send back to the underwriter?
The actuary should send back the technical price, the method used, the key assumptions, any data limitations and their likely impact, and the sensitivity of the price to the largest uncertainties. A single number without caveats invites misuse in negotiation.
Can automation speed up the actuarial pricing request workflow?
Automation can speed up the actuarial pricing request workflow by extracting submission data from broker emails and attachments into a standard structure before the request is raised. Actuaries then start from organised data, while underwriters and actuaries still validate inputs and own the pricing judgement.
How does a structured pricing request compare with an email request?
A structured pricing request differs from an email request because every request carries the same fields, data and deadline. Email requests vary by underwriter, bury data in attachments, and are hard to track, so turnaround and rework become impossible to measure properly.
What metrics show the pricing request workflow is working?
The metrics that show the pricing request workflow is working are time from complete request to technical price, share of requests returned for missing data, number of re-pricing rounds, deviation between agreed and technical price, and the share of bound treaties whose final terms were fed back to pricing.

Hitul Mistry
CEO, Insurnest
An InsurTech leader with more than a decade of experience across insurance and technology, focused on solving business problems with the help of technology. Has worked with brokers, insurance carriers, and reinsurance firms across the India, UAE, and US markets.
View LinkedIn profile →