Engineering Project Declarations to Treaties: A Field Guide
On this page
- Key Takeaways
- What Are Engineering Project Declarations to Treaties?
- Which Fields Should a CAR or EAR Project Declaration Carry?
- How Should Project Premium Be Spread Over Construction and Maintenance Periods?
- Which Red Flags Should Stop an Engineering Declaration?
- Who Checks What in Engineering Project Declarations?
- How Does Insurnest Support Engineering Treaty Declarations?
- What Can Engineering Reinsurance Heads Fix First?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
A tunnelling loss lands on the engineering desk, and the reinsurance manager searches for the project declaration.
The project was bound in 2026, extended twice, and the extensions appear on no treaty bordereau at all.
Engineering project declarations to treaties are the records telling reinsurers which CAR and EAR projects attached to a treaty, on what values, periods and shares.
Getting them right means one declaration per project, a field checklist used at binding and at every extension, and premium spread over the periods it really covers.
Key Takeaways
- A project attaches once. On a risks-attaching treaty, the project usually stays with its inception year, extensions included.
- Periods are fields, not notes. Construction, testing and maintenance dates each need their own field.
- Maintenance cover type matters. Visits and extended maintenance carry very different exposure.
- One straight line misstates earned premium. Construction and maintenance should be spread separately.
- Extensions are declarations too. An undeclared extension is a gap in cover and in the accounts.
What Are Engineering Project Declarations to Treaties?
Engineering project declarations to treaties are project-level records that place each CAR or EAR risk into a specific treaty and underwriting year.
Unlike an annual property risk, a construction project can run for several years on one premium. One declaration must carry the whole project life.
Engineering treaties commonly attach on a risks-attaching basis, so a project starting in 2026 stays with the 2026 treaty. Check each wording, as terms vary.
Structuring questions sit in our guide to CAR and EAR treaty structures. This article covers the declaration itself.
Which Fields Should a CAR or EAR Project Declaration Carry?
A CAR or EAR project declaration should carry four groups of fields: identity, values and periods, cover, and cession. A gap in any group breaks a later step.
Which identity fields link a project declaration to the right treaty?
Identity fields link a project declaration to the right treaty by tying one cedent policy to one treaty, one year and one site.
| Field | What to capture | Why it matters |
|---|---|---|
| Declaration reference | Unique ID, versioned on every change | Extensions update the record instead of duplicating it |
| Cedent policy number | Original CAR or EAR policy | Matches premium and claims to the project |
| Project type | CAR, EAR or combined | Drives treaty section and rating |
| Site location | Address and coordinates | Needed for accumulation by site |
| Principal and main contractor | Legal names | Spots one project declared twice |
| Treaty and underwriting year | Treaty ID and year of attachment | Fixes which year carries the whole project |
Which value and period fields matter most for engineering declarations?
Value and period fields matter most for engineering declarations because exposure changes as the works progress.
| Field | What to capture | Why it matters |
|---|---|---|
| Contract value | Estimated final value, not first-stage value | Base for cession and premium |
| Third-party liability limit | Per occurrence and aggregate | The treaty may cap or exclude it |
| Construction start and end | Planned dates, updated on extension | Sets the construction earning period |
| Testing and commissioning | Cold and hot testing dates for EAR | Often the highest-risk phase |
| Maintenance period | Type and number of months | Same months, very different exposure |
| Total project period | Months against the treaty maximum | Long projects may need referral or facultative |
Liberty Specialty Markets notes the end of an EAR period has no standard definition.
It also describes the period after feed enters the plant as the highest risk to construction insurers. Record the actual end trigger, not just a date.
Price Forbes explains that visits maintenance covers damage during snagging works only.
Extended maintenance adds damage in the defects period caused on site during construction. Both usually run 12 to 24 months after completion.
Which cover fields change what an engineering treaty pays?
Cover fields change what an engineering treaty pays because sections, deductibles and extensions decide whether a loss sits inside treaty scope.
| Field | What to capture | Why it matters |
|---|---|---|
| Sections covered | Material damage, liability, DSU or ALOP | Treaties may exclude or limit DSU |
| Deductibles | Standard, natural perils and testing | Different deductibles change the ceded loss |
| Wording and endorsements | Base form and each endorsement | Confirms the reinsured cover matches |
| Special extensions | Existing or surrounding property, offsite storage | May fall outside treaty scope |
Which cession fields complete an engineering declaration?
Cession fields complete an engineering declaration by recording how much of the project each reinsurer carries.
| Field | What to capture | Why it matters |
|---|---|---|
| Retention and cession basis | Quota share % or surplus lines | Sets the ceded share |
| Basis of lines | Sum insured or EML | A surplus on EML needs the EML recorded |
| Gross premium split | Construction and maintenance portions | Needed to spread premium correctly |
| Ceded premium and commission | At treaty terms | Ties the declaration to the bordereau |
| Reinsurer participations | Each reinsurer's share of the treaty | Drives reinsurer-level balances |
How Should Project Premium Be Spread Over Construction and Maintenance Periods?
Project premium should be spread over construction and maintenance periods separately, because the two carry different exposure. The figures are illustrative.
A hospital CAR project has a contract value of 60,000,000 at a rate of 3.0‰, so the gross premium is 180,000.
Construction runs 24 months, from 1 April 2026 to 31 March 2028. Extended maintenance runs 12 months to 31 March 2029.
The cedent allocates 9,000 (5%) to maintenance and 171,000 to construction. The project is declared to a 2026 engineering quota share at 40%.
What does a straight-line spread over 36 months produce?
A straight-line spread over 36 months produces 5,000 a month, treating a maintenance month like a construction month.
What does a split construction and maintenance spread produce?
A split construction and maintenance spread produces 7,125 a month in construction (171,000 ÷ 24) and 750 a month in maintenance (9,000 ÷ 12).
| Calendar year | Months covered | Split spread | Straight line | Difference | Ceded at 40% (split) |
|---|---|---|---|---|---|
| 2026 | 9 construction | 64,125 | 45,000 | +19,125 | 25,650 |
| 2027 | 12 construction | 85,500 | 60,000 | +25,500 | 34,200 |
| 2028 | 3 construction, 9 maintenance | 28,125 | 60,000 | −31,875 | 11,250 |
| 2029 | 3 maintenance | 2,250 | 15,000 | −12,750 | 900 |
| Total | 36 | 180,000 | 180,000 | 0 | 72,000 |
The straight line moves 44,625 of premium into 2028 and 2029 that was exposed in 2026 and 2027.
Even the split spread is a simplification. Value at risk rises as works progress, so some cedents use an increasing exposure curve.
How should a six-month construction extension be declared?
A six-month construction extension should be declared as an amendment to the original declaration, with its own premium and new dates.
If construction runs to 30 September 2028 for an extension premium of 15,000, the treaty cedes 6,000 at 40%. Maintenance then runs to 30 September 2029.
On a risks-attaching treaty this usually stays with 2026, not 2028. Check the treaty's limit on extended project periods first.
Which Red Flags Should Stop an Engineering Declaration?
Red flags that should stop an engineering declaration are conditions that put the project outside treaty scope or misstate its exposure.
| Red flag | Why it matters | Action |
|---|---|---|
| Total period above the treaty maximum | Project may sit outside automatic capacity | Refer before declaring |
| Contract value at first-stage estimate | Share and premium understated as value grows | Declare estimated final value; amend on change |
| DSU included without treaty cover | That loss falls outside the treaty | Cede material damage only, or arrange facultative |
| Maintenance type missing | Extended maintenance carries far more exposure | Ask for the endorsement wording |
| Extension not declared | A loss after the original end date has no ceded record | Amend the original declaration |
| Same site under two policies | Accumulation and possible double cession | Match on site and contractor |
| Declared to the renewal year | The wrong treaty year carries the loss | Correct to the year of attachment |
Our guide to treaty exclusion checks at cession covers scope tests in more depth.
Who Checks What in Engineering Project Declarations?
Checks in engineering project declarations are split by stage, with the cedent owning accuracy and the reinsurer testing scope.
| Role | Checks | When |
|---|---|---|
| Cedent engineering underwriter | Values, periods, sections, maintenance type | At binding and every endorsement |
| Cedent reinsurance manager | Treaty, year, share, maximum period, exclusions | Before the declaration is sent |
| Cedent finance | Premium split, earning spread, ceded premium | Each accounting period |
| Reinsurer engineering underwriter | Scope, red flags, referrals | On receipt of each declaration |
| Reinsurer technical accounting | Ceded premium per reinsurer against the account | Each statement |
How Does Insurnest Support Engineering Treaty Declarations?
Insurnest supports the share allocation and reconciliation side of engineering declarations. The declaration log and earning spread stay with your team.
Bordereaux Calculation & Reconciliation maintains participation percentages and allocates premium and claims by reinsurer share.
It calculates each reinsurer's net position and compares it with bordereaux, master data, premium and claim registers and settlement records.
Each reinsurer shows a status of reconciled or variance to investigate. It does not hold project periods or spread premium over construction months.
Those rules belong in your declaration process and in your earned premium calculation.
What Can Engineering Reinsurance Heads Fix First?
Engineering reinsurance heads can fix first the declaration gaps that carry live exposure, starting with open projects past their original end date.
- List projects past their original end date. Check each one has a declared extension and the right treaty year.
- Check maintenance types. Find declarations with no maintenance type and request the endorsement.
- Compare contract values. Flag projects whose declared value is below the latest endorsed value.
- Re-spread three large projects. Compare split and straight-line spreads, as in the example above.
- Match sites across policies. Look for one site under two cedent policies before the next cat return.
The share arithmetic behind each reinsurer's portion is covered in reinsurer participation share calculation.
Key Terms
- Risks-attaching basis: A treaty covers policies that incept during its period, for their full duration.
- Visits maintenance: Cover for damage caused during snagging or defect-rectification visits after completion.
- Extended maintenance: Visits cover plus damage in the maintenance period caused on site during construction.
- Contract value: The material damage sum insured of a project, ideally its estimated final value.
- DSU: Delay in start-up cover for lost revenue when a project completes late after a covered loss.
Sources
- Price Forbes: Understanding Post-Completion Cover in Construction All Risks Insurance (5 May 2026)
- Liberty Specialty Markets: The challenges associated with transferring from construction to operational cover (14 January 2020)
- Insurnest: Bordereaux Calculation & Reconciliation
Frequently Asked Questions
What are engineering project declarations to treaties?
Engineering project declarations to treaties are project-level records a cedent sends to place each CAR or EAR risk into a treaty and underwriting year. Each declaration carries the project's values, construction, testing and maintenance periods, cover sections and ceded share, and is amended at every extension.
Which treaty year does a multi-year construction project belong to?
A multi-year construction project usually belongs to the treaty year in which it incepted when the engineering treaty attaches on a risks-attaching basis. The project then stays there for its whole life, including extensions, subject to the treaty's maximum period and wording.
What is the difference between visits maintenance and extended maintenance cover?
Visits maintenance cover protects only against damage caused during snagging or defect-rectification visits. Extended maintenance cover adds damage occurring in the maintenance period that was caused on site during construction. Both commonly run 12 to 24 months after completion, so the type must be declared.
How should CAR premium be earned over the project period?
CAR premium should be earned separately over the construction and maintenance periods, because each carries different exposure. A straight-line spread over the whole period pushes premium into later years. Some cedents use an increasing exposure curve; the treaty and accounting policy decide the method.
How do you declare a construction period extension to a reinsurance treaty?
To declare a construction period extension, amend the original project declaration with the new end date, the shifted maintenance period and the extension premium. Check the treaty's maximum period first. On a risks-attaching treaty the extension usually stays with the original underwriting year.
Which CAR and EAR declaration fields change the reinsurer's exposure most?
The CAR and EAR declaration fields that change the reinsurer's exposure most are the estimated final contract value, the testing and commissioning dates, the maintenance cover type and the sections covered, especially DSU. Each changes what the treaty can pay, so each needs its own field.
Who should check engineering project declarations?
Engineering project declarations should be checked by the cedent's engineering underwriter for values and periods, the reinsurance manager for treaty, year and share, and finance for premium spread. At the reinsurer, the engineering underwriter tests scope and technical accounting ties ceded premium to the account.
Does Insurnest manage engineering project declarations?
Insurnest does not manage engineering project declarations or spread premium over project periods. Its Bordereaux Calculation & Reconciliation maintains participation percentages, allocates premium and claims by reinsurer share and compares the results against bordereaux and registers, surfacing variances for the team to investigate.

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 →