Keep The Story Beside The Source

Managed and Beta

A family history should show what is known, where it came from, and what remains uncertain.

Bring interviews, photographs, letters, documents, recordings, places, dates, relationships, citations, permissions, contradictions, and unanswered questions into one source linked family record.

Book it. Build it. Sell it. Run it. Capture it. Share it.

Open the appRequest a written scopeBrowse products and services

The Family Record · Video Explainer

Keep the Story Beside the Source.

A family history deserves more than a polished story with the uncertainty quietly removed.

Strategic Communication and Innovation Designed by Julie Good, MATC · Good Creative Media · San Antonio, Texas

Genealogy Research Software: IMC Machine Family Record

See interviews, photographs, documents, recordings, dates, relationships, citations, contradictions, permissions, and unanswered questions become one source-linked family research record.

Watch on YouTube

The Family Record is a managed beta. Family reviewers retain authority over names, relationships, access, corrections, permissions, and the final narrative. Source citation and human review remain central.

Current The Family Record application surface
Current IMC Machine application surface. Individual functions carry their own maturity, provider, access, and approval requirements. Open the full size application screen.

The Problem It Solves

The event record should not disappear between systems.

The Family Record

Families inherit boxes, stories, names, photographs, recordings, and confident recollections that do not always agree. A finished narrative can make uncertainty disappear. A useful family record preserves the story and the evidence without pretending they are the same thing.

Complete Workflow

Move from source to approved outcome.

The Family Record

  1. Define the family, subject, purpose, participants, permissions, privacy boundaries, sources, and responsible owner.
  2. Digitize or organize approved interviews, photographs, letters, records, media, places, dates, names, and relationships.
  3. Transcribe, describe, compare, research, cite, and identify agreements, conflicts, gaps, and questions.
  4. Let family reviewers correct names, relationships, dates, descriptions, access, and narrative choices.
  5. Prepare an approved chronology, dossier, story, media collection, map, memorial, reunion program, or private archive.
  6. Preserve the source links, citations, versions, permissions, uncertainties, and future research path.

What The User Gets

Useful work, visible responsibility, and a record worth keeping.

User outcomes

  1. A family narrative whose statements remain connected to sources.
  2. Privacy and permission choices visible throughout the work.
  3. Contradictions and uncertainty preserved instead of quietly edited away.
  4. A record that can grow across generations, events, interviews, and new discoveries.

Examples and samples

  1. A family records an elder’s interview and connects each story to photographs, documents, places, people, and review notes.
  2. A reunion becomes a live interview event, digitization day, family map, program, media archive, and next research plan.
  3. A musician’s family preserves recordings, performances, rights, press, photographs, instruments, oral history, and public or private access decisions.
  4. A historic property record connects owners, residents, renovations, photographs, maps, documents, interviews, and cited public history.

Visual Workflow

Family Record from source to approved outcome.

Follow the practical movement of the work. The machine organizes, drafts, compares, and prepares. The responsible person keeps authority over approval and release.

Family Record workflow for intake, authorized research, sources, identity confirmation, chronology, permissions, human review, dossier, and archive
Family Record. Interviews, records, photographs, letters, repositories, identity confirmation, chronology, uncertainty, permissions, human approval, the designed dossier, and the source archive remain together. Open the full size workflow. Open this workflow in Figma.

Evidence And Boundaries

Show what is current. Name what still requires people, providers, or a managed scope.

  1. The public Family Record product defines source linked genealogy and family history through records, interviews, photographs, timelines, citations, relationships, and uncertainty.
  2. Current core capabilities in intake, transcription, media organization, chronology, research, source records, review, dossier preparation, and archive support a managed Beta workflow.
  3. The product does not claim that generated relationships, historical conclusions, legal status, DNA interpretation, or identity findings are automatically true. Human review and source citation remain central.

Connected product areas

Real Estate StudioPodcast and Broadcast StudioCapture and AI DirectorEducationContracts and RightsTrust

Read. Compare. Decide.

The website should do the explaining.

Review the actual application surface, the complete workflow, the practical outcomes, and the maturity boundary. Then open the application, browse the catalog, or request a written scope.

Book it. Build it. Sell it. Run it. Capture it. Share it.

Open the appExplore all productsRequest a written scope