Submitting a community story in more than one Atlantic language requires more than a clean draft and a translation. This reusable checklist helps contributors prepare accurate local reporting, protect sources and participants, preserve names and meaning across languages, and give editors what they need to publish responsibly.
Overview
Multilingual community reporting can connect readers across islands, coastlines, cities and diaspora networks, but each language version must remain faithful to the reporting rather than sounding like an automatic conversion. The strongest submissions begin with one clearly reported story, a documented source trail and a plan for language review.
Before you begin, decide what kind of contribution you are making. It may be a short event report, a profile, a public-affairs update, a cultural feature, a service story or a first-person community perspective. The format affects the questions you ask, the evidence you need and the permissions required.
Prepare a reporting folder with the original notes, recordings or transcripts, contact details for verification, photographs, captions, consent records and a list of names and places. Keep the original-language material available. A translator or editor should be able to check a phrase against the source rather than relying only on a polished translated draft.
If you are adapting an existing report for another language audience, separate verified facts from interpretation. A useful workflow is to create a factual summary first, translate it, then have a fluent reviewer compare the translated version with both the summary and the original material. The workflow for translating and summarizing Atlantic community reports can help organize that process.
Checklist by scenario
For an event or community gathering
- Confirm the event name, date, time, location and organizer from a reliable source.
- Record the names and roles of people quoted or photographed.
- Ask whether the event is open to public reporting and whether any areas or participants are off limits.
- Check the spelling and preferred form of organization names in each relevant language.
- Explain how readers can find further information without implying endorsement.
For an interview or profile
- Tell the participant who you are, where the story may appear and which languages may be used.
- Ask for permission before recording audio, video or a detailed quotation.
- Confirm the person’s name, pronouns if relevant, title, affiliation and preferred spelling.
- Offer a clear way to correct factual details, while making no promise that the participant will control the finished article.
- Mark translated quotations as translations when the wording is not the speaker’s original language.
For public affairs or service information
- Identify the issuing body and the date of the announcement.
- Link or retain the underlying notice, document or public statement.
- Distinguish confirmed decisions from proposals, consultations, deadlines or unresolved questions.
- Check whether terminology has a formal local-language equivalent, especially for legal, health, education or migration topics.
- State what readers should do next and where they can verify changing details.
For a story intended for multiple languages
- Choose a source language and keep a fact sheet with dates, numbers, names and quotations.
- List the target languages and identify a fluent reviewer for each one.
- Flag words that should not be translated, such as personal names, place names, event titles or official program names.
- Give translators context for idioms, local references, humor and culturally specific terms.
- Review headlines separately; a literal translation may change the meaning, tone or level of certainty.
A reusable story brief
Send editors a brief that answers these questions:
- Working headline: What is the story about in one clear line?
- Why it matters locally: Who is affected, represented or likely to use this information?
- What happened: Summarize the verified facts, with dates and locations.
- Sources: List every interviewee, document, recording and public reference.
- Languages: Identify the original language and proposed publication languages.
- Access notes: Explain pronunciation, terminology, context or translation challenges.
- Rights: State who created each image, recording or document and what permission exists.
- Risks: Note privacy, safety, legal, identification or retaliation concerns.
- Files: Attach the draft, fact sheet, captions, transcripts and consent notes in clearly named files.
What to double-check
Names and place spellings: Do not assume that a familiar spelling is the preferred one. Check local usage, diacritics, transliteration and any distinction between a municipality, neighborhood, island, region or country. Keep a master list so every language edition uses the intended form.
Attribution: Make clear who said what and where information came from. A translated quotation should preserve the speaker’s meaning and level of certainty. If a phrase cannot be translated closely, explain the approach to the reviewer rather than silently rewriting it.
Consent and privacy: Consent should cover the actual use you expect: publication, photography, recording and possible translation. Take extra care with children, vulnerable people, private addresses, immigration situations, health information and anyone who could face consequences for being identified. If consent is unclear, pause publication and ask an editor for guidance.
Images and other media: Confirm the creator, permission, caption, date, location and identities of people shown. Do not treat a social-media post as automatic permission to republish. Supply descriptive captions and alternative text that convey the relevant information without guessing at identities or emotions.
Accessibility: Use informative headings, short paragraphs and plain explanations. Provide transcripts for important audio and describe meaningful visual information. Check whether numbers, abbreviations and names remain understandable when read aloud or translated.
Translation review: A fluent speaker should review more than grammar. Ask them to check tone, names, cultural references, formality, ambiguity and whether the headline accurately reflects the article. When possible, compare the final version with the original notes, not just with an intermediate translation.
Common mistakes
- Translating before reporting is complete: This creates duplicate work when facts or quotations change. Finish the fact check first.
- Using machine translation without review: Automated tools may mishandle dialect, honorifics, idioms, names and sensitive wording. Treat them as drafting aids, not final editors.
- Flattening local language: Removing dialect words or culturally specific expressions can erase the speaker’s voice. Explain unfamiliar terms where needed instead of replacing them automatically.
- Changing certainty during translation: “May,” “reportedly,” “according to” and “confirmed” are not interchangeable. Preserve the original level of confidence.
- Publishing inconsistent details: Different language versions can accidentally use different dates, figures or descriptions. Compare them against one shared fact sheet.
- Leaving corrections informal: Keep a record of what changed, when and why. If a factual error appears in one language edition, check the other editions too.
- Overpromising publication: Submission is not acceptance. Tell sources that editorial review, translation review and space or timing considerations may affect publication.
When to revisit
Return to this checklist before each new assignment, particularly when the story involves a new language, a sensitive source, a public deadline or material that will be republished across platforms. Review it before seasonal reporting cycles when community events, festivals or public meetings generate a higher volume of submissions.
Editors should also revisit submission instructions whenever the publication changes its accepted file formats, language coverage, privacy guidance, contact procedure, accessibility expectations or correction workflow. A quarterly review is a practical starting point, with an additional review whenever editorial policy or tools change.
Before sending your next story, take ten minutes to complete the following final pass:
- Read the original draft aloud and remove unsupported claims.
- Match every name, date, place and number to your notes or source documents.
- Confirm consent, image rights and any privacy concerns.
- Attach the fact sheet, source list, captions and translation notes.
- Ask a fluent reviewer to check each language version independently.
- Tell the editor what remains uncertain and what should be verified before publication.
- Keep a copy of the submitted materials so corrections can be made consistently later.
Good multilingual community reporting is careful at every handoff: from participant to contributor, from contributor to editor and from one language to another. A clear process protects that chain while allowing local voices to reach readers in the language that feels most direct and familiar.
