Retained baseline
Keep the earlier source versions, decision, test records, owners and open issues. A new file preserves what came before.
Proposed follow-up service / Separate written scope
Reopen the decision when its evidence changes.
Evidence Refresh is a proposed maintained review service. Compare a changed source with the retained file, identify the declared affected tests and decisions, and give the institution's reviewer a bounded queue.
The local browser method exists today. The maintained service, cadence and handling agreement are proposals; this page does not activate them.
The file for one agreed refresh.
Change and review register
Record the changed source, declared relationships, affected test, responsible reviewer and decision that needs to be reopened.
Reviewer disposition
The reviewer records whether to retest, retain, narrow or replace the earlier determination. An unchanged fingerprint does not complete the review.
Complete exit file
Keep versions, unresolved questions, reviewer records and the next trigger in a portable export. Retention, deletion and exit handling belong in the written scope.
Four steps for the proposed service.
Agree the trigger
Name the source, decision, owner, reviewer, delivery window and permitted handling route.
Compare the supplied versions
Keep the earlier file. Record what changed and which relationships were declared or independently checked.
Review affected cases
Queue the affected tests and decisions for the institution reviewer. Keep missing relationships and disputed scope visible.
Leave the refreshed file
Export the revised brief, supporting register, review disposition and next trigger with the earlier baseline intact.
The maintained service would require agreed capacity, sources, cadence, support, access controls and reviewer responsibilities. Those terms are not established by running the public tool.
What works now and what is proposed.
Current local method
The browser tool uses supplied records and explicit source-to-test-to-decision relationships. It preserves an earlier baseline and exports a review file. The institution performs and records its review.
Proposed maintained service
A defined follow-up review with agreed sources and people. Authenticated organizations, reviewer assignments, controlled document access, service deadlines and maintained history need separate infrastructure and verification.
There is no active monitoring, reminder delivery, cloud history, hosted workspace, account connection or core access in this proposed service. A fingerprint is a supplied-input comparison, not identity proof or completed review.
Read the current data routes Review the engagement questions