Sample · no client asked for this

What NICE had committed to on ID6586, as of 26 September 2026

A sample of the Historical Evidence-State Dossier: one appraisal at one cutoff, reconstructed from archived copies of the public record as it stood that day. Every source carries its capture date and digest, everything first seen after the cutoff is kept apart, and what the record cannot show is written down. A real engagement starts from your proposition, your cutoff and your authority; the Regulatory & Coverage Diligence Dossier applies the same method to one asset's whole history across the class.

Delivered within five business days of the kickoff call, or you don't pay. One-page order form; pay by card or invoice.

Illustrative
POSITION Sample reconstruction as of 2026-09-26
CONTEXT Oncology · NICE technology appraisal
UPDATED Sample: public sources only, no customer data

1 · The defined question

The proposition being reconstructed

NICE publishes final technology appraisal guidance for the appraisal ‘Epcoritamab with rituximab and lenalidomide for treating relapsed or refractory follicular lymphoma after 1 or more systemic treatments’ [ID6586], with a publication date on or before 2026-10-28, the expected publication date shown on its in-development page on 2026-09-22.

That is the frozen proposition of the forecast registered on this case, FF-016. The deciding body is the NICE Technology Appraisal Committee, England. Out of scope: what the guidance recommends, the clinical evidence for the medicine, and any safety data.

2 · The cutoff

Cutoff: 26 September 2026

The registered forecast was first frozen at 2026-09-22 and re-dated to 2026-09-26 on its registration day. A source is admitted only if an archived copy was captured on or before the cutoff. A date printed on a page — a “Published:” label or a timeline entry — is not treated as proof that the item was public on that date; section 5 shows a case where the two differ.

3 · Source inventory

Admitted: captured on or before the cutoff

IDWhatCapturedBytesSHA-256
A1NICE in-development page, gid-ta11768, as archived for the registered forecastretrieval date recorded as 2026-09-2218,270 sha256 deae7e61…a69b68
A2The same page, daily observation capture2026-09-2418,270 sha256 deae7e61…a69b68
A3The page's project-documents tab2026-09-2421,245 sha256 d55abbac…c987d2
A4Parsed record of A2 and A3 (status, schedule, timeline, document sections)2026-09-24— sha256 1b57a44a…401fe0

Digests are of the uncompressed bytes, recomputed on 2026-11-10. A1 and A2 are byte-identical.

Quarantined: captured after the cutoff, listed so they can be excluded

IDCapturedSHA-256 of the parsed record
Q12026-09-29 sha256 10f27142…905353
Q22026-10-21 sha256 93255468…f60bd0
Q32026-10-27 sha256 4d49ab8a…c9c9a3
Q42026-11-05 sha256 de6b412a…49c86f

4 · Authority state at the cutoff

What the record showed on 26 September, from A1–A4 only

ItemState in the captured bytesSource
Page label and status“In development”; status “In progress”A1, A4
ProcessSTA Standard (single technology appraisal)A1, A4
Expected publication date28 October 2026A1
Topic selectionDecision “Selected”, published 15 May 2025A1
ScopingScoping started 17 September 2025; consultation on remit and draft scope 17 Sep – 15 Oct 2025; final scope and stakeholder list published 24 November 2025A3, A4
Delay note“This appraisal has been delayed and will now be considered by the NICE Technology Appraisal Committee at a meeting on Tuesday 8 September 2026”, dated 15 April 2026A3, A4
Committee“Committee meeting: 1”, dated 8 September 2026, listed with no outcome attachedA3, A4
Draft guidanceNo draft-guidance section on the documents tabA3, A4
Final draft guidanceNot listedA4
Published guidanceNone; not terminatedA4
SponsorAbbVie (epcoritamab)A1

Reading. At the cutoff the committee had met once, and the page did not show whether that meeting reached a final recommendation. The page committed NICE to a schedule — an expected date — not to an outcome. This reading is an interpretation, attributed and dated 2026-11-10; the rows above are the observation.

5 · After the cutoff

What changed later, kept apart so it cannot leak into section 4

First seenChange on the pageSource
2026-09-29A “Draft guidance” section appears, with four documents each labelled “Published: 29 September 2026” (draft consultation document, public committee slides, equality and health inequalities assessment, committee papers). The schedule now shows a draft-guidance consultation from 29 September to 20 October 2026, “Committee meeting: 2” on 3 November 2026, and expected publication 6 January 2027.Q1
2026-10-21The consultation leaves the forward schedule and moves to the timeline. Expected publication is still 6 January 2027.Q2
2026-10-27Expected publication changes to “TBC”. “Committee meeting: 2” moves to 9 March 2027.Q3
2026-11-05A “Declaration of interests” section appears, carrying a timeline entry dated 8 September 2026. That date is before the cutoff, but the entry is not in A3 or A4. It was first seen 40 days after the cutoff.Q4

The 2026-11-05 row is why section 2 refuses printed dates. Admitted by its label, the 8 September declaration would put into a reconstruction “as of 26 September” something the captures do not show on the page at the cutoff.

How the forecast on this case resolved, and the count for its reference class, are on FF-016's record, generated from the registry. One case says nothing about how often anything happens.

6 · Limits

What could not be established

  1. The page on the cutoff day itself. The captures nearest the cutoff are 2026-09-24 (before) and 2026-09-29 (after); nothing archived shows the page between them. The draft-guidance documents carry a “Published: 29 September 2026” label, which fits their absence at the cutoff, but a label is not accepted as proof.
  2. When A1 was really retrieved. Its recorded retrieval date is 2026-09-22 and its bytes are identical to the 2026-09-24 capture. Either the page was unchanged between the two dates or the retrieval date is mislabelled; the archive cannot tell which.
  3. Independent dating of the captures. A digest proves which bytes are held. It does not prove when NICE first published them, or that NICE served the same bytes to every reader.
  4. What the committee decided on 8 September 2026. Neither the page at the cutoff nor any capture says it in words, and the draft-guidance documents themselves were not archived, only their listing.
  5. Why the expected date became “TBC” and the second meeting moved to 9 March 2027. The captured records give no reason.
  6. Anything not on nice.org.uk. No company statement, licence record or press coverage was consulted for this case.
  7. An external audit of the reading. The registered forecast on this case was read against the captured NICE page by the founder; the source URL and digest are published so any reader can check it.

This sample does not claim completeness, admissibility, any legal conclusion, verification of private conduct, or that a content hash proves a publication date. It has no comparator: a real engagement is compared with your team's own method.