Adoptions, Step-Parents, and Half-Siblings: How to Map Modern Families

Walk into most family tree software and the assumptions are obvious: one mother, one father, biological children, marriages that lasted forever. That's not what families actually look like. Here's how to record the real shape of yours.

Divorce and remarriage

The most common "complication" — and the easiest to handle. The trick is to think of marriage as an event with a start date and (sometimes) an end date, not as a permanent label. If your grandmother was married to your grandfather from 1955 to 1973, then to her second husband from 1976 onward, you record both: one ended marriage and one current.

Children get attached to their actual biological parents, not to whoever was around when. Your mother is your grandmother + your biological grandfather's child, regardless of who your grandmother is currently married to. Half-siblings from the second marriage are children of your grandmother + her second husband.

This pattern handles the bulk of "messy" families: divorces, remarriages, third marriages, even the rare relative whose status changes back and forth. Record marriages as events, attach kids to their actual parents.

Step-parents

A step-parent isn't a biological parent of the child — they're the spouse of the biological parent. If you want to acknowledge them in the tree (and you usually should — many step-parents are the actual parents in every way that matters), there are two approaches:

• By marriage only. Record the marriage to the biological parent, and the relationship is implicit — anyone reading the tree can see that this person was a step-parent to so-and-so during such-and-such years.
• As a parent with a "step" subtype. Some people add a parent edge from the step-parent to the child, marked as "step" rather than "biological." This is useful when the step-parent raised the child as their own. The biological parent edge stays too.

The right call depends on how you want to remember it. There's no universally correct answer — both are valid, both are honest.

Adopted children

Adopted children should appear in the tree as children of their adoptive parents, with the relationship marked as "adopted" rather than "biological." If the biological parents are known and you want to record that lineage too, you can — add parent edges from the biological parents with the same "biological" subtype.

This matters for two reasons: (1) accuracy, especially for medical history, and (2) some adopted children search for their biological families later, and a tree that already has a placeholder for them makes that search easier.

For closed adoptions where the biological parents aren't known, just leave them out. The adopted child stands on the tree as a child of the adoptive parents, and that's complete enough.

Unmarried co-parents

People have children together without getting married. This has always been true and is increasingly common. The right way to record it: a parent edge from each parent to the child, but no marriage record between the parents. If they have a relationship status worth noting (long-term partners, briefly together, etc.), most tools let you record an "unmarried partnership" — basically a marriage without the marriage.

Importantly: if the parents are no longer together, you don't add a "divorce." There was no marriage to dissolve. They were co-parents who didn't marry.

Half-siblings

Half-siblings share one biological parent, not two. They're already represented correctly if you've recorded each child's parents accurately. If your father had a daughter from a previous relationship, that daughter is your half-sister: she's your father's child but not your mother's. The tree shows this naturally — she has a parent edge to your father but not to your mother.

You don't need to add a "half-sibling" relationship type. The shared parent (and the unshared one) does all the work.

Same-sex parents

Two parent edges from two parents to the child, just like any other family. The biological mechanics (surrogacy, adoption, donor) can be recorded as subtypes if you want the detail, or left implicit. The relationship between the two parents is a partnership/marriage like any other.

Multiple marriages with overlapping kids

One of the trickiest cases: someone marries person A, has kids with A, divorces A, marries B, has kids with B, then later has another child with A again. Sounds rare, but if you go back far enough in any family you'll find something like this.

The tree handles it cleanly because each child is attached to their actual biological parents, regardless of marriage state. The kids with A are children of {parent + A}; the kids with B are children of {parent + B}. The marriage records (one ended, one current) sit alongside the parent edges. The whole picture is preserved.

Stillbirths, infant deaths, and miscarriages

This is hard. These are real children who lived briefly or never lived outside the womb, and they often go uncounted in formal trees. Whether to include them is a personal choice that varies by family.

If you do include them, they're children like any other — with whatever name (sometimes none), whatever dates, marked as deceased. A small note in the record honors what happened. Many families find that recording these losses, decades later, is meaningful.

The principle

The point isn't to make the tree look "normal." The point is for it to be accurate. Real families are blended, divorced, remarried, adopted, complicated. A tree that hides those facts to look neat isn't a record of your family — it's a fiction. Record what actually happened, in whatever shape it happened, and the tree will be useful to your descendants in a way a sanitized one never could be.