FTDNA Matrix Compiler and Reporter — Workflow Guide

Introduction

FTDNA Matrix Compiler and Reporter is a local-browser tool designed to progressively compile, track, analyze, and export FTDNA match-to-match matrix data.

The tool is built around an incremental workflow:

The workflow is intentionally cumulative.

Over time:


Forensics Mode and Local Use

The tool is designed around a local-browser, offline-safe workflow.

At the top of the application is the:

When enabled, Forensics Mode blocks common browser network APIs, including:

This is intended to provide additional assurance that:

remain processed locally within the browser session.

Important Clarification

If the tool is opened from a website, the HTML page itself is initially downloaded from that website in order to load the application.

However:

Additional Comfort Option: Save a Local Copy

For users who prefer maximum isolation or additional peace of mind:

This allows the tool to operate entirely from a local file instead of loading from a hosted web page.

In this configuration:

Many users prefer this workflow for:

Recommended Practice

For maximum operational reassurance:


Important Workflow Principle

The browser session itself does NOT permanently retain your compiled pair data.

If the page is:

the in-memory compiled dataset is lost unless exported.

Because of this:

Regular use of Export Saved Pair Dataset is one of the most important operational practices when using this tool.

The Saved Pair Dataset functions as the persistent working database for the project.

Recommended practice:

This prevents accidental loss of:


1. Choosing and Loading the Base Match List

The first step is selecting the match list that will define your working universe.

The match list provides:

In most workflows, this will be an exported match list from FTDNA or a manually prepared spreadsheet.

The tool supports multiple header styles automatically, including examples such as:

Only a name column and a subject cM column are required.

Standard Workflow

Once imported, this match list becomes the baseline reference for:


2. Restoring Existing Pair Data (Saved Pair Dataset)

If you have already gathered matrix data previously, import your Saved Pair Dataset before beginning additional ingestion.

This is one of the most important workflow concepts in the tool.

The Saved Pair Dataset contains:

Important Concept

The web page itself does not permanently store compiled data once the browser session is closed or refreshed.

This means:

Because of this, the recommended workflow is:

Standard Workflow

This allows the tool to:


3. Loading the Auto-Zero / ICW Pair Universe

The Auto-Zero / Gather Target Pair List is optional, but becomes extremely valuable for larger projects.

This file defines the pair universe that should exist within the project.

Conceptually, this functions similarly to an ICW (“In Common With”) universe:

Why This Matters

Without this file loaded, the tool assumes that every possible pair inside the active universe is still needed.

This creates a much larger gather universe and usually requires many more matrix pulls to complete coverage.

With the Auto-Zero / ICW file loaded:

Important Behavior

When this file is loaded:

Important Requirement

The target pair list should include all expected pairs down to the minimum cM threshold being used for the project.

Incomplete target universes can produce misleading automatic 0 assumptions.

Standard Workflow


4. Choosing the Selection Mode

After imports are complete, choose the active selection mode.

This determines the working match universe used for:

There are two primary modes.

Top N from Match List

This is the standard workflow.

The tool uses the top ranked matches from the imported match list.

Example:

The active universe becomes the selected top-ranked matches.

Standard Workflow

This mode is ideal when building structured coverage progressively outward from the strongest matches.

Pasted Data Only

In this mode, the active universe is determined entirely by the pasted matrix data itself.

Only matches observed in pasted grids become active.

Standard Workflow

This mode is useful when:

Choosing Between Them

In most structured projects:

For reconstruction or irregular ingestion workflows:


5. Gathering and Compiling Matrix Data

Once the base match universe has been established, the next phase is gathering match-to-match matrix data from FTDNA and compiling it into the project dataset.

This is the core operational workflow of the tool.

The goal is to progressively:

Understanding the Workflow

The tool is designed around incremental accumulation.

Each pasted matrix:

The process is intentionally cumulative.

Over time:

Standard Matrix Gathering Workflow

The tool will then:

The ingestion status output will report:

Important Concept: The Master Pair Dataset

Internally, the tool maintains a continuously growing master pair dataset.

This dataset becomes the single source of truth for:

Every successful paste contributes additional information into this dataset.

0 cM vs Missing Data

One of the most important distinctions in the tool is the difference between:

Observed 0 cM:

Ungathered pairs:

Duplicate Pairs

If the same pair is encountered again with the same value:

This is normal behavior.

The ingestion report will indicate how many pairs were:

Conflict Detection

Occasionally, the same pair may appear with different values across separate matrix pulls.

When this occurs:

Best Practices During Gathering

Recommended workflow:

This creates an incremental long-term build process instead of repeatedly restarting coverage collection from scratch.


6. Coverage Tracking and Best Next Runs

Once matrix data has been ingested, the tool can evaluate which pairs are still missing and recommend additional matrix pulls.

This is where the coverage-planning portion of the tool becomes useful.

Missing Pairs

Click:

The tool will generate a report of all currently ungathered expected pairs inside the active universe.

These represent:

If an Auto-Zero / ICW Pair Universe is loaded:

Without that file:

This can dramatically increase the number of required matrix pulls.

Best Next Run

Click:

The tool will recommend up to 10 matches that collectively cover the greatest number of currently missing pairs.

This is designed specifically around the FTDNA matrix limitation of selecting up to 10 people at a time.

Operational Workflow for Best Next Run

Over time:

Copy Name Buttons

The Best Next Run output includes:

Clicking a copy button:

This is intended to speed up:

Export All Best Runs CSV

Click:

This generates a staged sequence of recommended 10-person runs intended for:

Each exported run:

Important Guidance for Large Projects

The full Best Runs export performs repeated optimization passes across the active missing-pair universe.

For stability and performance:

Example:

Very large expansions can:


7. Reports and Outputs

Once matrix data has been gathered and compiled, the Reports tab provides multiple ways to view, analyze, and export the dataset.

These reports are built from:

The Reports tab is intended for:

Matrix Color Thresholds

At the top of the Reports tab are the matrix coloring thresholds.

Minimum Fair / Yellow cM

Default:

Minimum Good / Green cM

Default:

Values below the Fair threshold remain white.

Grouped matrix mode still uses:

However:

Pair Listing Report

The Pair Listing report displays the stored pair dataset in row format.

Pair Listing Export

Click:

This exports the current pair listing as a CSV file.

Compiled Matrix Report

Click:

The tool generates a popup matrix report based on:

Matrix Display Behavior

The matrix includes:

Matrix Coloring

In standard mode:

Subject cM Context

Both horizontal and vertical headers include:

Clickable Match Names

Clicking a match name opens:

Matrix CSV Export

Click:

This exports the compiled matrix in CSV format.

Matrix HTML Export

Click:

This generates a presentation-ready standalone HTML matrix file.

The exported HTML preserves:

Matches Both Analysis

The report shows:

Sorting

The Subject and Selected Match columns are sortable.

Matches Both CSV Export

Click:

This exports the currently selected Matches Both report as a CSV file.

Numeric UID Mode

When enabled:

This can be useful for:


Disclaimer

This tool is provided “as is” without warranties of any kind, either express or implied.

Use of this tool is at your own risk. The user is solely responsible for any interpretations, decisions, or actions taken based on its output.

Users are responsible for ensuring compliance with all applicable laws, privacy standards, and ethical guidelines when working with genetic or personal data.