Step-by-step explanation
Match each requested course to the correct syllabus version before quoting.
Start with the written request and the supplied academic records, not a folder name. Assign a neutral ID to every syllabus and record its visible course code, full title, institution, faculty or program, academic year or term, instructor or approving unit when shown, page count, attachments and version or revision date. Then create a separate link to the corresponding transcript entry using the source labels exactly as displayed. If the year, code or version conflicts, flag it for customer confirmation through a private workflow before translation. Do not decide that a similar course is an acceptable substitute.
Original fictional example: Isabel has a transcript entry for QUI-204 Química Orgánica from 2022 and two files called quimica.pdf. One visible syllabus is QUI-204, revised in 2022; the other is QUI-205, revised in 2024. The manifest maps only the 2022 QUI-204 source to that transcript line and lists the other file as unresolved. The provider does not choose the newer document because its title looks similar.
01
Build a page-level manifest for every requested syllabus.
List the neutral source ID, file, logical document, course code and title, institution, faculty or program, term or year, version, page range, content-bearing reverse, attachment and transcript match. Separate multiple syllabi bundled in one PDF and join split scans that clearly belong to one logical source. Record missing pages, cropped margins and duplicate scans before estimating word count, formatting or review effort.
Original fictional example: Marta uploads a 31-page PDF containing three syllabi and a repeated cover sheet. The manifest identifies BIO-110 on pages 1–10, BIO-215 on pages 11–21 and BIO-310 on pages 22–31, records the shared cover separately and marks which repetition is genuine source content rather than an accidental duplicate scan.
02
Reconcile the syllabus with the transcript without changing either source.
Create a mapping row for each requested course using the transcript code, title, term, grade row position or other neutral locator and the matching syllabus code, title and version. Preserve meaningful differences in spelling, abbreviations, numbering and dates. Ask for clarification when one syllabus could match several transcript rows or one row has no supplied syllabus. The mapping supports traceability; it is not a finding that the course is equivalent or transferable.
Original fictional example: the transcript lists MAT 3 Estadística Aplicada, while Luis supplies a syllabus headed MAT-III Estadística Aplicada a Negocios. The map records the variation and requests confirmation of the course and year; the translation does not normalize both titles or assert a match based only on similar words.
03
Preserve headings, hierarchy and the relationship among sections.
Translate the visible course title, unit headings, numbered modules, weekly topics, learning outcomes, prerequisites, methods and policies while preserving their source order and nesting. Keep headers, footers, page numbers, cross-references and appendices traceable. Formatting can be rebuilt for readability, but it should not flatten a module into an unrelated list or make optional material look mandatory.
Original fictional example: Elena supplies a syllabus where Unidad II contains three temas and each tema has two subtemas. The English layout retains that three-level hierarchy and the original numbering instead of turning all six entries into equal bullet points.
04
Keep hours, credits and workload figures as labeled source values.
Translate labels such as horas teóricas, horas prácticas, créditos, unidades, carga horaria and horas semanales in context, and reproduce the displayed numbers and units. Keep contact hours, independent work, laboratory time and totals in their separate source relationships. Do not convert local credits to U.S. semester credits, recalculate totals, repair an apparent inconsistency or insert an equivalency; record a visible discrepancy for review.
Original fictional example: Raúl supplies a table showing 32 horas teóricas, 24 horas prácticas and 5 créditos. The translation labels the three values faithfully and flags that the source total elsewhere says 60 hours. It does not change 56 to 60 or convert 5 local credits into another system.
05
Capture assessments, bibliography, tables and approval elements completely.
Include assessment names, percentages, formulas, grading legends, required and recommended readings, author and title data, tables, footnotes, stamps, signatures, approval dates, version-control notes and visible electronic-signature or QR-code labels. Preserve bibliographic titles as displayed unless the confirmed instruction requests another treatment, and distinguish translated labels from titles retained in the source language. Never imply that a visible seal or signature has been authenticated.
Original fictional example: Sofía has a two-page assessment table, a Spanish reading list with English-language book titles and an approval block carrying two signatures. The translation preserves each book title as displayed, translates the surrounding labels, rebuilds the table and represents both signatures as visible elements without claiming verification.
06
Control repeated content and shared institutional language.
Identify repeated policy blocks, institutional mission text, faculty templates, legends and boilerplate across the requested syllabi. Reuse approved terminology for identical source text, but retain every occurrence when it is part of each supplied syllabus unless the written scope explicitly defines another deliverable. Track near-duplicates separately because one changed percentage, date or sentence can affect the translation and QA effort.
Original fictional example: five syllabi from Andrés share a four-page faculty policy, but one version changes the attendance threshold from 80% to 85%. The quote records five occurrences and a reusable translation segment, while QA compares each instance and preserves the one changed value.
07
Run bilingual packet QA and issue a scope-specific delivery manifest.
Compare every source page with the English output for course identifiers, title, term, hierarchy, topics, hours, credits, percentages, bibliography, tables, footnotes, approvals, repetitions and notation for unclear text. Reconcile the output filenames and page ranges to the intake manifest and transcript map. The delivery note should identify what was translated, any source limitations and the certification format ordered, without stating an evaluation result, authenticity finding or acceptance prediction.
Original fictional example: Valeria orders translations of four requested syllabi totaling 68 pages. Final QA finds that one weekly-topic row was omitted during table reconstruction and that two output filenames use the wrong term. Both are corrected before the manifest is closed; the delivery note makes no statement about course equivalency or transfer credit.