How can I make a handover note so another relative can continue documenting keepsakes?
Quick answer
Write a short handover that explains what the catalog covers, how its records are structured, which conventions are already in use, and what remains uncertain. Show one example record, label guesses as unconfirmed, and give the next relative a small prioritized list of items or questions to tackle. Keep decisions and uncertainties visible so new entries stay consistent without turning assumptions into family facts.
The question, the details, the next step.
I’ve started a keepsake catalog, but another relative is going to help. What should the handover note actually cover so they can continue it without guessing?
Make it a working guide to the catalog, not a general household filing manual. A useful handover answers four questions: what is being documented, how to add a record, what conventions the current catalog follows, and what needs attention next.
Start with a brief scope statement, such as: “This catalog describes selected family keepsakes and the information we currently know about them.” Then name the catalog location using a placeholder if needed, such as [shared folder or binder], and identify who can answer family-history questions if that is known. Don’t imply that a guess is established family history.
Include the date the note was prepared and, if useful, who last updated the catalog. Keep the tone neutral: the note is there to help someone continue the work, not to certify every detail.
How do I explain the conventions? We have some incomplete entries, and I don’t want the new person to make them look more certain than they are.
List only the conventions the catalog actually uses. For each one, say what to enter and how to handle missing or uncertain information. For example, if your catalog uses fields for title, description, approximate date, source, and questions, explain those fields in plain language. Don’t add a convention simply because it seems tidy; first mark it as a proposed change.
You could include guidance like: “Use a short, recognizable title. Describe visible or known details without adding an assumed story. Write ‘unknown’ when the information is not known; use ‘possibly’ for a tentative identification. Keep questions in the questions field rather than resolving them by inference.” Adapt these labels to the system you already use.
A hypothetical example might read:
“Title: Blue-and-white serving dish. Description: Oval dish with a blue floral pattern; small chip on the rim. Date: Unknown. Family connection: Possibly from [relative’s household]—unconfirmed. Question: Can anyone identify the maker or remember who used it?”
The example demonstrates how to separate observation from interpretation. Replace the details and labels with your real catalog’s conventions; this is not a claim about an actual family object.
What should I do with open questions and the next items to document? There are more keepsakes than we can handle at once.
Give open questions their own section and make their status clear. For each one, record the item or entry it concerns, the exact question, what is already known, and a possible person to ask if appropriate. Leave the answer blank until someone provides it. If accounts differ, note that the information is unresolved rather than choosing the version that sounds most plausible.
Then choose a short next-step list. Prioritize items that are easy to identify or that have information likely to be lost, such as an object someone can still describe from memory. Mark these as suggestions, not a ranking of importance. A practical list might say: 1. Add basic descriptions for the keepsakes on [shelf or in box]. 2. Ask [relative or family member] about the unlabeled photograph. 3. Review entries marked “possibly” and keep or revise them only when there is a reason to do so.
Avoid assigning someone a task without checking that they want it. If a proposed priority depends on someone’s availability, label it as a question rather than a commitment.
Can you give me a copyable handover outline that’s short enough for someone to use while cataloging?
Use this outline and fill only what you know:
Keepsake catalog handover — [date]
Purpose and scope: [What this catalog covers; what it does not cover.] Where the current catalog is kept: [Location or placeholder.] How to add an entry: [Fields to complete and any established naming or numbering convention.] Conventions: [How to describe objects; how to mark unknown, approximate, or unconfirmed information.] Example entry: [One real catalog entry that demonstrates the conventions, with uncertain details labeled.] Open questions: [Item or entry — question — known information — possible person to ask, if appropriate.] Suggested next steps: [A few specific items or questions, in priority order; label these as suggestions.] Changes to discuss before adopting: [Any proposed convention changes or unresolved choices.]
Before handing it over, check that the example matches the current catalog, every uncertainty is labeled, and the next person can tell which decisions are established and which are still open.
A practical checklist
State the catalog’s scope and where its current records are kept.
Describe only the conventions already in use, including how uncertainty is marked.
Add one example entry that separates observed details from unconfirmed context.
List open questions with the relevant item and any known information.
Choose a few specific next steps and label them as suggestions.
Flag proposed convention changes for discussion rather than silently adopting them.
A few more useful answers
Should the new relative correct an entry if they think a detail is wrong?
They can flag the detail and add the reason or source of the correction, but should not silently replace an uncertain statement with another assumption. Keep conflicting accounts visible until there is a clear basis for a change.
What if there is no agreed convention for a particular field?
Mark the choice as unresolved in the handover and suggest a simple option for the family to discuss. Until then, avoid presenting a new preference as an established catalog rule.