The patronymic is derived from the father's given name by adding a gender-specific suffix. Understanding the formation rules helps translators verify that the patronymic matches the father's name across documents — and catch errors when it does not.
Male patronymics: Most male patronymics end in -ович or -евич. Examples: Александр → Александрович, Иван → Иванович, Сергей → Сергеевич, Дмитрий → Дмитриевич, Николай → Николаевич, Владимир → Владимирович, Андрей → Андреевич.
Female patronymics: Most female patronymics end in -овна or -евна. Examples: Александр → Александровна, Иван → Ивановна, Сергей → Сергеевна, Дмитрий → Дмитриевна, Николай → Николаевна, Владимир → Владимировна, Андрей → Андреевна.
Irregular forms to watch for: A handful of father's names produce irregular patronymics that a careless translator can get wrong. Илья → Ильич (m) / Ильинична (f); Никита → Никитич (m) / Никитична (f); Кузьма → Кузьмич (m) / Кузьминична (f); Фома → Фомич (m) / Фоминична (f). These do not follow the standard -ович/-овна pattern, and the feminine forms in particular are easy to mis-transliterate.
Russian vs Ukrainian patronymics: This is a critical distinction for Slavic document work. The same father's name produces different patronymics in Russian and Ukrainian. For a father named Сергей (Russian) / Сергій (Ukrainian): Russian male patronymic = Сергеевич, Ukrainian male patronymic = Сергійович. If a person's birth certificate shows one form and an older or cross-border document shows the other, the translator must recognize this as a language difference, not a name discrepancy.
Verification across documents: When translating a packet, the translator verifies that the patronymic is consistent with the father's имя. If the birth certificate shows Александровна and the father's name on the same certificate is Александр, the patronymic is confirmed. If they do not match, it may indicate a clerical error or a documentation issue the applicant should resolve before filing.