Log fields
- Request ID
- Reviewer organisation
- Evidence area
- Response owner
- Status and due date
- Export-pack treatment
A protected log template for turning external reviewer questions into attributable, owner-assigned, response-controlled evidence requests.
Reviewer evidence requests should become governed records with a named request, response owner, evidence link, condition treatment, and closeout state. This page is a documentation/export-readiness surface only and does not create live request logic.
| Request type | What is captured | Closeout requirement |
|---|---|---|
| Evidence clarification | Reviewer question, source artifact, requested clarification, owner, response due date. | Response attached to evidence map or Q&A surface. |
| Safeguards evidence | Safeguard area, risk posture, supporting document, unresolved condition. | Condition either resolved, escalated, or disclosed in export pack. |
| MRV or indicator lineage | Methodology, indicator, evidence object, verification logic, national MRV boundary. | MRV attachment note updated or exception recorded. |
| Data sovereignty | Residency, export control, access boundary, retention or ownership question. | Sovereignty posture confirmed before external release. |
| Committee pack question | Committee concern, linked artifact, owner response, decision-pack treatment. | Included in reviewer Q&A, committee map, or release gate. |
Reviewer question is captured with origin, purpose, and linked diligence area.
A response owner is recorded with the relevant programme, governance, MRV, safeguards, or data-room responsibility.
The answer is linked to an artifact, evidence map, reviewer Q&A, or condition register.
Unresolved items become release-gate conditions rather than disappearing from the record.