How to Create Your Origins Chart

You may have seen people sharing a different kind of family tree online. Instead of showing the names of their direct ancestors, each block shows a person's place of birth. I made a somewhat different version of this chart.

My family tree is so extensive, it includes nine of my 9th great grandparents. When I created my Elder Scroll, it was clear I had more ancestors from one town than any other. Having more Colle Sannita roots than any other justifies all the time I spend on this town.

But a visual is always nice, isn't it?

Get out your crayons! Create your Origins Chart and see clearly which places are the most important to your genealogy.

To make my origins chart, I used the 10-generation fan chart I exported from MyHeritage last April. These are so beautiful and fun to look at. If your tree is on FamilySearch or Ancestry, you can see your fan chart there, too.

I used Photoshop for this project, but you can make an old-school version. Print your fan chart in black and white and get out different colored markers or crayons.

The MyHeritage fan chart using blocks of color to separate my ancestral lines. It uses a different color for each of my 8 great grandparents. There's also a version that shows all the names rather than color blocks.

I opened the color-block chart in Photoshop and kept the fan chart with all the names open on MyHeritage. (You can keep your family tree open for reference if you aren't using MyHeritage.)

Divide and Color

Starting at the center with myself, I saw that my maternal grandmother, my mother, and I were all born in New York City. So I outlined the 3 of us, filled the area in with one color (yellow), and wrote New York City on top of it.

If you're doing this on paper, outline and/or color in each group of people from one place. Make a separate key to show which place each color represents.

Next I chose the area representing my father. It was already colored baby blue, so I kept that color and labeled it Ohio. He's my only ancestor born there. His mother is my only ancestor born in New York State, outside the city, so she gets her own label, too.

Now comes the parts of my family tree with the deepest roots. The reason I kept my tree open on MyHeritage was so that I could click any person and see where they were born. My maternal grandfather and all his ancestors came from Baselice, Benevento, Italy. I outlined them, made them red, and labeled them with the town name.

All my great grandfather Sarracino's ancestors came from one town. His wife and her paternal ancestors came from the same town. So I outlined those blocks and made them orange. I labeled them Sant'Angelo a Cupolo, Benevento, Italy. Then I carved up my great grandmother Saviano's maternal ancestors. I colored in and labeled them: (1) Santa Paolina, Avellino, Italy, and (2) Apice, Benevento, Italy.

My paternal grandmother's section was simple. Her maternal side came from one town. I colored them green and labeled them Pesco Sannita, Benevento, Italy. Her paternal side was all Colle Sannita. So is most of my paternal grandfather's side. I carved out the ancestors not from Colle and colored them dark blue. I labeled them Circello, Benevento, Italy. Everyone else on my paternal side is from Colle Sannita. I colored them a lighter blue and labeled them Colle Sannita, Benevento, Italy.

These colorful fan charts from MyHeritage inspired me to turn my family tree into an Origins Chart.

How to Use Your Origins Chart

As you look at your colorful origins chart, remember to keep the scale in mind. My chart has a big chunk of yellow from New York City, but that represents only 3 people. The big chunk of baby blue from Ohio is only one person—Dad. His family was only in Ohio for a short time, and he moved to New York City as a toddler. So despite the large block of color, Ohio represents a very small part of my genealogy research.

It's the earlier color blocks that drive my genealogy research. When you consider the scale, Colle Sannita is an enormous chunk of my family tree. The second largest is Baselice. I've spent years researching these towns' vital records. I created and published inventories of all the available vital records. I have fit almost everyone from these towns into my family tree.

But it's clear I can do a lot more work with the other towns. I've gathered the vital records for all my direct ancestors already. But with such deep roots, there's much more to discover.

• Sant'Angelo a Cupolo is problematic because they have no vital records before 1861. But I can try to connect more of the town's families.
• Pesco Sannita holds a lot of promise for me.
• Santa Paolina is my only ancestral town outside of the Benevento border. It's close by in the neighboring province of Avellino. I've found DNA cousins with roots in this town. I need to connect more of those families.
• Circello has an added bonus to drive my research. My aunt's husband had roots there and in Colle Sannita. That gives me lots of ways to connect to him and his children, my maternal 1st cousins.
• Apice, the little ghost town I've written about before, is my latest target. I've almost completed an inventory of its available vital records. My nearest ancestor from Apice, my 3rd great grandmother, was born in 1816. That's so early that I didn't expect to find a lot of relatives. I was wrong. Like all these small towns, every family intermarried. That creates a lot of connections I'm eager to pull into my family tree.

You can see how your origins chart can focus and drive your research. Of all the towns I've visited, it was Colle Sannita and Baselice that had the strongest pull on my heart. My origins chart actually bears that out.

Can you see which places in your origins chart make up the most of you? If you have lots of unknown places—areas you can't color in—that's where you should focus your work. What if you haven't done any research in a place that winds up being a very important part of your story?

I invite you to create and share your origins chart. Then use it to guide your genealogy research.

5 Details to Review for a Richer Family Tree

You know the old phrase, "If I'd only known then what I know now"? It relates to genealogy very well because we build our family trees over a long period of time. Over the years I've learned so much about building a family tree. I'm sure you have, too.

As I continue to add source citations to my family tree, I revisit my early inexperienced work. Now that I know what I didn't know then, I can see past my incorrect conclusions and make breakthroughs.

Take a fresh look at your early genealogy work with these details in mind.

My "newbie" errors fall under a few categories. Here are 5 details you can review to enrich your family tree.

1. Not Assuming a Country of Origin

Years ago I documented all the available vital records from my grandfather's hometown. When I entered people with no birth record available into my family tree, I left their place of birth blank. I decided not to assume they came from the same town, or even the same country, where they later lived.

Tens of thousands of documents later, I know it was uncommon for people in this place to leave home. My roots are in small, remote, rural towns. Evidence shows people stayed in place unless they moved to the next town to marry.

Historic events in your ancestors' country may have led to a lot of migration at different times. But in my family tree, people were rarely uprooted. So even though I don't have proof of a person's town of birth, I can assume a couple of things:

• If they lived in a town where their last name was common, I'll assume they were born there. No harm done.
• If their last name is not found in their town, I'll assume they were born in Italy. This way they won't show up in a report as missing their 1870 U.S. Federal Census. (See "How to Find Location Errors in Your Family Tree".)

But let's say you're researching people in a country that saw a lot of immigration (the United States, Brazil, Australia, Canada, etc.). You shouldn't assume anyone was born in that country. You're going to need to find other documents to narrow down their place of birth.

2. Missing Certain Annotations

I looked at a ton of vital records before I realized certain important clues could be hiding there. Now that I'm hunting down source citations, I get a second chance to scan those records for clues like these:

• If a baby is born after their father died, check the birth record for a note about the his date and place of death.
• If a child is born and the father doesn't report the birth, there may be an explanation why. You may see that he was ill, the weather was terrible, he was dead, or he was somewhere else working. I have a lot of records in my family tree that say the father was in America when the baby was born. This is a good prompt to search for his immigration records.
• On Italian vital records, you may overlook the fact that a baby was stillborn. Look for the words "nato morto" (stillborn), "senza vita" (without life), or a death date in the column of a birth record. It's important to notice this because of the next item to review.

3. Not Recognizing Human Error

A town clerk is the person who creates these old vital records. And being human means there's a possibility of human error.

Some marriage records confused me long ago because the dates didn't line up. Here's what was happening. To get married in Italy, the bride and groom had to show a copy of their birth record. It's not like today. You didn't have your birth certificate in a strongbox at home. You had to request that a town clerk find the original record and hand-write a copy of it. (No Xerox machines, either.)

I found cases where the clerk copied the birth record of the bride or groom's dead older sibling with the same name. Since I have access to the birth records, I can see that this was human error. But there's another wrong-person error that can lead to big problems for your family tree.

Aside from their own birth records, the bride and groom needed their parents' consent to marry. If their mother was dead, they needed a copy of her death record. If their father was dead, they needed his death record. And if their father's father was dead, they needed a copy of his death record. Grandpa may have died many decades ago. If the town clerk didn't have the right details, he might copy the death record of a different man with the same name. And they all had the same name, didn't they?

Not recognizing this error may lead you two merge two very different people in your family tree. If the details seem off, try to search for the man who fits this stray death record.

4. Overlooking Marriage Clues

Early on I made this mistake over and over. If a couple posted marriage banns, but there was no marriage record to go with it, I assumed they never married.

Sometimes that is the case. (See "When Is a Marriage Not a Marriage?") But then I learned two important facts. In Italy, if a bride and groom came from two different towns:

• they had to post marriage banns in both towns
• they almost always married in the bride's town, even if they were going to live in the groom's town.

A couple's second marriage banns should tell you if one of them was born in another town. (See where to look in "How to Read Italian Marriage Records REVISED".) If she was born somewhere else, you can expect they married there. Now I'm making sure I check the other town for marriage records. And I'll find the original birth record of the out-of-towner.

5. Not Expanding the Search

Building on that last point, the original vital record is always better to have. The town clerk is less likely to misspell a name that's common in his town. If marriage records tell me the groom's father died in another town, I'll get the original record in that town. Then I use the original document for the source citation.

In the past I was more likely to stay within my ancestral hometown and not chase down the out-of-towners. But the purpose of my family tree is to help countless other family tree researchers. If I can cite the original birth record of my third great uncle's second wife from another town, why not do it? I won't build her entire family tree, but I want to put together enough facts to make that possible for someone else.

---

It took a huge source citations project to get me to review everyone in my tree. But it's so worthwhile. I've made discoveries, added new people, and enriched my family tree. Find a way to give your family tree a thorough review. What big discoveries will you make?

How to Use Ancestry ThruLines for Research Leads

The other day I found myself looking at Ancestry ThruLines® for the first time in a while. That's when I hit on a way to kickstart more growth in my family tree. I scrolled way down my list of direct ancestors to my 5th great grandfather. His name is Biaggio Trancuccio from Apice. That's the Italian ghost town whose vital records I've indexed so they're searchable.

Don't have an AncestryDNA test? MyHeritage has a similar feature. Choose Cousin Finder™ from the Discoveries menu. Find an interesting match and click View relationship.

What a pleasant surprise it was to find DNA matches among Biaggio's descendants. I have 2 DNA matches belonging to Biaggio's son, Giuseppe, my 4th great granduncle. I've already documented Giuseppe and his 9 children in my family tree. But I haven't looked into the marriages and descendants of the 9 kids yet.

Take advantage of these evidence-based line of succession genealogy hints.

Thanks to ThruLines, I have some evidence of Giuseppe's direct descendants. I can use the names I see on ThruLines, search the vital records, and make my way down to these new DNA matches. Note that ThruLines shows these direct descendants based on other family trees. Maybe the builders of those trees have discovered more than you have.

Start With What You Know

In ThruLines, I see that my DNA matches descend from Giuseppe's son Angelo, my 1st cousin 5 times removed. I can use the town's vital records to find all his children. I'll start with the 1878 birth record of my matches' ancestor, another Giuseppe. His birth record tells me who his father Angelo married. Knowing her name is Teresa d'Oro, I can find the couple's other children.

Going through the vital records, I found 9 children for Angelo and Teresa. Later I'll document Teresa and her family, but first I'll look at ThruLines again. My DNA matches descend from Angelo's son Giuseppe and his son Salvatore. Salvatore and his siblings were born too late to be in the online Italian vital records. This would be the end of the paper trail, but one of the DNA matches doesn't have an Italian last name. There's a good chance I can find the family in U.S. records.

Jackpot! Salvatore was born in New York and is well-documented. That means his father Giuseppe came to America. The search results for Giuseppe are an absolute treasure trove. He came to New York in 1902, single. Census records from 1920 through 1950 show me his children's names. He married a woman called Florence.

Take advantage of a different kind of genealogy hint that puts you on the right trail.

You've Got to Get Down to Climb Up

The real game-changer is the New York, New York Extracted Marriage Index. I see two mangled names with a 1911 Bronx marriage certificate number. At first glance, this seems to me to be Giuseppe Trancuccio and Fiorentina Frusciante. The transcription says Torentino Truscianti. But my knowledge of Apice names tells me it should be Frusciante. And Fiorentina is a common first name in the town.

I found the 1911 marriage certificate on the NYC Municipal Archives website. The clerk wrote Giuseppe's last name as Trangucci—exactly like the transcription. His birthplace is Apice, and his parents are Angelo and Teresa d'Oro. This confirms his identity. His wife's name, it's clear to me, says Fiorentina Fruscianti, born in Apice. Her parents are Sabato and Rosa Verginio.

With these details, I can climb cousin Giuseppe's Apice-born wife's family tree.

Turning to the Apice vital records, I found Maria Fiorentina Frusciante. She was born in 1893 to Sabato Frusciante (who is already in my family tree) and Rosa Virgilio. The last name Virgilio is not an Apice name, but it's clear she was there. She and Sabato Frusciante had 5 children besides Maria Fiorentina in Apice. Three of them married in Apice.

Be Ready to Pivot

So far, ThruLines looks correct. One of the DNA matches should be my 4th cousin twice removed, and the other, her granddaughter, my 6th cousin. I know exactly where they fit in my family tree. Now it's my job to use available records to prove it.

But something is off. ThruLines lists the older match (who died in 2017) as the daughter of Salvatore Trancuccio. Her obituary and her last name say otherwise. Evidence says she was the grandmother of the younger DNA match. But there's no connection to the Trancuccio name. Was the older match born out of wedlock? She came from the same New York borough as my Trancuccio clan, and she was born 5 years before Salvatore married.

She and I share 3 matches I've already connected to my 3rd great grandmother from Apice. I know we're related, but every record says otherwise.

She made it onto the 1940 census as an infant of 0 months. But there's a twist. The head of household is her mother. There is no husband listed, but there are 4 children, ages 7, 6, 5, and 0. In the 1950 census, my match's mother is a widow, but there's a new child who was born in 1943. The more I dug into this family, the less I understood.

In the end, I won't add these DNA matches to my family tree. I'll add notes to my DNA match list and drop the matter. If it is a case of misattributed parentage (I hate that phrase), I don't want to make any assumptions. But all is not lost. The leads generated by ThruLines have helped me expand my family tree and deepen my roots in the town of Apice.

Keep Expanding

Everything I found through this exercise gives me more leads to follow to expand my family in Apice. And it's all thanks to an Ancestry ThruLines line of succession from my 4th great granduncle. It would be easy to spend weeks harvesting these leads. And a lot of fun.

The Dangerous Jobs Your Ancestors Endured

When you look at early 1900s ship manifests, one thing is very clear. Rich people didn't leave their homeland. They didn't need to leave. Anyone related to me arrived in New York City with a few dollars in their pockets and nothing more. They were lucky to have scraped together enough money for the ticket.

Fourteen-and-a-half million people came to the United States between 1890 and 1920. They came to earning a living and escape hardship. Their numbers are staggering:

• nearly 4 million Italians
• almost 3 million Eastern Europeans
• more than 2 million Germans
• close to 2 million from Austria-Hungary
• 1¼ million from the UK and Ireland
• just over 1 million from Mexico
• ½ million from Scandinavia
• less than ½ million from Canada
• almost 1½ million from other countries

Read about what was going on in their homeland when your ancestors emigrated. After visiting Italy, I couldn't imagine why my ancestors left such a beautiful place. But history was never kind to Southern Italy. My grandfathers and some of their ancestors needed employment. They heard about the availability of jobs in other countries, so they left home.

How does your life compare to your recent ancestors' lives? A little research adds eye-opening insight to your family tree.

Hard Work Was Their Only Option

When the 14½ million did arrive, were their lives better? Well, they were alive. They were able to secure jobs. They managed to start families and raise their children. But these immigrants often worked the most difficult, dirty, and downright dangerous jobs.

During these years, most men in my family tree worked for:

• railroads
• steel manufacturing plants
• coal mines

These jobs had long hours, low pay, and almost no safety oversight.

My great grandfather Pasquale's job was to clean the boiler in locomotive trains. He was scrubbing the caked-up coal residue off the walls of the boiler. Were there any safety precautions? No. Did he develop black lung disease? Yes, he did.

My grandfather Pietro worked in two steel mills before getting fed up with the work and leaving. (The second part sounds like me!) He wanted a job that wasn't as likely to kill or maim him. He moved his family to New York City and landed a job as a stone setter for a jewelry manufacturer. He sat at a workbench all day and used hand tools. My grandmother Lucy worked, as so many women in New York City did at the time, for a clothing manufacturer. Talk about specialization, her job was to snip off the extra bit of thread around button holes on shirts. Together they earned enough money to raise and educate their children. They were lucky.

Many of Pietro's friends from the old country went to work in the coal mines of Western Pennsylvania. Every day they risked:

• collapsing cavern roofs
• gas explosions
• suffocation
• black lung disease
• serious physical harm.

In the steel mills, men worked near open furnaces, gigantic ladles of liquid metal, and coke ovens. It wasn't uncommon for them to suffer serious burns, amputation, heatstroke, and worse.

The labor conditions for shipyard workers weren't any better. Injuries, many fatal, were common. Think about the wives and children of these injured men. Imagine how difficult their lives became without their primary wage-earner. But at least child labor was plentiful. All the little kids in the family could earn a pathetic wage for dangerous, difficult work, too!

My grandfather Adamo fared much better because he had a trade. Trained as a shoemaker, he worked for shoe manufacturers, and even opened up his own shoe repair shop. He was lucky to have a trade to keep him out of the mines, railyards, and steel plants.

Death-defying work conditions led to workers' unions. Was anyone in your family tree an organizer?

Class Struggles Lead to Progress

Both immigrants and native-born Americans had hoped for better lives than this. Imagine risking life and limb for 12 hours a day, six days a week, and still struggling to feed your family. While the titans of industry became obscenely wealthy, their workers fought to survive.

It's no wonder these conditions led to the formation of unions. Before unionization, workers were faceless cogs in the machinery. They had to stand together to force corporations to treat them with any decency at all. What a rough time it was to make your way in America.

Many of today's U.S. immigrants work in farming, construction, manufacturing, and healthcare. They're also finding work in hotels, restaurants, and warehouses. There are more safeguards in place than our ancestors enjoyed. But many workplaces slip through the cracks of oversight and safety regulations.

It's fascinating to think of how conditions can change for one family over a few generations. My ancestors left behind abject poverty. They each found different ways to provide for their families. A boiler cleaner, a stone setter, a shoemaker, a tavern keeper. The stone setter's children became an insurance executive and an IBM manager. Their children became an insurance executive, a television producer, a college sports commissioner, and a website manager. And we all take work safety conditions for granted.

My family improved their lot over a couple of generations. But today is day one in another immigrant family's story. They're struggling now so their grandchildren can have a safe job and a good education. The cycle continues on and on. We all hope for a better life for our children.

Take a closer look at your ancestors' occupations on their census forms. It's one thing to know that an ancestor worked for the city department of sanitation. It's quite another thing to research the conditions of that job in that place and at that time. It makes you feel lucky to be alive.

Note that I used Microsoft Copilot to ask questions and get summaries and links to more information. Here are a few resources I found to get you started:

• "Labor Strife during the Development of Industry in America, 1890-1920" from Rutgers University.
• "America at Work, America at Leisure: Motion Pictures from 1894 to 1915" from the Library of Congress.
• "American Labor in the 20th Century" from the U.S. Bureau of Labor Statistics.

How to Find Location Errors in Your Family Tree

I love how family tree software uses predictive typing to keep us consistent. Predictive typing is a software feature that suggests words or phrases as you type. It can save you keystrokes and avoid typos.

I take advantage of this feature when entering addresses in my family tree. Why type out the full church address (Chiesa di San Leonardo Abate, Via Roma, 6, Baselice, Benevento, Campania, Italy) when I can type is "chiesa di san l" and choose the matching result?

But I've been adding facts to my family tree since 2002. I'm sure I've made mistakes. The places in our family tree need us to review them.

Let's see how the free Family Tree Analyzer (FTA) can help us find mistakes and inconsistencies.

Make that genealogy map work for you! Use this tool to find inconsistent place names in your family tree.

Your first step when using FTA is to generate your tree's latest GEDCOM file. If you use desktop family tree software, you can export a GEDCOM file from your software. If you work on your family tree online, go to your tree and export a GEDCOM file from the website.

Now open your GEDCOM in FTA and give it a moment to load. Then click the Export menu and choose Locations to Excel. This will open a spreadsheet in the generic *.csv format on your computer. Since I have Excel software, I'm prompted to save it in the Excel format right away.

Because genealogists love maps:

• Collect Important Family Places to 'Tour' Anytime
• 3 Spring Cleaning Tasks for Your Family Tree
• Without Vital Records, What Can You Do?

Get Your Places in Order

If your spreadsheet software allows, sort the contents by Country, Region, Subregion, Address, and Place, in that order. Scroll through and scan your spreadsheet for anomalies. Look for anything that strikes you as being a possible mistake. Highlight the suspicious Places in yellow so you can find and act on them later.

Here's one surprising thing I found. Looking at the town of Santa Paolina, Italy, I noticed two different church addresses. I thought I knew which one of them was wrong. But when I went to Google Maps, I realized I'd been using the wrong church name and address for this town! The bad information comes from an Italian parishes website I use often. From now on I'll have to double check its facts on the map.

Did a bad address creep into your family tree? I had one that came from a "reliable" source!

I switched to Family Tree Maker and looked at the Places tab. When I located the now-wrong church information, I was ready to make the correction. Here it's easy to overwrite all uses of the wrong address at once. With a copy and paste, I changed them all to the correct church name and address. This eliminated the wrong church from my family tree file. That will prevent the wrong church from showing up in predictive typing, too.

If your family tree is online only, open your GEDCOM file in your favorite text editor. This is how you'll see where you used the bad address. Search the entire file for the street address in question.

If the place is part of a birth, baptism, death, or residence fact, scroll up until you see a line beginning with 1 NAME. This shows you the name of the person in your family tree who needs you to fix this address. But if the address is part of a shared fact, like a marriage, look just above it for a line beginning with 1 HUSB or 1 WIFE. Copy either of their ID numbers (e.g., @I30048@) and scroll to the top of your GEDCOM file. Now search for another instance of that ID. I found a line showing 0 @I30048@ INDI. The very next line gave me the name I needed, 1 NAME Rocco Enrico /Gambino/.

Focus on the Street Address

There's another way to sort the Locations spreadsheet that will be useful to you. Try a new A to Z sort on the Place column only. When I did this I noticed three entries for 210 Ridgewood Avenue. Each one was in Allegheny County, Pennsylvania. But they all showed different towns: Bellevue, Pittsburgh, and West View. What's going on there?

Use this free genealogy tool to find location errors in your family tree. Fix them and improve your consistency.

I looked for the street address in Family Tree Maker's Places tab, but you can search your GEDCOM file, too. All three instances belong to one man. His 1930 and 1940 censuses say the address is in the West View Borough of Pittsburgh. His World War II draft registration card says it's in Bellevue. His 1950 veterans compensation application says it's in Pittsburgh.

On Bing Maps* and Google Maps, I found that 210 Ridgewood Avenue is part of the West View borough of Pittsburgh. The front window of the nearest U.S. post office (seen on Google Maps) says, "West View Branch, Pittsburgh, PA". I'll use 210 Ridgewood Avenue, West View, Allegheny County, Pennsylvania, USA, as the location. This puts a very accurate pin in the map within Family Tree Maker. The pin is right at the front door.

* I love Google Maps for its Street View, but Bing Maps points out the county or province and gives you the full information.

But why does his draft registration card say Bellevue? They wrote his address as 210 Ridgewood Ave., Bellevue, Allegheny Co., Penna., twice. On Google Maps, I found another Pittsburgh borough of Bellevue. It's right near West View, but it doesn't have a Ridgewood Avenue.

The logical answer was on the back of the draft card. The local draft board itself was not located in tiny West View, but in tiny Bellevue. It may have been a clerical error, or else that's how they were recording everyone they registered.

Without Family Tree Analyzer, there's only one way I could have found this discrepancy. I'd have to be looking at this man's list of facts in my family tree. Since he's the father-in-law of my 3rd cousin, that might never have happened. I'm glad to be able to sort this out today so I can see this cute little house in Google Street View.

I'm eager to work with this spreadsheet and add consistency to all my addresses.

Have Your Genealogy Plan B Ready to Go

My missing source citations project has exciting side effects. Revisiting some people uncovers my past errors. And sometimes I can merge two people because I found solid evidence that they're the same person.

Imagine how upset I was when I couldn't work on this project for about a week. A programming error broke the website I need the most for gathering source citations!

I needed a Genealogy Plan B so I could stay productive. Sometimes I go to Plan B late in the day when I'm getting tired of source citations. My usual Plan B is renaming the entire set of vital records I downloaded for my 3rd great grandmother's hometown of Apice. I've made tremendous progress, but I've got a ways to go.

The only problem with that Plan B is it makes me feeling like I'm neglecting my family tree. I needed something else. A Genealogy Plan B+ or a Plan C.

Take advantage of your GEDCOM file to see exactly who needs more research.

I don't remember which train of thought led me to it, but here's what I did. And it was super productive and fulfilling.

Eighty-five people in my tree have a special note in their birth date description field. It says their father was in America when they were born. This note is on their Italian birth records because it was the father's duty to report the birth. If he was away, the midwife or a grandparent would report the birth. Since this isn't the norm, they included an explanation. The reasons I've seen include:

• the weather was too bad to bring a newborn into town
• the father was ill
• the father was dead (look for a date!)
• the father was working somewhere in the countryside
• the father was out of the country, often in America.

Whenever I see that the father was in America, I add a stock phrase to the birth date description field:

• Her father was in America when she was born, or
• His father was in America when he was born.

Last week, searching for these fathers this became my Genealogy Plan B. I opened my GEDCOM file in Notepad++. This software has a GEDCOM language filter that makes the huge file easier to understand. I searched for every instance of "was in America".

One by one, I found these people in my Family Tree Maker file and began researching their father. Almost all were men who I didn't know had gone to America. I found their immigration records first. Then I searched for more U.S. documents, like draft registration cards and censuses. Sometimes I learned that they brought over their family and stayed here.

Many of the U.S. documents led me to discover later generations for the first time. I found distant cousins I didn't know existed. In some cases they had lived close to me.

After a few days of following my Italian cousins to America, I was still eager to return to source citations. Each morning I checked the Antenati site. On July 18th the website worked again!

Getting back to Genealogy Plan A, I had 2 productive days of citing sources for more than 100 people per day.

Not everyone is as driven as I am to be productive every day. But if you have more than a casual interest in your family tree, consider working on projects. Choose projects that will improve your family tree with every step you take.

Here are some project suggestions you may want to use as your Genealogy Plan A, B, and C:

• Collect missing census records and cite them immediately.
• Search for immigration and naturalization records and cite them immediately.
• Gather draft registration cards for every eligible man and cite them immediately.
• Try to fill in missing dates and cite them immediately.
• Add those missing source citations!

If your family tree has more than a handful of people, you'll need help figuring out what's missing. My tree is so vast, I abandoned my Document Tracker, but it's a great tool for seeing what you have and what you need. I used it with great results when the 1940 U.S. census came online, and a bit for the 1950 census.

Use the free Family Tree Analyzer to find missing fact types and missing censuses in your family tree.

Family Tree Analyzer offers an efficient way to see who's missing their census data. Here's how:

• Use Family Tree Analyzer to open your GEDCOM file.
• Click the Census tab.
• Choose the Relationship Types you want to search. You could restrict the search to closer relatives or test the entire file.
• Choose a census year for the UK, US, or Canada.
• Click the button labeled Show Not Found on Census.

A new window shows you who should be in the census you selected, but is missing that census citation. You can download the results as a spreadsheet and work through them.

The report works very well except when you have no mention of a country for someone. I have some English people in my tree, so I wanted to see the report for who's missing the 1881 UK census. It included a bunch of Italians for whom I have no country entered. I need to give them Italy as a place of birth even if I don't know their town. That's another project that can add value to your family tree and mine.

As for missing or incomplete dates, you have two good options. Option 1: If you use any type of desktop family tree software, sort your index list by birth date. Now you can see who has no birth date (they'll be at the bottom of the list) and who has an incomplete or estimated birth date.

I always enter an estimated birth date if a document isn't available. My rule of thumb is this:

• If you know their spouse's year of birth, give them about the same year (e.g., Abt. 1886).
• If you know the year their eldest child was born, subtract 25 and make that their estimated year of birth. This will prevent you from confusing two people with the same name who were born many decades apart.

Option 2: If your family tree is online only, go to the website where you keep it and download your GEDCOM file. Then:

• Use Family Tree Analyzer to open your GEDCOM file.
• Click the Facts tab.
• Choose the Relationship Types you want to search. (Choose them all.)
• Next to the long list of fact types, click the button that has a right arrow on it. This opens up a second long list of fact types.
• Click to select Birth in the second list.
• Click the button above that list. It's labeled, Show all Facts for Individuals who are missing the selected excluded Fact Types.

I'm happy to see that no one in my 84,044-person family tree is missing a birth date. I try to check each day to make sure I didn't add someone and forget to enter their year of birth.

I hope you're feeling inspired to choose a project or two to fortify your family tree. Here are some other value-packed projects to try:

• Another Way to Find Errors in Your Family Tree
• How to Find Distant Cousins on Facebook
• Taking the Time to Take Care of Our Own
• Work in Sprints to Strengthen Your Family Tree