# Russian Empire Revision Lists: How to Read a Ревизская Сказка and Follow a Family Across 140 Years

Revision lists are the closest thing Eastern European genealogy has to a longitudinal record. Every entry carries two ages, and every person who disappeared between revisions has a reason written next to their name. Here is how the document works and where the surviving lists actually are.


Open an 1834 revision list and find your ancestor. He is 27. Open the 1850 list for the same village and find him again. The clerk has written two numbers next to his name: 27, and 43.

That is not redundancy. It is the whole reason this record type matters. The 1850 list carries his age at the previous revision and his age at the current one, on the same line, in adjacent columns. If the two do not reconcile against the sixteen years that passed, you are either looking at a different man or looking at a lie, and either way the document has told you so.

No other record group in Eastern European genealogy does this. Parish registers give you events. Revision lists give you a household, re-audited every fifteen years or so, with the previous audit quoted back at you and a written reason for every person who is no longer there.

## What a revision list is

A revision list (*ревизская сказка*, plural *ревизские сказки*) is a household return filed for the Russian Empire's poll tax audit. Ten of these audits, called *ревизии*, were conducted between 1719 and 1859. Each one required the head of a household, an estate steward, or a community's officials to declare every taxable person under their responsibility.

It is not a census in the modern sense. A census counts people where they are. A revision list registers people where they are liable for tax, which is a different question with different failure modes. Understanding that distinction is most of what separates a useful reading of the document from a misleading one.

The upside for a researcher is that a tax audit has to be repeatable. To assess whether a community's tax burden had changed, the state needed each new list to be checkable against the last one. That requirement is what put the second age column on the page, and it is what makes revision lists usable as a series rather than as isolated snapshots.

## The ten revisions

| Revision | Conducted | Where most returns are dated | Women recorded |
| --- | --- | --- | --- |
| 1st | 1719-1727 | 1719-1722 | No |
| 2nd | 1744-1747, supplements to 1756 | 1744-1746 | No |
| 3rd | 1761-1767 | 1762-1763 | Yes |
| 4th | 1781-1787 | 1782 | Yes |
| 5th | 1794-1808 | 1794-1795 | Yes |
| 6th | 1811, unfinished | 1811 | No |
| 7th | 1815-1825 | 1815-1816 | Yes |
| 8th | 1833-1835 | 1833-1834 | Yes |
| 9th | 1850 | 1850 | Yes |
| 10th | 1857-1859 | 1857-1858 | Yes |

Three revisions counted only men: the 1st, the 2nd, and the 6th. The 6th was cut short by the French invasion, which is why so many communities have an 1811 list that stops mid-volume and then a full one in 1816.

The spread in the second column is real but misleading, which is why the third exists. The bulk of filings cluster near the start of each window. In practice you should expect to find your community's returns dated 1795, 1811, 1816, 1834, 1850, and 1858, and treat anything later in the window as a supplement rather than the main list.

Two more things about the dates on the page. They are **Julian**, which puts them twelve days behind the Gregorian calendar in the nineteenth century, and the year on the cover is the year the list was *filed*, which can be one or two years after the ages inside were reckoned. Our guide to [reading dates in old records](/blog/reading-dates-old-records-julian-gregorian-feast-days) covers the conversion and the traps.

## How the page is laid out

From the 7th revision onward the return was filed on a printed form, one household per block, spread across two facing pages. Men on the left, women on the right.

The left page runs five columns:

| Column heading | What it holds |
| --- | --- |
| Семьи № | The family number in this revision |
| Мужской пол | Names of the males: head, then sons, brothers, nephews, with relationships stated |
| По последней ревизии состояло и после оной прибыло - Лета | Age at the previous revision, or a note of arrival since |
| Из того числа выбыло - Когда именно | Who has left the household, and in what year |
| Ныне налицо - Лета | Age now, at this revision |

The right page runs four:

| Column heading | What it holds |
| --- | --- |
| Семьи № | The same family number, repeated |
| Женский пол | Names of the females |
| Во временной отлучке - С которого времени | Temporarily absent, and since when |
| Ныне налицо - Лета | Age now |

Note what the women's page does not have: a previous-revision age. Women were tracked for the record, not for the tax, so the state had no reason to make their entries auditable. When you are checking continuity between two lists, you are checking it on the men.

### The two age columns

This is the column pair to read first, before names, before anything.

A man who was in the household at the last revision has a number in column three and a number in column five. The difference between them should equal the interval between the two revisions. When it does, you have confirmed that the clerk was working from the earlier document and that this is the same person. When it does not, something happened, and the something is usually one of three things: a copying error, an age that was adjusted to move a son in or out of conscription range, or two different men with the same name collapsed into one entry.

A man with column three empty and column five filled arrived since the last revision. The reason is normally written into column three in place of the age: *прибыл в 1815 г. из Посволя*, arrived in 1815 from Pasvalys. That single phrase is a migration record, and it is the sort of thing that never makes it into an index.

Newborns since the last revision appear the same way, as do people entered with *был пропущен*, was omitted, meaning the household is admitting they were missed last time.

### The departure column

Column four is the one most researchers skim and should not.

When a person present at the last revision is gone, the form requires a reason and a year. The vocabulary is small and repetitive:

| Phrase | Meaning |
| --- | --- |
| умер в 18хх году | died in the year 18xx |
| отдан / сдан в рекруты | given up as a conscript |
| переселен, переведен | resettled, transferred |
| бежал, в бегах с 18хх г. | fled, in flight since 18xx |
| пропал без вести | went missing |
| выбыл | departed, left the register |

Consider what that means as evidence. For a death, you now have a year and a place to search a burial register, and you had neither before. For a conscript, you have a date that sends you to military records rather than to a death you will never find. For *переселен*, you have the moment a branch of the family left, which is often the single fact that explains why the parish registers stop.

And when the departure column is empty across an entire household from one revision to the next, that is [negative evidence](/blog/negative-evidence-in-genealogy) worth recording: for those fifteen years, nobody in that house died, enlisted, or moved, according to a document whose author had a financial reason to report all three.

## Why the family number does not carry over

The *ревизский номер* looks like a household identifier. It is not one. It is a position in a sequence, assigned fresh at each revision.

The 7th revision instructions are explicit about it: the lists were to be written by the *current* division of families, not by how they had been divided at the last revision. Households that split between revisions get new numbers. Households that merged collapse into one. The numbering follows the community's order of filing, which is not stable either.

So do not chain two revisions on the number. Chain them on the names, the two age columns, and the departure notes, and treat a matching number as a pleasant coincidence rather than a link.

The one exception is worth looking for. Some 10th-revision forms carry two number columns, one for the 9th revision and one for the 10th, and where that appears the continuity is documented rather than inferred. Check the form's headings before you assume you have to reconstruct it yourself.

## Supplemental revision lists, and why you are probably missing them

A revision did not close when the main list was filed. Additional returns, *дополнительные ревизские сказки*, were filed afterwards on the same printed form, entering people who had been omitted, who had returned from flight, or who had arrived and had to be registered somewhere.

The scale of this catches people out. One documented Lithuanian community's 8th revision consists of the main list filed on 26 April 1834 plus eleven supplements filed between 1835 and 1844. If you read the main 1834 list and stop, you have read one of twelve documents.

Two practical consequences. First, an absent ancestor in a main list is not an absent ancestor in that revision. Second, each supplement carries its own family numbering, which is another reason not to trust the numbers.

## Who filed the list, and what that tells you

For state peasants, the village elder filed. For a private estate, the landowner or his steward. For a town, municipal officials. For a Jewish community, the *kahal* and its elders, with the rabbi and community scribes involved.

That last case has a detail worth knowing. Jewish community returns were sometimes drafted in Hebrew and then translated for filing, with the translator signing the result. The totals of male and female souls were written at the end and signed, often in Hebrew with a transliteration alongside. When you meet Hebrew or Yiddish annotations in the margins of an otherwise Cyrillic document, that is what you are looking at, and it is frequently more legible than the Russian. We cover the scripts separately for [Hebrew](/transcribe/hebrew-records) and [Yiddish](/transcribe/yiddish-records) records.

There is also a procedural fact that bears on reliability. Lists were read aloud at public assemblies, three times, so that the community itself could confirm nobody had been left out. A revision list is a document its own subjects heard.

## Revision lists and Jewish families

For most of the Pale of Settlement, the 5th revision of 1795 is the first one that matters, because the territories came into the empire with the partitions. Lands annexed in 1772 can appear as early as the 4th, in 1781 and 1782.

The point researchers care about is surnames. Hereditary Jewish surnames were required by the *Положение о устройстве евреев* of 9 December 1804, whose article III paragraph 32 obliged every Jew to take an unchangeable hereditary surname and to have it recorded in all documents. Compliance was poor enough that further decrees followed over the next three decades, which tells you how well the first attempt went. The 1835 statute repeated the requirement in paragraph 16. The kahals were abolished separately, on 19 December 1844, and that edict did carry a surname provision of its own: after the next revision each Jew was to be informed of the hereditary name he was to use in all transactions.

So revision lists frequently are the earliest document showing a family's surname. Frequently, not reliably. The 1816 lists often still have no surnames at all, or carry one on a son and not on his father. And where surnames do appear they mutate hard across revisions, both because the clerk was writing what he heard and because the family had not settled on a spelling. Expect a name to move a long way between 1816 and 1858, and search on the sound rather than the letters.

## Where the surviving lists actually are

There is no single index. Access is per-country and, inside Russia and Ukraine, per-archive. Here is the current picture.

| Where | What is there | Access |
| --- | --- | --- |
| **RGADA, Moscow, fond 350** | Landrat books and the 1st-3rd revisions | Finding aids published as PDFs at rgada.info; document images are not online |
| **Russian regional archives** | 4th-10th revisions, in the fond of each gubernia treasury chamber (*казённая палата*) | Per-archive. Several publish their own catalogues and some their own scans |
| **Yandex Поиск по архивам** | Roughly 22 million sheets of Russian archival documents with handwriting recognition applied, revision lists included | Free. Regional coverage only, not national |
| **Ukrainian Wikisource** | Alex Krakovsky's scanning project: thousands of volumes including revision-list series for Kyiv, Podillia, Volhynia and Katerynoslav gubernias | Free, no registration |
| **Raduraksti, Latvia** | Soul revisions (*dvēseļu revīzijas*): Livland from 1782, Courland from 1797, both running to 1858 | Free, registration required, Latvian interface |
| **Saaga, Estonia** | Soul lists (*hingeloendid*) 1782-1858, browsable by parish and estate | Free |
| **LitvakSIG All Lithuania Database** | 2.8 million records of translated and indexed census and revision data, 1795 into the twentieth century, across 13 district research groups covering Kovno, Vilna and Suwalki gubernias | Public database free; contributors to a district research group get earlier access to that group's data |
| **JewishGen Belarus collection** | 100,000+ revision-list records inside a Belarus database of 800,000+ entries: 5th to 10th revisions, supplements, conscript lists and family lists | Free with registration |
| **NIAB, Minsk and Grodno** | Belarusian originals | No public scan viewer. Copies supplied per page, on request, for a fee |
| **FamilySearch catalogue** | Microfilmed revision lists for Russia, Ukraine, Belarus, Lithuania, Latvia, Estonia and Bessarabia | Mixed. Many are restricted to Family History Centre viewing; Bessarabian images are blocked online |

Three warnings about that table.

**Congress Poland did not use revision lists in practice.** The Kingdom kept its own fiscal administration, and although the statute for the 10th revision nominally extended to it, the system never ran there as it did in the interior. The equivalent record is the *księgi ludności stałej*, the books of permanent residents, maintained from the middle of the nineteenth century until 1932 and recording only those with legal residence in the gmina. Some series start earlier: the Łódź volumes run from 1827. If your family was in Warsaw or Lublin, this article is not your record type, and our [Polish State Archives guide](/blog/polish-state-archives-szukaj-w-archiwach-guide) is. The eastern gubernias, Grodno, Vilna, Volhynia and Podolia, *were* under the revision system.

**Archive access in Ukraine is unpredictable** and has been since 2022. Krakovsky's Wikisource holdings are the reliable route because they are already scanned and already public. Treat reading-room access as something to verify rather than assume.

**FamilySearch's full-text search does not read Cyrillic.** As of this writing it covers English, Spanish and Portuguese, with Chinese, French, German, Dutch and Italian in progress through 2026. Russian is not on the announced roadmap. This matters because the single most common wrong assumption about revision lists in 2026 is that the big platforms have already made them searchable by name. They have not. For Cyrillic revision lists you are still working from a shelf-mark to a volume to a page, by hand.

## The method

Given no name index, the workflow that works is the opposite of what you would do on an indexed collection. You do not search for a person. You find the community, then the revision, then read.

1. **Fix the community, not the town.** A revision list registers a person to the society they were assessed in, which may be a *mestechko* two districts from where they lived. Establish the tax registration before you go looking for the volume.
2. **Start at 1858 and work backwards.** The 10th revision is the most complete, the most likely to survive, and the most legible. It also sometimes carries the 9th-revision family number, which hands you the next step.
3. **Read the whole household block, not the line with your name on it.** The value is in the relationships, the departure notes, and the ages of the people you were not looking for.
4. **Reconcile the two age columns before you record anything.** If the arithmetic fails, note the failure in the record rather than picking the age you prefer.
5. **Find the supplements.** Look for additional lists filed in the years after the main one, under the same fond and often the same opis.
6. **Take the departure notes as leads.** Each one is a year and an event type that tells you which record group to open next.

Steps 3 through 5 are where the work is, because the document is in Cyrillic, in a nineteenth-century hand, in a formulaic register that becomes readable once you know the twenty phrases it uses and is close to impenetrable before that.

If you are working the pages yourself, our reference on [Russian and Cyrillic records](/transcribe/russian-cyrillic-records) covers the letterforms that cause the most misreadings. If you are having them read for you, open the [Research Companion](/docs/research-companion) in [KleioBase](/transcribe), a research platform that transcribes handwritten records in any language and keeps every person named in them in one searchable archive, attach the page, and ask for the structure rather than for a paragraph:

> This is a page from an 1858 Russian Empire revision list, tenth revision, on the printed two-page form. Transcribe it as a table with these columns: family number, name, relationship to head, age at previous revision, departure note with year, age at present revision. Keep the Russian for any departure phrase and give a translation alongside. Mark anything you cannot read clearly rather than guessing.

The last sentence of that prompt is the one that matters. A transcription you cannot check is not a source, and a proper name guessed from context is exactly where handwriting recognition fails, because unlike the formulaic parts of the form a surname has nothing around it to constrain the reading. Give the system the surnames you already expect, and keep the image next to the transcription in your notes. The [upload workspace](/docs/uploading-records) has a Context box for precisely this: put in the community under every name it goes by, the revision year, the language, and the surnames you are expecting.

From there each list adds people, ages and events that get matched against everyone already in your [knowledge base](/docs/knowledge-base), so the 1834 household attaches itself to the 1850 one without you reconciling anything by hand.

## What a revision list is not

Every strength above has a matching limit, and stating them is not a caveat so much as the operating manual.

**Registration is not residence.** The *ревизская душа* was a fiscal unit attached to a community. A man could be assessed in one place and living in another for twenty years. The form acknowledges this on the women's page, with a column for temporary absence and since when. Never read a revision list as proof that a family was physically present.

**Whole social estates are missing.** Nobles, both hereditary and personal, civil servants, honoured citizens, lower military ranks, private tutors, and holders of academic and medical degrees were outside the revision entirely. Clergy and their families, and soldiers and cantonists, were enumerated but on separate returns. Merchants and townsmen were included, and merchant revision lists are common, so do not assume commercial families are absent. An absent family may be an untaxed family, and the correct next step is to look for the other series in the same fond rather than to conclude the record is lost.

**Dead people stay on the rolls.** A registered soul counted as present until the next revision updated the status, whether or not the person was alive. That was not an error, it was how the tax worked, and it is what Gogol's *Dead Souls* is about. It means a name in an 1850 list is not evidence of life in 1850.

**The counts do not agree with other state figures.** Where nineteenth-century Jewish revision returns can be set against governors' own population reports, the two routinely disagree, sometimes by a quarter or more. The gap is attributed to a mix of evasion, which suppresses the count, and double registration, which inflates it, so the arithmetic can fail in either direction. What you should take from it is that a revision total is a tax figure, not a population figure, and an absence from one is weak evidence of anything.

## After 1858

The 10th revision was the last. What replaced it was the *посемейный список*, the family list, kept by rural township boards and town councils and made systematic by the 1874 conscription statute.

The family list is a different animal and the difference is easy to miss. It is not a periodic snapshot. It is a single living register, amended in place year after year, with entries struck through and new lines added as people were born, married, conscripted or died. Surviving family lists cluster in the 1860s to 1890s, and for Jewish communities most commonly 1885 to 1894.

Then in 1897 came the first and only general census of the Russian Empire, taken on 28 January, and the first record that counted people where they actually lived rather than where they paid. Its central copy in St Petersburg is gone; regional copies survive patchily.

If you have not worked with enumerated household records before, our guides to [reading old census records](/blog/reading-old-census-records) and the [census record](/what-is/census-record) definition cover the general shape. Revision lists are the harder case of that pattern, and the more rewarding one.

## Vocabulary you will meet

| Russian | English |
| --- | --- |
| ревизия | revision, the audit itself |
| ревизская сказка | revision list, the household return |
| ревизская душа | registered soul, the taxable unit |
| дополнительная ревизская сказка | supplemental revision list |
| посемейный список | family list, the post-1858 register |
| казённая палата | gubernia treasury chamber, the office that held the lists |
| мещанин / мещане | townsman, burgher class |
| купец | merchant |
| крестьянин | peasant |
| кагал | kahal, the Jewish community administration |
| местечко | shtetl, small market town |
| приписан | registered, assessed to a community |
| фонд / опись / дело | fond / inventory / file, the archival hierarchy |

## Where to start tomorrow

If your family was Jewish and from Lithuania or Belarus, start with the LitvakSIG All Lithuania Database and the JewishGen Belarus collection, because someone has already translated a large share of these lists and you can search by surname today.

If your family was from Ukraine, go to Ukrainian Wikisource and find the gubernia and revision year. The scans are there and they are free.

If your family was from Latvia or Estonia, register on Raduraksti or open Saaga and browse by estate.

If your family was from the Russian interior, identify the gubernia treasury chamber fond in the relevant regional archive, and check whether Yandex's archive search covers that region before you commit to a reading-room visit.

Whichever route you take, the thing to hold onto is the shape of the document. Two ages on every line, and a written reason next to every person who left. The empire built that structure to stop people cheating on their taxes. It works just as well for stopping you from cheating on your evidence.

For the other partitions of Poland, see our guides to the [Prussian partition](/blog/prussian-partition-records-standesamt-poznan-project) and [Austrian Galicia](/blog/austrian-galicia-records-agad-lviv-gesher-galicia).

Canonical: https://kleiobase.com/blog/russian-empire-revision-lists-revizskie-skazki