Renewal
Version: Not versioned (stub)
This version: 2026-09-01
Status: Stub. Scope indicated only; not yet open for comment.
Licence: CC BY 4.0 (text). Schemas, when published, under Apache 2.0.
Conventions: RFC 2119 keywords and addressed roles
Steward: Marrow (onmarrow.com), on behalf of the Agent Mediated Insurance (AMI) working group
Interaction: Renewal
Action risk class: 2 Transact
This is a scope stub, not a standard. It records the shape of an interaction that will be specified in a later version, so that an implementer building against New Business today can see what is coming and where it will attach. It states no requirements.
Scope
Renewal is the interaction at the end of a term, where the customer continues, shops, or declines. It is an action risk Class 2 interaction and reads policy and renewal-terms data under read:policy. Where the customer has granted renew:auto, a renewal within the granted cap may proceed without re-confirmation and a renewal that would exceed the cap triggers step-up confirmation. Renewal is the interaction where autonomy and the Consumer Duty fair-value duty meet most directly, which is why the reconciliation between them is an open question in the Consent standard rather than a settled rule.
Distinctive requirements
These are the requirements that distinguish renewal from New Business. They will be specified in full in a later version.
- Renewal invitation handling.
- Consumer Duty fair value, and the prior-year-premium disclosure.
- Auto-renewal consent, as a separate and revocable grant.
- The customer's right to shop, preserved rather than obstructed by an autonomous renewal.
- Switching-continuity warnings, which are acute in pet, where switching makes existing conditions pre-existing.
Authority and cap semantics are not restated here. They are defined in the scope ladder (Consent, Authority and Scopes 4.2) under renew:auto and read:policy, and in Section 6.
Not yet open for comment. Scope indicated so implementers can see the direction of travel.