# Blank evidence ledger and instructions

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

## 1. Which file to start with

Start with the [project evidence ledger Excel](/journal/project-evidence-ledger/materials/en/asset-07.xlsx). The five blank tables are separate from the fictional examples. For other tools, import the UTF-8 CSVs below. Blank CSVs contain only field names and empty rows, with no client information.

| Table | Blank CSV | Entry scope |
| --- | --- | --- |
| Claims ledger | [Claims_ledger_blank.csv](/journal/project-evidence-ledger/materials/en/asset-12.csv) | Proposed claim, subject and basis, verification progress, qualified internal wording and gaps |
| Evidence index | [Evidence_index_blank.csv](/journal/project-evidence-ledger/materials/en/asset-13.csv) | Provider, version, storage and exact location |
| Verification links | [Verification_links_blank.csv](/journal/project-evidence-ledger/materials/en/asset-14.csv) | What each document does and does not support for each claim |
| Actions and changes | [Actions_changes_blank.csv](/journal/project-evidence-ledger/materials/en/asset-15.csv) | Evidence needed, proposed follow-up, review method and affected locations after changes |
| Use approvals and records | [Use_approvals_blank.csv](/journal/project-evidence-ledger/materials/en/asset-16.csv) | Text version, intended audience, channel, approval and conditions |

Do not paste the fictional examples into an actual business ledger and continue numbering from them. Start with the blank tables. Excel dropdown options only assist data entry; they do not approve conclusions automatically. This template does not replace a document-access management system.

## 2. How one record connects

C identifiers denote claims awaiting verification; E identifiers denote documents; L identifiers link a specific claim revision with a specific document version; A identifiers record evidence requests and changes; U identifiers record specific wording and channels of use.

C01 r1 → L01 → E01 v1 indicates only that this link has been recorded. Determine the level of support from L01’s “Scope supported” and “Not yet supported or conflicting” fields; it cannot be inferred from the identifiers themselves.

Create separate L records when one claim uses several documents, and when one document supports several claims. Do not put different claims into the same “scope supported” cell.

Retain E-identifier and version relationships when adding materials. For substantive content or conclusion changes, keep the old row, add a revision and record the action. New links must not overwrite earlier verification dates.

## 3. Create the first record

1. Record the original statement, entity, subject, period, units, quantitative basis and conditions. Split multiple actions for checking; create separate claims when independent ongoing tracking is needed.
2. Identify existing files and record versions, storage, issue and receipt dates, and access scope. If the original is unavailable, record the actual form obtained.
3. Give exact physical page, heading/clause, sheet/row or record ID. Put original excerpts in quotation marks and separate them from your judgment.
4. Record support, gaps, conflicts and specific checking actions in the links table; carry qualified wording and working status back to the claim table.
5. Record proposed evidence, follow-up/provider/review roles and planned dates in the actions table. Mark unresolved assignments as “proposed” and “pending assignment”. Enter actual dates only when action occurs.
6. Add a use record only when use is needed, specifying the exact text version, audience, channel, authority basis and conditions. Without approval evidence, retain “not approved”.

## 4. Rules to retain when filling in

- The ledger is a working record. Complete documents, filled fields and correct formulas do not automatically constitute professional due-diligence clearance or permission for external use.
- Do not turn “not provided in this batch” into “does not exist”, or treat a screenshot as the complete, continuously valid current facts.
- Mark copies, forwarded versions and excerpts from one source as related; they do not add up to independent confirmations.
- Keep source materials read-only; record checks and revisions separately. The access-scope field records requirements only; actual file permissions must still be configured.
- For professional judgments, record the professional or institution, document version, applicable scope and date. A name or title alone is not a formal opinion.
- Check the need for renewed review when materials, scope or approval conditions change, conflicts arise, or external citation is planned.

## 5. Further resources

[Field and status definitions](/journal/project-evidence-ledger/materials/en/asset-09.md) · [Two fictional completed examples](/journal/project-evidence-ledger/materials/en/asset-05.md) · [Update review and citation checklist](/journal/project-evidence-ledger/materials/en/asset-10.md)

[Blank single-conclusion check SVG](/journal/project-evidence-ledger/materials/en/asset-11.svg)