Jurisdiction design9 min readUpdated 2026-04-26en-CA

Scale province-aware operations without forking the product.

Why Blocora uses one shared jurisdiction layer for templates, rulesets, deadlines, and wording rather than separate product branches by province.

Shared ruleset layerTemplate version controlQC / ON / BC / AB rollout logic

Keep the operating model shared

The product should not fragment into province-specific clones just because rules, deadlines, and templates vary.

Use one organization-scoped workflow model for records and permissions.

Push jurisdiction differences into rulesets and template layers.

Keep route structure and operator navigation consistent across provinces.

Operators need to know which wording, required fields, and deadlines were active when a document or notice was produced.

Track jurisdiction code, template key, and ruleset version on critical records.

Maintain active template versions instead of overwriting old behavior.

Surface rollout status and required-field changes per province.

A staged rollout keeps the product clean and lets the team deepen the jurisdiction layer without compromising the shared operating core.

Roll out by pack priority instead of all jurisdictions at once.

Use compliance workspaces to review deadlines, template versions, and exports.

Extend the same layer into notices, renewals, and future annual delivery workflows.