The Research Like a Pro with DNA Airtable research log has been updated for 2026! Version 4.2 includes several enhancements designed to streamline your DNA research workflow and make tracking matches more efficient. While the changes might make the base look a little different—especially in the DNA Match Details table—I think you’ll find these improvements make your research process smoother.
You can access the new templates here:
RLP with DNA Research Log 4.2 (2026)
RLP with DNA Research Log 4.2 (2026) – Blank
Note: This blog post was written with the help of artificial intellgience. AI used my Airtable base change log (that I made manually) and my spoken notes to craft the sections and paragraphs. I provided the final edit removing superfluous information and correcting phrases here and there.
Why These Changes?
The primary goal of this update was to create more flexibility in how we track DNA relationships and reduce duplicate data entry. With testing companies like Ancestry now showing Pro shared matches (how much your matches share with each other) and other testing companies / databases displaying similar information, we needed a new way to conceptualize and label the “Test Taker” and “DNA Match” fields. The 2026 update addresses this need while also centralizing where we store tree URLs and admin names to reduce redundant data entry.
Major Changes at a Glance
Person 1 and Person 2: More Flexibility for Recording Matches
The biggest change you’ll notice in the DNA Match Details table is that “Test-taker” and “DNA Match” fields have been renamed to “Person 1 (P1)” and “Person 2 (P2).” This simple change opens up new possibilities for your research.
Previously, it looked like you could only record the DNA shared between a test-taker and their match. Now, these field titles show that you can record the DNA shared between any two people—including matches and their shared matches. This is particularly useful when you’re analyzing:
- Ancestry Pro shared matches that show how much DNA two of your matches share with each other
- MyHeritage shared match data (that have always showed how much two matches share with each other in the shared matches list)
- People in GEDmatch who match each other, etc.
For example, if you manage a test for your uncle and discover two matches who share DNA with each other, you can now create a record showing their relationship—even though neither one is “your” test taker. This gives you a more complete picture of how your DNA matches cluster together.
Centralized Tree Management in the People Table
One of the most time-saving improvements is the centralization of family tree links. Previously, tree URLs appeared in multiple places throughout the base (DNA match details, Kit Acess). Now, all tree links are stored exclusively in the People table.
The People table now includes:
- Tree URL – for the primary tree (often Ancestry or MyHeritage)
- Tree URL #2 – for a second tree on a different platform (like Ancestry, MyHeritage, FamilySearch or WikiTree)
These fields now appear as lookup fields in the DNA Match Details table and Kit Access table, which means you only enter tree information once. When you update a tree link in the People table, it automatically updates everywhere that person appears in your base. No pasting the same URL for a person who matches multiple people in your project!
Centralizing Additional Fields to the People Table
Admin Field: Many of us manage DNA tests for family members, or encounter matches whose tests are managed by someone else. The 2026 update moves the fields for tracking test administrators from the DNA match details table to the People table:
- Ancestry Admin – links to the person who manages the test at Ancestry
- MH Admin – links to the person who manages the test at MyHeritage
When you add an admin for a test, Airtable automatically creates reciprocal fields called “Ancestry Kits Managed” and “MH Kits Managed” in the People table for the person who is the admin. This makes it easy to see all the kits a particular person manages, which can be helpful for noticing patterns and if you need to contact them about multiple matches.
Usernames Field: DNA matches don’t always use their real names on testing platforms. This long-text field lets you record the pseudonyms or usernames they use, so you can remember what they’re going by at each testing company—even after you’ve figured out their real name and updated your records.
Streamlined Timeline Table
The Timeline table received an improvement that will save you time with every entry. The “Sortable Date” field is now a formula field that automatically converts whatever date format you enter into a standardized sortable format (M/D/YYYY).
For example, if you only know an event occurred in “March 1857,” you can simply type that in the Date field. The sortable date will automatically populate (as 3/1/1857), making it easy to chronologically sort your timeline without having to manually format dates. If you only enter a year, the formula converts it to January 1st of that year for sorting purposes.
What Stayed the Same
The following tables remain unchanged, so your existing workflows for these areas will work exactly as before:
- Locations
- FANs (Friends, Associates, and Neighbors)
- Citation Templates
- Segments
- Surnames
- Shared cM
The Research Log table also remains largely the same, with only minor description updates to the Timeline and Add to Timeline fields for clarity.
Practical Example: Entering a Match
Let me walk you through how these changes work in practice. Let’s say I enter a match between myself (Nicole Dyer) and LD, whose test is managed by JD. We share 70 centiMorgans across four segments, and our common ancestors are Elam Hollingsworth and Martha McKee.
Step 1: Enter Person 1 – I started by typing my name in the Person 1 field. Since I already existed in the People table, my role and tree URL automatically populated through the lookup fields.
Step 2: Create Person 2 – For LD, I created a new person by typing “LD” and clicking “create LD.” Since this was a new person, the role and tree fields were initially blank.
Step 3: Add Details to the People Table Opening LD’s record, I added:
- Role: DNA match
- Line of descent from the research subject: Elam Hollingsworth > Marvin Hollingsworth > Private > JD > LD
- Tree URL: copied from the Ancestry tree link
Step 4: Record the Test Administrator Since LD’s test is managed by JD, I created a new person record for JD and linked them as the Ancestry Admin. I then added JD’s profile page URL, which gives me access to all the tests JD manages.
Step 5: Enter the DNA Match Details Back in the DNA Match Details table, I recorded:
- Shared centiMorgans: 70
- Number of segments: 4
- Database: Ancestry
- Relationship: 2nd cousin once removed
- Most recent common ancestors: Elam Hollingsworth and Martha Mae Keetch
The lookup fields automatically pulled in the roles and tree URLs I had entered in the People table, saving me from having to re-enter that information.
Bonus: Recording Shared Matches Later, I demonstrated recording the DNA shared between LD and one of his matches, DW (LD’s grand aunt). This is where the Person 1 and Person 2 fields really shine. I entered:
- Person 1: LD
- Person 2: DW
- Shared cM: 736
- Database: Ancestry
- Match page: the URL from the shared matches page
Because both LD and DW were already in my People table, their information auto-populated. The base calculated that 736 cM falls within the expected range for a grand aunt/great nephew relationship—within one standard deviation of the mean.
Making the Transition
If you’re currently using an older version of the Research Like a Pro with DNA base, you might be wondering about migrating your data. Here are a few tips:
- Start with new research: Consider using the 2026 base for new research projects while maintaining your existing base for ongoing work.
- Tree URLs: If you decide to migrate, you’ll need to move tree URLs from the DNA Match Details table to the People table. This is a good opportunity to review and update any outdated links.
- Copy and paste: We recommend copying and pasting data from an older base into the new base, if you decide to migrate your data to the new base. Just be sure to add, hide or rearrange fields to have the same number of columns in the base you’re copying from.
- Make the field updates yourself: If you’re tech savvy and comfortable with Airtable, you might prefer using my change log to update your RLP with DNA 4.0 or 4.1 Airtable base with these changes yourself. Change log: RLP with DNA Airtable Template 2026 – Updates and Change Log
Looking Forward
I hope you find these updates helpful as you work on your DNA research projects. The changes are designed to make your workflow more efficient so you can spend less time on data entry and more time on analysis and discovery. If you have ideas for how the base can be improved, please let me know in the comments.
Learn More
To learn more about how to use the Research Like a Pro with DNA Airtable base, visit our Youtube Airtable Playlist or check out our Research Like a Pro with DNA eCourse for comprehensive training on using this research log for your genetic genealogy projects.
Good luck as you fill out your base and add more DNA matches, sources, and timeline entries!
Leave a Reply
Thanks for the note!