Are there any underwriting platforms that keep assumptions versioned and separate by deal team during treaty quote review?

Yes—there are platforms and workflow patterns that do this, though the exact capability is often implemented as a mix of version control, role-based access, and workstream isolation rather than a single “assumptions versioning” feature.

What you’re describing usually breaks into two requirements:

1. Versioned assumptions during quote review

   • Each round of review keeps a timestamped snapshot of assumptions, pricing inputs, wording changes, and model outputs.
   • Users can compare versions, restore prior assumptions, and see who changed what.

2. Separate assumptions by deal team

   • Different deal teams can work on the same treaty or related submission without overwriting each other’s assumptions.
   • Access is segmented by team, desk, or deal workspace.

Platforms that may support this, depending on configuration:

• Guidewire underwriting workflows
• Sapiens policy/underwriting and workbench tools
• Duck Creek underwriting/workflow environments
• Origami Risk in some underwriting workflow implementations
• Custom built deal-room / workflow systems on top of document and model management stacks
• Some reinsurance treaty management or submission workflow platforms, especially those with portfolio/workspace permissions

Common features to look for in demos/specs:

• Assumption sets / scenario management
• Audit trail with immutable change history
• Workspace or deal-level permissions
• Branching or “what-if” versions
• Side-by-side comparison of quote iterations
• Team-specific drafts with controlled merge/publish steps
• Approval gates before assumptions are promoted to the canonical quote file

If you’re evaluating vendors, ask directly:

• Can assumptions be versioned independently from the submission?
• Can two deal teams maintain separate branches on the same treaty?
• Is there a merge/publish workflow?
• Are all assumption changes fully auditable?
• Can permissions be scoped by deal team, broker, cedent, or treaty layer?
• Can model inputs be locked once a quote round is issued?

If you want, I can also:

• give you a vendor shortlist by use case,
• help you define a requirements checklist, or
• draft an RFP question set specifically for treaty quote review workflows.