WEBVTT

1
00:00:00.180 --> 00:00:09.588
This guide explains how to organize a
large collection of records requests,
receipts, responses, and appeals so
another reader can locate a specific
document.

2
00:00:10.188 --> 00:00:19.617
The article proposes one row per artifact,
with an identifier, agency, control
number, filing and receipt dates,
response type, location, and hash
reference.

3
00:00:20.217 --> 00:00:28.239
The guide recommends identifiers that
survive sorting and re-export. A row's
position in a spreadsheet should not be
its only identity.

4
00:00:28.839 --> 00:00:39.079
If an email mentions an unavailable
attachment, the guide says to retain the
reference and describe the gap. A
reference must not be presented as the
missing document itself.

5
00:00:39.679 --> 00:00:48.617
Chronological, agency, and issue views
can organize the same underlying
records. Changing the view should not
change what an artifact contains.

6
00:00:49.217 --> 00:00:58.263
The guide favors additive updates with a
new volume, index, and change note.
This keeps older citations connected to
the version originally reviewed.

7
00:00:58.863 --> 00:01:08.399
A preserved hash helps detect whether
a file matches a recorded copy. It does
not independently establish the
document's truth, authorship, or legal
effect.

8
00:01:08.999 --> 00:01:19.196
Open the guide. Use the identifier and
location to read the actual request,
receipt, or decision. The index helps
navigation; the underlying record
supports the claim.

9
00:01:19.796 --> 00:01:28.244
The method is useful when another
person can locate the document without
accepting the compiler's interpretation. A
filing is not a finding.