Talent & Cross-Border Leadership School · Learning track
Communicate business meaning clearly across English and Spanish—not merely word for word.
Start Lesson 1No signup, cloud storage, cross-device sync or verified completion. Saving is optional. This browser profile is shared with anyone who can use it; private mode, browser cleanup or storage limits may remove work. Use only fictional or non-sensitive material. Export a copy before relying on this device.
Not saved. Worksheets, answers and practice notes currently last only in this tab.
Practice markers are self-reported, never credentials.
A different tab changed this track. Nothing was overwritten. Export your current draft first if needed, then load the saved version before editing and saving again.
01 Learning plan
Public foundation 2026.10.08-learning-paths-1 · published 2026-10-08. Independent subject-matter review is pending; paid delivery and credential issuance remain closed. This track is organized around inspectable work, not attendance alone.
Workload
No validated completion time is published. Read the six modules, then complete the six case assignments and self-review across as many sessions as needed. This release has not yet been timed with learners; no facilitated capstone is included.
Prerequisites
Outputs
Working vocabulary
02 Public foundation curriculum
Each module states what to understand, what to practice, what evidence to retain, and the criteria for moving forward. The case lab turns those standards into six realistic assignments.
Module 1
Objective: Define purpose, audience, decision, risk, language needs, and review authority before drafting or adapting a business message.
Open Lesson 1: examples, worksheet & feedback →Clear bilingual communication begins before translation. Identify who will read or hear the message, what they know, what decision or action is needed, who owns it, when it is due, and what happens if meaning is wrong. Mark numbers, dates, currencies, units, names, product identifiers, legal qualifications, safety statements, and commitments that must not drift. Decide whether English, Spanish, or both are required and which version is the controlled record. Do not assume a country, surname, accent, or job title reveals a person's preferred language or literacy.
Choose the work type deliberately. A routine operational message may be drafted bilingually by a competent professional; creative marketing adaptation needs approved claim and brand review; legal, certified, medical, safety, technical, immigration, court, or regulated material may require a qualified translator, interpreter, attorney, engineer, clinician, or other specialist. Record the boundary before work starts. Use plain structure in the source because ambiguity multiplies across languages. The communicator's job is to preserve approved meaning, surface uncertainty, and make action clear—not to create authority or certainty the source does not contain.
Practice
Classify eight fictional communications by audience, decision, controlled language, consequence of error, and required reviewer; rewrite one ambiguous source brief before translating anything.
Evidence to keep
An audience-and-risk matrix, language-of-record decision, specialist-routing map, and approved source brief.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 2
Objective: Write concise English and Spanish email that preserves professional intent, makes requested action explicit, and closes the response loop.
Open Lesson 2: examples, worksheet & feedback →A useful business email can be scanned for purpose, context, requested action, owner, deadline with time zone, attachments or links, and next step. Put the decision near the beginning and use short paragraphs or bullets for complex requests. Acknowledge what is known and what remains uncertain. English and Spanish versions do not need identical word order, but they must preserve scope, authority, conditions, numbers, and tone. For example: English—‘Please approve the revised shipment date by 3:00 p.m. MDT (UTC−06:00; America/Denver) on October 14, 2026. If we do not receive approval, production remains on hold.’ Spanish—‘Por favor, apruebe la fecha de envío revisada antes de las 3:00 p. m. MDT (UTC−06:00; America/Denver) del 14 de octubre de 2026. Si no recibimos la aprobación, la producción permanecerá en espera.’ The controlled details are the requested decision, deadline, time zone, condition, and consequence—not identical syntax. Avoid unexplained idioms, sarcasm, vague pronouns, excessive formality, and machine-translated phrases that no competent reviewer has checked.
Tone depends on relationship, channel, country, organization, and individual preference; there is no single Latin American or U.S. style. Choose an appropriate greeting and form of address, and confirm preferences rather than inferring status. When replying, answer the requested decision, identify incomplete items, and state when the next update will arrive. If a message changes payment details, requests credentials, creates unusual urgency, or conflicts with prior authority, pause and verify through a known channel. Preserve the approved record and do not send confidential information through an unapproved translation or messaging tool.
Practice
Complete one pathway: if competent in both languages, draft English and Spanish versions of a project-delay email, decision request, and correction and route them for review; if competent in one language, prepare the controlled source brief and review checklist, then assess Academy-supplied bilingual drafts with an approved translation workflow and competent bilingual reviewer. In both pathways, check action, tone, protected details, and uncertainty; do not claim authorship or approval in a language you cannot competently review.
Evidence to keep
A six-message portfolio with source brief, reviewer comments, revision history, and a protected-detail back-check.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 3
Objective: Support bilingual meetings with prepared terminology, inclusive clarification, and a decision record that participants can verify.
Open Lesson 3: examples, worksheet & feedback →Before the meeting, state purpose, desired decisions, participants, languages, accessibility needs, time zones, agenda, pre-read, and terminology. Decide whether bilingual facilitation, consecutive interpretation, simultaneous interpretation, or written support is appropriate. A bilingual employee is not automatically a qualified interpreter and should not be assigned high-risk interpretation without consent, competence, preparation, and role clarity. Share key terms and documents early. During discussion, use manageable segments, identify speakers, avoid talking over others, and pause for interpretation or questions.
Clarification is a quality control. Ask what a term means in context, restate the proposed decision, and invite correction without embarrassing the speaker. Do not use idioms, jokes, speed, or accent as tests of competence. The meeting summary should record decisions, owners, due dates with time zones, open questions, risks, and approved language, not a word-for-word transcript unless required. Distribute promptly in the agreed language or languages and give participants a correction window. Confidential, privileged, personal, or regulated discussions follow specialist, consent, retention, and access rules.
Practice
Complete one pathway: plan and facilitate a simulated bilingual supplier meeting with a competent bilingual partner or interpreter and publish a two-language decision record; or, as a solo one-language learner, prepare the agenda, language-support brief, terminology questions, and correction checklist, then assess an Academy-supplied bilingual meeting record. Preserve three terminology clarifications and a defined correction window.
Evidence to keep
Meeting brief, terminology sheet, interpretation-role decision, facilitation checklist, bilingual decision record, and corrections log.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 4
Objective: Build and govern a bilingual glossary that keeps operational meaning consistent and routes uncertain or high-risk terms to qualified owners.
Open Lesson 4: examples, worksheet & feedback →Terminology is contextual. The same English or Spanish word can change meaning by country, industry, product, law, or organization. Capture the source term, approved target term, definition, part of speech where useful, context sentence, prohibited or discouraged variants, source, owner, approval date, and revision. Include product names, process steps, roles, status labels, units, and standard phrases that recur. Do not copy an online glossary blindly or assume the most common dictionary equivalent fits the business decision.
Govern the glossary like a working control. Contributors may propose terms, but designated subject-matter and language reviewers approve high-impact entries. Record regional variants when they matter rather than declaring one form universally correct. Link each term to the authoritative specification, law, customer direction, or brand source where applicable. When no approved equivalent exists, preserve the source term, explain it, and flag the uncertainty instead of improvising certainty. Review after product, process, legal, or brand changes, and prevent obsolete terms from remaining in templates. A glossary improves consistency; it does not replace specialist translation review.
Practice
Create the source-term inventory, definitions, contexts, owners, and review states for a 20-entry manufacturing glossary. If competent in both languages, propose English–Spanish terms for reviewer approval; otherwise assess Academy-supplied target terms with an approved workflow and competent bilingual reviewer. Include two regional variants, three protected product terms, and four entries requiring technical or legal review; do not self-approve unfamiliar target-language terms.
Evidence to keep
A controlled glossary with definitions, context, sources, owners, approval states, variants, prohibited terms, and change history.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 5
Objective: Respond to customers and conflict in both languages with factual empathy, explicit next actions, and appropriate escalation.
Open Lesson 5: examples, worksheet & feedback →A trustworthy customer response acknowledges the experience without admitting facts or liability that have not been established. State what is known, what will be checked, the next action, owner, realistic timing, and reference number. Preserve the customer's key terms and emotional concern while avoiding canned empathy that does not match the issue. Confirm names, product identifiers, dates, currency, quantities, and requested remedy in both languages. Do not promise refunds, warranties, legal outcomes, or technical fixes beyond authority.
Conflict communication should lower uncertainty, not silence disagreement. Separate fact, interpretation, impact, need, and proposed resolution. Ask clarifying questions, summarize the other person's meaning, and offer choices within authority. Avoid translating insults, threats, discriminatory language, or legal allegations casually; preserve necessary evidence and route the matter through the approved safety, conduct, legal, HR, or security process. For vulnerable customers or legally required language access, follow applicable policy and qualified interpreter or translator procedures. Document outcome and follow-up with access and retention appropriate to the case.
Practice
Prepare responses for a late delivery, disputed charge, and product-safety allegation. If competent in both languages, draft both versions and route them for review; otherwise create controlled source responses and review Academy-supplied bilingual versions with a competent reviewer. Classify routine elements and specialist escalations, and do not claim bilingual authorship or approval beyond demonstrated competence.
Evidence to keep
A customer-response set, fact/interpretation map, authority checklist, escalation record, and reviewer-approved final versions.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Module 6
Objective: Deliver concise bilingual presentations and transfer high-risk language work to specialists with complete context and review evidence.
Open Lesson 6: examples, worksheet & feedback →A bilingual presentation needs one narrative, not two competing slide decks. Define audience, decision, language format, speaking roles, time, accessibility, and questions. Keep slides visually simple, use consistent approved terminology, and protect numbers, units, dates, citations, claims, and qualifications. Decide whether text appears in both languages, alternates by section, or is supported by interpretation; avoid shrinking type to fit duplicate paragraphs. Rehearse transitions and pronunciation of names and specialist terms without mocking accents or demanding imitation.
A strong specialist handoff includes the source file, purpose, audience, jurisdiction, medium, deadline, controlled language, glossary, reference material, protected elements, known uncertainties, required certification or credentials, formatting needs, reviewer, and acceptance process. State whether work is translation, interpretation, localization, transcreation, legal review, or technical review. Protect confidential information through approved contracting, access, and tool controls. On return, check completeness, protected details, terminology, layout, and unresolved queries; do not claim certified accuracy unless the required qualified process actually occurred. Retain versions and approval evidence according to policy.
Practice
Prepare a five-minute launch briefing and a specialist handoff for a safety instruction. If competent in both languages, deliver the approved bilingual format; otherwise deliver the controlled source-language briefing and assess an Academy-supplied bilingual version with a competent reviewer. Review returned work with the controlled checklist and do not claim certified or bilingual accuracy unless the required qualified process occurred.
Evidence to keep
Presentation brief, accessible slides, speaker plan, source citations, specialist work order, query log, back-check, and final approval record.
Ready to move on when
Module provenance
External authorities, common professional practice, and Academy-selected controls are identified separately. A source supports only the stated scope; it does not convert this lesson into legal, licensed, accredited, or regulatory advice.
Free operational lesson
Identify the purpose, action, owner, deadline, and risk before adapting language. Preserve meaning, mark uncertain terminology, and never improvise legal or technical certainty.
Identify purpose, audience, action, owner, deadline, consequence of error, and controlled language before choosing words.
Mark names, numbers, dates, units, claims, qualifications, authority, safety statements, and commitments that must survive adaptation unchanged.
Use plain, audience-appropriate English or Spanish without stereotyping region, accent, formality, fluency, or preferred communication style.
Use sourced glossary entries, version history, named reviewers, and visible uncertainty instead of improvised technical or legal equivalents.
Route certified, legal, medical, safety, regulated, technical, or high-impact language to qualified specialists with complete context.
Worked example
An English customer email says the team will 'review eligibility for a replacement within five business days.' A rushed Spanish version says the company 'will replace the product in five days.'
Send the Spanish version because it sounds more helpful and is grammatically fluent.
Return to the approved source meaning, protect the conditional eligibility review and business-day timing, use the controlled warranty terminology, and have the authorized customer-policy owner review both versions. Issue a corrected message promptly if the inaccurate version was sent, without concealing the error.
Why it matters: Fluent wording is not enough. Bilingual business quality depends on preserved authority, conditions, deadlines, and remedies, with visible review when consequences are material.
03 Control the work
Common failure modes
Ambiguity does not disappear in another language. Clarify decision, scope, owner, qualifications, and protected details before adaptation.
Use neutral language where appropriate, document regional or industry variants, and ask the actual audience rather than ranking dialects.
Fluency does not confer legal, certified, technical, medical, safety, or interpretation credentials; obtain consent and qualified review.
A polished sentence can still change amount, date, condition, authority, risk, or requested action. Back-check protected meaning.
Operating measures
Percentage of sampled bilingual communications preserving approved names, numbers, dates, units, qualifications, claims, duties, and decisions without material error.
Use it to decide: Any high-consequence error triggers correction, impact review, and stronger source or specialist controls.
Percentage of identified material ambiguities resolved or formally escalated before the communication is approved and released.
Use it to decide: Low performance indicates pressure to guess, unclear ownership, or an unsafe review process.
Percentage of sampled controlled terms used according to the approved glossary and current revision across relevant communications.
Use it to decide: Recurring variation prompts glossary, template, tool, reviewer, or training correction rather than blame for dialect difference.
Percentage of bilingual meeting or customer records containing confirmed decision or next action, owner, date, open issue, and distribution evidence.
Use it to decide: Missing closure fields trigger process correction even when language quality appears fluent.
04 · Applied case lab · 2026.08.31-practice-3
The packet contains contradiction and incomplete evidence on purpose. Each assignment now identifies the exact fictional inputs available to the learner. Complete a bounded starter, mark missing records instead of inventing them, and compare your reasoning with the debrief—not with a pretend single perfect answer.
This is a fictional, sanitized bilingual communication case. Companies, people, contracts, messages, numbers, and terminology are fabricated; it is not legal translation, interpretation, employment, safety, or regulatory advice.
CB01 · citable versioned case brief
PuenteWorks is a fictional U.S.–Mexico product team preparing a bilingual launch for an industrial maintenance kit. The approved English source says orders placed by October 10 are expected to ship within 15 business days after final artwork approval. A Spanish draft says orders are guaranteed to arrive within 15 days of purchase. The source price is $2,450 before applicable taxes and freight; one Spanish sales email states $2,450 total delivered. The warranty draft uses replace, repair, and remedy inconsistently, and the team's glossary gives two Spanish terms for nonconformance without stating which applies to a product defect versus a process record. A supplier email from Monterrey uses ahorita for timing; one colleague interprets it as immediately and another as later today. The launch meeting is scheduled for 3:00 p.m. Mountain, but the action note records 3:00 p.m. Mexico City without a date-specific conversion. The meeting transcript says legal will review the final warranty, while the summary says legal approved the warranty. A customer complaint in Spanish describes calentamiento and olor extraño after installation. A sales representative translates this as normal heat and requests a reassuring response, but no qualified technical assessment exists. The customer also asks whether continued use is safe. The presentation contains a chart with translated labels but no units, source period, or accessible text alternative. Leadership wants both language versions sent today and says bilingual staff can approve any translation. Learners must clarify audience and purpose, structure email, preserve meeting decisions, control terminology, respond to conflict and safety-sensitive customer language, and prepare an accessible presentation and specialist handoff. They must preserve meaning rather than word count and must not turn bilingual ability into legal, technical, safety, or certified translation authority.
Judgment required: Ask the source owner for the intended time and record a precise action without judging the dialect.
Do not assume: Do not select a dictionary meaning or rank one regional variety as more professional.
Judgment required: Preserve the report and use approved safety direction while qualified specialists assess the product.
Do not assume: Do not reassure, diagnose, assign fault, or instruct continued use without authority.
Bounded case starter
Classify each communication by audience, decision, authority, sensitivity, and consequence before revising language.
Deliverable: A bilingual communication brief and material-meaning checklist.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F01, F02, F03, F04, F05, F06, F07, F08, F09, F10, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 2 authored artifacts with 12 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: Communication risk depends on purpose and consequence. The brief should identify which meanings cannot change and who has authority to approve them before drafting begins.
Bounded case starter
Rewrite the launch email so action, conditions, price, owner, deadline, and clarification route are explicit in both languages.
Deliverable: An English and Spanish email pair with back-check record.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F01, F02, F03, F04, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 3 authored artifacts with 4 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: The improved email need not mirror word count, but conditions and exclusions must remain explicit. A back-check should focus on decisions, numbers, dates, and authority.
Bounded case starter
Resolve time-zone and approval-status conflicts and publish a correction without rewriting the transcript.
Deliverable: A bilingual correction notice, decision-summary starter, attendee-confirmation template, and missing-date escalation; no local-time conversion is represented as verified.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F07, F08, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 4 authored artifacts with 7 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: A summary should correct the operational record while preserving the underlying transcript. Pending review cannot become approval through translation or condensation.
Bounded case starter
Clarify ahorita and establish context-specific terms for warranty and nonconformance concepts.
Deliverable: A controlled glossary entry set and terminology-decision log.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F05, F06, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 2 authored artifacts with 6 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: Controlled terminology accepts legitimate variants while choosing one meaning for a defined business context. Source-owner clarification is stronger than guessing from dialect stereotypes.
Bounded case starter
Prepare an empathetic response and technical escalation without normalizing an unassessed condition.
Deliverable: A bilingual holding-response draft and specialist-handoff starter with the continued-use question preserved and approved immediate safety wording marked not supplied.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F09, F10, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 2 authored artifacts with 3 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: The response should be empathetic and precise about uncertainty. It must retain the customer's actual observations and route safety questions without adding reassurance or diagnosis.
Bounded case starter
Repair the bilingual presentation and define review requirements for high-risk content.
Deliverable: A six-slide accessible briefing outline, source-and-gap index, and reviewer-signoff matrix with unknown chart units and source period left visibly pending.
Completion boundary: Complete a bounded starter and gap analysis using only CB01, F08, F11, F12, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.
Workbook plan: 3 authored artifacts with 10 stable practice rows. The download includes a prerequisite check, six-to-eight task-specific operating steps, field-by-field guidance, completed supported and known-gap examples, supporting-artifact examples where authored, stop/go/escalate rules, and an exact completion test.
Provided inputs
Evidence criteria
Debrief lens: Accessible presentation quality includes data meaning, not just translated labels. Review authority should follow subject competence rather than bilingual fluency alone.
Self-review standard
There is no single universal translation for every audience or region. Strong bilingual work preserves the approved decision, makes ambiguity visible, and escalates specialist meaning. The downloadable rubric is formative guidance only—not a grade, verified completion, credential assessment, or professional approval.
Route to: Appropriately qualified legal translator or interpreter and authorized legal, technical, safety, or regulatory owner
Learner boundary: Bilingual ability alone does not establish specialist competence, certification, or approval authority.
Route to: Approved emergency or product-safety pathway and qualified engineering, quality, or regulatory responders
Learner boundary: The communicator preserves meaning and urgency but does not diagnose or authorize use.
05 Editable working tool
Use one row per material phrase or decision. Record the intended business meaning before selecting language, cite the approved term source, and assign a qualified reviewer when consequence or specialization requires it. Add as many rows as needed, export a CSV, or print only this tool. Entries are not transmitted. They last only in this tab unless you opt into device-only saving in the learning-work panel. No account or cross-device sync is provided.
| Source phrase or decision | Intended meaning | Approved term | Audience note | Reviewer |
|---|---|---|---|---|
Completed example
Data boundary: Work only in an approved system. Do not place passwords, payment-card data, government identifiers, health information, export-controlled material, client secrets, or unpublished invention details in this public worksheet.
Each two-question check works independently. Review any answered question immediately; you do not need to finish all twelve. Feedback is formative, not a verified grade or credential.
07 Sources and handoffs
Module provenance distinguishes external authorities, legal-status evidence, and Wealth Synergy internal operating standards. Requirements change; verify current source text and obtain qualified advice when a decision carries legal, financial, technical, employment, safety, or regulatory consequences.
digital-gov-plain-language · Official guidance
Current official U.S. General Services Administration guidance for audience-centered organization, concise wording, informative headings, document design, and comprehension testing.
Open reviewed external source ↗iso-17100-2015 · Official standards-body overview
Official ISO overview of the translation-services standard covering processes, resources, and review; obtain the licensed standard where formally applied.
Open reviewed external source ↗digital-gov-multilingual-glossaries · Official guidance
Official U.S. government guidance on using multilingual glossaries to improve consistency, quality, and understandability; a qualified reviewer remains necessary for legal, safety-critical, or specialized content.
Open reviewed external source ↗ftc-advertising-marketing-basics · Official guidance
Official U.S. guidance on truthful, nondeceptive advertising claims; bilingual or localized marketing must preserve material qualifications and evidence.
Open reviewed external source ↗nist-local-time-faqs · Official guidance
Official NIST guidance distinguishing MST (UTC−07:00) from MDT (UTC−06:00) and explaining Arizona exceptions.
Open reviewed external source ↗nist-dst-rules-2026 · Official guidance
Official NIST guidance confirming the 2026 U.S. daylight-saving period used in the dated example.
Open reviewed external source ↗iana-tzdb-2026c-northamerica · Canonical technical data
Canonical time-zone data defining America/Denver and its U.S. mountain-time rules.
Open reviewed external source ↗ws-bilingual-operating-standard · Academy internal operating standard
Academy-selected protected-meaning, review-pathway, glossary, handoff, and evidence controls. This is an internal operating standard selected by Foundry Academy; it is not law, accreditation, licensure, or an external-standard requirement.
Version 1.0 · reviewed 2026-09-01 · owner: Foundry Academy curriculum ownerExplore bilingual operational support for routine business communication while keeping certified, legal, regulated, safety, and specialist work with qualified professionals.
Explore the handoff →Connect approved bilingual messaging to brand, campaign, website, and customer-communication systems with appropriate claim and audience review.
Explore the handoff →Future facilitated pathway · not open
The public case lab is available now. A future facilitated cohort may add assignments, feedback, and human capstone review only after a named qualified facilitator and reviewer, schedule, rubric, privacy controls, support, price, refund terms, and delivery terms are published in writing. No enrollment or payment is accepted here.
Course material supports professional development. It does not replace legal, tax, accounting, cybersecurity, engineering, regulatory, employment, translation, or other qualified professional advice where that expertise is required.
The public knowledge check and portal review markers are learning aids only. They do not award a credential. Pilot curriculum and credential assessment are in quality review; Foundry Academy is not currently representing these pages as accredited instruction or an automatic path to a certificate.
Participation does not guarantee employment, client work, funding, licensure, certification by a public authority, or any business outcome.
Use the public foundation
All public materials and case files are available without enrollment. A fit conversation is non-binding and does not reserve a place in a future pilot.
Ask about this track