Sample Documentation: English Language Translations

Applicability

For projects that are located in a place (or that have regular occupants) speaking a first language other than English, many relevant pieces of documentation are likely initially available in this other language. For your project submission, all relevant information that demonstrates compliance with the strategy requirements must be provided in English or translated into English on the documentation submitted to Fitwel for review.

Types of Documentation

Official Statements

Official statements must be fully provided in English or accompanied by complete translations into English of all relevant content that demonstrates compliance with the strategy requirements. To learn more about official statements, please see our sample documentation article.

Calculations

If calculations include labels or language that are relevant to the strategy, ensure that they are translated into English on the documentation submitted for review. To learn more about calculations, please see our sample documentation article.

Policies, Plans, and Protocols

Policies, plans, and protocols must be fully provided in English or accompanied by complete translations into English of all relevant content that demonstrates compliance with the strategy requirements. Translated annotations must be provided for all excerpts that include criteria outlined on the Fitwel Platform or included in the corresponding relevant Fitwel Standard PDF document.

The following information must be clearly annotated and translated into English:

• Complete and detailed information rather than blanket/vague statements, for example: For Strategy WP/MFR 12.1 Emergency Preparedness Plan, the translation to English should not only state “the project identifies a minimum of one potential emergency scenario for the geographic region”, but should detail the scenarios identified, such as “fire emergencies,” “tornados,” or “suspicious mail.”
• Full paragraphs and relevant excerpts rather than titles and subtitles only, for example: For Strategy WP 10.1/ MFR 10.2 Healthy Food and Beverage Policy, the English translation should not only include a translated table of contents identifying the “appetizers and entrees,” “sides,” and “desserts,” but should detail the options offered, such as: “Offer protein foods from legumes and other plant proteins daily, offer seafood twice per week […].”

To learn more about policies, plans, and protocols, please see our sample documentation article.

Floor Plans and Sections

If floor plans and sections include labels, keys, or specifications that are relevant to the strategy, ensure to include annotations translated into English.

The following information must be clearly annotated and translated into English:

• Floor level numbers and labels, for example: “basement,” “ground floor,” or “3rd floor.”
• Keys and table identification, for example: “window specifications.”
• Identification labels of rooms and spaces relevant to the strategy/area types must also be labeled in English, where relevant (for example: ”lactation room,” “common break area”). 
• Identification tags of amenities and features relevant to the strategy, for example: “shower in women’s locker room,” “the qualifying stair,” or “publicly accessible use: XYZ Cafe.”
• Any specifications about materials used in the project, for example: “mold-resistant paint provided behind the washing machine” to detail any additional information required by the specific strategy.
• Signage language, for example: “Smoking and tobacco use is prohibited in the building and site,” or “Washing hands helps to prevent diseases.”
• Relevant units, measurements, and distances, for example: “250 meters,” or “30-foot walking distance.” 
  • Note: Units of measurement and distances must clearly be shown in feet (ft), meters (m), miles (mi), or kilometers (km).

To learn more about floor plans and sections, please see our sample documentation article.

Maps

If maps, as well as site master plans, include information that is relevant to the strategy, ensure to include annotations translated into English.

The following information must be clearly annotated and translated into English:

• Keys and identification, for example: “Building 1,” “Building 2," or “Parking lot.”
• Tags and labels that identify amenities, spaces, or project entrances, for example: “Pedestrian pathway,” “Common shared backyard,” “main building entrance,” or “secondary pedestrian entrance.”
• Relevant units, measurements, and distances, for example: “250 meters”, or “30-foot walking distance.” 
  • Note: Units of measurement and distances must clearly be shown in feet (ft), meters (m), miles (mi), or kilometers (km).

To learn more about maps, please see our sample documentation article.

Renderings and Photographs

If renderings and photographs, as well as technical design drawings include text in another language, ensure that they include annotations translated into English. 

The following information must be clearly annotated and translated into English:

• Captions and annotations, such as where the photograph was taken within the project, for example: “Quiet room located on the 5th floor.”
• Signage language provided in a local language other than English, for example: “signage reads as ‘smoking and tobacco use is prohibited in the building and site,’" or “language means ‘washing hands helps preventing diseases.’” As long as the translations are provided, Fitwel can accept signage physically displayed in a project that is not in English.

To learn more about renderings and photographs, please see our sample documentation article.

Surveys

If surveys are provided and fielded in another language, please include the translation of all relevant content to English.

The following information must be clearly annotated and translated into English:

• Questions, responses, and results, for example: “How satisfied are you with the building’s bicycle parking and changing facilities?”, or “Very satisfied.”
• Relevant categories, as applicable, for example: “Category 1: Public Transportation.”
• Response rates, for example: “47% of all regular occupants responded to the survey.”

To learn more about surveys, please see our sample documentation article.

Other Types of Documentation

Any strategy-specific documentation not covered in the categories above must also include relevant portions and excerpts translated into English in order to show that all strategy requirements and criteria to demonstrate compliance have been met.

• For tenant leases, include a full translation of the document in a separate document or annotate the original document, for example: For Strategy MFR 2.8/WP 2.6 Parking Efficiency Practices, include annotations confirming how it addresses “separating the cost of renting a tenant space on site from the cost of renting parking areas.”
• For testing results, include annotations to indicate the relevant metrics and levels of the contaminants tested, for example: For Strategy MFR/WP 6.4 IAQ Testing/Monitoring, include annotations in the Indoor Air Quality testing or monitoring results detailing the English names of each air contaminant tested.
• For benefits and programming, translate relevant portions of documents and booklets that clearly address all strategy requirements, for example: For Strategy MFR 8.8/WP 8.11 Health Programming, when providing “a detailed summary of the planned health programming initiative,” detail in English the activities provided, the schedule, and place where they will be hosted, such as “mental health programming: yoga and meditation sessions, every other Wednesday in the multi-purpose room.”