Asking an AI “what happened in the spring of 1848 in Vienna” gives you a competent secondary-source summary you could have lifted from any encyclopedia. Real archive research starts from a primary document — a letter, a ledger, a parish register, a court filing — and reads outward. AI helps you find the document, decode the handwriting, translate the unfamiliar language, and cross-reference dates. It never replaces reading the actual scan. This tutorial walks the workflow historians and serious genealogists are settling into.
What this covers
A primary-sources-first research workflow with AI in four narrow roles: finding the right archive and collection, decoding handwritten or printed text in old scripts, translating from period languages, and cross-referencing dates against calendars and known events. The output is your own notes from documents you have opened, with AI as the assistant that made the documents legible.
Who this is for
Graduate students in history, archivists building finding aids, serious genealogists tracing family lines pre-1900, journalists chasing a story into the archives, and writers researching historical fiction who want their period details to survive a specialist’s read. Not for: casual “what happened in year X” curiosity — for that, a Wikipedia article is faster and equally accurate.
When to reach for it
When you have a specific person, event, or place to investigate, access to a real archive (online or in-person), and a willingness to read primary documents in their original language and script. Skip when your question is broad (“the Renaissance”) — narrow first; AI cannot do the narrowing for you.
Before you start
- Frame your question as narrow as possible. “Who signed the 1812 parish register at St. Stephen’s in Vienna as godfather to Maria Schmidt” is researchable. “Vienna in 1812” is not.
- Identify candidate archives. National archives, diocesan archives, municipal records, university collections — each have catalogues. AI can suggest candidates but cannot replace the catalogue search.
- Set up a notes file with one section per document you actually open. Citation first (archive, fonds, box, folder, item), then your reading.
- Pick a vision-capable model: Claude Opus 4.7, GPT-5.5, or Gemini 3 Pro. You will need to upload scans for transcription help.
Step by step
- Use AI to suggest archives, not to answer the question. “For research on [person / event / place] in [period], which national, regional, ecclesiastical, and university archives hold relevant fonds? List specifically by archive name and likely series.” Take the list, verify each archive exists, check their online catalogue yourself.
- Search the archive catalogue yourself. No AI here. Archive catalogues use controlled vocabulary, period-specific naming conventions, and indexing systems that AI does not navigate well. Use the archivist’s reference desk if you are stuck — they are the actual experts.
- For a candidate document, upload the scan to AI for transcription help. Old German Kurrent, Italian humanist hand, 18th-century English chancery — AI is now decent at all of these, but always wrong somewhere. Ask “transcribe this scan line by line; mark uncertain readings with [?].” The bracket markers are non-negotiable.
- Verify the transcription against the scan, line by line. Especially for proper names, dates, and numbers. AI confidently invents plausible-looking names that match the script’s style. This is the single highest-fidelity step in the whole workflow.
- Translate with context, not in isolation. Ask the model “translate this 18th-century Italian notarial passage; note any archaic terms or formulas and explain them.” The explanation is more valuable than the translation. For broader research workflow context, see the AI industry research workflow — the spot-check discipline is the same.
- Cross-reference dates against the right calendar. Pre-1582 Catholic Europe is Julian; pre-1752 Britain is Julian; Eastern Europe used Julian into the 20th century. Ask the model to confirm which calendar applies and convert if needed — then sanity-check against a known event from the same document.
- Notes go in your file with a verbatim quote, your translation or transcription, and the page/folio reference. Never paraphrase a primary source without quoting it first. If you cannot find your way back to the original line, you cannot defend the citation.
First-run exercise
Pick a single document you can access online — a single page of a parish register, a one-page letter, a single notarial entry. Run the full workflow on it: transcribe with AI, verify against scan, translate, cross-reference one date. Time it. Most first runs take 45-60 minutes for one document; that is the actual unit of archive work, and AI compresses it modestly, not dramatically.
Quality check
- Every transcription has been read against the scan, line by line. Uncertain readings are marked.
- Proper names and dates have been double-checked. These are where AI fails most often.
- Translations include notes on archaic terms, abbreviations, and standard formulas — not just the modernized text.
- Dates have been converted to a consistent calendar with the conversion shown.
- Every note has a full citation traceable back to the archive’s reference system. No “the letter says” without a folio number.
How to reuse this workflow
- Build a personal cheat-sheet of the scripts and languages you keep encountering. AI helps for the first decoding; over time you stop needing it for the common abbreviations.
- Save a transcription prompt and a translation prompt as templates. Period-specific. The 18th-century notarial prompt is different from the 19th-century parish-register prompt.
- Keep a log of every document opened with a one-line summary. Over a long project, this becomes the index you wish the archive had.
Recommended workflow
Narrow question → candidate archives → catalogue search you do yourself → scan upload → AI transcription with uncertainty marks → line-by-line verification → translation with archaic-term notes → calendar conversion → notes with full citation. One document per 45-60 minute working block.
Common mistakes
- Letting AI summarize “what happened” without ever opening a primary source — you are writing from Wikipedia.
- Trusting the transcription without verifying against the scan — AI invents plausible names that fit the handwriting style.
- Using a translation without the archaic-term notes — you lose the legal or religious formula, which is often the most informative part.
- Confusing calendars. A date that is “off by 11 days” is almost always a Julian-Gregorian issue, not a mistake.
- Skipping citation discipline. Notes without folio references are notes you cannot defend in a footnote.
- Asking AI for “what is this document about” before reading it yourself. The summary will be confidently wrong.
FAQ
- Which model is best for old handwriting?: Vision models from major providers all handle common scripts; Claude Opus 4.7 and Gemini 3 Pro are currently strongest for Kurrent and humanist hands. None is reliable on heavily damaged documents.
- What about right-to-left scripts (Arabic, Hebrew)?: Modern AI handles printed text well, handwritten poorly. For Ottoman or rabbinic hands, expect to verify every line.
- Can AI help me find a specific person in an archive?: Indirectly. It can suggest where to look, but the actual name-matching has to happen against an indexed catalogue or a digital finding aid.
- What about copyright and archive terms of use?: Many archives restrict uploading scans to third-party services. Check the archive’s terms; some require local-only processing.
- Is paraphrasing a primary source ever acceptable?: Only after you have quoted it once. The paraphrase is a working note; the quote is the citation.