What does it mean when the other spouse's data is blank on a Russian divorce certificate?
A Russian divorce certificate (свидетельство о расторжении брака) issued by Pervouralsk ZAGS carried full personal data only for the wife — the bearer of this copy — while the husband's date-of-birth, citizenship, nationality, and place-of-birth fields were blank. We rendered every empty field as '[Blank in original]' and added a Translator's Note explaining that post-2018 FGIS ЕГР ЗАГС practice issues each ex-spouse a copy with full data for the bearer only. The translation was delivered for a USCIS family-based filing.
What We Received
A client submitted a Russian Свидетельство о расторжении брака (Divorce Certificate) printed on watermarked Goznak security paper and issued by the Civil Registry Department [Otdel ZAGS] of the City of Pervouralsk, in the Office of Civil Status Acts Registration of Sverdlovsk Region. The form is the post-2018 FGIS ЕГР ЗАГС state template — Russia's centralized civil-registry system — with an embedded QR code in the upper-left corner that links to the Federal Tax Service verification portal.
The certificate was issued to the wife in 2026. The wife's personal-data block (full name, date and place of birth, citizenship) is fully populated. The husband's block shows only his surname, given name, and patronymic — the date-of-birth, citizenship, nationality, and place-of-birth fields are all blank. The certified translation was needed for a USCIS family-based filing.
Why This Required Special Handling
On a US-issued vital record, blank fields normally signal incomplete information — and incomplete information triggers Requests for Evidence. A USCIS adjudicator unfamiliar with Russian civil-registry practice may read the husband's empty fields the same way and pause the file pending clarification. A literal translation that simply leaves the value lines empty, or that omits the field labels entirely, looks indistinguishable from a translation oversight.
Russian post-2018 ZAGS practice for court-ordered divorces issues each ex-spouse their own copy of the certificate. The form template carries fields for both spouses, but full personal data is populated only for the bearer of that particular copy — here, the wife. The husband's matching copy, when he comes to ZAGS to collect it, will have his data fully populated and her block partial. The blank fields are a privacy and data-minimization choice by the registry, not a defect in the document.
The certificate also chains three distinct dates that must be kept in their correct chronological roles: the date of the underlying Justice of the Peace ruling; the date of marriage termination, which falls after the ruling (the operative dissolution date under Russian Family Code Art. 25); and the later date on which ZAGS registered the divorce act. A USCIS officer reviewing remarriage eligibility on a marriage-based petition needs to know which of the three dates is the legal dissolution date.
How We Handled It
We rendered every empty field on the husband's block as '[Blank in original]' — the marker we use whenever ink is absent on the source, distinct from '[Illegible]' which signals ink that cannot be read. This makes the absence-of-data structurally visible to the reviewer rather than buried in white space.
We then added a numbered Translator's Note on the certification page explaining the issuing convention.
For the act registration number, we transcribed the full 21-digit FGIS ЕГР ЗАГС sequence digit-for-digit, without internal grouping or formatting (it is not reproduced on this page) — the centralized registry treats the number as a single sequence and any added separators would diverge from the source. The certificate's series identifier, a Roman numeral followed by two Cyrillic letters, was rendered under BGN/PCGN Russian transliteration: the Roman numeral stays Roman, and only the Cyrillic letters are transliterated. The QR code in the upper-left corner was described as '[QR Code]' without content extraction — it is a verification artifact for the registry's lookup portal, not translatable data.
For the three dates, we labeled each one in its operative role: the date of the Justice of the Peace ruling, with the court precinct named as printed; the marriage-termination date; and the act-registration / certificate-issuance date. The Russian-language phrasing of the registration date in the original ('[year] года [month] месяца [day] числа' — 'in the year …, in the month of …, on the …th day') was rendered in equivalent English long form to keep the source register intact, with the conversion documented in a Translator's Note.
We preserved the eight-digit ZAGS office code exactly as printed, accompanied by the bracketed transliteration '[Otdel ZAGS]' on the institutional name so a Russian-speaking reviewer can match the English rendering against the Federal Tax Service registry portal. The round official seal in the lower-left bears the Russian Federation coat of arms with peripheral inscription partially obscured by overlap with the form text — described in brackets at its location, with a Translator's Note flagging the partial illegibility.
The Outcome
The certified translation was delivered to the client for inclusion in their USCIS family-based filing, with Translator's Notes covering the blank-field convention, the BGN/PCGN transliteration, the date-format conversion, and the partially illegible peripheral seal text.
Each Translator's Note positions a feature of the original Russian form as a registry-design choice rather than a translation gap, so the adjudicator's review path is clear when comparing the English translation against the source.
What This Means for You
Blank fields for the non-bearer spouse on a Russian divorce certificate are a registry-design feature of the post-2018 FGIS ЕГР ЗАГС system, not a defect in the document. A certified translation should mark every blank field explicitly as '[Blank in original]' and include a Translator's Note explaining the ZAGS issuing convention so a reviewer does not read the structure as missing information.
Have a similar situation?
$24.95 per physical page · no word cap
Authorship, sources & history
Update log
- Updated
Re-checked the cited source and replaced a retired USCIS page with 8 CFR 103.2(b)(3) and (b)(8). Personal details generalized further in the text and the image.
- Published
This case study was first published.
Sources & references
- 8 CFR 103.2(b)(3) and (b)(8) — Translations; requests for evidence
Electronic Code of Federal Regulations (eCFR) · Verified
Continue reading
All translation casesAll identifying information has been removed from document images. Case details are shared with client permission. No personal data is stored or displayed on this page.
Back to top