Reference Center
Is this my family member?
Maybe a cousin told you a name. Maybe you found a record, a photo, or a funeral program and something in it feels like yours. Ask here. You tell us what you know, and the archive checks it against everything the family and the public record already hold.
How the check works
- Slot matching: is there a place in the known tree where this person fits, an unnamed child, a line that stops where yours begins?
- Fact matching: do your facts meet facts a stranger could not guess, a maiden name, a burial place, a household from a census page?
- Perspective matching: has a family member already mentioned you, "my cousin in Tulsa," even if nobody entered you formally?
- Questions, when it is close: the archive may ask about things that live in family memory. It scores your answers silently.
The one way promise
The check runs one way: your facts against the archive, scored in silence. The archive never reveals its side to an unverified asker, and living people's information is never used as an answer key and never shown to prove a claim.
If the match is verified, the archive adds you to the tree, merges what you sent into your person page, and tells you exactly where you attach. If it is probable, a branch captain makes the family call. If there is no match yet, your claim stays on file, because a future upload may be the missing piece.
Checking a record instead?
Members can also run it in reverse: "Is the man in this 1930 census household my great grandfather?" The engine weighs age math, town, household members, occupation, and neighbors, and answers with the evidence for and against. See that weighing at work in a Connection Case.
Every addition the archive makes is logged with the evidence that justified it, and a captain can undo any of it. The tree stays honest because its work stays visible.