.png)
Every state has its own rules. Fraud disclaimers, statutory language, required notices: the specifics vary by jurisdiction, and getting them wrong creates real compliance exposure. For most carriers, the answer has been to build a massive library of templates: one version for Texas, another for California, another for Florida. Multiply that across every letter type, and template sprawl becomes its own operational burden.
The cost isn't just storage or complexity. It's fragility. When a state DOI updates a required disclaimer, that change needs to propagate across every affected template. In practice, this means IT tickets, prioritization battles, and timelines that stretch into months, even for a single comma. Meanwhile, adjusters are left selecting the right template manually, hoping they picked the correct state version.
This is how compliance risk compounds. Not through negligence, but through the sheer difficulty of keeping a brittle system current across dozens of jurisdictions.
Jurisdictional Requirements in Kyber
Kyber's jurisdictional requirements feature addresses template sprawl by making compliance dynamic. Instead of maintaining separate templates for each state, carriers define their jurisdictional language once, in a single, centralized location, and Kyber automatically applies the correct version based on either the recipient address or the loss location.
Adjusters no longer need to select the right version of the template. Admins no longer need to chase down IT for every regulatory update. The system handles it.
How It Works
When an adjuster generates a letter in Kyber, the platform automatically detects the relevant jurisdiction:
- Automatic detection: Kyber identifies the correct state based on the recipient's address or the loss location. No manual selection required.
- Dynamic insertion: The appropriate fraud disclaimer, statutory language, or required notice is inserted into the document automatically, similar to how parameter auto-population pulls claim-specific data.
- Centralized management: All jurisdictional language is stored as organization-level parameters, updated in one place and reflected everywhere instantly.
- Single template, multiple states: Dynamic fields within a single template handle all state-specific variations, working alongside Flows for end-to-end automation.
Example: Branch Insurance consolidated 46 state-specific templates into a single template using this approach, reducing their template library by 80%.
Why This Matters
Compliance without the manual burden. Every communication automatically includes the correct jurisdictional language, whether it's a status letter, denial, or payment notice.
Template consolidation at scale. Carriers managing sprawling template libraries can collapse dozens of state-specific versions into single, dynamic templates. The Template Import Tool makes migration straightforward.
Faster regulatory updates. When a DOI changes a required disclaimer, admins update it once. The change applies across every communication immediately.
Audit-ready documentation. Because jurisdictional language is centrally managed and automatically applied, carriers have a clear audit trail showing exactly what language was used and when.
Learn More
For questions about how jurisdictional requirements work in your Kyber environment, reach out to your Customer Success Manager or contact us.
.png)
.png)
.png)
