Find out if an inherited model will hold up
- Delivery
- Up to 6 weeks from a clean dataset
- Price
- Fixed, quoted after the call
- Typical model risk
- Rated in the audit
What is at stake
Models change hands: a CRO switch, a licensing deal, a team that moved on. Before an inherited model supports a decision or a filing, someone has to check that it reproduces and that it fits the new question.
Question of interest
Can we rely on the model we inherited for the decision we now need to make?
The audit reproduces the inherited model from its delivered code and data, assesses it against the M15 framework for its intended context of use, and identifies what is needed to make the evidence reviewable.
What reviewers will ask
Does the model reproduce from the delivered files?
We re-run it in a clean environment and compare estimates against pre-set tolerances.
Was the dataset built correctly?
Where source data exist, we re-derive it independently and compare record by record.
Is it fit for the new context of use?
The assessment is written for the decision you face now, not the one the model was built for.
What you receive
- Gap report with an M15 assessment table for the intended use
- Remediation plan with a fixed price per item
- Reproduction record for the model and the dataset
What we need from you
- The model files, code, analysis datasets and report you received
- Source data, if available, for dataset re-derivation
- The decision or submission the model now needs to support
Is this the decision in front of you?
Fixed price, paid in two parts: at the start and when you receive the gap report. A guaranteed date. Pricing · How we work