A Request for Evidence (RFE) is USCIS's way of asking for additional documentation when the initial submission is incomplete or raises questions. RFEs delay processing by weeks or months and add stress to an already complex process. Based on my experience reviewing thousands of Mexican-origin immigration packets, here are the RFE triggers I see most often — and how to avoid them.
Incomplete translation — missing CURP or registry data: This is the most common translation-related RFE. The translator renders the main fields (name, date, place of birth, parents) but skips the CURP, the book and entry numbers, or the oficialía reference. USCIS considers these administrative fields part of the document. If they appear on the source but not in the translation, the translation is technically incomplete. Always ensure the CURP is reproduced character-for-character and all registro civil references are included.
Omitted marginal notes (anotaciones marginales): Marginal notes on a Mexican birth certificate can reflect name corrections, paternal recognition, adoption, or legitimation. These notes modify the original record and carry legal weight. If the translation omits them, USCIS may question whether the translation is complete or may not understand why basic identity information (like a name) appears differently on other documents in the packet. A translator should always include marginal notes, even if they seem minor.
Name inconsistencies across the packet: Mexican naming conventions use two surnames (paterno and materno). U.S. forms typically have one "Last Name" field. If the birth certificate translation shows "García López" as the family name but the I-485 form shows "Garcia" as the last name, the adjudicator may issue an RFE asking for clarification. The fix is preventive: when translating multiple documents together, the translator should ensure consistent name rendering across the packet and add translator's notes explaining the two-surname system where relevant.
Missing Certificate of Accuracy: Sometimes people submit a translation without the required certification statement, or the certification uses vague language that does not meet the standard. The Certificate of Accuracy must explicitly state that the translation is complete and accurate and that the translator is competent to translate from Spanish to English. A certificate that says "I translated this document" without the competency and accuracy statement may trigger an RFE.
Illegible source document: If the original Mexican birth certificate is old, faded, water-damaged, or poorly scanned, USCIS may question the reliability of the translation. The translator can only translate what they can read. If portions of the document are genuinely illegible, the translator should note that in the translation (e.g., "[illegible — approximately 2 words]") rather than guessing. But the better solution is to obtain a current certified copy on formato único paper before translating — the new copy contains the same registration data in a clean, legible format.
Date format confusion: Mexican birth certificates use the day-month-year format (15/03/1990 = March 15, 1990). U.S. documents use month-day-year. If the translator does not clearly convert the date format or does not note the conversion, an adjudicator might misread the date. Best practice is to render the date in U.S. format with the original format in parentheses: "March 15, 1990 (15/03/1990 in original)."