Step-by-step explanation
Identify the exact source record before deciding what belongs in the translation.
Record the complete displayed title, issuing country and office, source date, certificate, extract or copy wording, page count, content-bearing sides and every supplied continuation, certification or authentication page. Use a neutral source label so replacement scans and attachments remain tied to the same record. A customer shorthand such as “marriage certificate” is useful for intake but must not replace the title and form shown on the source. This inventory defines production scope; it does not decide whether the record is current, official, legally sufficient or acceptable.
Original fictional example: a two-sided record titled “Acta de Matrimonio de Puerto Claro” arrives with a separate one-page registry certification. The quote labels the act as MR-1 and the certification as MR-1A, records three content-bearing sides and does not rename the certification as part of the act.
01
Inventory every page, side and attachment.
List visible page numbers, fronts and content-bearing backs, continuation sheets, marginal-note pages, certifications, apostilles and other supplied attachments. Keep each component in source order and record duplicate, replaced, cropped or missing files before quoting. A blank-looking reverse should be checked, not assumed blank from a thumbnail.
Original fictional example: source page 1 says “Página 1 de 2,” but only one image was supplied. Production requests page 2 instead of treating the one-page capture as the complete source or describing it as complete in the translation certification.
02
Map parties, roles and every labeled name field.
Create a field map for names exactly as displayed under labels such as contrayente, cónyuge, esposo, esposa, parte, testigo, celebrante, registrador or funcionario certificante. Preserve accents, punctuation, order, initials, prior-name fields and blank fields. Do not translate personal names, assign gender or family relationships from assumptions, fill a blank from another document or silently replace source spelling with a passport spelling.
Original fictional example: “Ana María López Ruiz” appears under “Contrayente A,” while “Apellido anterior” is blank. The English version keeps the full name and the blank field instead of borrowing a surname from a separate identity document.
03
Keep marriage, registration, issue and annotation dates distinct.
Tie every date to its source label and location. The marriage or ceremony date, registration date, filing date, certification date, issue date and date of a later marginal entry can differ. Render a clear written date in an approved unambiguous English style; if a numeric date remains ambiguous after context review, raise a query or use approved transparent notation rather than swapping day and month automatically.
Original fictional example: “married on 14 March 2018,” “registered on 16 March 2018” and “issued on 2 August 2026” remain three labeled events. QA does not collapse them into one certificate date.
04
Translate registry, ceremony and witness fields in context.
Preserve the relationship among registry office, book, volume, folio, page, entry or act number, place, officiant, witnesses and any displayed capacity. Use one reviewed term for each source label within the project while keeping distinct source fields separate. Translate property-regime wording or other legal labels only as source text; do not explain ownership, rights, duties or present legal status.
Original fictional example: “Tomo 12 / Libro 4 / Folio 084 / Acta 031” remains four separate labeled registry references, and “Régimen: sociedad conyugal” is rendered under the project terminology without stating who owns any property.
05
Account for marginal notes, corrections and later entries.
Translate every legible annotation included in the agreed source scope and preserve its date, authority, reference number and connection to the main entry. Distinguish source wording from translator notation and flag any cropped or unreadable part. A note may mention a correction, later registration, separation, divorce or another event; reproducing it does not authorize the translator to interpret current marital status or legal effect.
Original fictional example: a margin contains a dated correction changing one letter in a surname and cites entry 44-B. The translation reproduces the correction and reference beside the main entry; it does not silently overwrite the earlier spelling or decide which spelling controls elsewhere.
06
Represent certifications, stamps, seals, signatures and validation elements.
Translate legible wording in certification blocks, stamps and seals and describe visible non-text elements under the approved notation convention. Record which page, official, date or attachment each mark appears beside. Do not copy a signature, recreate a seal, validate a QR code or electronic identifier, or treat a visible mark as proof that the record is authentic or acceptable.
Original fictional example: a round mark reads “Registro Civil de Puerto Claro” beside an unreadable signature and a cropped QR label. The translation identifies all three elements and requests an uncropped image; it does not reproduce the signature or claim the code was verified.
07
Run bilingual, field and page-level QA before delivery.
Compare the English output with every source component in scope. Check the document title, issuer, party labels, names, dates, places, registry coordinates, officiant and witness fields, marginal notes, numbers, stamps, seals, signatures, page order and attachments. Resolve production queries, then prepare a delivery manifest stating exactly which source files, sides and attachments the translation and any certification cover.
Original fictional example: QA finds that “Folio 071” was typed as “017” and that the reverse-side certification is absent from the delivery list. Both production errors are corrected before certification, without adding an opinion about the record’s validity.