Policy Operations Requiring Derogations
Derogations can be requested for various policy operations throughout the policy lifecycle. These include creating a new policy (New Business), modifying an existing policy during its term (Mid-Term Adjustment), adjusting the premium (Repricing), renewing a policy, or cancelling a policy. Each operation may require wholesale broker approval when the requested action falls outside standard product rules or pricing parameters.Derogation States
State Progression
Derogations move through a defined workflow with three possible states: Created:- Initial state when derogation is created by retail broker
- Awaiting review and decision by wholesale broker
- Policy operation is on hold
- Retail broker cannot proceed until decision is made
- Wholesale broker has granted the exception
- Policy operation can proceed with the requested exception
- Retail broker is notified and can complete the transaction
- Wholesale broker has declined the exception
- Policy operation cannot proceed as requested
- Retail broker must inform customer and explore alternatives
- A comment can be added to explain the denial
- The project is forked
State Transitions
When a derogation is created, it enters the Created state and awaits the wholesale broker’s decision. The wholesale broker can either approve or deny the request. Once a decision is made, the derogation reaches a final state and cannot be changed. When a derogation is denied, the project is forked so that comments and changes can be taken into account and a new derogation can be requested. State Finality:- Denied derogations are final and cannot be changed
- Approved derogations are final and enable the policy operation to proceed
- If circumstances change, a new derogation request must be created

