Why every Case Orientation Report (COR)
starts from the same standard.

What Outcomer prepares, and what your reviewer decides.

Six properties behind every Case Orientation Report.

1. Sourced from the issuing authorities.Every requirement traces to the statute, regulation, scheme manual or supervisory guidance it comes from — captured from the authority that issued it, not paraphrased or second-hand. Every requirement on the report names its source, so your reviewer can see where the standard originates.
2. The right requirements, for this case.Applicability is resolved by explicit rules — the date of the case, its type, and the recognized characteristics of the file — selecting the complete requirement set and nothing outside it. The report shows which authorities were selected and why, so the scope of every preparation is visible and challengeable.
3. Every authority versioned.Each authority is held under change control with its state at every point in time retained. When a provision changes, the prior version is not overwritten. Each report records the corpus version that applied, so the standard used is never in question.
4. The same case, prepared the same way.Requirement selection is deterministic: the same case characteristics always resolve to the same authorities and the same requirement set. Two reviewers opening the same case are given the same requirement set — which is what removes preparation as a source of drift.
5. Reproducible at the date it was worked.Because every authority is versioned and selection is deterministic, the requirement set for any preparation can be reproduced as it stood when the case was worked — not as the standard reads today. The evidence mapping is recorded with it, so what was put in front of the reviewer can be shown.
6. Every preparation accountable.Each requirement, its source, its version, the evidence set against it and the reasoning are all recorded. The report is itself the audit artifact — a reviewer, an auditor or a regulator can trace any position back to the standard behind it.

One precision worth stating plainly. Requirement selection is deterministic — the same case always resolves to the same set. Evidence mapping is recorded and reproducible against a pinned corpus and model version. Different guarantees, both checkable.

Three things are agreed before any case is processed.

1. The statutory matrix, signed off. Every provision your case type engages, its source, the version in force and the point at which it applies. You review the whole set and confirm it matches your own reading.
2. Your internal matrix, signed off. Your own policies decomposed into requirements. You confirm the rendering faithfully represents your manual — only you can, because the standard is yours.
3. Maintenance, discussed and approved. How the matrix stays current, how you tell us when your own standards change, and how each update is recorded and versioned.

Sign-off is recorded and dated, and the configuration version is stamped on every report — so “complete against the configuration you approved” is checkable two years later. It is signed by a named person, not a team.

When a requirement changes, the corpus changes under control.

Requirements are not static. The governance question is not whether the corpus changes, but whether every change is controlled, dated, and leaves historic preparations reproducible. Four steps, and you keep the decision.

1. We monitor the instruments in your requirement set.
2. We decompose the change — which requirements are affected, what the new wording requires, and what it replaces.
3. You sign it off, as you did the original matrix. Until you do, the change is flagged as pending rather than applied.
4. We apply it from the effective date, so cases before it still resolve against the old requirement and cases after it against the new.

Your own standards change only when you tell us they have, and you certify the new rendering as you did the first. We do not take standing authority over a document that is yours.

An update never changes the answer on a case already examined. A case worked in 2021 remains reproducible against the version in force then. That is what lets a determination made two years ago be defended against the standard that applied two years ago — not the one that reads today.

None of this is a closed box.

The authorities the corpus holds, their versions, and the applicability rules that select them are open to your inspection.

The standard behind every Case Orientation Report can be verified,
not taken on trust.

Claims and complaints teams · Financial review teams · Quality assurance teams