Meetings with owners who speak different languages: preparing the information
Prepare meetings with owners who speak different languages: review translations, amounts and conditions, coordinate versions and make questions easier.
An owner may converse comfortably in Spanish yet need help understanding a proposal about works, charges or contracts. At a meeting, those differences matter: people must understand the proposal, its cost and outstanding conditions before forming a view.
For a practice managing international communities, preparing information means taking care of both content and its different versions. The same proposal must remain recognisable when someone reads it in another language, returns to it days later or asks a question.
Start with a simple process: prepare a clear explanation, review elements affecting the decision and keep versions aligned when changes occur.
Find out what support owners need
Ask which language owners prefer for reading information and what difficulties they encounter. Do not infer it from their name or nationality. Someone may prefer reading in English and asking questions in Spanish; another may need help opening documents on a phone.
This helps prioritise the work. Identify the languages the community needs and the support the practice can offer, directly or through professionals. Discover unmet needs early so you can find a specific solution.
Also consider how information is accessed: text, spoken explanation or audio, where available. Each format must retain the information needed to understand the proposal.
Prepare a clear reference text
Before translating, review the original explanation. Long sentences, unexplained abbreviations and references such as “as previously agreed” force readers to reconstruct context. That difficulty then carries over into other versions.
Explain the proposed decision first. Add its purpose, alternatives and documents with further information. When a technical term is needed, include a brief explanation in context.
W3C’s cognitive accessibility guidance recommends clear words and explanations of unfamiliar terminology. It is useful guidance for understandable content; applying it alone does not certify a document’s accessibility. W3C guidance on clear language (opens in a new tab).
Review anything that could change the meaning of the decision
A translation can sound natural yet omit an important condition. Compare versions with particular attention to:
- The matter’s status: proposal, pending information or an adopted resolution.
- Amounts and whether taxes are included.
- Dates, deadlines and conditions for starting work.
- The scope of each alternative and its exclusions.
- Negations and expressions of possibility or obligation.
If you use machine translation or AI, include a review proportionate to the content’s importance. Uncertainty about a contract’s scope or a legal expression requires someone qualified to check it. Keep the reference document and make the translation’s purpose clear.
An example: preserving status, amount and uncertainty
Imagine a community considering roof repairs. The following example is fictional and provided for information:
| Version | Brief explanation |
|---|---|
| Español | Se propone aprobar un presupuesto total de 18.000 euros, impuestos incluidos, para reparar la cubierta. La fecha de inicio está pendiente de confirmación. |
| English | The proposal is to approve a total budget of €18,000, including taxes, to repair the roof. The start date has yet to be confirmed. |
Both versions preserve three facts: this is still a proposal, the amount includes taxes and no start date is confirmed. A translation announcing the start of work would describe a different situation.
This brief explanation would accompany the full documents. The repair’s scope and quote conditions, among other things, would still need checking. It also does not establish how much each owner would contribute.
Keep explanations and versions in sync
Give the item a shared reference and its explanations an update date. This makes it easier to check that the owner’s version matches the proposal the team is working with.
When a detail changes, identify affected languages and formats. A revised quote also requires reviewing explanations that summarised the previous one. If audio exists, make sure it is not still reading outdated information.
It helps to have one person coordinating updates and another able to review language questions when needed. The responsible person should find the reference text, versions and latest clarification without searching several conversations.
Make questions easier too
Sharing information in another language opens the next step: letting owners express what they have not understood. Explain how to do so and what support is available.
When a question arrives translated, check its meaning before answering. If ambiguous, confirm whether it concerns the total cost, an individual contribution or the payment schedule. These different questions can look alike in a short message.
If an answer clarifies something relevant to all owners, add that information to the relevant versions while protecting personal data. One question can then improve the explanation shared with the whole community.
Test the process before sharing it
Test a real agenda item with someone able to review the target language. Ask them to find the proposal, amount, outstanding conditions and how to ask a question. Also check they can open documents on their intended device.
If something is unclear, the test lets you fix instructions, complete an explanation or spot an old version before the meeting. Keep those lessons for the next item and future meetings.
