# Field and status definitions

Andrew David W.Y. · G01 companion tool · 19 October 2026

## 1. Fields in the five tables

Complete each field according to the actual work status. A blank means “not yet entered”, not automatically “not applicable” or “no issue”. Keep required-information gaps visible; incomplete information cannot justify approval for external use.

## 2. Claims ledger

| Field | Entry instructions |
| --- | --- |
| Claim ID | Stable ID for a statement to be checked, such as C01; it does not establish the claim. |
| Revision | Revision of the same claim, such as r1; retain old revisions and add a record for substantive changes. |
| Original statement awaiting verification | Copy the complete original statement; keep it separate from the reviewer's analysis. |
| Subject, scope and basis | Entity, subject, period, units, quantity/percentage base, conditions and scope; figures alone are insufficient. |
| Nature of claim | Fact, plan or target, calculation, or analytical judgment; split mixed claims for checking. |
| Verification status | Support provided by this batch of documents within the defined subject and scope; add checking actions and dates. |
| Link ID | L identifiers pointing to verification links; multiple links are possible, but identifiers do not establish support. |
| Current qualified wording_for internal review | Wording pending review within existing evidential support; not automatically approved for external use. |
| Gaps and next steps | Identify the specific missing document, confirmation or action; do not write only “pending”. |
| Follow-up role | Confirmed follow-up person/role; if unresolved, mark as proposed and pending assignment. |
| Review role | Appropriate review role and whether assigned; for specialist matters, identify the professional opinion and scope. |
| Planned evidence-supplement date | Planned review/evidence date; if unagreed, leave blank and note the pending date in next steps. It is not a completion date. |
| Actual verification date | Date the recorded check was actually performed; all example dates are simulated. |
| Triggers for renewed review | Triggers such as changes in materials, subject, basis, approval, scope or channel. |

## 3. Evidence index

| Field | Entry instructions |
| --- | --- |
| Evidence ID | Stable document ID, such as E01; note common-source relationships for copies. |
| Evidence version | Exact saved-file version, such as v1; retain original files and relationships when adding versions. |
| Filename | Identifiable filename; “final” in its name does not confirm effectiveness. |
| Provider | Actual source and provider role; distinguish issuer, forwarder and compiler. |
| Issue date | Issue date stated on the document; mark unknown if unconfirmed, rather than using its receipt date. |
| Receipt date | Actual date this version was obtained; separate from issue date. |
| Evidence form | Original, copy/scan, excerpt/screenshot, draft, record excerpt, recalculation working paper, etc.; not a credibility score. |
| Document acquisition status | Whether received, complete and legible; does not confirm authenticity, applicability or current validity. |
| Storage location | Accessible file path or controlled document location; examples resolve relative to the tool-materials directory. |
| Exact location | Physical file-page sequence and passage/clause, or sheet/row/record ID; add printed page numbers where needed. |
| Source and duplication relationships | Common issuer, forwarding, excerpting or copying; duplicate materials are not independent evidence. |
| Access scope | Who may access, whether disclosure is permitted, confidentiality, etc.; enforce actual permissions in the file system. |

## 4. Verification links

| Field | Entry instructions |
| --- | --- |
| Link ID | L identifiers pointing to verification links; multiple links are possible, but identifiers do not establish support. |
| Claim ID | Stable ID for a statement to be checked, such as C01; it does not establish the claim. |
| Claim revision | Specific claim revision linked; a C identifier alone loses the basis applicable at the time. |
| Evidence ID | Stable document ID, such as E01; note common-source relationships for copies. |
| Evidence version | Exact saved-file version, such as v1; retain original files and relationships when adding versions. |
| Evidence location | Page, clause, row or record ID actually used in this link; retain original excerpts where needed. |
| Scope supported | Specific support this document provides for this claim; arithmetic supports results only under the given inputs. |
| Not yet supported or conflicting | Uncovered steps, conditions and scope, and conflicts with other materials; not provided does not mean nonexistent. |
| Checking actions and results | What was actually read, compared or recalculated, and the result; “verified” alone is insufficient. |
| Checking role | Person/role that actually performed the check; label fictional examples as simulated. |
| Verification date | Date this linked check was completed; do not record future work as already completed. |

## 5. Actions and changes

| Field | Entry instructions |
| --- | --- |
| Record ID | Stable ID for an evidence request or change, such as A01. |
| Related claims and revisions | Affected C identifiers and revisions; multiple claims are allowed if each is traceable. |
| Related evidence and versions | Affected E identifiers and versions, including old and new materials. |
| Record type | Actual action type: evidence supplementation, conflict confirmation, version change, citation check, etc. |
| Gap or trigger | Why evidence or review is needed, identifying changes and affected scope. |
| Proposed evidence or basis for revision | Specific document, confirmation or revision basis needed; state if not yet created. |
| Proposed provider and follow-up roles | Proposed provider and follow-up roles; record confirmation when assigned. A proposal is not a commitment. |
| Proposed review or confirmation role | Proposed fact checker, specialist, basis confirmer or approver; verify role authority separately. |
| Planned date | Planned date; its arrival does not automatically complete or approve the work. |
| Actual action date | Actual date the action was completed; leave blank if not yet handled. |
| Old/new basis or wording and applicable scope | Old/new differences, approval/effectiveness/supersession, historical conditions and current scope; explicitly retain unknowns. |
| Affected materials and action records | Record each citation location, proposed action and actual result; retain incomplete items as pending. |

## 6. Use approvals and records

| Field | Entry instructions |
| --- | --- |
| Use record ID | ID for one text/channel use, such as U01; separate channels and versions. |
| Claim ID | Stable ID for a statement to be checked, such as C01; it does not establish the claim. |
| Claim revision | Specific claim revision linked; a C identifier alone loses the basis applicable at the time. |
| Proposed wording and version | Exact wording under review and its material version; an article title alone is insufficient. |
| Audience and channel | Who may see it, at which meeting, webpage, document or channel; one approval cannot cover every use. |
| Use status | Approval/use status of this text version for a defined audience, channel and conditions; separate from verification status. |
| Confirming role and approval basis | Authorized role, basis of authority and actual approval record; without evidence retain “not approved”. |
| Approval date | Actual date of the applicable approval; do not enter a date without approval. |
| Validity period or conditions of use | Specify period, subject, scope, confidentiality and reconfirmation conditions; do not assume permanent validity. |
| Citation locations and update actions | Actual citation locations and post-change action records; truthfully state if unused. |

## 7. Record statuses separately

| Dimension | Available working statuses/categories | Limits of use |
| --- | --- | --- |
| Nature of claim | Factual statement, plan or target, calculation statement, analytical judgment | Describes the kind of statement, not a credibility level. |
| Evidence form | Original, copy/scan, excerpt/screenshot, draft plan, record excerpt, recalculation working paper, other (specify) | Records document form; original/copy status does not automatically determine authenticity. |
| Document acquisition status | Not provided, partly received, received, legible copy required, not applicable (explain) | Acquisition status only; “Received_Simulated” in examples is a demonstration label. |
| Verification status | Pending verification, partially supported, supported within a defined scope, conflicting, not supported by this batch, renewed review pending | Tied to the subject, document version and checking action; not a professional due-diligence clearance. |
| Use status | Not approved, approved for limited use, review required, use suspended, withdrawn | Tied to text version, audience, channel and conditions; not generated automatically by a formula. |

## 8. Understanding verification and use statuses

| Working status | Meaning |
| --- | --- |
| Pending verification | Registered; required checks not yet completed. |
| Partially supported | Evidence supports some steps; explicit gaps remain. |
| Supported within a defined scope | Supported only for the stated subject, period, conditions and document scope; no extension beyond them. |
| Conflicting | Materials, inputs or accounts differ; the differences and applicable basis require confirmation. |
| Not supported by this batch | The materials reviewed in this batch do not support the claim; this does not deny that the fact may exist in reality. |
| Renewed review pending | Materials, scope or conditions underlying the earlier judgment have changed; check again. |
| Not approved | No valid approval basis for this text version and intended use. |
| Approved for limited use | Approved only for the specified wording, audience, channel and conditions. |
| Review required | Resubmit for review if wording, facts, audience, channel or conditions change. |
| Use suspended | Suspend use under the appropriate authority; record the basis and follow-up. |
| Withdrawn | Specified materials withdrawn as recorded; still document scope and actual results. |

“Received” does not automatically become “supported”, and “supported” does not automatically become “approved for limited use”. Status is not a score, and filling every field is no substitute for performing the checks.

[Return to blank ledger and instructions](/journal/project-evidence-ledger/materials/en/asset-08.md)