Symphony Assumptions

What it improves

Assumptions live in shared drives, in workbooks, in someone's head and in a PDF that nobody can find. The process to update them is informal. The audit trail is reconstructed from emails. Every external review reopens the same questions.

What it does

• A single, versioned source of assumptions across products, reporting bases and entities.
• Simple bulk import of your existing assumptions. Bring your current Excel workbooks, drive folders or database tables in as-is — the platform reads the shape, tracks the source, and versions every assumption on the way in. On engagements we have run, most teams have been loaded and governed within the first sprint — actual timing depends on scope, source-system access and the team’s review capacity.
• Workflow for proposed changes: who owns it, who reviews it, who approves it, when it takes effect.
• Reporting basis awareness — the same demographic assumption can be approved for IFRS 17 and pending for SAM.
• Full change history and reason-for-change capture — with one-click revert to any prior version (the rollback an AI agent’s edits rely on).
• API-first: feeds Symphony Modelling, the actuarial engines you already operate, in-house code or BI tools.
• Shares the common architecture across the platform: API, lineage, role-based access, observability.
• Available inside Excel, on the web, and via the API — actuaries work in the tool they already know, with full audit trail back to the platform.

Controls and audit

Every assumption has an owner, a reviewer, an approver, a version, a basis and a reason-for-change. Nothing changes silently.

Engagement model

Deployed inside an engagement, on your environment, with documented handover. We do not licence this as a standalone product. Onboarding is deliberately frictionless — bring your existing Excel assumption workbooks and the platform imports them in bulk, preserving structure, source and ownership. In-engagement deployment has typically landed inside 4 to 8 weeks on engagements we have run: import existing assumptions, configure governance workflow, integrate with the first downstream consumer, then expand — actual timing depends on scope, source-system access and the team’s review capacity. If you want to take the component forward, you take it — full source, docs, supported handover.