How to build a household digital document index

A household document index is a short map of the digital records you have chosen to keep. It can tell you what a file is called, which folder it belongs in, where copies are held and whether the item is a draft or final version. The index does not need to contain the document itself, and it should not contain passwords, full account numbers or other secrets simply to look complete.

This guide applies a few published personal-archiving principles to an original home-admin worksheet. It is not legal, financial, cybersecurity or records-retention advice. You decide which documents matter to your household, which versions you are entitled to keep and where they may be stored. The worked figures below are invented and do not describe files that HomeMojo has inspected.

Choose the scope before naming files

Start with one bounded collection, such as appliance manuals you already hold, household project notes or family-history documents. Do not begin with every file on every device. Write a one-sentence scope: ‘Index the final manuals and receipts that I have chosen to retain for current household items.’ That is an organising decision, not a recommendation about what any law, insurer, supplier or warranty requires.

The Library of Congress digitalpreservation.gov — personal digital records guidance says to identify where digital document files are held, decide which have long-term value, give selected documents descriptive file names, create a directory or folder structure and write a brief description of that structure and its documents. It also notes that a person may choose final versions alone or include drafts and revisions. Those are the source facts used here; the fields and codes in this worksheet are HomeMojo suggestions.

Map locations before you reorganise

Make one row for each location you intend to inspect. Use a neutral label such as Laptop / Home admin, Cloud folder / Manuals or USB drive / Selected archive. At this stage, count file sightings rather than claiming a count of unique documents. The same document may appear in several places, and similar names may refer to different versions.

Suppose an invented first pass finds 7 selected-looking files on a laptop, 5 in a cloud folder and 4 on removable media. The location count is 7 + 5 + 4 = 16 file sightings. It is not yet a total of 16 distinct records. If four pairs are later confirmed as copies of the same four documents, the number of unique items would be 16 − 4 = 12 only under that confirmed pairing. Keep ‘possible duplicate’ as a status until the contents and provenance are actually checked.

On a narrow screen, scroll the table sideways. Keyboard users can focus it and use the arrow keys.

The distinction matters because adding location totals answers ‘how many files did I see?’ rather than ‘how many records do I own?’. If a file cannot be opened, record that observation without repeatedly changing it or guessing its contents. If a location is unavailable, mark the map incomplete instead of filling the gap from memory.

Use a descriptive name pattern, not a mystery code

A descriptive filename can combine a date, subject and version label. For example, `2026-10-kettle-manual-final.pdf` states more than `scan004.pdf`. This is an illustrative pattern, not a universal standard. Retain an original name in the index when changing it could break a reference, create confusion or conflict with the system that supplied it.

Pick separators and date formatting once for this small collection. Then write the rule above the table so another household member does not have to reverse-engineer it. If exact dates are unknown, do not invent them; use a clearly labelled approximate period in the notes while keeping the filename conservative.

Treat drafts and finals as separate decisions

The Library of Congress guidance explicitly allows selection of final versions alone or drafts and revisions too. Use a version column rather than deleting every apparent duplicate on sight. A draft may be irrelevant to your purpose, or it may contain context you deliberately want to retain. The index should show that decision rather than silently collapsing the files.

For an unresolved set, give each file its own temporary row and add a relationship note such as ‘same title, contents not compared’. Once checked, record the basis for treating files as copies or separate versions. File size and filename alone can be useful clues, but this worksheet does not treat them as proof that contents are identical.

Keep the index distinct from the copies

The source also recommends making at least two copies of selected documents in different places, keeping a summary description with important papers, checking files at least annually and creating new media copies every five years or when necessary. Those are the Library of Congress recommendations, not a guarantee that any particular device, service or routine prevents loss.

Your index can therefore include separate fields for ‘copy locations’ and ‘last readability check’. Do not mark a second location as checked merely because a sync icon appeared. If backup design, encryption, account recovery or sensitive-document security matters, use appropriate specialist guidance rather than treating this organising sheet as a security system.

Run a ten-file trial

Test the structure on no more than ten selected files. For each one, confirm the scope rule, copy its current name, choose or record a descriptive name, label its version, record its folder and list unresolved questions. Then try to find three items using only the index. This is a usability check for your naming map, not evidence of completeness or disaster recovery.

If physical papers must be matched to the digital map, the drawer-zone worksheet can help reserve a labelled paper area without claiming archival suitability. If you are considering a document box, the shelf-measuring worksheet keeps external dimensions, entry route and storage position separate. The goal is one readable map whose limits remain visible.