External Notes | November 18, 2025
Features
Policy Versioning
What is it? Support for creating and maintaining multiple versions of the same policy and for storing a version reference with each policy record.
Who is it for? Policy administrators responsible for creating the basic rule set for the policy.
Why use it? Allow policy variations based on effective and expiry dates, including changes to Assured details, conveyances, commodities, and basic policy rules. View the start, end and creator of all versions and access individual versions through the menu.
Certificate Template Versioning
What is it? Support for creating and maintaining multiple versions of a certificate template.
Who is it for? Certificate and document administrators responsible for document accuracy and compliance.
Why use it? Trigger the use of specific certificate templates and their unique content based on the effective date of the template and the voyage dates of the booking transaction. View the start, end and creator of all versions and access individual versions through the menu.
Ruleset Versioning
What is it? Support for creating and maintaining multiple versions of policy rulesets.
Who is it for? Policy compliance and rate administrators responsible for creating detailed rating and referral triggers.
Why use it? Trigger the use of specific policy rates or rules (conveyance or commodity limits, referral triggers etc.) based on the effective and expiry dates of the ruleset and the voyage dates of the booking transaction. View the start, end and creator of all versions and access individual versions through the menu.
Clause Versioning
What is it? Support for creating and maintaining multiple versions of stored clauses.
Who is it for? Clause administrators responsible for document accuracy and compliance.
Why use it? Trigger the use of specific clauses and their unique content based on the effective date of the template and the voyage dates of the booking transaction. View the start, end and creator of all versions and access individual versions through the menu.
Fixes
- Voyage number was not being copied to the new transaction record when a booking was duplicated. Now the voyage number is carried forward to the new transaction record.
- When a conveyance descriptor associated to a specific conveyance was selected, and later a different conveyance was selected, the original conveyance descriptor remained. Now the conveyance descriptor is cleared when a new conveyance is selected.
These materials are provided for general informational purposes. They are not intended to be comprehensive and should not be construed as legal advice. Redkik does not warrant any statements in these materials. Redkik’s products and services are provided under the terms and conditions of Redkik’s service agreements and any applicable product-specific addenda, and pursuant to Redkik policies, guidelines, and procedures. Please contact Redkik for more information. For additional details, visit: https://redkik.com/