Step-by-step explanation
First freeze the selected source set; do not ask the translator to build the evidence strategy.
Record that the customer or qualified adviser selected the materials, the receiving organization or use if known, the dated instruction that applies and the exact files authorized for translation. Then give every file or logical item a neutral label such as Civil Record A, Letter B or Message Set C. The label identifies translation scope only; it does not state that the item is genuine, persuasive, required or sufficient. When selection remains unresolved, leave that decision with the customer and any qualified adviser; the translator should quote only the clearly authorized set.
Original fictional example: Amalia’s representative selects one marriage record, two signed letters and a six-image message set. The quote labels four source items and prices their complete translation; it does not add bank records, remove one selected message or claim that the selected bundle proves a marriage.
01
Build a source map before counting words or pages.
List each logical item, document family, source language, file name, page or image count, content-bearing reverse, date range and relationship to adjacent files. Keep a multi-page acta together, keep separate letters separate and state when screenshots form one conversation sequence. The source map drives pricing, assignment, review and delivery without deciding evidentiary value.
Original fictional example: Source A is a two-page family book entry; Source B is one signed letter; Source C contains eight ordered chat screenshots with two overlaps. The quote records eleven supplied pages or images across three logical sources and flags the overlaps instead of billing them silently as new content.
02
Preserve the document family and the voice of each source.
An official civil record, a sworn or signed statement, an informal letter, a message thread and a bank or address record have different structures and voices. Translate the exact title, speaker, issuer, field labels and narrative register shown. Do not rewrite an informal message as an affidavit, turn a customer label into an official title or present a shared-address record as a finding about the people named.
Original fictional example: Luis submits a note titled “Carta de apoyo” and a municipal marriage certificate. The English set keeps “Support Letter” as the writer-provided title and “Marriage Certificate” as the official title displayed on the issued record; it does not describe both items as official certificates.
03
Keep message participants, timestamps and sequence visible.
A chat screenshot can itself be the supplied communication source; that does not make a screenshot of an official record equivalent to a complete record scan. For chats, emails and social-message captures, preserve visible account labels, sender changes, dates, times, reply markers, attachments, reactions and omitted-media indicators under the project convention. Record the supplied order and disclose gaps, cropped edges or overlapping captures. A translation should not invent a sender, timezone, missing message or conversation start.
Original fictional example: Carmen supplies screenshots numbered 1, 2 and 4; image 4 begins mid-sentence. The translation maps the visible speakers and times, marks the missing sequence and partial text, and does not create screenshot 3 from context.
04
Preserve names, roles, dates and relationship words without inference.
Reproduce personal names from each source under the approved naming convention, translate explicit family or document-role labels such as esposo, madre or arrendatario in context and keep uncertain abbreviations or nicknames transparent. Do not change one source to match another, infer marital status from tone, expand a nickname into a legal name or silently reformat an ambiguous message date without recording the source format and project convention.
Original fictional example: a letter says “mi esposo Daniel,” a utility bill lists “Daniel R. Vega” and a chat shows “Dani.” The translations preserve all three displayed forms and flag the differences for cross-source review without declaring that they identify the same individual.
05
Translate complete legible content and represent visible non-text elements.
Within the approved scope, translate complete legible Spanish and represent seals, signatures, logos, handwritten notes, image captions, attachment labels and illegible or obscured material consistently. A photograph with no readable language has no text for the translator to render; whether the selected bundle needs a reference or accompanying page for that image remains a recipient-specific scope question. Describing a visible mark or caption does not authenticate the image, document, sender or event.
Original fictional example: a photo shows two people beside a handwritten caption, “Navidad 2024,” and a date stamp. The translation covers the caption and visible date stamp; it does not identify the people, verify when the photo was taken or state what their relationship is.
06
Control excerpts, duplicates, mixed language and redactions explicitly.
Record customer-selected excerpts, repeated pages, overlapping screenshots, already-English passages, visible redactions and pages excluded from scope in the source map. Do not silently omit any visible content from a source described as complete. When the written scope permits an excerpt, identify its boundaries; when the applicable instruction requires completeness, request the missing or uncropped material before certification.
Original fictional example: Mateo authorizes translation of pages 3–6 from a 40-page statement after his attorney confirms the scope. The quote and final label say “customer-selected pages 3–6 of 40”; they do not present the excerpt as the complete statement.
07
Pair every translation and certification with its source, then quote privately.
Use stable labels in filenames, cover pages, page headers or a delivery manifest so the recipient can match each English output to the supplied source. Confirm whether certifications are separate or grouped, what each one identifies and how the bundle will be delivered. For the initial quote, share only source types, countries, counts, date ranges, languages, condition, deadline and destination; send names copied from sources, account data, addresses, private messages and images only through the approved secure path when review is necessary.
Original fictional example: Sofia’s manifest maps A-ES to A-EN, B-ES to B-EN and Message Set C to C-EN plus one clearly scoped certification. Her first inquiry states counts and date ranges only; personal messages enter the project later through secure upload.