Facultative Reinsurance Requests by Email: Roles and Log
On this page
- Key Takeaways
- Who Does What When a Facultative Request Arrives by Email?
- How Fast Should a Fac Underwriter Respond to Each Type of Request?
- What Fields Belong in a Fac Request Log?
- How Does an Ageing Sweep Catch Unanswered Fac Requests?
- How Does Insurnest Help With Facultative Reinsurance Requests by Email?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
The fac request reached the shared inbox at 18:05 on Friday. The risk incepted at 00:01 on Monday.
Nobody owned the inbox over the weekend, and the cedent placed the line elsewhere.
Facultative reinsurance requests by email are cedent or broker emails asking a reinsurer to accept a share of one risk.
The IAIS Glossary defines facultative reinsurance as cover for a single risk or a defined package of risks.
Neither side is compelled. So an unanswered request is a lost decision, not a deferred one.
This guide gives you a who-does-what table, response-time tiers, a fac request log template and an ageing sweep.
Key Takeaways
- Every request gets an owner within hours. An inbox is not an owner.
- Tier by urgency and authority. Inception date and referral need set the clock.
- Log before you read deeply. The log is the only record that a request existed.
- Sweep weekly, by age. Overdue requests get a named owner and an action.
Who Does What When a Facultative Request Arrives by Email?
When a facultative request arrives by email, five roles share the work. Each has a deadline measured from receipt.
| Role | Owns | Must do | By when |
|---|---|---|---|
| Cedent underwriter | The risk and the request | Send one email per risk with the core facts and a needed-by date | Ideally 10 working days before inception |
| Broker | The placement | Pass a complete request to fac markets; consolidate questions | Same working day |
| Underwriting assistant | The fac request log | Log, assign a tier and owner, acknowledge, list missing items | Within 2 working hours |
| Fac underwriter | The decision | Quote, decline or ask, within the tier target | See tiers below |
| Head of facultative | Referrals and ageing | Approve requests above authority; review the weekly sweep | Weekly, and on urgent escalation |
Special acceptances under a treaty are a different flow. See special acceptance requests.
How Fast Should a Fac Underwriter Respond to Each Type of Request?
A fac underwriter should respond by tier, with targets set from inception date and authority.
The targets below are illustrative; set your own and publish them to brokers.
| Tier | Request type | Acknowledge | Quote, decline or question |
|---|---|---|---|
| 1 | Urgent: inception within 5 working days | 2 working hours | 1 working day |
| 2 | New risk within authority | Same working day | 3 working days |
| 3 | Renewal with no material change | Same working day | 5 working days |
| 4 | Referral above authority or complex risk | Same working day | 7 working days, with an interim update |
| Life | Life fac case awaiting medical evidence | Same working day | Per evidence; see life facultative case tracking |
| Change | Extension or mid-term change | Same working day | Before the effective date |
Extensions also feed facultative cover expiry tracking.
What should a cedent underwriter put in a fac request email?
A cedent underwriter should put enough in a fac request email for the reinsurer to quote without asking back.
That means insured, location, occupancy, sum insured or limit, retention, share sought, period and terms offered.
Add a needed-by date and attach any survey. Group life requests have their own data; see group life facultative quotes.
How should a broker pass a fac request on to reinsurers?
A broker should pass a fac request on to reinsurers as one email per risk, with a consistent subject line.
A useful pattern is cedent, insured, class and inception date. Bundled risks in one email get logged as one, and the rest go missing.
Subject: FAC | [Cedent] | [Insured, site] | [Class] | Inception [dd Mon yyyy]
| Needed by [dd Mon yyyy]
What does the underwriting assistant log when a fac request lands?
The underwriting assistant logs the request the moment it lands, before anyone reads it in depth.
The assistant checks the request against the cedent field list above and records each missing item by name.
The tier and owner are set at logging, and the acknowledgement names the missing items. See submission acknowledgement automation.
When must a fac underwriter refer a request upward?
A fac underwriter must refer a request upward when the line, sum insured or class sits outside written authority.
Illustration: authority is USD 15m per risk. A request for 20% of a USD 120m plant is 0.20 × 120 = USD 24m, so it is referred.
A missed tier 1 target on an urgent risk also goes up the same day. Referral time counts against the tier, so refer early.
How does a fac quote become firm cover without deal now, detail later?
A fac quote becomes firm cover without "deal now, detail later" when all terms are agreed and recorded before inception.
Lloyd's describes contract certainty as replacing that culture.
Terms are agreed before the contract is entered into, with documents following promptly. An email saying "OK, on" is not a full record.
What Fields Belong in a Fac Request Log?
A fac request log needs one row per risk, opened at receipt and closed only with a reason.
FAC REQUEST LOG
Ref | Received (date, time) | Cedent | Broker | Insured | Class | Sum insured / limit
| Share sought | Inception | Needed-by | Tier | Owner | Missing items
| Status: New / Acknowledged / Info requested / Quoted / Declined / Bound / Closed
| Close reason: Bound / Declined / Placed elsewhere / Inception passed
| Last action (date) | Next action (date)
Two fields do most of the work. Needed-by drives the tier; missing items drive the acknowledgement.
Keep declined rows too. A decline with a reason tells the cedent what to change next time.
The close reason matters. "Inception passed" with no reply is the number your head of facultative needs to see.
How Does an Ageing Sweep Catch Unanswered Fac Requests?
An ageing sweep catches unanswered fac requests by bucketing every open row by age, then checking each against its tier.
Run it every Monday from the log, and sort each bucket by inception date, nearest first.
This illustrative sweep found 42 open requests.
| Age since receipt | Open requests | Rule | Action |
|---|---|---|---|
| 0 to 2 working days | 25 | Within most tier targets | Check tier 1 items only |
| 3 to 5 working days | 11 | Past tier 1 and 2 targets | Owner confirms next step today |
| 6 to 10 working days | 4 | Past tiers 1 to 3 | Head of facultative reviews each |
| Over 10 working days | 2 | Past every target | Decide: quote, decline or close |
The total is 25 + 11 + 4 + 2 = 42. One of the four aged requests incepted the next day, so it went straight to the head of facultative.
Both requests over 10 days had passed inception. They were closed as "inception passed" and the broker was told.
Track one measure from the sweep: the share of requests answered within their tier target each month.
Email volume is often the root cause. See reinsurance underwriter email overload.
How Does Insurnest Help With Facultative Reinsurance Requests by Email?
Insurnest helps with facultative reinsurance requests by email through Reinsurance Email Intelligence.
It reads the email body and attachments, such as schedules and surveys, and identifies the attachments of each submission.
It extracts limits, dates, territory, exclusions, conditions and party details into one view, and flags missing information.
It does not log, route, acknowledge or track requests, and it does not reply to brokers. The log and sweep stay with your team.
Key Terms
- Needed-by date: The date the cedent needs an answer, usually before inception.
- Tier: A response-time class set by urgency, authority and request type.
- Ageing sweep: A regular review of open requests by age against their targets.
Sources
- IAIS: Glossary (facultative reinsurance entry)
- Lloyd's: Contract certainty requirements
- Insurnest: Reinsurance Email Intelligence
Frequently Asked Questions
Who does what when a facultative request arrives by email?
When a facultative request arrives by email, the underwriting assistant logs and acknowledges it, the fac underwriter decides, and the head of facultative handles referrals and ageing.
How fast should a fac underwriter respond to each type of request?
A fac underwriter should respond by tier: urgent risks within one working day, standard new risks within three, clean renewals within five, and referrals within seven.
What should a cedent underwriter put in a fac request email?
A cedent underwriter should put the insured, location, occupancy, sum insured or limit, retention, share sought, period, terms offered and a needed-by date in a fac request email.
What does the underwriting assistant log when a fac request lands?
The underwriting assistant logs the received time, cedent, broker, insured, inception date, needed-by date, tier, owner and missing items when a fac request lands.
When must a fac underwriter refer a request upward?
A fac underwriter must refer a request upward when the line, sum insured or class is outside written authority, or when the tier target is missed on an urgent risk.
How does a fac quote become firm cover without deal now, detail later?
A fac quote becomes firm cover without deal now, detail later when all terms are agreed and recorded before inception, with documents following promptly.
What fields belong in a fac request log?
A fac request log needs a reference, received time, cedent, broker, insured, class, sum insured, share sought, inception, needed-by date, tier, owner, status and close reason.
How does an ageing sweep catch unanswered fac requests?
An ageing sweep catches unanswered fac requests by bucketing every open request by age against its tier target, then naming an owner and action for each overdue one.

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 →