Insurance renewal or D&O review
Produce a defensible cross-portfolio exposure number instead of a manually reconciled estimate.
— Risk & Compliance
Reads every liability cap in a contract portfolio, derives actual exposure as a number, and aggregates it by entity, flagging uncapped contracts separately.
2–3 weeks → ~25 minutes
For a full population, not a sample
No coding required
— USE CASES
Produce a defensible cross-portfolio exposure number instead of a manually reconciled estimate.
Identify which contracts carry disproportionate uncapped or high-cap liability before valuation assumptions are finalised.
Spot the ten contracts contributing the most exposure so negotiation priority is data-driven.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Each row of your export is processed on the same basis, so no clause is skipped however long the table is.
Movement across the contract portfolio is visualised from the computed data, so the trend is legible at a glance.
Findings on the contract portfolio are written up as a document that reads like professional output, with each claim tied back to a clause.
Derived columns are added row by row, keeping your source data and the judgement about each clause side by side.
Detail rows are summarised into the grouped view of the contract portfolio without losing the underlying clauses.
The number insurers and finance ask for — total liability exposure across the portfolio — is usually buried in contracts with caps expressed as multiples, fixed sums or uncapped carve-outs. Insurance renewal or D&O review is the typical trigger — produce a defensible cross-portfolio exposure number instead of a manually reconciled estimate. Done properly it is defensible; done at pace it becomes a judgement call nobody can retrace. And "properly" usually means 2–3 weeks of manual work.
Here the same job runs as a Skill. Your material goes in; an exposure heatmap aggregated by entity comes out, alongside a separate total for uncapped contracts. The judgement is built in — how items are broken up, what standard they are held to, and where the run stops for a human review. The practical effect: 2–3 weeks of manual work becomes a ~25 minutes run, held to an identical standard on the tenth engagement as on the first.
Cross-portfolio liability cap aggregation exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Assesses a data subject access request end to end and returns a governed decision on whether to fulfil it, fulfil it in part, refuse it with reasons or extend the deadline, having verified identity, mapped the request to the systems that actually hold the data and held the outcome for a data protection sign-off before anything is disclosed.
Fans multiple audit or review reports into individual findings, deduplicates repeats, and sorts them by severity into one consolidated register with sources retained.
Pairs a full evidence set against every audit assertion or PBC item to produce a coverage matrix, naming the assertions nothing supports and the documents supporting nothing.
Reads a submitted claim against the policy wording that governs it and returns a coverage assessment showing whether it appears covered, potentially excluded or in need of specialist review, mapped clause by clause and never issued without a handler's sign-off.
Assesses a reported incident against your response playbook and policies, assigns the severity band the evidence supports, and returns the matching response plan with the notifications, owners and timelines that band requires.
Assesses personal-data processing and cross-border transfers against privacy policy and jurisdiction rules, producing a documented approval outcome with conditions, policy evidence and grounds for referral.