Step-by-step explanation
Confirm the exact personal report before translating its title.
The official Importass catalog separates the Informe de tu vida laboral from the Informe de situación actual del trabajador and the Informe de bases de cotización. A personal Informe de Vida Laboral records situations of registration and deregistration across Social Security schemes and days registered, and may be complete or filtered to the selected search. Vida Laboral de Empresas is another company-level report. Read the complete heading, issuer, subject, date and stated scope before using Employment History Report or another approved English title. Keep each different source on its own manifest and quote line.
Original fictional example: secure upload contains “Informe de Vida Laboral — periodo 01/2021 a 06/2026” and a separate “Informe de Bases de Cotización.” The manifest records one filtered employment-history report and one contribution-base report; it does not merge both as a single work-history file.
01
Classify the title, issuer, subject and report scope.
Record the full non-personal title, the Tesorería General de la Seguridad Social as printed, whether the report concerns one person, and whether it states a complete or filtered period. Keep a current-status report, contribution-base report, company report, employment certificate, payslip and CV separate even if they repeat employer names or dates. Use Employment History Report only as a contextual English rendering and retain Informe de Vida Laboral on first reference when that preserves identity.
Original fictional example: “Informe de Situación Actual del Trabajador” has one current-status statement, while “Informe de Vida Laboral” has eight dated rows. The first remains a current-status report; the second is the employment-history report.
02
Build a scope, issue-date, page and continuation manifest.
Record whether the source is complete or filtered, the displayed search dates if any, report issue date, every page, row range, continuation heading, legend and visible verification or reference block. Count content-bearing pages and attachments rather than filenames. Do not put names, DNI or NIE, NUSS or NAF, addresses, company identities, codes or employment dates in ordinary quote notes.
Original fictional example: three uploads are labeled “page 1 of 3,” “page 2 of 3” and “page 2 copy.” The quote covers a three-page report only after page 3 arrives securely; the duplicate does not become a fourth translated page.
03
Lock the issuer, person and report-summary block.
Map the issuing-body name, report title, issue date, name and surname fields, displayed identity-document label and value, Social Security number label, address if present and printed total days. Translate labels and preserve every value, spacing and mask; if the approved English number style changes a thousands separator, keep the numeric value directly traceable to the source. Do not expand a partial identifier, normalize a name without an approved instruction, or treat the report total as a calculation to be corrected.
Original fictional example: the header shows “NUSS: ••••4192” and “Total días: 2.146.” Under the documented English number style, the translation renders the same total as “2,146 days” and ties it to the source value; it does not infer hidden digits or convert the total to years.
04
Preserve each regime and company or assimilated-status row.
Keep the Régimen column attached to its row and preserve the complete Empresa / Situación asimilada a la de alta text, employer name, Contribution Account Code (CCC) label and value, and any displayed province or status wording. Translate a generic label in context, but do not replace the issuing-country institution with a destination-country agency or turn an assimilated status into an employer. Repeated names and overlapping-looking entries stay as separate source rows.
Original fictional example: one row names “Taller Mar Azul S.L.” and another says “Vacaciones retribuidas y no disfrutadas.” The translation keeps an employer row and a separately labeled assimilated-status row; it does not invent a second employer.
05
Keep start, effective-start and end dates distinct.
Map Fecha de alta, Fecha de efecto del alta and Fecha de baja as three source fields whenever they appear. Apply the approved English date style without changing the underlying date and preserve blanks, open entries and repeated dates. Do not collapse start and effective-start dates because they often match, infer an end date from the next row, calculate duration, or decide what a date means for a legal right or benefit.
Original fictional example: a row prints start date 03/02/2024, effective-start date 05/02/2024 and end date 30/06/2024. The translation preserves all three labeled values and flags the unusual difference for source comparison without rewriting it.
06
Handle CT, CTP and GC as coded source fields.
Retain each abbreviation and code value in its printed column. A project glossary may explain C.T. as contract type, C.T.P. as the part-time coefficient and G.C. as contribution group when the official legend and context support those explanations. Do not convert a numeric code into a job title, unsupported contract classification or percentage that the source does not print. Keep dashes, zeros and blank cells distinct.
Original fictional example: one row shows “CT 100 / CTP — / GC 07,” and another shows “CT 200 / CTP 500 / GC 05.” The English table copies those exact codes and explains only the column labels; it does not announce full-time status or decode either contract.
07
Run row, total, continuation and bilingual QA.
Compare every English row with the matching source row from left to right, then review page order, repeated headers, continued company names, footnotes, legends, row days and the printed report total. The official explanation notes that overlapping situations may affect the total, so do not assume visible row days should add arithmetically. Flag a discrepancy for source review, preserve the printed values and request a secure replacement for any cropped or unreadable field.
Original fictional example: two June rows overlap and show 18 and 20 days while the summary does not increase by 38. QA confirms every printed value and leaves the official total unchanged; it does not delete a row or force a new sum.