A frozen-date replay re-runs a model against a file exactly as it stood on a past date, using only information available on that date, and then compares the output to what later happened. It is the practical test of whether a score would have been available and correct at the time a decision was made.
The replay fixes a cutoff date, rebuilds the inputs from records as they existed then, and discards anything dated after it. The model version is the version in force on that date. The output is stored, and the matter's actual course is joined afterward from the sealed outcome.
Done properly, a replay answers a question an ordinary backtest can blur: could this number have been produced before the result was known. Records that were revised or back-filled after the cutoff are the usual source of silent leakage, and the replay is built to expose them.
A replay is not a claim about future performance. It is evidence about the past behavior of a frozen method, and it is only as strong as the discipline used to freeze the inputs.
Working a file that turns on this term?
Working through a diligence process?
Institutional partners evaluating a position against this platform's outcome and duration models are welcome to reach out directly.